PM30238: DB2 ABEND04F during DB2 Version Migration with OMEGAMON for DB2 monitoring subsystem

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 ABEND04F during DB2 Version Migration with OMEGAMON for DB2
  monitoring subsystem
  .
  From LOGREC detail report we have seen the following sequences:
  1) abend0c4 pic4 dsnwards pointing to the old DB2 V9 lib
     with jobname from OMPE STC task
  2) abendu3590 rc00200010 with jobname from DB2 DBM1 task
  3) abend04F rc00E80100 from DB2 task
  .
  It appears that this problem occurred because the customer was
  taking the following action:
  .
  1 - Started the DB2 subsystem at the DB2 V9 level.
  2 - Started OMPE with Object Analysis (OA)against that DB2
  3 - Performed the migration actions required to migrate the DB2
      subsystem to DB2 V10
  4 - Stopped the DB2 subsystem
      As a result, OA for that subsystem went into "auto-restart
      mode." Auto-restart makes a number of assumptions, one being
      that the DB2 version will not change.
  5 - Restarted the DB2 subsystem, which is now at the DB2 V10
      level.
  6 - OA Auto-restart recognized that the subsystem was active,
      and attempted to activate collection for that subsystem.
      However, as it assumed it was a DB2 V9 subsystem, the
      incorrect DB2 dependent module was loaded, causing OA to
      issue a user ABEND 3590, which resulted in the 04F abend
      of the DB2 subsystem.
  =============================================================
  Additional Search words:
  Upgrade cycle recycle restart
  

Local fix

• When performing a version migration on a DB2 subsystem, i.e.,
  from DB2 V9 to DB2 V10, before stopping/restarting the DB2
  subsystems, all OMPE servers that are monitoring the subsystem
  must be shut down, and not restarted until AFTER the DB2
  subsystem has been restarted after the version migration is
  complete.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   OMEGAMON collector                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: DB2 ABENDUE06 caused by OA              *
  *                      being active across DB2 version         *
  *                      migration jobs.                         *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  DB2 could experience ABENDUE06 if Object Analysis is active when
  subsystem is brought down and back up to perform version
  migration.
  
  PROBLEM CONCLUSION:
  If Object Analysis recognizes DB2 version change,
  use appropriate interface modules.
  

Problem conclusion

• If Object Analysis recognizes DB2 version change,
  use appropriate interface modules.
  
  KEYWORDS : DB2 ABENDUE06 OBJECT ANALYSIS
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK66171

Modules/Macros

•    HKDB510J KDB510J  KO2EGX1A KO2EGX1K KO2EGX13
  KO2EIXMF KO2EOJAB KO2EOJSA KO2EOJSK KO2EOJS2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R510 PSY UK66171

     UP11/03/31 P F103 Ž

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.