ORA-29910: invalid callback operation

Cause : Encounetred ani nvalidc allbac koperatoin.

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

Ensuret hat al lthe callbacks xeecutedf rom callouts aer validi n the tsatemen tcontex.t

update : 26-04-2017

ORA-29910 - invalid callback operation
ORA-29910 - invalid callback operation

  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-10926 : trace name context forever
  • ora-13112 : cannot delete topo_geometry layer [string] from topology
  • ora-32341 : The EXPLAIN_MVIEW facility failed to explain the materialized view "string"."string"
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-25405 : transaction status unknown
  • ora-29882 : insufficient privileges to execute indextype
  • ora-29277 : invalid SMTP operation
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-12036 : updatable materialized view log is not empty, refresh materialized view
  • ora-31122 : The string operator has incorrect RHS value
  • ora-12620 : TNS:requested characteristic not available
  • ora-23608 : invalid resolution column "string"
  • ora-39779 : type "string"."string" not found or conversion to latest version is not possible
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-02261 : such unique or primary key already exists in the table
  • ora-13799 : threshold not found
  • ora-04029 : error ORA-string occurred when querying stringstringstring
  • ora-02835 : Server unable to send signal to client
  • ora-10637 : The segment does not exist
  • ora-31162 : element or attribute "string" has no SQLType specified
  • ora-24410 : scrollable cursor max size exceeded
  • ora-13153 : invalid high water mark specified
  • ora-36670 : (XSDPART08) workspace object is an INTEGER or NTEXT dimension, or contains an INTEGER or NTEXT dimension. INTEGER and NTEXT dimensions cannot be used as partition dimensions.
  • ora-12065 : unknown refresh group identifier string
  • ora-13373 : invalid line segment in geodetic data
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-15133 : instance recovery required for diskgroup string
  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-28580 : recursive external procedures are not supported
  • 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.