IBM Support

IT32751: HADR STANDBY FAILS WITH "BAD ENTRY STATE" REPORTED FROM SQLRLC_AUTH_GR_PROCESS_ENTRY_STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem only affects HADR standby with both DB2_HADR_ROS
    and DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW register variables
    enabled.
    
    The standby database might encounter abnormal termination, with
    the following message from db2diag.log:
    
    2020-04-28-15.50.06.929421-240 I1260104E556     LEVEL: Severe
    PID  : 99310        TID : 139831770343168 PROC : db2sysc 0
    INSTANCE: xxx       NODE : 000      DB : xxx
    APPHDL : 0-293        APPID: *LOCAL.DB2.200428195006
    HOSTNAME: xxx
    EDUID : 394         EDUNAME: db2redom (xxx) 0
    FUNCTION: DB2 UDB, catcache support,
    sqlrlc_auth_gr_process_entry_state, probe:20
    MESSAGE : bad entry state
    DATA #1 : Hexdump, 4 bytes
    0x00007F2BABED1D34 : 0500 0000                 ....
    
    2020-04-28-15.50.06.929627-240 I1260661E940     LEVEL: Error
    PID  : 99310        TID : 139831770343168 PROC : db2sysc 0
    INSTANCE: xxx       NODE : 000      DB : xxx
    APPHDL : 0-293        APPID: *LOCAL.DB2.200428195006
    HOSTNAME: xxx
    EDUID : 394         EDUNAME: db2redom (xxx) 0
    FUNCTION: DB2 UDB, catcache support, sqlrlc_broadcast, probe:0
    MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT
         "SQLCA has already been built"
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA  sqlcabc: 136 sqlcode: -901 sqlerrml: 15
    sqlerrmc: bad entry state
    sqlerrp : SQLRC008
    sqlerrd : (1) 0x801A006D   (2) 0x00000000   (3) 0x00000000
          (4) 0x00000000   (5) 0xFFFFFFEC   (6) 0x00000000
    sqlwarn : (1)   (2)   (3)   (4)    (5)   (6)
          (7)   (8)   (9)   (10)    (11)
    

Local fix

  • On standby server, run: db2set
    DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW=OFF
    Note: Changes to this variable will take effect after deactivate
    and activate of the standby database.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.5m4fp0 or higher                           *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.5m4fp0
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32751

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-05-04

  • Closed date

    2020-06-30

  • Last modified date

    2020-06-30

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

    IT32719

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RB50 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
17 December 2021