ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Detector is not showing the data in production
Article ID: 130714
Updated On:
Products
Bind Analyzer for DB2 for z/OS
SQL-Ease for DB2 for z/OS
SYSVIEW Performance Management Option for DB2 for z/OS
Plan Analyzer for DB2 for z/OS
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.
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.
So Detector will collect the -905 SQL error only if it is generated by DB2.
Environment
z/os
DB2
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.
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.
Feedback
Yes
No
Powered by
