|
Problem IT15527
|
Status: Closed |
IN SPECIFIC TIMING CONDITIONS WITH MULTIPLE DB2READLOG API CALLERS(CDC, ETC), "NO ROOM FOR RETRIEVED LOG" occurs in db2diag.log |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| 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 : <preformatted>
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. |
| Problem Summary: |
****************************************************************
* 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 : <preformatted> *
* 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. *
**************************************************************** |
| Local Fix: |
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. ) |
| Solution |
First fixed in Version 10.5 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 01.06.2016
23.11.2016
23.11.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
