Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

ORA-02396: Exceeded Maximum Idle Time, Please Connect Again

Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
Breadcrumb Abstract Shape
  • User AvatarKiran Dalvi
  • 14 Dec, 2023
  • 0 Comments
  • 2 Mins Read

ORA-02396: Exceeded Maximum Idle Time, Please Connect Again

PROBLEM: The application is unable to connect to the database after it was idle for a long time.

First, you need to identify, with which user, the application is connecting to the database. Let’s say the user is TESTUSER.

Now find the value of the IDLE_TIME resource limit set in the profile of that user(TESTUSER)

1
2
3
4
5
6
select a.username,b.profile,b.RESOURCE_NAME,b.LIMIT from dba_users a, dba_profiles b where
b.resource_name='IDLE_TIME' and a.profile=b.profile and a.username='&USERNAME';
 
USERNAME PROFILE RESOURCE_NAME LIMIT
------------- -------------- -------------------------------- --------------
TESTUSER DEFAULT IDLE_TIME 125500

Here the idle_time is set to 125500 minutes. So if the session is idle for this much time, then it will be disconnected with the error,

Solution : To fix this, alter the profile with the IDLE_TIME set to a higher value or UNLIMITED.

1
2
3
4
5
6
7
8
ALTER PROFILE DEFAULT LIMIT IDLE_TIME UNLIMITED;
 
select a.username,b.profile,b.RESOURCE_NAME,b.LIMIT from dba_users a, dba_profiles b where
b.resource_name='IDLE_TIME' and a.profile=b.profile and a.username='&USERNAME';
 
USERNAME PROFILE RESOURCE_NAME LIMIT
------------- -------------- -------------------------------- --------------
TESTUSER DEFAULT IDLE_TIME UNLIMITED