DBMS0003: Report failed due to defined time-out
Pega Predictive Diagnostic Cloud™ (PDC) creates a DBMS0003 event when a query exceeds the time-out threshold that is specified in the report definition.
Reason for the event
When a report fails because query execution exceeds a time-out threshold that is specified in the report definition, Pega Platform™ generates an exception. PDC identifies and parses the exception to find the name of the faulty report. For every report that fails due to a query exceeding the specified threshold, PDC creates a DBMS0003 event and a corresponding ReportTimeOut case.
Example message text
Report AllOpenItems failed due to timeout per report definition
Recommended next steps
Perform the following actions:
- Optimize the query’s performance
Evaluate the report definition, tables, and indexes to seek performance improvements. Engage a database specialist as a subject matter expert to analyze and optimize the query’s performance. Review the time-out threshold defined on the report definition.
- Optional: Change the time-out threshold in the report definition
If the performance of the report or query cannot be optimized further, update the time-out threshold in the report definition. Use this setting carefully, because even though the time-out threshold in the report definition has no maximum value, the system might have limits at the database or database driver level. Therefore, if you increase the time-out threshold in the report definition too much, you might resolve the problem that the DBMS0003 event represents, but cause a report failure due to socket time-out (DBMS0002).