The monitoring agent cannot insert all requested data rows into the persistent data store

Failure to write data to the persistent data store can indicate performance problems, or the problem might occur if the persistent data store is full.

About this task

If you determine that a performance issue is the cause of the problem, see Troubleshooting performance issues.

If the problem is that the persistent data store is full, then log messages in the RKPDLOG sysout data set will indicate issues with components prefixed by KPD or KPX. The KPD and KPX prefixes indicate problems with the persistent data store.

Procedure

Perform the following steps to determine whether the persistent data store files (Short Term History) are full.

Note: Processor and memory usage might increase in the z/OS address space where the persistent data store stores data, regardless of whether the persistent data store is in the monitoring agent address space or the Tivoli Enterprise Monitoring Server address space.

  1. From the TSO SDSF log (=S.LOG), enter the following commands against your IBM® OMEGAMON for IMS on z/OS monitoring agent job, for example IBMI5. 
    /F IBMI5, KPDCMD QUERY CONNECT
/F IBMI5, KPDCMD QUERY DATASTORE
  2. Examine the RKPDLOG as follows:
    1. To view the RKPDLOG from the TSO SDSF Status panel (=S.ST), enter a ? next to the name of the agent job, for example, IBMI5.
      This action causes the RKPDLOG to be presented.
    2. Enter an S next to the RKPDLOG entry to open it.
    3. Review the RKPDLOG to see the output of the QUERY command and determine whether the RKIPHIS* files are full.