|
Problem IC67870
|
Status: Closed |
SQL REPLICATION CAPTURE PROGRAM CAN GET ERROR READING THE DB2 LOG FILES: SQL -2650, RC 8 |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
During replication capture, the following error might be raised
if LOGFILSZ configuration parameter was changed:
In db2diag.log:
2010-04-03-01.19.43.245665+120 I965554A563 LEVEL: Error
PID : 9348 TID : 283 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-3792 APPID:
*LOCAL.db2inst3.100331235208
AUTHID : DB_REPL
EDUID : 283 EDUNAME: db2agent (SAMPLE)
0FUNCTION: DB2 UDB, data protection services,
sqlp_AsyncLogReadAPI, probe:210
DATA #1 : String, 123 bytes
Error: sqlcode -2650, rc 8, hflag2LsnReuse 0
The capture log will report :
2010-04-03-01.19.43.255329 <logrd::readTheLog> ASN0005E CAPTURE
"ASN" :
"WorkerThread". The Capture program encountered an error when
reading
the DB2 log. The log sequence number is
"0000:0000:0774:E9D8:9453", the
SQLCODE is "-2650", and the reason code is "piStartLSN
db2ReadLog 5".
The main reason for this issue is a reported log file size
modification during database recovery in the db2diag.log which
is most likely to happen in an HADR context:
2010-03-31-23.53.15.583475+120 I41717A560 LEVEL: Info
PID : 9348 TID : 269 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-9 APPID: *LOCAL.DB2.100331214415
EDUID : 269 EDUNAME: db2redom (HRS) 0
FUNCTION: DB2 UDB, recovery manager,
sqlpChangeLogFileSizeDuringRecovery, probe:10
DATA #1 : <preformatted>
Log file size is changing during database recovery. Old:
dbcb->logfhdr.logsize 10000, New: Extent 201260, ExtSize 25000,
firstlsn 07717D6B8000
This log file size modification being applied through database
recovery can have DB2 mis-calculate the log file record for a
given LSN since the initial log file size was picked up earlier
during the startup of the instance. This APAR will make so that
the initial log file size is reset correctly in this particular
case. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All version 9.1 or version 9.5 using HADR *
* Version 9.7 is not impacted by this issue *
****************************************************************
* PROBLEM DESCRIPTION: *
* SQL REPLICATION CAPTURE PROGRAM CAN GET ERROR READING THE *
* DB2 LOG FILES: SQL -2650, RC 8 *
* *
* During replication capture, the following error might be *
* raised if LOGFILSZ configuration parameter was changed: *
* *
* *
* *
* In db2diag.log: *
* *
* *
* *
* 2010-04-03-01.19.43.245665+120 I965554A563 LEVEL: *
* Error *
* PID : 9348 TID : 283 PROC : *
* db2sysc 0 *
* *
* INSTANCE: db2inst1 NODE : 000 DB : SAMPLE *
* APPHDL : 0-3792 APPID: *
* *
* *LOCAL.db2inst3.100331235208 *
* *
* AUTHID : DB_REPL *
* *
* EDUID : 283 EDUNAME: db2agent (SAMPLE) *
* *
* 0FUNCTION: DB2 UDB, data protection services, *
* *
* sqlp_AsyncLogReadAPI, probe:210 *
* *
* DATA #1 : String, 123 bytes *
* *
* Error: sqlcode -2650, rc 8, hflag2LsnReuse 0 *
* *
* *
* *
* *
* *
* The capture log will report : *
* *
* *
* *
* 2010-04-03-01.19.43.255329 <logrd::readTheLog> ASN0005E *
* CAPTURE "ASN" : *
* *
* "WorkerThread". The Capture program encountered an error *
* when reading *
* *
* the DB2 log. The log sequence number is *
* "0000:0000:0774:E9D8:9453", the *
* *
* SQLCODE is "-2650", and the reason code is "piStartLSN *
* *
* db2ReadLog 5". *
* *
* *
* *
* *
* *
* The main reason for this issue is a reported log file size *
* *
* modification during database recovery in the db2diag.log *
* which *
* is most likely to happen in an HADR context: *
* *
* *
* *
* 2010-03-31-23.53.15.583475+120 I41717A560 LEVEL: Info *
* *
* PID : 9348 TID : 269 PROC : *
* db2sysc 0 *
* *
* INSTANCE: db2inst1 NODE : 000 DB : SAMPLE *
* APPHDL : 0-9 APPID: *
* *LOCAL.DB2.100331214415 *
* EDUID : 269 EDUNAME: db2redom (HRS) 0 *
* *
* FUNCTION: DB2 UDB, recovery manager, *
* *
* sqlpChangeLogFileSizeDuringRecovery, probe:10 *
* *
* DATA #1 : <preformatted> *
* *
* Log file size is changing during database recovery. Old: *
* *
* dbcb->logfhdr.logsize 10000, New: Extent 201260, ExtSize *
* 25000, *
* firstlsn 07717D6B8000 *
* *
* *
* *
* *
* *
* This log file size modification being applied through *
* database *
* recovery can have DB2 mis-calculate the log file record for *
* a *
* given LSN since the initial log file size was picked up *
* earlier *
* during the startup of the instance. This APAR will make so *
* that *
* the initial log file size is reset correctly in this *
* particular *
* case. *
****************************************************************
* RECOMMENDATION: *
* install version 9.5 fixpak 6 *
**************************************************************** |
| Local Fix: |
Stop and start the instance after this
"sqlpChangeLogFileSizeDuringRecovery, probe:10" is captured in
the db2diag.log will set the initial log file size to the proper
value. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
first fixed in version 9.5 Fixpak 6 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67873 IC67874 IC67875
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.04.2010
17.05.2010
17.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.
|
| Problem solved according to the fixlist(s) of the following version(s) |
