PM84206: DSNI005I AUTO LPL RECOVERY FAILED FOR GBP DEPENDENT LOB AFTER A CANCEL

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A job was cancelled ( abend222 ) while it was updating a LOB
  page for DSNDB01.SYSDBDXA . This invoked online page recovery .
  The online page recovery was holding a DRAIN which in turn
  caused the LPL recovery to time out , and -START DB to timeout .
  As the page is in LPL and online page recovery can't continue,
  the object was placed in WEPR .
  Some of the messages:
  DSNB209I  -DSN  DSNB1RTR - BUFFER MANAGER
             TABLESPACE/INDEXSPACE
             CLEANUP ROUTINE (DSNB1CFC)
             HAS BEEN SCHEDULED FOR
             DBNAME=DSNDB01
             SPACENAME=SYSDBDXA
             INSTANCE=1
             PSID=X'00010001'
  ..
  DSNB250E  -DSN  DSNB5SCM A PAGE RANGE WAS ADDED TO
             THE LOGICAL PAGE LIST
             DATABASE NAME=DSNDB01
             SPACE NAME=SYSDBDXA
             ..
             LPL TRACE ID=00000001
             LPL REASON TYPE=LOCK
  ..
  DSNI006I  -DSN  DSNISREC ASYNCHRONOUS GRECP OR LPL
             RECOVERY IN PROGRESS FOR
             AUTOMATIC LPL RECOVERY-ID = 129
             TYPE 00000200
             NAME DSNDB01 .SYSDBDXA
  DSNT376I  -DSN  PLAN=BCT..... WITH
             CORRELATION-ID=010.LPLALR01
             ..
             IS TIMED OUT. ONE HOLDER OF THE RESOURCE IS PLAN=
             WITH
             CORRELATION-ID=010.RTRCFC01
             ..
  DSNT501I  -DSN  DSNILMCL RESOURCE UNAVAILABLE
             CORRELATION-ID=010.LPLALR01
             ..
             REASON 00C900BA           <-timeout on drain
             TYPE 00002002
             NAME DSNDB01 .SYSDBDXA
  ..
  DSNI005I  -DSN  DSNISREC LPL OR GRECP RECOVERY CANNOT
             BE DONE FOR
             AUTOMATIC LPL RECOVERY-ID = 129
             OBJECT TYPE 00000200
             OBJECT NAME DSNDB01 .SYSDBDXA
             REASON 00C900BA
             TYPE 00002002
             NAME DSNDB01 .SYSDBDXA
  ..
  *DSNU086I  -DSN  DSNUCDA1 - READ I/O ERRORS -
              ON SPACE=DSNDB01.SYSDBDXA
              DATA SET NUMBER=1
              I/O ERROR PAGE RANGE= ...
  *DSNB217I  -DSN  DSNB1CFC - ONLINE RECOVERY FOR AN
              INCONSISTENT PAGE WAS UNSUCCESSFUL
              FOR
              DBNAME=DSNDB01
              SPACENAME=SYSDBDXA
              INSTANCE=1
              PAGE NUMBER=...
                                                                 .
  Additional keywords: rc00c900ba , logical page list ,
                       write error page range , asynch , async ,
                       asynchronous , pgbroken .
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: DB2 data sharing users.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: After canceling a job which updates a   *
  *                      GBP-dependent LOB space, a page of the  *
  *                      LOB may be put into LPL by DSNB5SCM.    *
  *                      The page later gets put into the write  *
  *                      error page range (WEPR , so LPL         *
  *                      recovery cannot repair it.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If an application is canceled while updating a GBP-dependent LOB
  page, and the LOB page is marked "broken", the begin-abort
  processing will schedule online page recovery asynchronously.
  This process will have to wait for the application to commit
  since it requires a drain.  Meanwhile, the application's commit
  processing cannot write the broken page and puts it into LPL.
  Then the online recovery gets control, but cannot recover the
  page since it is now in LPL.  So the failed recovery puts it
  into the write error page range, which requires the RECOVER
  utility to fix it.
  

Problem conclusion

• The begin-abort processing for a broken LOB page has been
  modified to perform the online recovery synchronously, as is
  done for non-LOB objects.  This will prevent having the broken
  page put into LPL and WEPR.  The online recovery logic has been
  modified to handle LOB objects correctly for the synchronous
  case (needs to preserve the invoker's write intent).
  

Temporary fix

• HIPER
  

Comments

APAR Information

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

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

  UK94868 UK94873

Modules/Macros

• DSNB1CFC DSNB1RTR
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK94868

     UP13/06/20 P F306

• R910 PSY UK94873

     UP13/06/20 P F306

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.