PI37588: TIMEOUT OCCURRED FOR A ROW LOCK OF DSNDB06.SYSTSTAB, THE HOLDER WAS PIT RECOVER UTILITY AND THE VICTIM WAS COPY UTILITY.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The timeout scenario is :
  In UTILINIT phase of a COPY utility, it needs to expands the
  list by searching SYSTABLES/SYSTABLESPACE/SYSINDEXES because
  LIST requires all INDEXSPACE to be included for a specific
  tablespace. It got timeout on a row of SYSTSTAB, because a PIT
  RECOVER held X lock on this row for about 10 min. The RECOVER
  ran against a list of about 1000 tablespaces/partitions. There
  is no lock escalation on SYSTABLES, and Recover ran completely
  in the end. Based on the syslog and joblog, there is only one
  DSNU971I message appears indicating CHECK PENDING OR AUX CHECK
  PENDING has been successfully set on BCQJ100.SBC2PRL. Its time
  matches when RECOVER utility started to hold X lock on this
  row of SYSTSTAB, then Recover didn't release this X lock until
  the SLIP dump fired after 10 mins.
  
  The timeout resource can also be RID of SYSTSTSP or SYSTSTPT.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS and DB2 11 for z/OS      *
  *                 users of RECOVER utility with PARALLEL       *
  *                 to a prior point in time at the same time    *
  *                 as other utilities using LISTDEF             *
  ****************************************************************
  * PROBLEM DESCRIPTION: DSNT501I (RESOURCE UNAVAILABLE)         *
  *                      REASON 00C9008E (TIMEOUT)               *
  *                      TYPE 00000304 (ROW)                     *
  *                      NAME DSNDB06.SYSTSTAB.X'00000013'.X'10' *
  *                      on a utility using certain LISTDEF      *
  *                      defined lists when run at the same      *
  *                      time as a point-in-time RECOVER.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
    User ran a RECOVER utility job with PARALLEL on a list of
  objects to a prior point in time.  While that job was running,
  a separate utility job was submitted on a list of objects
  defined by LISTDEF utility.  The LISTDEF in the second job
  contained a clause similar to this:
  ... INCLUDE INDEXSPACES TABLESPACE dbname.tsname
    In order for LISTDEF to expand this clause, it needs access
  to tables in the DB2 Catalog, including those found in table
  spaces DSNDB06.SYSTSTAB, DSNDB06.SYSTSTSP, and DSNDB06.SYSTSTPT.
    Since the RECOVER utility contained objects with referential
  integrity (RI) relationships defined, and was to a prior point
  in time, RECOVER must honor and protect the RI on the objects
  being recovered.  To do this it had already locked and accessed
  some of the same catalog tables needed by the LISTDEF in the
  second job, and because there were many objects being recovered,
  these locks were held for some time.
    The result of this was that the second job timed out waiting
  for a catalog row lock held by the RECOVER job:
  ABEND04E MSGSNT501I RC00C9008E TYPE 00000304
  NAME DSNDB06 .SYSTSTAB.X'00000013'.X'10'
  .
  additional keywords: TOLOGPOINT TORBA
  

Problem conclusion

• RECOVER utility code was changed to release unneeded
  resources during RESTORE phase when run to a prior point
  in time with the PARALLEL keyword specified.
  

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:

  UI29003 UI29004

Modules/Macros

• DSNUCBMT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UI29003

     UP15/07/16 P F507

• RB10 PSY UI29004

     UP15/07/16 P F507

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.