PK70196: OEM SQL MONITOR ISSUES THE FOLLOWING MESSAGE: DSNT408I DSNT408I SQLCODE = -204,ERROR: DB2PM.PARAMETER IS UNDEFINED NAME

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The OMEGAMON Server subtask PESERVER continuously issues SQL
  SELECT statements to the table DB2PM.PARAMETER no matter
  whether the functionality requesting the SELECT is enabled
  or disabled and whether the table exists or not.  When the
  DB2PM database does not exist, DB2 returns SQL -204 repeatedly
  as a response to the SELECT statements.  The SQL code is handled
  internally by the issuing PESERVER instance.
  External query monitoring tools might report the experienced DB2
  SQL code -204 as error condition.
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component                           *
  *                 - PE Server                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: When the Performance Warehouse (PWH)    *
  *                      database DB2PM does not exist for a     *
  *                      monitored DB2 subsystem in a Data       *
  *                      Sharing Group (DSG) and DB2 Connect     *
  *                      Monitoring is not activated, the        *
  *                      monitoring PESERVER instance does still *
  *                      repeatedly try to access tables in      *
  *                      database DB2PM which are related to DB2 *
  *                      Connect Monitoring (for example table   *
  *                      DB2PM.PARAMETER). DB2 returns SQLCODE   *
  *                      -204. The error condition is handled    *
  *                      internally by the PESERVER instance and *
  *                      not externalized but will become        *
  *                      visible to other monitoring tools or in *
  *                      an SQL activity trace.                  *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  When the Performance Warehouse (PWH) database DB2PM does not
  exist for a monitored DB2 subsystem in a Data Sharing Group(DSG)
  and DB2 Connect Monitoring is not activated, the monitoring
  PESERVER instance does still repeatedly try to access tables in
  database DB2PM which are related to DB2 Connect Monitoring
  (for example table DB2PM.PARAMETER). DB2 returns SQLCODE -204.
  The error condition is handled internally by the PESERVER
  instance and not externalized but will become visible to other
  monitoring tools or in an SQL activity trace.
  
  PROBLEM CONCLUSION:
  When DB2 Connect Monitoring is disabled, tables in database
  DB2PM which are related to DB2 Connect Monitoring are no longer
  repeatedly accessed by the monitoring PESERVER instance.
  
  KEYWORDS: SQLCODE -204 DB2PM.PARAMETER DB2 CONNECT MONITORING
  

Problem conclusion

• PROBLEM CONCLUSION:
  When DB2 Connect Monitoring is disabled, tables in database
  DB2PM which are related to DB2 Connect Monitoring are no longer
  repeatedly accessed by the monitoring PESERVER instance.
  
  KEYWORDS: SQLCODE -204 DB2PM.PARAMETER DB2 CONNECT MONITORING
  

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:

  UK39168

Modules/Macros

•    DGOVMSTR FPE@WRP2 FPEVWRP2
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R410 PSY UK39168

     UP08/08/23 P F808

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.