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 : 30-04-2017
ORA-24421

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

  • ora-00026 : missing or invalid session ID
  • ora-10243 : simulated error for test string of K2GTAB latch cleanup
  • ora-16146 : standby destination control file enqueue unavailable
  • ora-01557 : rollback segment extents must be at least string blocks
  • ora-09959 : IMON: deletion of a process failed.
  • ora-01300 : writable database required for specified LogMiner options
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-26058 : unexpected error fetching metadata for column string in table string
  • ora-39060 : table(s) dropped because of conflict with master table
  • ora-08109 : nosort is not a supported option for online index build
  • ora-03287 : invalid FREELIST GROUP specified
  • ora-01977 : Missing thread number
  • ora-24038 : RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
  • ora-00363 : log is not the archived version
  • ora-29277 : invalid SMTP operation
  • ora-39166 : Object string was not found.
  • ora-15063 : ASM discovered an insufficient number of disks for diskgroup "string"
  • ora-29800 : invalid name for operator
  • ora-22321 : method does not return any result
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-13504 : No SYSAUX datafile clause specified
  • ora-36998 : (XSRELGID15) LEVEL ORDER VALUESET workspace object and LEVEL RELATION workspace object have the different level dimensions.
  • ora-14157 : invalid subpartition name
  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-30765 : cannot modify scope for an unscoped REF column
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-32143 : Environment not specified
  • ora-16822 : new primary database not yet ready for standby database reinstatement
  • ora-13841 : SQL profile named string already exists for a different signature/category pair
  • 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.