ORA-13802: failed to purge SQL Tuning Base entry from sql$

Cause : An error occured while try to delete a SQL Tuning Base object.

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

Look at the underlying error(s) on the error stack.

update : 21-07-2017

ORA-13802 - failed to purge SQL Tuning Base entry from sql$
ORA-13802 - failed to purge SQL Tuning Base entry from sql$

  • ora-25200 : invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
  • ora-16552 : an error occurred when generating the CLIENT OPERATION table
  • ora-06528 : Error executing PL/SQL profiler
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-22346 : Type has cyclical dependency. Should use CASCADE option
  • ora-27198 : skgfpvl: sbtpcvalidate returned error
  • ora-25966 : join index cannot be based on an index organized table
  • ora-12488 : maximum label does not dominate minimum label
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-06571 : Function string does not guarantee not to update database
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-30484 : missing window specification for this function
  • ora-16115 : %s\% of LogMiner dictionary loading is done
  • ora-01164 : MAXLOGFILES may not exceed string
  • ora-26062 : Can not continue from previous errors.
  • ora-22326 : cannot change a type to FINAL if it has subtypes
  • ora-01638 : parameter string does not allow ORACLE version string to mount cluster database
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-00469 : CKPT process terminated with error
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-32314 : REFRESH FAST of "string"."string" unsupported after deletes/updates
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-07844 : sllfop: LIB$GET_VM failure
  • ora-16177 : media recovery is not required
  • ora-12422 : max policies exceeded
  • ora-29514 : class name contains illegal character
  • ora-36316 : (PHYS02) Relation workspace object must be a single-dimensional relation that relates one INTEGER dimension to another.
  • ora-22132 : hexadecimal string does not correspond to a valid REF
  • ora-39042 : invalid transform name string
  • ora-22167 : given trim size [string] must be less than or equal to [string]
  • 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.