home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC93241 Status: Closed

db2ReadLog API WAS RETURNED SQLCODE -1273 DURING ONLINE BACKUP.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 3.                   * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95466 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.06.2013
21.10.2013
21.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList