Unable to list unexternalized SQL errors for a specific time range in Detector for Db2 for z/OS.
search cancel

Unable to list unexternalized SQL errors for a specific time range in Detector for Db2 for z/OS.

book

Article ID: 438481

calendar_today

Updated On:

Products

Detector for DB2 for z/OS Database Management for DB2 for z/OS - Administration Suite Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Utilities Suite DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

Is there a utility in Detector for Db2 for z/OS (PDT) that can list SQL errors for a specific time range (e.g., between 6:00 PM and 6:30 PM) that have not yet been externalized to the PDT datastore?

Cause

By design, Detector collects SQL error data in memory during the active collection interval. This data is typically made available for external utility reporting and long-term analysis once the interval is completed and the data is saved (downloaded) to the datastore. There is currently no standalone utility provided to report on "in-flight" or unsaved error data for a user-defined time range.

Resolution

There is no standalone utility in Detector to list unexternalized SQL errors for a specific time range. To view current error activity, you must use the standard Detector collection viewing panels (e.g., the SQL ERROR Summary Display) while the collection is active.