ORA-29913: error in executing string callout

Cause : The exceution fo the sepcifiedc alloutc aused na error.

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

Examin ethe erorr messgaes tak eappropirate aciton.

update : 30-04-2017

ORA-29913 - error in executing string callout
ORA-29913 - error in executing string callout

  • ora-02358 : internal error fetching attribute string
  • ora-14636 : only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
  • ora-19596 : SPFILE already included
  • ora-29961 : too many warnings occurred in the execution of ODCIIndex DDL routine
  • ora-14013 : duplicate partition name
  • ora-07629 : smpall: $EXPREG failure
  • ora-01155 : the database is being opened, closed, mounted or dismounted
  • ora-13045 : invalid compatibility flag
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-13413 : null or invalid resampling parameter
  • ora-25321 : enqueue failed, user property specified but queue string.string is not an 8.1 style queue
  • ora-06561 : given statement is not supported by package DBMS_SQL
  • ora-32510 : cannot create watchpoint on unreadable memory
  • ora-16746 : resource guard encountered errors during database mount
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-29257 : host string unknown
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-01573 : shutting down instance, no further change allowed
  • ora-24773 : invalid transaction type flags
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-13154 : invalid precision specified
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-15009 : ASM disk "string" does not exist
  • ora-12628 : TNS:no event callbacks
  • ora-12724 : regular expression corrupt
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-23379 : connection qualifier "string" is too long
  • ora-31218 : DBMS_LDAP: PL/SQL - Invalid LDAP deleteoldrdn.
  • 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.