home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC95466 Status: Geschlossen

db2ReadLog API WAS RETURNED SQLCODE -1273 DURING ONLINE BACKUP.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Q replication was returned the following error messages during 
online backup. 
 
From QCAP.log 
db2inst1.capture_server.qcapture_schema.QCAP.log 
================================== 
2013-06-05-17.33.53.403713 <logrdDB2LUW::readTheLog> ASN0552E 
"Q Capture" : "qcapture_schema" : "xxxxx" : The program 
encountered an SQL er 
ror. The server name is "capure_server". The SQL request is 
"db2ReadLog". The table name is "". The SQLCODE is "-1273". The 
SQLSTATE is 
" 
2013-06-05-17.33.53.403745 <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 the following messages. 
 
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."
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.5 fixpack 3.                   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.5 Fixpack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.08.2013
27.02.2014
27.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList