Fixes are available
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
Closed as program error.
The Replication Capture program sets a very small buffer size for the log entries to be read. When this issue is encountered, a message similar to the following will be seen in the Capture log: 2008-11-11-22.214.171.1248826 ASN0005E CAPTURE "ASN16" : "txrdThread". The Capture program encountered an error when reading the DB2 log. The log sequence number is "0000:0000:0386:D2A2:3D8E", the SQLCODE is "-2650", and the reason code is "poLogBufferdb2ReadLog8". A message similar to the following will be seen in the db2diag.log: 2008-10-30-11.01.10.074716-240 I8913095E578 LEVEL: Error PID : 9255 TID : 206745626976 PROC : db2sysc 0 INSTANCE: SAMPLE NODE : 000 DB : TEST_V9 APPHDL : 0-102 APPID: *LOCAL.SAMPLE.081023154329 AUTHID : TEST EDUID : 78 EDUNAME: db2agent (IDGDM_V9) 0 FUNCTION: DB2 UDB, data protection services, sqlp_AsyncLogReadAPI, probe:220 DATA #1 : String, 125 bytes Error: sqlcode -2650, rc 256, hflag2LsnReuse 0 action 1, startLSN 036F EEE3 CFBC, endLSN 036F EF3D 7F97, logBufferSize 204800 The internal hardcoded buffer size for Capture was changed from 50K to 200K in V91 FP7. In V91, however, the LOGRDBUFSZ Capture startup paramter is not available. If you are seeing this error at V91, please install V91 FP7 to get the benefit of the increased hardcoded buffer size for Capture. The LOGRDBUFSZ Capture startup parameter is available in V95 FP3+ and V97 GA. In V95 FP3+ and V97 we no longer have a hardcoded buffer size for Capture. Capture uses the LOGRDBUFSZ value which is 256 by default on Linux, Unix and Windows. If Capture still gets the same error, you can try starting Capture with a higher LOGRDBUFSZ, like 512 or 1024, and so on.
At V91, upgrade to V91 FP7. At V95, upgrade to V95 FP3 and use a a suitably high LOGRDBUFSZ value. At V97, use a suitably high LOGRDBUFSZ value.
AS DESCRIBED IN THE APAR
FIXED IN FP7
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
12 October 2021