z/OS DFSMSdfp Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Diagnosing DB2 problems

z/OS DFSMSdfp Diagnosis
SC23-6863-00

These are some common DB2® problems that may occur during initialization and use of OAM.

When running CBRSAMPL to establish the optical configuration database:
  • You must have SYSADM (system administrator) authority to create the required storage group. If the job fails because of a lack of authority, run it under a user ID having SYSADM authority.
  • Be sure references to a storage group have been changed to match the name chosen for the storage group created in the first step of CBRSAMPL.
When using DB2I:
  • If DSNE110E ("ssid NOT VALID SUBSYSTEM ID, COMMAND TERMINATED," where "ssid" is most often DSN, the default subsystem identifier (ssid)) is issued, set the subsystem name to the name of your DB2 subsystem.
During OAM initialization:
  • If OAM fails to initialize and message CBR0100I, CBR0120I, CBR0140I, CBR0160I, or CBR0180I is issued, consult the accompanying DSNT501I message for the corresponding reason and type codes. If the SQLCODE in CBR0xxxI is -904, and the type and reason codes in DSNT501I are 200 and 00C90081 respectively, the table space corresponding to the table in CBR0xxxI is probably not started. Use a -DISPLAY DATABASE command from DB2I option 7 to verify that this is the case, and then use a -START DATABASE command to correct the problem.
  • If OAM fails to initialize and message DSNE106E is issued, OAM does not have the proper authority to execute application plan CBROAM. Use SPUFI to execute an SQL GRANT command that gives execute authority on plan CBROAM to the public.
  • If OAM fails to initialize with SQLCODE of -818, the level of your DBRMs does not match the level of your object code. Run CBRABIND, the OAM bind job. After receiving message DSNT200I BIND FOR PLAN CBROAM SUCCESSFUL, try to start OAM again.
When using OAM:
  • If frequent resource contention problems occur, check the isolation level parameter used when each application plan was bound. For the optical configuration database, it must be CS for cursor stability, except in the CBRHDUPD plan used by OSMC, which uses level RR for repeatable read.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014