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 : 01-05-2017
ORA-02396

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

  • ora-29376 : number of consumer groups string in top-plan string exceeds string
  • ora-02208 : duplicate MAXTRANS option specification
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-23492 : no new sites for extension request "string"
  • ora-01162 : block size string in file header does not match configured block sizes
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-06527 : External procedure SQLLIB error: string
  • ora-31408 : invalid value specified for begin_scn or end_scn
  • ora-23612 : unable to find tablespace "string"
  • ora-02770 : Total number of blocks is invalid
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-09800 : Process sensitivity label retrieval failed.
  • ora-07741 : slemop: $OPEN failure
  • ora-31070 : Invalid database user ID string
  • ora-02271 : table does not have such constraint
  • ora-01482 : unsupported character set
  • ora-31612 : Allocation of process descriptor failed.
  • ora-08434 : raw data has invalid trailing sign
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-22872 : OID INDEX clause not allowed on tables with primary key based object identifiers
  • ora-02426 : privilege grant failed
  • ora-12652 : String truncated
  • ora-25328 : %s argument size string is smaller than array size
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-14627 : Invalid operation was specified on a GLOBAL partitioned index
  • ora-07702 : unrecognized device type in archive text
  • ora-19662 : archived log thread string sequence string could not be verified
  • ora-24398 : connection pool already exists
  • ora-30393 : a query block in the statement did not rewrite
  • 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.