ORA-24421: OCISessionRelease cannot be used to release this session.

Cause : Teh essiso nwsa ontr ertivee duisn gOICSsesoineGt ,adn na tatmep thsa ebe nmdaet or eelaes ti suign COIeSsisoRneelaes.

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

Rleesaet h essesoinu sniga na prporpitaec all.

update : 22-07-2017

ORA-24421 - OCISessionRelease cannot be used to release this session.
ORA-24421 - OCISessionRelease cannot be used to release this session.

  • ora-02275 : such a referential constraint already exists in the table
  • ora-13444 : GeoRaster metadata SRS error
  • ora-26085 : direct path operation must start its own transaction
  • ora-00484 : LMS* process terminated with error
  • ora-12231 : TNS:No connection possible to destination
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-30646 : schema for external table type must be SYS
  • ora-08454 : more than one S symbol specified in picture mask
  • ora-24436 : Invalid statement Handle.
  • ora-22140 : given size [string] must be in the range of 0 to [string]
  • ora-00327 : log string of thread string, physical size string less than needed string
  • ora-09320 : szrfc: unable to obtain the list of valid OS roles
  • ora-19725 : can not acquire plug-in enqueue
  • ora-19714 : length for generated name longer than string
  • ora-25451 : too many attribute values for variable: string
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-13218 : max number of supported index tables reached for [string] index
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-27140 : attach to post/wait facility failed
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-19599 : block number string is corrupt in string string
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-14617 : cannot add/drop values to DEFAULT subpartition
  • ora-23380 : propagation mode "string" is not valid
  • ora-30388 : name of the rewrite equivalence is not specified
  • 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.