IDLE_TIME parameter not working as expected. It still disconnects the session even with activity.
The DBA recently added IDLE_TIME = 30 to our profile. It is expected that it would result in "ORA-02396: exceeded maximum idle time, please connect again" after 30 minutes of inactivity, but users are reporting that they are actively moving from table to table looking at data when they get the error message.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.