IBM Support

PI22405: ZOS_DATA_PROVIDER_0 UNEXPECTED INTERNAL EXCEPTION MESSAGE IN OPMLOG, OPM INSTANCE TERMINATED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • OPM issues the following messages
    
    [2014-07-10 16:10:46.218][3]Operation alert issued:
     Alert ID: opm.operationalert.db2z.plugin.internal.error
     Alert message: An unexpected internal exception occurred.
     Issuing component: Statement Text Tracker
     Alert type: MONITORED_DB
     Alert severity: CRITICAL
     Connection name: DB4E
    [2014-07-10 16:10:50.661][3] Shutdown request from
    [com.ibm.db2pm.server.statementtracker.PEStatementTracker]:
    Error while retrieving Statement Text data from the
    iterator.ZOS_DATA_PROVIDER_0 Unexpected internal exception.
    [2014-07-10 16:10:50.662][3]Terminating :Error while retrieving
    Statement Text data from the iterator.ZOS_DATA_PROVIDER_0
    Unexpected internal exception.
    [2014-07-10 16:10:51.040]Status of [3]: shutting down. [Node:
    NODE0503, Database: DB4E, Host: 10.72.10.2, Port: 5040, OS: ZOS,
    DB2: V11R1FP0]
    [2014-07-10 16:10:51.665][3]Data cleaner has shut down.
    [2014-07-10 16:10:51.677][3]Unexpected error in thread
    PEStatementTracker, thread terminates,
    com.ibm.db2pm.server.statementtracker.StmtTrackerException:
    ZOS_DATA_PROVIDER_0 Unexpected internal exception.
    [2014-07-10 16:10:51.677][3]Statement text collector has shut
    down.
    [2014-07-10 16:10:51.788][3]Listening for incoming Extended
    Insight client data has shut down.
    [2014-07-10 16:10:51.789][3]Transaction and statement data
    aggregator has shut down.
    [2014-07-10 16:10:51.790][3]Transaction and statement data
    loader has shut down.
    [2014-07-10 16:10:51.790][3]Transaction and statement merger has
    shut down.
    [2014-07-10 16:11:02.633][3]Statement metric collector has shut
    down.
    [2014-07-10 16:11:02.636][3]Monitoring has shut down.
    [2014-07-10 16:11:03.041]Status of [3]: stopped. [Node:
    NODE0503, Database: DB4E, Host: 10.72.10.2, Port: 5040, OS: ZOS,
    DB2: V11R1FP0]
    [2014-07-10 16:11:09.046]Operation alert issued:
     Alert ID: opm.operationalert.startup.monitoring.permdisabled
     Alert message: Monitoring is disabled for monitored instance.
     Alert property:
    opm.operationalert.startup.monitoring.permdisabled.prop.monitore
    dconnections.key=DB4E
     Alert property:
    opm.operationalert.startup.monitoring.permdisabled.prop.consolel
    ogfile.key=/opt/ibm/instances/db2inst1/opm/v5/db2inst1/db2pesrv.
    log
     Alert property:
    opm.operationalert.startup.monitoring.permdisabled.prop.instance
    id.key=3
     Issuing component: OPM server startup
     Alert type: REPOSITORY_DB
     Alert severity: CRITICAL
    [2014-07-10 16:11:09.082]The monitoring of [3] was terminated
    because of a severe problem and will not be restarted (no
    restart after shutdown), details: error code = 14, error message
    = "Error while retrieving Statement Text data from the
    iterator.ZOS_DATA_PROVIDER_0 Unexpected internal exception."
    
    and terminates monitoring for the instance without restart.
    This occurs when OPM monitores stored procedures even if
    PM94773 is applied.
    

Local fix

  • Turn off monitoring stored procedures in OPM Webconsole for the
    instance(s) in problem
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - OPM                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the Web Console has the Stored       *
    *                      Procedure Monitoring feature enabled    *
    *                      and the stored procedures are only      *
    *                      short living, by the time the stored    *
    *                      procedure information is retrieved      *
    *                      from the DB2 catalog (by the            *
    *                      Repository Server), the stored          *
    *                      procedure is already dropped. This      *
    *                      causes an internal exception in the     *
    *                      Repository Server to be triggered that  *
    *                      causes the monitoring for the           *
    *                      respective DB2 subsystem to stop.       *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF.                              *
    ****************************************************************
    PROBLEM SUMMARY:
    If the Web Console has the Stored Procedure Monitoring feature
    enabled and the stored procedures are only short living, by the
    time the stored procedure information is retrieved from the DB2
    catalog (by the Repository Server), the stored procedure is
    already dropped. This causes an internal exception in the
    Repository Server to be triggered that causes the monitoring
    for the respective DB2 subsystem to stop.
    
    PROBLEM CONCLUSION:
    The exception handling within the Repository Server needs to be
    improved to allow for continued monitoring.
    
    KEYWORDS:
    ZOS_DATA_PROVIDER_0, STORED PROCEDURE MONITORING
    
    CIRCUMVENTION:
    Disable Stored Procedure Monitoring in Web Console or OMPE
    Collector.
    

Problem conclusion

  • PROBLEM CONCLUSION:
    The exception handling within the Repository Server needs to be
    improved to allow for continued monitoring.
    
    KEYWORDS:
    ZOS_DATA_PROVIDER_0, STORED PROCEDURE MONITORING
    
    CIRCUMVENTION:
    Disable Stored Procedure Monitoring in Web Console or OMPE
    Collector.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI22405

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    511

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-07-22

  • Closed date

    2014-09-18

  • Last modified date

    2017-01-26

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

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

    UI20434 UI20435

Modules/Macros

  • FPEO$INF
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R511 PSY UI20434

       UP14/09/20 P F409

  • R520 PSY UI20435

       UP14/09/20 P F409

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
26 January 2017