The Foglight Oracle agent intermittently fails to collect data from monitored Oracle instances. The following error messages appear in the agent logs:
ERROR [<instance>-lowPriorityPool-XXX-[DBO_Datafile_IO_Activity]]
com.quest.qsi.fason.oracle.collection.processor.DBOInstanceProcessor -
Failed to run DBODatafileIOActivityProcessor processor of DBO_Datafile_IO_Activity collection of <instance> instance.
java.lang.RuntimeException: Failed to execute collection [DBO_Datafile_IO_Activity], reason=ORA-02396: exceeded maximum idle time, please connect again
Additional errors may include:
ERROR [<instance>-lowPriorityPool-XXX-[DBO_Instance_General]]
com.quest.qsi.fason.framework.connections.oracle.OracleConnectionImpl -
"Failed to set context info, reason=<instance>-DBO_Instance_General"
com.quest.qsi.fason.framework.connections.common.exceptions.FrameworkQueryException:
ORA-02396: exceeded maximum idle time, please connect again
The Oracle database enforces an IDLE_TIME limit via user profiles. When the Foglight agent's session remains idle longer than the configured threshold, Oracle terminates the session, resulting in the ORA-02396 error. This typically occurs when:
IDLE_TIME setting.IDLE_TIME LimitSELECT username, profile FROM dba_users WHERE username = 'C##USERNAME';
ALTER PROFILE <profile_name> LIMIT IDLE_TIME UNLIMITED;Or set a higher value (in minutes):
ALTER PROFILE <profile_name> LIMIT IDLE_TIME 120;
Note: This change affects all users assigned to the profile. Use with caution.
CREATE PROFILE foglight_profile LIMIT IDLE_TIME UNLIMITED; ALTER USER C##USERNAME PROFILE foglight_profile;
Reduce the collection interval in the Foglight Oracle agent configuration to ensure the session remains active within the allowed idle time.