00D70012

Explanation

A password or security error has occurred. An attempt to access a integrated catalog facility (ICF) catalog entry for a cluster (data set) failed because of some security violation. This is probably a user error. It may be caused either by the incorrect specification of a password or the changing of the password in the Db2 catalog (via SQL ALTER) but not in the integrated catalog facility (ICF) catalog (via access method services ALTER) or vice versa.

System action

A 'resource not available' code is returned to the user.

System programmer response

Notify the database administrator if appropriate. Otherwise, check the passwords and/or RACF® authorizations.

User response

Ensure that the correct password is being used. If you are unable to resolve the problem yourself, notify the database administrator.

Problem determination

Obtain output from SQL SELECT * FROM SYSIBM.SYSTABLESPACE and (if storage group related) SELECT * FROM SYSIBM.SYSSTOGROUP. Also obtain integrated catalog facility (ICF) catalog listing, details of the request that resulted in this code, and contents of the SQLCA. Also obtain operator's console sheet showing related messages, if any. This documentation will assist you in determining the cause of the problem if it is not merely an incorrect password. If you suspect an error in Db2, If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
  • IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the Db2 subsystem catalog that defined the failing index or table.
  • Listing of the results produced by the SQL statements.
  • Listing of Db2 catalog tables.
  • SYSPRINT output, including JCL, for the application program or batch job, and system messages that were issued. Make sure that MSGLEVEL=(1,1) on the JOB statement so that all diagnostic information is sent to SYSPRINT.
  • Definitions of views and tables involved in the error.