IBM Support

IT33463: HADR STANDBY FAILED WITH SQLP_LMAX ERROR WHEN LOCKLIST IS CONFIGURED AS AUTOMATIC

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • This problem only occurs when the HADR standby is enabled with
    reads on standby feature (DB2_HADR_ROS is enabled), and the
    DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW register variable is
    enabled, and the LOCKLIST database configuration parameter is
    set to AUTOMATIC.
    
    The db2diag.log might contain the following messages, resulting
    in abnormal termination of the standby database.
    
    2020-04-27-21.20.56.453610-240 I194457122E1112       LEVEL:
    Warning
    PID     : 370969               TID : 48427329120000  PROC :
    db2sysc 0
    INSTANCE:              NODE : 000            DB   :
    APPHDL  : 0-38765              APPID: *LOCAL.DB2.200428012044
    HOSTNAME:
    EDUID   : 354                  EDUNAME: db2agent () 0
    FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster,
    probe:2470
    MESSAGE : ZRC=0x021001DD=34603485=SQLP_LMAX
              "Caller should trigger locklist escalation"
    DATA #1 : String, 142 bytes
    We have exceeded the max attemps to automatcially restart HADR
    replay and could not make any progress. We will force the
    database to shutdown.
    DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1042   sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlpRepl
    sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6)
    0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
    sqlstate:
    
    2020-04-27-21.20.56.453866-240 I194458235E1005       LEVEL:
    Severe
    PID     : 370969               TID : 48427329120000  PROC :
    db2sysc 0
    INSTANCE:              NODE : 000            DB   :
    APPHDL  : 0-38765              APPID: *LOCAL.DB2.200428012044
    HOSTNAME:
    EDUID   : 354                  EDUNAME: db2agent () 0
    FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster,
    probe:2500
    MESSAGE : ZRC=0x021001DD=34603485=SQLP_LMAX
              "Caller should trigger locklist escalation"
    DATA #1 : String, 37 bytes
    Replay master fatal error: localSqlca
    DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1042   sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlpRepl
    sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
               (4) 0x00000000      (5) 0x00000000      (6)
    0x00000000
    sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
               (7)      (8)      (9)      (10)        (11)
    sqlstate:
    
    2020-04-27-21.20.56.454079-240 I194459241E614        LEVEL:
    Severe
    PID     : 370969               TID : 48427329120000  PROC :
    db2sysc 0
    INSTANCE:              NODE : 000            DB   :
    APPHDL  : 0-38765              APPID: *LOCAL.DB2.200428012044
    HOSTNAME:
    EDUID   : 354                  EDUNAME: db2agent () 0
    FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster,
    probe:2500
    MESSAGE : ZRC=0x021001DD=34603485=SQLP_LMAX
              "Caller should trigger locklist escalation"
    DATA #1 : <preformatted>
    Fatal error during HADR replay.  Forcing the database to shut
    down.
    

Local fix

  • Change LOCKLIST database configuration parameter to a fixed
    value.
    
    Another workaround is to disable
    DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * AIX/Linux                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v11.1.4.6                                         *
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT33463

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-08

  • Closed date

    2021-03-13

  • Last modified date

    2021-03-13

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

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

Fix information

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
14 March 2021