DB2 - Problembeschreibung
Problem IC96739 | Status: Geschlossen |
DB2READLOG API WAS RETURNED SQLCODE -1273 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
QCAP stopped with "-1273" error when reading LOG. CDC may encounter the same issue. Current validation of end of stream is too strict, so it may generate false alarm for continuous reader such as ReadLog application. From QCAP.log ================================== 2013-09-03-09.04.59.266760 <logrdDB2LUW::readTheLog> ASN8041D "Q Capture" : "qcapture_schema" : "xxxxxxxxxx" : db2LogRead API is sending us backwards in theDB2 Log: First LSN is "XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX" while Next Start LSN is "0000:0000:0000:0000:0000:0000:0000:0000" 2013-09-03-09.04.59.266793 <logrdDB2LUW::readTheLog> ASN0005E CAPTURE "qcapture_schema" : "xxxxxxxxxx". The Capture program encountered an error when reading the DB2 log. The log sequence number is "XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX", the SQLCODE is "-1273", an d the reason code is "". db2diag.log has messages as following: 2013-09-03-09.04.58.254598+480 I320096572A1226 LEVEL: Error PID : 10879184 TID : 52693 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-118 APPID: *N0.db2inst1.130805032853 AUTHID : DB2INST1 EDUID : 52693 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, recovery manager, sqlpshrValidateLogStreamEndPoint, probe:1130 MESSAGE : ZRC=0x86100026=-2045771738=SQLPR_MISSING_LOG_EXT "Used by various operations reading the logs to indicate a missing log extent." DATA #1 : <preformatted> Forward phase of recovery on stream 0 did not reach end of logs. stream returned log records: yes found logRecs after end pt: no lastExt: 1935 lastExtNeededForRecovery: 1935 lastExtNeededForTbspRfwd: 0 nextRecLso: 64658637625 LastRecLsoLFH: 64658576626 shrScanEndLso: 18446744073709551615 shrLastDiskLso: 64658638312 shrScanNextFlagsOut: 0x1 highestLfsLsnProduced: 32360291/00000000106A532C maxStopLfsLsn: 18446744073709551615/FFFFFFFFFFFFFFFF isReadLogOrOlic: true isTbspRfwd: false | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * The user is call db2readlog api. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix * * Pack 4) or higher. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.10.2013 15.09.2014 14.10.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |