PM87052: DB2STOP COMMAND CAN END BEFORE DB2 IS TOTALLY DOWN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• It is possible for the DB2STOP command to end before DB2 is
  totally down.
  
  This can cause a subsequent DB2START command to fail with the
  message:
  CKZ25536E DP11MSTR DID NOT START WITHIN MSTR-DETECT-WAIT TIME
  LIMIT While the DB2START command is executing the system log
  can show the messages:
  CKZ25570I STARTING DB2 SUBSYSTEM: DB2T
  -DB2T START DB2
  DSN3106I -DB2T DSN3EC0X - SUBSYSTEM STOPPED. THIS COMMAND NOT
  PROCESSED:
  -START DB2
  DSN3104I -DB2T DSN3EC0X - TERMINATION COMPLETE
  DSN3100I -DB2T DSN3EC0X - SUBSYSTEM DB2T READY FOR START COMMAND
  
  The START DB2 command was being issued before DB2 was totally
  down because DB2STOP ended before DB2 was totally down.
  

Local fix

• Add a 5 second delay after DB2STOP ends and before DB2START is
  run.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Cloning Tool.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: It is possible for the DB2STOP command  *
  *                      to end before DB2 is totally down.      *
  *                      This can cause a subsequent DB2START    *
  *                      command to fail with the message:       *
  *                      CKZ25536E DP11MSTR DID NOT START        *
  *                      WITHIN MSTR-DETECT-WAIT TIME LIMIT      *
  *                      While the DB2START command is           *
  *                      executing the system log can show the   *
  *                      messages:                               *
  *                      CKZ25570I STARTING DB2 SUBSYSTEM: DB2T  *
  *                      -DB2T START DB2                         *
  *                      DSN3106I -DB2T DSN3EC0X - SUBSYSTEM     *
  *                       STOPPED. THIS COMMAND NOT PROCESSED:   *
  *                      -START DB2                              *
  *                      DSN3104I -DB2T DSN3EC0X - TERMINATION   *
  *                       COMPLETE                               *
  *                      DSN3100I -DB2T DSN3EC0X - SUBSYSTEM     *
  *                       DB2T READY FOR START COMMAND           *
  *                      The START DB2 command was being issued  *
  *                      before DB2 was totally down because     *
  *                      DB2STOP ended before DB2 was totally    *
  *                      down.                                   *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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:

Modules/Macros

• CKZ00222
  

Fix information

• Fixed component name

  DB2 CLONING TOO

• Fixed component ID

  5655N1000

Applicable component levels

• R310 PSY UK94615

     UP13/06/01 P F305

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.