|
Problem IC64697
|
Status: Closed |
DB2READLOG API SKIPS LOG RECORDS WHEN CALLED DURING AN ARCHIVE LOG OR SET WRITE SUSPEND COMMAND, OR AT END OF ONLINE BACKUP |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Under rare timing conditions when a call made to the db2ReadLog
API coincides with an ARCHIVE LOG command, a SET WRITE SUSPEND
command, or the end of an online backup, the API may return an
incorrect value for nextStartLSN that causes log records to be
skipped if the API user resumes reading from that LSN. The
potential impact of this problem depends upon the application
using the API; for example, if the application replicates the
database, then some data may not be replicated correctly.
No errors are reported to the API user, but the following
messages may appear in the db2diag.log file:
2009-06-26-11.40.35.588398-240 I4888003A488 LEVEL:Warning
PID : 905756 TID : 1 PROC : db2agent (TEST)
INSTANCE: db2instance NODE : 000 DB :TEST
APPHDL : 0-14 APPID: *LOCAL.db2instance.090626153936
FUNCTION: DB2 UDB, data protection, sqlpALR_PageFromLSN,
probe:900000
DATA #1 : String, 123 bytes
returnCode SQLPLFR_RC_MOVE_LSN_TO_NEXT_LOGFILE -2146434658
firstlsn 000001388000
loadstartLsn is changed 000000000177000C
2009-06-26-11.40.35.588920-240 I4888492A477 LEVEL: Warning
PID : 905756 TID : 1 PROC : db2agent (TEST)
INSTANCE: db2instance NODE : 000 DB : TEST
APPHDL : 0-14 APPID: *LOCAL.db2instance.090626153936
FUNCTION: DB2 UDB, data protection, sqlpALR_ReadPagesDisk,
probe:600
MESSAGE : FYI: readStartLSN 00000138900C, loadStartLSN
00000138900C, userEndLSN 00000176FFFB, firstlsn 000001388000,
ExtSize 1000 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of readlog api *
****************************************************************
* PROBLEM DESCRIPTION: *
* Under rare timing conditions when a call made to the *
* db2ReadLog API coincides with an ARCHIVE LOG *
* command, a SET WRITE SUSPEND *
* command, or the end of an online backup, the API may return *
* an incorrect value for nextStartLSN that causes log records *
* to be skipped if the API user resumes reading from that LSN. *
* *
* The potential impact of this problem depends upon the *
* application using the API; for example, if the application *
* replicates the database, then some data may not be *
* replicated *
* correctly. *
* *
* No errors are reported to the API user, but the following *
* messages may appear in the db2diag.log file: *
* *
* 2009-06-26-11.40.35.588398-240 I4888003A488 LEVEL:Warning *
* PID : 905756 TID : 1 PROC : db2agent (TEST) *
* INSTANCE: db2instance NODE : 000 DB :TEST *
* APPHDL : 0-14 APPID: *LOCAL.db2instance.090626153936 *
* FUNCTION: DB2 UDB, data protection, sqlpALR_PageFromLSN, *
* probe:900000 *
* DATA #1 : String, 123 bytes *
* returnCode SQLPLFR_RC_MOVE_LSN_TO_NEXT_LOGFILE -2146434658 *
* firstlsn 000001388000 *
* loadstartLsn is changed 000000000177000C *
* *
* 2009-06-26-11.40.35.588920-240 I4888492A477 LEVEL: Warning *
* PID : 905756 TID : 1 PROC : db2agent (TEST) *
* INSTANCE: db2instance NODE : 000 DB : TEST *
* APPHDL : 0-14 APPID: *LOCAL.db2instance.090626153936 *
* FUNCTION: DB2 UDB, data protection, sqlpALR_ReadPagesDisk, *
* probe:600 *
* MESSAGE : FYI: readStartLSN 00000138900C, loadStartLSN *
* 00000138900C, userEndLSN 00000176FFFB, firstlsn *
* 000001388000, *
* ExtSize 1000 *
****************************************************************
* RECOMMENDATION: *
* Apply v9.7.2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in DB2 UDB Version 9.7 fix pack 2. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC93346
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.11.2009
18.02.2010
18.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.2,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
