IT15527: IN SPECIFIC TIMING CONDITIONS WITH MULTIPLE DB2READLOG API CALLERS(CDC, ETC), "NO ROOM FOR RETRIEVED LOG" occurs in db2diag.log
IT15527: IN SPECIFIC TIMING CONDITIONS WITH MULTIPLE DB2READLOG API CALLERS(CDC, ETC), "NO ROOM FOR RETRIEVED LOG" occurs in db2diag.log
https://www.ibm.com/mysupport/s/defect/aCI0z000000TOfW/dt010963?language=en_US
-
Show more
1. Problem description
In specific timing conditions with multiple db2readlog API
callers (CDC, etc),
DB2 generates dump files with "No room for retrieved log"
warning message in db2diag.log.
2. Diagnostic information
db2diag.log
FUNCTION: DB2 UDB, data protection services,
sqlpgRetrieveStartUse, probe:190 ...
-
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* 1. Problem description *
* In specific timing conditions with multiple db2readlog API *
* callers (CDC, etc), *
* DB2 generates dump files with "No room for retrieved log" *
* warning message in db2diag.log. *
* *
* *
* 2. Diagnostic information *
* *
* db2diag.log *
* *
* FUNCTION: DB2 UDB, data protection services, *
* sqlpgRetrieveStartUse, probe:190 *
* DATA #1 : *
* WARNING: No room for retrieved log number XXXXX in *
* retrieveArray. Index XXXXXXX entryCount 264 *
* *
* PID:XXXX TID:XXXXXXXX NODE:000 Title: SQLP_DBCB *
* Dump File: /db2dump/XXXXX.XXXXX.000.dump.bin *
* *
* PID:XXXX TID:XXXXXXXX NODE:000 Title: SQLP_LFPB *
* Dump File: /db2dump/XXXXX.XXXXX.000.dump.bin *
* *
* ..... *
* *
* 3. Symptom *
* Once this message happens, db2readlog API callers (CDC, etc) *
* may *
* receive SQL2038N error or are not able to continue *
* retrieving *
* log files until database reactivation. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 8. *
****************************************************************
Show more
-
First fixed in Version 10.5 Fix Pack 8
-
1. Reactivate the database.
db2 deactivate db <dbname>
db2 activate db <dbname>
2. In case of 'OVERFLOWLOGPATH' is configured for the database,
set 'OVERFLOWLOGPATH' as the same as full archive log path.
( NOTE : The OVERFLOWLOGPATH value needs to be full path to the
archived log files. )
For example, if current full archive log path is
'/archive/aaa/db2inst1/aaa/NODE0000/LOGSTREAM0000/C0000001',
db2 update db cfg for <dbname> using OVERFLOWLOGPATH
/archive/aaa/db2inst1/aaa/NODE0000/LOGSTREAM0000/C0000001
( NOTE : After changing, "NODE0000/LOGSTREAM0000" path will be
added automatically on "OVERFLOWLOGPATH" parameter.
Even with that, the path which is specified in 'db2
update db cfg' will be referenced. )Closed
Programming Error - Fix provided (PER)
A fix is available
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and WindowsDB2 Version 10.5 Fix Pack 11 for Linux, UNIX, and WindowsDB2 Version 10.5 Fix Pack 10 for Linux, UNIX, and WindowsFixed Version(s) :
Subscribe
By subscribing, you receive periodic emails alerting you to the status of the known issue, along with a link to the fix after it becomes available.
Notify me when a known issue for this product changes
Manage my notifications-
Db2 Linux, Unix and Windows
10.5
DT010963
2023年8月24日 GMT+8 18:49
-
IT15527
DB2FORLUW
A50
Closed
NoPE
NoHIPER
NoSpecatt
-Product Specific
2016年6月01日 GMT+8 11:00
2016年11月23日 GMT+8 10:00
2023年8月24日 GMT+8 18:49
------------------------------------------------------------------------------------------
如果你觉得文章有用,欢迎打赏
-