IBM Support

JR31296: THE REPLICATION CAPTURE PROGRAM SETS TOO SMALL A BUFFER SIZE FOR SOME LOG ENTRIES TO BE READ.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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-15.57.43.278826 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.
    

Local fix

  • 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.
    

Problem summary

  • AS DESCRIBED IN THE APAR
    

Problem conclusion

  • FIXED IN FP7
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31296

  • Reported component name

    REPLICATION SER

  • Reported component ID

    5724N9800

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-12-02

  • Closed date

    2008-12-11

  • Last modified date

    2011-03-01

  • APAR is sysrouted FROM one or more of the following:

    JR31289

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    REPLICATION SER

  • Fixed component ID

    5724N9800

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021