KO2O0602W %%%% Trace data lost - too many buffers in use.

Explanation

%%%% is the name of the Db2 subsystem. Db2 produces IFCID records faster than the Near-Term History Collector can process. Currently, more than 15 buffers are used. The collection of IFCID records is suspended until 15 or less buffers are used.

System action

Records are skipped until the Near-Term History Collector can reduce the backlog of records to be processed.

User response

You can solve the problem by doing one or more of the following actions.
Note:

Use the Configuration Tool (previously called ICAT, panel KD261P8 and KD261PB) to modify the BUFSIZE-, NEGSQL-, SCAN-, SORT-, DYNAMICSQL- and POSTPCT- parameters below.

If you do not use the Configuration Tool to record and update the parameter library, changes might be reversed the next time you are using it.

  1. Increase the buffer size by setting its value to 2048. Try different values and evaluate the results.

    By default, the buffer size (BUFSIZE) is 1024. This value might be too small for high volume production systems. The upper limit for the buffer size is the maximum value for a -START TRACE command. For more information, see the Db2 commands reference.

    For the OMEGAMON® Near-Term History collector, the recommended value for the buffer size is 2048.

  2. Reduce the number of IFCIDs to be written to the OPx by using the following settings:
    NEGSQL(NO)
    Use this setting to not collect return codes on SQL events.

    Affected IFCIDs: 58, 59, 60, 61, 62, 64, 65, 66, 233.

    If Near-Term History data is not collected to sequential files, there is no reason to collect this data.

    Near-Term History data is not externalized by the real time product. However, it can be externalized by batch reporting if it is collected to sequential files.

    SCAN(NO)
    Use this setting to not collect SCAN data.

    Affected IFCIDs: 15, 16, 17, 18.

    SORT(NO)
    Use this setting to not collect SORT data.

    Affected IFCIDs 95, 96.

    DYNAMICSQL(NO)
    Use this setting to not collect SQL text from dynamic SQL statements.

    Affected IFCIDs 22, 63.

    The collection of NEGSQL-, SCAN-, SORT-, and DYNAMICSQL-data results in a high volume of trace data that is generated by the Db2 subsystem. This increases the CPU utilization. Furthermore, it exposes the application to DSNW133I messages.

  3. Reduce the POSTPCT value to read buffers more frequently. Try different values and evaluate the results.

    By default, the POSTPCT value is set to POSTPCT(70). This means that the OP buffers are read when they are full up to 70%.

  4. Ensure that the OMPE Collector task is running at the same or at a higher service level than the monitored Db2 subsystems.
  5. Restart the OMEGAMON for Db2 PE started task to start using the modified parameters.