Detector is not showing the data in production

Article Id: 130714

Status: Published

Updated On: 22-05-2019 08:05

Products:

CA Bind Analyzer for DB2 for z/OS , CA SQL-Ease for DB2 for z/OS , CA Sysview Performance Management Option for DB2 for z/OS , CA Database Detector for DB2 for z/OS , CA Plan Analyzer for DB2 for z/OS , CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction:

Running tests and a procedure failed due to a -905 error exceeding CPU limit.
In Omegamon can be seen a specific thread pointing to package SCC355 (Elapsed Time 01min 52sec).
In CA Detector the -905 error is not reported with an Exception recorded.

Cause:

For R19 and above releases, -905 threshold setting under profile options has been deprecated.
So Detector will collect the -905 SQL error only if it is generated by DB2.

Environment:

z/os
DB2

Resolution:

Be aware that for R19 and above releases, -905 threshold setting under profile options has been deprecated.
So Detector will collect the -905 SQL error only if it is generated by DB2.
The Detector profile threshold setting to flag -905 SQL error is not supported anymore.