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 : 28-05-2017

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

  • ora-31403 : change table string already contains a column string
  • ora-00072 : process "string" is not active
  • ora-01048 : Couldn't find the specified procedure in the given context
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-08187 : snapshot expression not allowed here
  • ora-26052 : Unsupported type number for SQL expression on column string.
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-14259 : table is not partitioned by Hash method
  • ora-01576 : The instance string is not enabled
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-38491 : could not evaluate subexpression for rowid "string"
  • ora-25132 : UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
  • ora-16131 : An error occurred during a Terminal Recovery of the standby.
  • ora-19124 : fn:one-or-more() called with a sequence containing no items
  • ora-10618 : Operation not allowed on this segment
  • ora-07635 : smsdbp: $SETPRT failure
  • ora-02098 : error parsing index-table reference (:I)
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-12408 : unsupported operation: string
  • ora-04941 : required operating system patch needs to be applied
  • ora-32838 : exceeded maximum number of properties
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-23436 : missing template authorization for user
  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-13421 : null or invalid cell value
  • ora-24191 : the property name string has existed
  • ora-23331 : column group string does not exist
  • ora-26013 : List allocated may not be big enough
  • ora-38793 : cannot FLASHBACK the database to a future SCN/time
  • ora-12637 : Packet receive failed
  • 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.