Kbase P66774: PeerDirect replication fails with error: Unable to read next record from
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/09/2004 |
|
Status: Unverified
FACT(s) (Environment):
PeerDirect 6.1
Progress 9.1D
SYMPTOM(s):
PeerDirect replication fails with error: Unable to read next record from <table_name>
D 0904 0209-08:15:38 dresyncs3747 FSM:Entering S1a_GenDL
E 0904 0209-08:15:39 dbutil 715 ODBC statement failed: -1 from function Fetch
E 0904 0209-08:15:39 dbutil 722 ODBC statement: SELECT ct."PDCID" AS PDDPK1,ct."PDCID", <table_fields>, ct."PDCCTime",ct."PDCDel",ct."PDCRepl",
ct."PDC1",ct."PDC2",t<fields>
FROM "PDC<table_name>" ct,"PUB".<table-name>" t
WHERE <where_clause>
ORDER BY ct."PDCID"
WITH (READPAST NOWAIT)
E 0904 0209-08:15:39 dbutil 737 ODBC: S1000(4294747395)[DataDirect][ODBC PROGRESS driver][PROGRESS]Internal error 0 (unknown sql92 error) in SQL from subsystem SQL92 function tpl_fetch called from stub_tpl_scan_t::tpl_scan_fetch on PUB.<table_name> for 1. Save log for Progress technical support.
I 0904 0209-08:15:39 dbutil 656 Bound parameters for SQL statement:
I 0904 0209-08:15:39 dbutil 662 P1: I/O:INPUT, SType:SQL_TIMESTAMP, CType:SQL_C_TIMESTAMP, Prec:19, Scale:0, MaxLen:16, Value:31/05/1997 19:00:00
E 0904 0209-08:15:39 tblqry 1271 {An ODBC error occurred}: Could not fetch next row from table <table_name>
E 0904 0209-08:15:39 dresyncs3697 FSM:{An ODBC error occurred}: Could not get next row from <table_name>
D 0904 0209-08:15:39 dlistenm 574 DListenerManager::Send is enqueueing: dataLen[59] tag[145]
5364 4572 526f 523a: SdErRoR:
I 0904 0209-08:15:39 dcontrol1253 SMSG: (pdre,33219)-Unable to read next record from <table_name>
E 0904 0209-08:15:39 dresyncs8947 Unable to read next record from <table_name>
E 0904 0209-08:15:39 dsessbas 560 An error occurred in the sync session envelope.
W 0904 0209-08:15:39 dresyncs1700 Rolling back uncommitted transactions
D 0904 0209-08:15:39 dbcont 1276 Rolling back transaction
I 0904 0209-08:15:39 dcontrol1253 SMSG: (pdre,33209)-PDZIJW5T002 replication has ended because of an error - check log for details
Select statements executed from the SQL Explorer also fail for this specific table
CHANGE:
PeerDirect Replication Engine is trying to complete the replication between the nodes and is having some problems accessing one table from the database due index corruption
FIX:
By the time this error appears the database is up and running so the best approach is to rebuild the indexes online
The best option to acomplish this task is to execute proutil dbname -C idxfix, then select the faulting table with option 3, the index will be fix .
If we run a SELECT statement for the table from the SQL Explorer we should be able to access the table with no problems at all, then we can proceed to complete the replication using PeerDirect.