ORA-01013 errors during Oracle database monitoring (4232611)

ORA-01013 Oracle errors are found in an Oracle agent log within a one hour timeframe.

FMS server yourserver reports: Warning: agentname@yourserver: <Collection Name> Failed with the exception:Failed to execute query on instance [yourserver-agentname], user account [youraccount]. Reason : [ORA-01013: user requested cancel of current operation- Profile:OracleProfile{host='yourserver', instance='instancename', username='youraccount', asSysDBA=false, ports='49125', Socket read timeout=900000, QueryTimeout=600}

"ORA-01013 is known as an "information" error.  It is letting you know that the operation has been cancelled by either:

• caused by the user (pressing CTRL-C or a different method like front-end application),
• caused by a response to congruent errors OR
• the result of timeouts.

Resolution #1

Confirm that the "Script Execution Timeout" parameter in the sqlnet.ora on the monitored host is set to a value larger (in minutes) then the duration for the SQL collection takes to run
sqlnet.expire_time = <integer_minutes>

Resolution #2

This occurs when a SQL collection query does complete within the query timeout period, typically this is caused due to temporary heavy load on the instance.

Resolution #3

Increase the collection timeout in the agent administration

1. Navigate to Database dashboard
2. Choose the database agent encountering the issue by enabling the appropriate checkbox.
3. Click the "Adminster Agents" button in the top right corner of the panel.
4. Choose "Collection Frequencies" in the Global Administration panel.
5. Highlight the appropriate collection and click the "Edit" button
6. Increase the Real-Time Frequency and Query timeout (e.g. from 60 to 180 seconds)
7. Click the "Set" button and then click the "Save Changes" button.

Resolution #4

Make sure the database statistics are up-to-date. Connect to the database via SQL*Plus using the same user the DB agent is using to collect metrics. Run a simple "Select count(*) from <problematic table>;". The table name should be displayed in the Foglight error message you get.

If the query takes long to finish, it could be related to the old database statistics.

Please contact your DBA to update the statistics.