ORA-21301: not initialized in object mode

Cause : This function requires the OCI process to be initialized in object mode.

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

Specify OCI_OBJECT mode when calling OCIInitialize().

update : 18-08-2017
ORA-21301

ORA-21301 - not initialized in object mode
ORA-21301 - not initialized in object mode

  • ora-13462 : invalid blocking specification
  • ora-19029 : Cannot convert the given XMLType to the required type
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-07623 : smscre: $CRMPSC failure
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-16576 : failed to update Data Guard configuration file
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-18008 : cannot find OUTLN schema
  • ora-14307 : partition contains too many list values
  • ora-09817 : Write to audit file failed.
  • ora-27490 : cannot open disabled window "string.string"
  • ora-19734 : wrong creation SCN - control file expects converted plugged-in datafile
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-30733 : cannot specify rowid constraint on scoped ref column
  • ora-33078 : (XSAGDNGL39) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must refer to a dimension.
  • ora-01422 : exact fetch returns more than requested number of rows
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-01125 : cannot disable media recovery - file string has online backup set
  • ora-13111 : cannot add topo_geometry layer [string] to topology
  • ora-30432 : summary 'string.string' is in INVALID state
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-13290 : the specified unit is not supported
  • ora-16033 : parameter string destination cannot be the same as parameter string destination
  • ora-10651 : incorrect file number block number specified
  • ora-13159 : Oracle table string already exists
  • ora-02084 : database name is missing a component
  • 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.