PI28198: LPL RECOVERY TIMED OUT ON RESOURCE SYSLGRNX

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer had a cloned system envirnoment and they used DEFER ALL
  to restart the DB2.  some objects were put into LPL status
  after restart ..SYSLGRNX was in LPL as well.
  The clone tool used command '-START DB(DSNDB01) SP(*) ' to
  recover involved DSNDB01 objects and the LPL recovery got time
  out on syslgrnx after about 10 mins.
  
  START command task tried to do LPL recovery for DSNDB01.*
  objects and got drains on LPL objects including SYSLGRNX.
  During lpl recovery, fast log apply child task tried to do
  pseudo open and create new entries in SYSLGRNX for SYSSPUXA and
  SYSSPUXB.
  Pseudo open tasks had to wait claimers on syslgrnx as the start
  task held drains.
  This caused delays of LPL recovery and the LPL recovery could
  time out eventually.
  
  Besides the case listed above, LPL recovery could also be
  impacted if syslgrnx is in other exceptional status like
  stop,etc.
  

Local fix

• resolve unavilable status of SYSLGRNX first
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 users.                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Delays during LPL recovery, while       *
  *                      accessing DSNDB01.SYSLGRNX.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The LPL log apply process may unnecessarily insert a row into
  SYSLGRNX, even though it is not generating any new log records.
  This may cause delays or failures if SYSLGRNX is unavailable.
  

Problem conclusion

• The pageset pseudo-open process has been modified to recognize
  LPL recovery as a non-logging process, which does not require
  any SYSLGRNX coverage.
  

Temporary fix

Comments

APAR Information

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

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

  UI22900 UI22901

Modules/Macros

•    DSNB1SWS
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI22900

     UP14/11/25 P F411

• RB10 PSY UI22901

     UP14/11/25 P F411

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.