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 : 26-03-2017
ORA-02396

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

  • ora-19694 : some changed blocks were not found in the change tracking file
  • ora-19762 : invalid file type string
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-23382 : materialized view repgroup "string"."string" is not registered at site string
  • ora-32139 : Cannot write to the stream
  • ora-32151 : Environment not specified
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-39099 : cannot create index for "string" on master table string
  • ora-02405 : invalid sql plan object provided
  • ora-23441 : object does not exist for refresh group template
  • ora-00227 : corrupt block detected in control file: (block string, # blocks string)
  • ora-19238 : XP0018 - focus not defined
  • ora-14188 : sub-partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-31436 : duplicate change source string
  • ora-14051 : invalid ALTER MATERIALIZED VIEW option
  • ora-16515 : no rcv channel
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-38312 : original name is used by an existing object
  • ora-23469 : %s is different between templates
  • ora-19038 : Invalid opertions on query context
  • ora-37102 : (XSVPART02) Invalid partition name string.
  • ora-36642 : (XSDUNION06) Concat dimension list contains duplicate leaf dimension workspace object.
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-23293 : Cannot rename a column which is part of a join index
  • ora-14079 : illegal option for a partition marked Index Unusable
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-24781 : branches don't belong to the same global transaction
  • ora-29513 : referenced class name too long
  • ora-38791 : flashback did not start because file string was not in a valid incarnation
  • 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.