PL33944: MSGDSNT408I SQLCODE -904 REASON 00C90084 TYPE 230 NAME 4K AFTER CATALOG RECOVERY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CUSTOMER TESTED CATALOG RECOVERY BY EXECUTING FOLLOWING SCENARIO
  1- IMAGE COPY OF DSNDB01 AND DSNDB06
  2- STOP DB2
  3- DELETE CLUSTERS OF DSNDB01 AND DSNDB06
  4- START DB2
      AT THE END OF STARTUP, AFTER MSG DSNR006I (=BACKWARD
      RECOVERY DONE) HE RECEIVES :
      DSNP012I % DSNPGNP0 ERROR IN VSAM CATALOG LOCATE FUNCTION
               FOR DB2T.DSNDBD.DSNDB01.DBD01.I0001.A001
               CTLGRC = 00000008  CTLGRSN = C5C7002A
      DSNI004I % RESOURCE HAS BEEN STOPPED
               TYPE 00000200   DSNDB01.DBD01
      DSNR002I % RESTART COMPLETE
  5- % START DATABASE(DSNDB01) SPACENAM(DBD01)
  6- DEFINE ALL CLUSTERS FOR DSNDB01 AND DSNDB06
  7- RECOVER ALL DSNDB01 AND DSNDB06 TABLESPACES PLUS INDICES IN
     THE RIGHT SEQUENCE
  8- WHEN EXECUTING A QUERY, HE RECEIVES :
      DSNT408I SQLCODE = -904      REASON= 00C90084
               TYPE = 00000230     RESOURCE NAME = 4K
  ON THIS, CUSTOMER TOOK STANDARD ACTION BUT WITHOUT RESULTS.
  THE ONLY SOLUTION TO GET OUT OF THIS IS TO STOP AND START DB2.
  CUSTOMERS REQUEST IS THAT FOR DSNT408I, THE EXPLANATION IN
  'MSGS AND CODES' SHOULD BE EXTENDED FOR THIS MSG. ALSO THE
  'SYSTEM AND DATA BASE ADMINISTRATION GUIDE' SHOULD HANDLE THIS
  SITUATION IN THE CHAPTER OF CATALOG RECOVERY.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: ALL DB2 USERS.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: SQLCODE -904 RC00C90084 TYPE 230 NAME   *
  *                      4K AFTER DBD01 UNAVAILABLE DURING       *
  *                      DB2 STARTUP.                            *
  ****************************************************************
  * RECOMMENDATION: APPLY PTF WHEN AVAILABLE.                    *
  ****************************************************************
  AFTER A DB2 STARTUP IN WHICH TABLESPACE DSNDB01.DBD01 WAS
  UNAVAILABLE, AN SQL STATEMENT THAT REQUIRED A WORKFILE RECEIVED
  RESOURCE UNAVAILABLE CONDITION ON THE TEMPORARY WORKFILE
  TABLESPACE. THE WORKFILE DATABASE, DSNDB07, WAS NOT INITIALIZED
  DURING DB2 STARTUP BECAUSE IT'S DBD COULD NOT BE ACCESSED. A
  SUBSEQUENT STOP AND START OF DSNDB07 SPECIFYING SPACENAM DID
  NOT CORRECT THE SITUATION.
  

Problem conclusion

• CODE WAS ADDED TO THE PAGESET START ROUTINE TO CHECK IF A
  TEMPORARY WORKFILE TABLESPACE IS BEING STARTED AND THE WORKFILE
  DATABASE HAS NOT YET BEEN INITIALIZED, THEN WORKFILE DB
  INITIALIZATION IS INITIATED BEFORE PROCEDING. AN RPC HAS BEEN
  SUBMITTED TO UPDATE THE RECOVERY SECTION OF THE SYSTEMS &
  DATABASE ADMINISTRATION GUIDE TO REMIND USERS THAT DSNDB07 MAY
  BE STOPPED AND STARTED AGAIN TO INITIALIZE THE WORKFILE
  DATABASE AFTER DB2 HAS BEEN STARTED WITH A RESOURCE
  UNAVAILABLE CONDITION ON DSNDB01.DBD01.
  

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:

  UL44412

Modules/Macros

•    DSNISPS
  

Fix information

• Fixed component name

  5740 IBM DATABA

• Fixed component ID

  5740XYR00

Applicable component levels

• R210 PSY UL44412

     UP89/02/14 P F903

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.