PK47796: DB2 INSTANCE STOPPING FAILURE DUE TO ERROR HANDLING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 INSTANCE STOPPING FAILURE DUE TO ERROR HANDLING
  
  FYI.
  
  PE Server Instance start of DES versus DWD
  -> DES stopped with code 8 is okay
  -> DWD should have been stopped as well with code 8 instead of
     restart.  It's an error handling.
  
  Don't know why only one of the two systems: DES and DWD fails.
  DES fails but DWD tries several times until TRACE is started.
  
  .
  12.29.59 STC05484  FPEV0128S
           DES  CONNECT TO DB2 FAILED. MONITOR TRACE IS NOT
           STARTED
  12.29.59 STC05484  FPEV0128S
           DWD  CONNECT TO DB2 FAILED. MONITOR TRACE IS NOT
           STARTED
  12.29.59 STC05484  FPEV0165I
           DES INSTANCE FOR DB2 SUBSYSTEM DES IS STOPPING
  12.29.59 STC05484  FPEV0165I
           DWD INSTANCE FOR DB2 SUBSYSTEM DWD IS STOPPING
  12.30.01 STC05484  FPEV0169E
           MSTR SERVER INSTANCE FOR DB2 SUBSYSTEM DES STOPPED WITH
           ERROR CODE 8
  12.30.02 STC05484  FPEV0164I
           DWD INSTANCE FOR DB2 SUBSYSTEM DWD IS STARTING
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   PE Server                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the OMEGAMON Server subtask        *
  *                      PESERVER starts a monitoring PESERVER   *
  *                      instance for a DB2 subsystem and the    *
  *                      DB2 monitor trace is not started, the   *
  *                      PESERVER instance issues message        *
  *                      FPEV0128S and stops. The PESERVER       *
  *                      master will then try to restart the     *
  *                      instance resulting in a restart loop.   *
  *                      This may cause contention on data base  *
  *                      DB2PM resources.                        *
  *                                                              *
  *                      for V310                                *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.211          *
  *                                                              *
  *                      for V410                                *
  *                      The service level of the                *
  *                      OMEGAMON server subtask PESERVER        *
  *                      FPEV0000I  DATA SERVER INITIALIZATION   *
  *                      FPEV0114I  PTF BUILD IS 07.211          *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF.                              *
  ****************************************************************
  When the OMEGAMON Server subtask PESERVER starts a monitoring
  PESERVER instance for a DB2 subsystem and the DB2 monitor trace
  is not started, the PESERVER instance issues message FPEV0128S
  and stops. The PESERVER master will then try to restart the
  instance. Thus restarts are performed in a loop. This may cause
  contention on data base DB2PM resources or locking among
  PESERVER subtasks.
  

Problem conclusion

• When the OMEGAMON Server subtask PESERVER starts a monitoring
  PESERVER instance for a DB2 subsystem and experiences error
  conditions during start up, the PESERVER instance stops and will
  not be restarted again. Message FPEV0169E is issued to the
  server log.
  
  KEYWORDS :
  FPEV0128S INSTANCE STARTING STOPPING LOOP RESOURCE CONTENTION
  LOCKING
  

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:

  UK27609 UK27610

Modules/Macros

•    DGOVMIDI DGOVMSTR
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK27609

     UP07/08/01 P F707

• R410 PSY UK27610

     UP07/08/01 P F707

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.