Data classes and IFCIDs used by BMC AMI Ops Monitor for Db2 - Data Collector

BMC AMI Ops Monitor for Db2  - Data Collector provides additional trace data collection options for both online and batch functions.

This trace data can also be used as input to batch reporting, so that Db2 SMF recording becomes optional. In addition, the shared Explain function in the Data Collector provides expanded SQL analysis through a direct hyperlink and menu access from BMC AMI Ops Monitor for Db2  views.

The following table describes the trace records that are defined for collection in the BMC AMI Ops Monitor for Db2  - Data Collector.


Data classes

Data class

IFCIDs

DB2ACCT

Db2 accounting records

Db2 IFCIDs:

  • 3–Accounting
  • 239–Accounting DBRM/Package Overflow

DB2AUDIT

Db2 audit records

Db2 IFCIDs:

  • 140–Audit Authorization Failures
  • *141–Audit GRANTs and REVOKEs
  • *142–Audited Object DDL
  • *143–Audited Object First Write Attempt
  • *144–Audited Object First Read Attempt
  • *145–Audited Object DML at BIND
  • 146–User-Defined Audit Trace
  • 312–Audit Trail for DCE Security Processing

DB2PERF

Db2 performance records (all other Db2 IFCIDs)

BMC AMI Ops Monitor for Db2 - Data Collector IFCIDs:

  • *022 and *063–Dynamic SQL Tracing
  • *023-025–Utility Processing
  • 090–Text of Db2 Command
  • 125–RID List Processing
  • 173–ASUTIME Exceeded
  • *225–Storage Summary

DB2SYS

Db2 system records

Db2 IFCIDs:

  • 31–EDM POOL IS FULL EVENTS
  • 001–System Statistics
  • 002–Database Statistics
  • 105–MAPS FOR DATABASE, TABLESPACE, INDEXSPACE
  • 107–Page Set OPEN/CLOSE
  • 172–DEADLOCK EVENTS
  • 196–TIMEOUT EVENTS
  • 199–DATASET STATISTICS

MVDBACC

BMC AMI Ops Monitor for Db2 - Data Collector Accounting Summary Records. (BMC IFCIDs 350-352)

Important

  • IFCIDs that are preceded by an asterisk (*) are disabled by default. For instructions on how to activate additional IFCIDs when you want to produce a report that requires them, see  Activating optional IFCIDs for batch reporting Open link .

    IFCIDs that are not preceded by an asterisk (*) are started for collection automatically, but administration options in the Data Collector allow you to specify that they should be discarded and not written to trace data sets. The data classes can be defined to output groups for logging to different trace data sets. For more information, see Working with DOMPLEX option sets Open link .
  • In general, these data classes should be assigned to the same output group (this option is the default). If changes are made, DB2ACCT and MVDBACC should be kept in the same output group.

The IFCIDs are used as follows:

  • IFCIDs 90, 107, 173, 125, and 140 provide data for system event trace views in BMC AMI Ops Monitor for Db2 .

  • IFCIDs 1, 2, 3, 239, and optionally the audit IFCIDs 140-145, the utility IFCIDs 23-25, and the storage IFCID 225 can be used to provide input to batch reporting instead of SMF.

  • IFCIDs 3, 239, 350-352 are used to provide thread interval history views in BMC AMI Ops Monitor for Db2 . Because the Data Collector trace data sets are compressed, you can usually access a longer time period than from the BMC AMI Ops Monitor for Db2  THRDHIST trace logs.

For information about using the batch reporting program, see DOMBRPT1 utility Open link .

Was this page helpful? Yes No Submitting... Thank you

Comments