How to clear "Query Execution Timed Out" (or) "Socket Read Timed Out" error alerts during Oracle monitor data collection?

How to clear "Query Execution Timed Out" (or) "Socket Read Timed Out" error alerts during Oracle monitor data collection?

Applications Manager throws the Query timed out/Socket read timed out error in some scenarios as below: 
Socket read timed out due to this query group(s) : xxxxxxxx
Error Message :  java.sql.SQLRecoverableException: IO Error: Socket read timed out. 
(OR)
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

Solution:  

If the alert is Query execution timed out alert then
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 alert is Socket read timed out alert then
From the Applications Manager GUI, Go to respective Oracle Monitor's details page -> Monitor Actions -> Edit Monitor -> Increase the seconds mentioned in " Socket Read 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.

For other query group (s), reach out to our support ( appmanager-support@manageengine.com) with the latest  support information file generated with print all logs enabled from Applications Manager.  

This issue occurs on INSTANCESTAUS/ TABLESPACESTATUS because the queries against the dictionary table  DBA_FREE_SPACE were taking a long time to execute. 

(I) Recommendation of Oracle Support for " Queries on DBA_FREE_SPACE are Slow (Doc ID 271169.1)" states the following reasons: 
  1. In release 10g, the view DBA _FREE_SPACE was modified to also include objects in the recycle bin.
  2. A large number of objects in the recycle bin can slow down queries on DBA _FREE_SPACE. This is normal behavior. 
  3. 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;

(II) Next recommendation of Oracle Support for " How to Gather Statistics on Objects Owned by the ‘SYS’ User and ‘Fixed’ Objects (Doc ID 457926.1)" to gather dictionary and fixed table stats (with customers permission).
  • SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; 
  • SQL> EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

Note : For multi-tenant enabled Oracle, the container database and the pluggable databases require independent purge.


      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...

                    • 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 running ...

                    • Self monitor Applications Manager using Real User Monitoring

                      We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...

                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...

                    • 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 ...

                      Related Products