IBM Support

PI41630: SOME DB2 LOG RECORDS ARE NOT REPLICATED IN V11

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer identified that they have missing inserts/updates on
    replication target site.
    
    Log analysis on source system shows that we have one log record
    with bad LRHLRSN FFFFFFFFFBAD
    --
    000B0C8BBD707EE  MEMBER(M01     )  TYPE()
             LRSN(00FFFFFFFFFBAD000000)
             SUBTYPE(DBD VIRTUAL MEMORY COPY)
    
    *LRH* 00460046 00100009 0E800000 00000000 00000000 00000826
    B0C8BBD7 07A8FFFF FFFFFBAD 0002
    --
    
    The log record with bad LRHLRSN could cause log reader to stop
    if log reader is specified with Start/End LRSN explicitly.
    So the rest of logs in the log dataset are not read and
    replicated.
    This can only occur in DB2 V11.
    

Local fix

  • .
    A bad LOG record can be found using this jobstep -->
    .
    //LOGP01   EXEC PGM=DSN1LOGP,REGION=0M
    //SYSPRINT DD SYSOUT=*
    //ARCHIVE  DD DISP=SHR,DSN= DB2 Archive LOG dataset
    //*
    //SYSIN    DD *
      LRSNSTART(00FFFFFFFFFBAD000000)
        LRSNEND(00FFFFFFFFFBAD000000)
    /*
    .
    If this step shows a record like the following,
    then the problem exists (bad LOG record).
    .
       TYPE()  LRSN(00FFFFFFFFFBAD000000)
       SUBTYPE(DBD VIRTUAL MEMORY COPY)
    .
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Version 11 users of DB2 for zOS that     *
    *                 have not converted the BSDS data sets with   *
    *                 the DSNJCNVT utility to use 10 byte RBA      *
    *                 values.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: In DB2 11 for z/OS, an application      *
    *                      reading the DB2 logs with the IFI READS *
    *                      function for IFCID 306 (e.g., QRep) may *
    *                      not receive all log records in the      *
    *                      requested log range.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When building a log record, the log record LRSN is initially set
    to 'FFFFFFFFFBAD'x to catch errors during the build. If a thread
    is cancelled during log record build, there is a timing window
    where the log record would be written to the log with LRSN value
    of 'FFFFFFFFFBAD'x.
    
    The invalid LRSN value can cause DB2 to incorrectly return end
    of data before all log records in the requested log range have
    been returned to the application.
    

Problem conclusion

  • DB2 has been changed so that the LRSN value is no longer set to
    'FFFFFFFFFBAD'X during the log record build process.
    
    To determine if the system contained any log records with LRSN
    value of 'FFFFFFFFFBAD'X, please run DSN1LOGP with
    LRSNSTART 00FFFFFFFFFBAD000000 and LRSNEND 00FFFFFFFFFBAD000000.
    
    Additional keywords: IFCID306 IFC306 IFI306
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI41630

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-05-25

  • Closed date

    2015-06-08

  • Last modified date

    2015-07-01

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

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

    UI28315

Modules/Macros

  • DSNJW001
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI28315

       UP15/06/17 P F506

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2015