How to clear "Query Execution Timed Out" error alerts during Oracle monitor data collection?
Applications Manager throws the query timed out error in some scenarios as below:
Query execution timed out due to this query group(s) : xxxxxxxx
Error Message : java.sql.SQLRecoverableException: IO Error: Socket read timed out.
Query execution timed out due to this query group(s): xxxxxxxx
Error Message: java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation.
xxxxxxxx - is the query group name
From the Applications Manager GUI, Go to respective Oracle Monitor's details page -> Monitor Actions -> Edit Monitor -> Increase the seconds mentioned in "Query Execution Timeout" field.
If the query group reported is INSTANCESTATUS or TABLESPACESTATUS and If the alert still continues even after performing the above step then check the below KB and perform the steps in the corresponding Oracle Database with the help of your Oracle DBA.
This issue occurs on INSTANCESTAUS/TABLESPACESTATUS because the queries against the dictionary table DBA_FREE_SPACE were taking a long time to execute.
- In release 10g, the view DBA _FREE_SPACE was modified to also include objects in the recycle bin.
- A large number of objects in the recycle bin can slow down queries on DBA _FREE_SPACE. This is normal behavior.
- For release 11g, the view DBA _FREE_SPACE does not contain a hint which in case there are only a few objects in the recycle bin, you may want to gather underlying stats of tables/dictionaries to get better performance.
Run the below query and check count in recycle bin:
- SQL> SELECT count(*) FROM dba_recyclebin;
If the count is higher, then purge the recycle bin using below command:
- SQL> PURGE dba_recyclebin;
- SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
- SQL> EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
For multi-tenant enabled Oracle, the container database and the pluggable databases require independent purge.
Windows Monitor Data collection is running too slow and it is timed out
Applications Manager uses VB scripts for connecting and fetching Telemetry data from remote servers. This error occurs when the script execution times out (default timeout value is 300 seconds). Possible Reasons: Data collection script may be ...
The Oracle monitor is not working / The Oracle monitor is not collecting any data. What can I do?
Reason 1 - This could be because the Oracle user provided in Applications Manager does not have the necessary permission to run the query Go to <AppManager/logs> directory and check if you have an error print in stderr.txt / stderr.txt.1 / ...
How do I monitor Oracle Alert Logs?
Alert Log monitoring in Applications Manager is not enabled by default. Here is how you can enable monitoring of Alert Log statistics: Go to the Admin tab. Click Performance Polling under Discovery and Data Collection. Under Performance Data ...
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
No data available (or) error in Microsoft Dynamics AX monitor
If data is not available or any error occurs during data collection for Microsoft Dynamics AX monitor, follow the steps below: Open command prompt in administrator mode in Applications Manager-installed machine. Go to <Applications Manager ...