ORA-21522: attempted to use an invalid connection in OCI (object mode only)

Cause : User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to dereference a REF obtained from a connection which has been terminated.

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

Ensure that the connection exists and is still valid.

update : 26-09-2017

ORA-21522 - attempted to use an invalid connection in OCI (object mode only)
ORA-21522 - attempted to use an invalid connection in OCI (object mode only)

  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-09959 : IMON: deletion of a process failed.
  • ora-02261 : such unique or primary key already exists in the table
  • ora-26040 : Data block was loaded using the NOLOGGING option
  • ora-39212 : installation error: XSL stylesheets not loaded correctly
  • ora-10944 : trace name context forever
  • ora-00453 : backgroud process 'string' is dead
  • ora-28528 : Heterogeneous Services datatype conversion error
  • ora-10281 : maximum time to wait for process creation
  • ora-13142 : invalid PROXIMITY window definition
  • ora-19932 : control file is not clone or standby
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-23347 : datatype string for column string table string not supported
  • ora-39703 : server version and script version do not match
  • ora-01864 : the date is out of range for the current calendar
  • ora-28591 : agent control utility: unable to access parameter file
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-10664 : Table has bitmap join indexes
  • ora-28661 : Object already has COMPRESS clause specified
  • ora-14252 : invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-07743 : slemop: incorrect error file attributes
  • ora-28666 : option not allowed for an index on UROWID column(s)
  • ora-12448 : policy string not applied to schema string
  • ora-27060 : could not set close-on-exec bit on file
  • ora-03281 : invalid ALLOCATE EXTENT option
  • ora-02061 : lock table specified list of distributed tables
  • ora-06027 : NETASY: channel close failure
  • 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.