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 : 27-06-2017

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

  • ora-14009 : partition bound may not be specified for a LOCAL index partition
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-16072 : a minimum of one standby database destination is required
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-12663 : Services required by client not available on the server
  • ora-10924 : import storage parse error ignore event
  • ora-12089 : cannot online redefine table "string"."string" with no primary key
  • ora-01489 : result of string concatenation is too long
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-31225 : DBMS_LDAP: invalid BER_ELEMENT
  • ora-25502 : concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
  • ora-27159 : failure setting process scheduling priority
  • ora-32051 : mapping service not available
  • ora-36646 : (XSDUNION08) Only concat dimensions can be redefined as UNIQUE. workspace object is not a concat dimension.
  • ora-27211 : Failed to load Media Management Library
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • ora-01743 : only pure functions can be indexed
  • ora-00128 : this command requires a dispatcher name
  • ora-06135 : NETTCP: connection rejected; server is stopping
  • ora-02230 : invalid ALTER CLUSTER option
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-27144 : attempt to kill process failed
  • ora-27017 : skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
  • ora-23447 : missing user parameter value
  • ora-30354 : Query rewrite not allowed on SYS relations
  • ora-19588 : %s recid string stamp string is no longer valid
  • ora-07432 : unable to perform nested sleep
  • 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.