DB2 - Problem description
Problem IT41873 | Status: Closed |
INCORRECT NUMBER OF LOG RECORDS COPIED FROM EXTRACTION LOG FILES | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Log read operation with ALSM feature enabled might encounter a problem reading extraction files. The operation is still successful, by retrieving the required log files from archive. The following message is written to db2diag.log. 2022-08-09-18.54.15.659822-240 I1126357706A1497 LEVEL: Error PID : 47644968 TID : 37010 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-7 APPID: *LOCAL.db2inst1.220809225410 AUTHID : SVTDBM11 HOSTNAME: Localhost1 EDUID : 37010 EDUNAME: db2shred (SAMPLE) 0 FUNCTION: DB2 UDB, data protection services, sqlpExtractionReadLogRecordsHandle::endCurrentFile, probe:1528 MESSAGE : ZRC=0x82100001=-2112880639=SQLP_NONSEVERE_PRGERR "DPS detects non-severe programming error" DIA8532C An internal processing error has occurred. DATA #1 : Unexpected condition!!! Incorrect number of log records copied from the extraction log files for this log file number. curExtNum = 35419 curExtNumNumLrecsExpected = 1088 curExtNumNumLrecsCopied = 2165 curNumTidElements = 5 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users with ALSM fature enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to product version 11.5.8 * **************************************************************** | |
Local Fix: | |
To avoid this issue, disable ALSM feature via 'db2set DB2_ADVANCED_LOG_SPACE_MGMT=OFF' | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users with ALSM fature enabled * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to product version 11.5.8 * **************************************************************** | |
Comment | |
Fixed in 11.5.8 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.08.2022 06.09.2022 06.09.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |