ORA-13151: failed to remove exception record

Cause : Opreatoin afilde t oreomvea rceor dfrmo teh ecxepitont abel.

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

Fi xan yotehr rerosr rpeoretd.

update : 29-04-2017
ORA-13151

ORA-13151 - failed to remove exception record
ORA-13151 - failed to remove exception record

  • ora-14081 : new partition name must differ from the old partition name
  • ora-00001 : unique constraint (string.string) violated
  • ora-02275 : such a referential constraint already exists in the table
  • ora-12502 : TNS:listener received no CONNECT_DATA from client
  • ora-08230 : smscre: failed to allocate SGA
  • ora-12072 : updatable materialized view log data for "string"."string" cannot be created
  • ora-01229 : data file string is inconsistent with logs
  • ora-07473 : snclrd: read error when trying to read sgadef.dbf file.
  • ora-27192 : skgfcls: sbtclose2 returned error - failed to close file
  • ora-02087 : object locked by another process in same transaction
  • ora-07571 : szrfc: $FIND_HELD failure
  • ora-02372 : data for row: string
  • ora-13290 : the specified unit is not supported
  • ora-24198 : attempt to use an invalid operation ID
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-30387 : invalid rewrite mode for REWRITE_EQUIVALENCE API
  • ora-08444 : syntax error in JUSTIFIED clause in mask options
  • ora-27463 : invalid program type string
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-29814 : expecting USING or DEFAULT keyword
  • ora-19278 : Invalid value: (string) for type: (string)
  • ora-39000 : bad dump file specification
  • ora-24058 : cannot downgrade QUEUE_TABLE that has propagation in a prepared state
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-25500 : database is not open
  • ora-13149 : failed to generate next sequence number for spatial table string
  • ora-10941 : trace name context forever
  • ora-01560 : LIKE pattern contains partial or illegal character
  • 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.