PM45290: KO2O0920E FAILED TO LOCATE DB2 CONTROL BLOCK SPRM FOR SSID after DB2 was restarted in conversion mode. NTH terminates.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After migration of DB2 from v9 (NFM) to v10, DB2s were recycled
  to pick up version 10 code. OMPE monitor successfully
  reconnected, but NTH did not resume. The following error was
  displayed:
  KO2O0920E FAILED TO LOCATE DB2 CONTROL BLOCK SPRM FOR SSID
  .
  After start of NTH via modify command, NTH collection started
  successfully with no apparent issues.
  

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.
  .
  .
  If this was not followed and NTH failed to start, please issue
  the following command to start NTH for newly migrated DB2
  .
  F cccccccc,START H2WLMGR,OPTION=COPTxxxx
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   Near-Term History                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Near-term history collection would not  *
  *                      resume if a DB2 subsystem was stopped   *
  *                      and restarted with a different release  *
  *                      such as in conversion mode.             *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  *                                                              *
  ****************************************************************
  PROBLEM SUMMARY:
  Release-dependent modules were not all reloaded.
  
  PROBLEM CONCLUSION:
  Ensure all release-dependent modules are reloaded & initialized.
  

Problem conclusion

• Ensure all release-dependent modules are reloaded & initialized.
  
  KEYWORDS : NEAR-TERM HISTORY DB2 SUBSYSTEM STOPPED NTH
  

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:

  UK77046 PM71020

Modules/Macros

• KO2$QIOB KO2HDTIB KO2HDTPB KO2HINTB KO2HSQIB
  KO2HSVIB KO2HSVPB KO2HVINB KO2HWLMB KO2IINTB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R510 PSY UK77046

     UP12/03/20 P F203

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.