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 : 28-04-2017
ORA-21301

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

  • ora-28008 : invalid old password
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-17622 : failed to deregister the memory with Oracle Disk Manager library
  • ora-23355 : object string.string does not exist or is invalid at master site
  • ora-31645 : unable to read from dump file "string"
  • ora-36688 : (NTEXTCNV00) Error during conversion from TEXT to NTEXT.
  • ora-02402 : PLAN_TABLE not found
  • ora-07501 : scgtoa: $deq unexpected return
  • ora-13029 : Invalid SRID in the SDO_GEOMETRY object
  • ora-31516 : CDC change set string already exists
  • ora-16151 : Managed Standby Recovery not available
  • ora-02707 : osnacx: cannot allocate context area
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-06042 : NETDNT: message receive failure
  • ora-22951 : NULL returned by ORDER method
  • ora-19595 : archivelog string already included in backup conversation
  • ora-07270 : spalck: setitimer error, unable to set interval timer.
  • ora-16640 : CRS warns that multiple instances may still be running
  • ora-10946 : trace name context forever
  • ora-12839 : cannot modify an object in parallel after modifying it
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-00238 : operation would reuse a filename that is part of the database
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-10372 : parallel query server kill event proc
  • ora-09341 : scumnt: unable to mount database
  • ora-09821 : Numeric label is not valid
  • ora-01182 : cannot create database file string - file is in use or recovery
  • 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.