DB2 - Problem description
Problem IC95594 | Status: Closed |
SQLE_SAL_CACHE_RAR_NODATA USING THE DB2READLOG API | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The db2ReadLog API may get an error message SQLE_SAL_CACHE_RAR_NODATA indicating that log record could not be decompressed. This situation does not present under normal DSB2ReadLog operating conditions, it can happen during DB2ReadLog after the system goes down, is restarted and then db2ReadLog begins again. This is the relevant db2diag.log message: 2013-07-17-08.32.29.952088-240 I1333195A856 LEVEL: Info PID : 21037252 TID : 30205 PROC : db2sysc 0 INSTANCE: inst1 NODE : 000 DB : mydb APPHDL : 0-217 APPID: xxxxxxx.130717123229 AUTHID : auth1 HOSTNAME: hostname EDUID : 30205 EDUNAME: db2agent (TST) 0 FUNCTION: DB2 UDB, data protection services, sqlpgReadLogCopyLogRecordToUserBuffer, probe:100 MESSAGE : ZRC=0x852700AF=-2061041489=SQLE_SAL_CACHE_RAR_NODATA "CA_CACHE_RAR_NODATA" DATA #1 : String, 36 bytes log record could not be decompressed DATA #2 : SQLP_LRH, PD_TYPE_SQLP_LRH, 64 bytes recLfs 97142 recLsn 0000000000400C56 lrecsize 145 lrectype 004E lrecflags 0402 backlso 0 maps to pso 0000000000000000 thistid 000000002ED3 DATA #3 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes -902 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW * **************************************************************** * PROBLEM DESCRIPTION: * * The db2ReadLog API may get an error message * * SQLE_SAL_CACHE_RAR_NODATA indicating that log record could * * not * * be decompressed. This situation does not present under * * normal * * DSB2ReadLog operating conditions, it can happen during * * DB2ReadLog after the system goes down, is restarted and then * * db2ReadLog begins again. * * * * * * * * This is the relevant db2diag.log message: * * * * 2013-07-17-08.32.29.952088-240 I1333195A856 LEVEL: * * Info * * PID : 21037252 TID : 30205 PROC : * * db2sysc 0 * * INSTANCE: inst1 NODE : 000 DB : * * mydb * * APPHDL : 0-217 APPID: xxxxxxx.130717123229 * * AUTHID : auth1 HOSTNAME: hostname * * EDUID : 30205 EDUNAME: db2agent (TST) 0 * * FUNCTION: DB2 UDB, data protection services, * * sqlpgReadLogCopyLogRecordToUserBuffer, probe:100 * * MESSAGE : * * ZRC=0x852700AF=-2061041489=SQLE_SAL_CACHE_RAR_NODATA * * "CA_CACHE_RAR_NODATA" * * DATA #1 : String, 36 bytes * * log record could not be decompressed * * DATA #2 : SQLP_LRH, PD_TYPE_SQLP_LRH, 64 bytes * * recLfs 97142 recLsn 0000000000400C56 lrecsize 145 lrectype * * 004E * * lrecflags 0402 * * backlso 0 maps to pso 0000000000000000 thistid 000000002ED3 * * DATA #3 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes * * -902 * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.5 FP3 * **************************************************************** | |
Local Fix: | |
If the user selects from each of the tables before starting the DB2ReadLog operation, this will load up the entire set of internal TCBs and thus there will be no need for loading any of these on-the-fly (a simple select count(*) will do). This will prevent the issue. | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.08.2013 28.02.2014 28.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |