I have the IDLE_TIME limit set to 480 in one of our databases (for the
Default profile). The resource_limit parameter is set to true.
According to my reading of the docs, this means after 480 minutes (8
hours) your session will be Sniped if your session was idle for that
time. To the best of my knowledge, this is how IDLE_TIME and
RESOURCE_LIMIT have been set for months. Today, "out of the blue ",
users start getting ORA-02396 (See ORA-02396.ora-code.com) errors. Some preliminary testing seemed
to indicated that the IDLE_TIME was behaving like 8 minutes, not 8
hours. Our test database is configured the same way, but does not
exhibit this odd behavior.
The system time looks normal (at the OS and database level). There are
no alert log errors or trace files. V$TIMER doesn 't appear to have
recently reset to 0.
Any thoughts on this one?
Thank you,
Jay Hostetter
Oracle DBA
D&E Communications
Ephrata, PA USA
**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the use of the individual or entity to which they are addressed and may contain information that is privileged, proprietary and confidential. If you are not the intended recipient, you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this communication in error, please notify the sender and delete this e-mail message. The contents do not represent the opinion of D&E except to the extent that it relates to their official business.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
