PM80194: TIMEOUT RC00C900BA FOR SQL UPDATE WHILE REORG SHRLEVEL REFERENCE IS EXECUTING AND TABLE SPACE IS ACCESS ( RO )

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SQL UPDATE can get a timeout rc00c900ba if run while a REORG
  SHRLEVEL REFERENCE is also executing on table space that was
  started access (ro) read only.
  DSNT376I  @ PLAN=DSNTEP3 WITH
            CORRELATION-ID=P3092104
            CONNECTION-ID=BATCH
            LUW-ID=DSNCAT.SYEC1DB2.CABDEFE23BE4=64
            THREAD-INFO=SYSADM:BATCH:SYSADM:P3092104:DYNAMIC:8:*:*
            IS TIMED OUT.
            ONE HOLDER OF THE RESOURCE IS PLAN=DSNUTIL WITH
            CORRELATION-ID=REORG
            CONNECTION-ID=UTILITY
            LUW-ID=DSNCAT.SYEC1DB2.CABDEEB69499=61
            THREAD-INFO=SYSADM:UTILITY:SYSADM:REORG:*:*  :*:*
            ON MEMBER VA1A
  DSNT501I  @ DSNILMCL RESOURCE UNAVAILABLE
               CORRELATION-ID=P3092104
               CONNECTION-ID=BATCH
               LUW-ID=DSNCAT.SYEC1DB2.CABDEFE23BE4=64
               REASON 00C900BA
               TYPE 00002008
               NAME D30921  .T30921  .00000000
  .
  The customer was expecting the UPDATE to receive sqlcode904
  -904 and RC00C90080 for this case.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 for z/OS users of DB2 Utilities      *
  *                 executing on partitioned table spaces that   *
  *                 are started in read-only mode (RO state)     *
  *                 running concurrently with INSERT, UPDATE or  *
  *                 DELETE                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: Timeout MSGDSNT376I MSGDSNT501I with    *
  *                      RC00C900BA and TYPE00002008 was         *
  *                      encountered by SQL UPDATE while         *
  *                      executing concurrently with REORG       *
  *                      SHRLEVEL REFERENCE that was running on  *
  *                      a partitioned table space started in    *
  *                      read-only mode (RO state), when instead *
  *                      RC00C90080 should have been issued      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  REORG SHRLEVEL REFERENCE and SQL UPDATE were running
  concurrently on a partitioned table space that was started read
  only (e.g. -START DATABASE(...) SPACENAM(...) ACCESS(RO)). The
  SQL UPDATE then encountered a timeout with RC00C900BA (timeout
  waiting for a drain lock).
  
  The following is an example of the timeout encountered by the
  SQL UPDATE:
  
   DSNT376I  @ PLAN=DSNTEP3 WITH
             CORRELATION-ID=P3092104
             CONNECTION-ID=BATCH
             LUW-ID=DSNCAT.SYEC1DB2.CABDEFE23BE4=64
             THREAD-INFO=SYSADM:BATCH:SYSADM:P3092104:DYNAMIC:8:*
             IS TIMED OUT.
             ONE HOLDER OF THE RESOURCE IS PLAN=DSNUTIL WITH
             CORRELATION-ID=REORG
             CONNECTION-ID=UTILITY
             LUW-ID=DSNCAT.SYEC1DB2.CABDEEB69499=61
             THREAD-INFO=SYSADM:UTILITY:SYSADM:REORG:*:*  :*:*
             ON MEMBER VA1A
  
   DSNT501I  @ DSNILMCL RESOURCE UNAVAILABLE
                CORRELATION-ID=P3092104
                CONNECTION-ID=BATCH
                LUW-ID=DSNCAT.SYEC1DB2.CABDEFE23BE4=64
                REASON 00C900BA
                TYPE 00002008
                NAME D30921  .T30921  .00000000
  
  The expectation was that the SQL UPDATE would receive SQLCODE904
  -904 with RC00C90080 (resource was started in read-only mode)
  but instead RC00C900BA was issued.
  
  Had the REORG utility not been running, SQL UPDATE would have
  received SQLCODE904 -904 with RC00C90080 as expected.
  

Problem conclusion

• DB2 was modified such that an INSERT, UPDATE or DELETE executing
  on a partitioned table space started as read-only (RO state),
  where a utility running concurrently on the same object, will
  encounter RC00C90080.
  

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:

  UK92706 UK92707

Modules/Macros

• DSNIDBCP
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK92706

     UP13/04/10 P F304

• R910 PSY UK92707

     UP13/04/10 P F304

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.