ORA-02396: exceeded maximum idle time, please connect again

Cause : as stated

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

none

update : 23-01-2017
ORA-02396

ORA-02396 - exceeded maximum idle time, please connect again
ORA-02396 - exceeded maximum idle time, please connect again

  • ora-06503 : PL/SQL: Function returned without value
  • ora-38771 : unnamed datafile(s) added to control file by flashback recovery
  • ora-14290 : PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-00160 : global transaction length string is greater than maximum (string)
  • ora-28025 : missing or null external name
  • ora-19380 : invalid plan filter
  • ora-36635 : (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.
  • ora-29760 : instance_number parameter not specified
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-14062 : one or more of table's partitions reside in a read-only tablespace
  • ora-24418 : Cannot open further sessions.
  • ora-02759 : Not enough request descriptors available
  • ora-39772 : column array reset disallowed after OCI_CONTINUE or OCI_NEED_DATA
  • ora-16050 : destination exceeded specified quota size
  • ora-07577 : no such user in authorization file
  • ora-19124 : fn:one-or-more() called with a sequence containing no items
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-00081 : address range [string, string) is not readable
  • ora-27463 : invalid program type string
  • ora-13153 : invalid high water mark specified
  • ora-37013 : (XSACQUIRE_DEADLOCK) Cannot wait to acquire object workspace object since doing so would cause a deadlock.
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-19104 : invalid XQueryX: missing attribute string
  • ora-30182 : invalid precision specifier
  • ora-01609 : log string is the current log for thread string - cannot drop members
  • ora-12058 : materialized view cannot use prebuilt table
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-01070 : Using an old version of Oracle for the server
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.