AwE-5001 Database Query and AwE-5079 SQL Execution Timeout Errors trying to fetch job execution history

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

When trying to get job execution history, users run into  ErrorMsg: AwE-5001 Database Query Error. Logs indicate SQL Execution Timeout errors as below:

ErrorMsg: AwE-5079 SQL Execution Timeout 
Details: SQL query execution exceeded 10 seconds
java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation

Environment

Release : 9.4.4

CA Automic Applications Manager

Cause

 AwE-5001 followed by a exectuion timeout in logs, is not an error but a warning that a timeout was reached with too many results matching the search criteria. This warning is caused by the new Execution timeout feature added in 9.4.4 to avoid problems with huge query results bringing system down. 

Prior to 9.4.4 The History Query option in Applications Manager does not have any options available that would stop a User from doing an query that pulls so much data that the RMI process will temporarily unavailable and can result in a Java Heap on the CR thread.

Resolution

 With version 9.4.4 we have 2 new fields to return rows limit and query timeout on AM History filter:

• Max Returned Rows, default to 1000 rows
• Query Execution Timeout with default value of 10 sec

Adjusting the searches results to match default Max Returned Rows and Query Execution Timeout values allowed to complete the results without errors.

Please note the 2 values above  can be increased, but keeping in mind running queries that need longer timeout could pull large amount of data thereby causing performance / crashing issues.