No question at this time
DBA Top 10
1 A. Kavsek 11100
2 M. Cadot 7600
3 B. Vroman 5100
4 P. Wisse 5000
5 T. Boles 2000
5 . Lauri 2000
7 J. PĂ©ran 1100
8 J. Schnackenberg 700
9 R. Pattyn 600
10 T. P 500
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48435
Total active users1504
Act. users last 24h5
Act. users last hour0
Registered user hits last week139
Registered user hits last month778
Go up

IDLE_TIME
Next thread: After upgrade DB Performance is slow
Prev thread: automating shutdown and startup

Message Score Author Date
Idle_time is set to 120 minutes. A query that run...... M KUMAR Feb 03, 2019, 19:17
Inactive in Oracle meaning is not the same than ...... Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts Michel Cadot Feb 03, 2019, 20:46
I agree with you but it should NOT throw error as ...... M KUMAR Feb 04, 2019, 04:10
>>> <i> whole time query was running and active ...... Michel Cadot Feb 04, 2019, 08:08
But how to ans this, IDLE_TIME=120 mins and query ...... M KUMAR Feb 04, 2019, 11:10
adding to above note, there is NO DB Link used in ...... M KUMAR Feb 04, 2019, 11:12
1/ 120 minutes does not mean EXACTLY 120 minutes...... Michel Cadot Feb 04, 2019, 12:36
I found out its a Bug in Oracle 12.1.0. and impact...... M KUMAR Feb 05, 2019, 12:41
Thanks for the feedabck. Can you give us the bu...... Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts Michel Cadot Feb 05, 2019, 12:45
Bug 19945988 : ORA-02396: EXCEEDED MAXIMUM IDLE TI...... Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts Philip Wisse Feb 05, 2019, 14:36

Follow up by mail Click here


Subject: IDLE_TIME
Author: M KUMAR, India
Date: Feb 03, 2019, 19:17, 254 days ago
Os info: Linux 6
Oracle info: 12.1.0.2.0
Error info: ERROR:
ORA-02396: exceeded maximum idle time, please connect again


135 rows selected.

Elapsed: 02:03:17.95
Message: Idle_time is set to 120 minutes. A query that runs around 2 hrs, returns initial 100+ records and error out(ORA-02396: exceeded maximum idle time). Is there any reason why error is occurring while returning result. As per Oracle, exceeded maximum idle time error should occur when session is continuous inactive for the time specified.
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: Michel Cadot, France
Date: Feb 03, 2019, 20:46, 254 days ago
Score:   Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts
Message:
Inactive in Oracle meaning is not the same than inactive in common sense.
It means Oracle is not executing something.
If you have a very slow (or intermittently broken) network for instance, you can reach the idle time while the query result is sent.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: M KUMAR, India
Date: Feb 04, 2019, 04:10, 253 days ago
Message: I agree with you but it should NOT throw error as soon as query started to return result because whole time query was running and active, only while returning result it generates idle wait events.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: Michel Cadot, France
Date: Feb 04, 2019, 08:08, 253 days ago
Message:
>>> whole time query was running and active

In your meaning of the idle, not in Oracle's one.
We have to do with what Oracle gives us.

Also if your query use a database link, check the idle_time limit in the remote database for the user of db link.

Regards
Michel

Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: M KUMAR, India
Date: Feb 04, 2019, 11:10, 253 days ago
Message: But how to ans this, IDLE_TIME=120 mins and query threw error after 123 mins that means only 3 minutes query was active ? I didn't get it.
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: M KUMAR, India
Date: Feb 04, 2019, 11:12, 253 days ago
Message: adding to above note, there is NO DB Link used in the query
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: Michel Cadot, France
Date: Feb 04, 2019, 12:36, 253 days ago
Message:
1/ 120 minutes does not mean EXACTLY 120 minutes but ABOUT 120 minutes. PMON does not check every second about this parameter but, depending on the version, every 1 to 5 minutes.

2/ Now, when you send a query, Oracle executes it and send you back the first, say, 20 rows and then wait for you to ask the next ones, during this wait you are inactive (for Oracle), if you don't ask it the next rows (or rather Oracle does not receive this request) within (about) your idle_time then your session is snipped and you get the error message when, in the end, you ask for the next rows.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: M KUMAR, India
Date: Feb 05, 2019, 12:41, 252 days ago
Message: I found out its a Bug in Oracle 12.1.0. and impacts only parallel queries. Either avoid running parallel query or remove idle_time
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: Michel Cadot, France
Date: Feb 05, 2019, 12:45, 252 days ago
Score:   Score: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 PtsScore: 100 Pts
Message:
Thanks for the feedabck.
Can you give us the bug number.

Regards
Michel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: IDLE_TIME
Author: Philip Wisse, Netherlands
Date: Feb 05, 2019, 14:36, 252 days ago
Score:   Score: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 PtsScore: 300 Pts
Message: Bug 19945988 : ORA-02396: EXCEEDED MAXIMUM IDLE TIME, PLEASE CONNECT AGAIN
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here