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-08-2017

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

  • ora-02425 : create table failed
  • ora-00100 : no data found
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-13009 : the specified date string is invalid
  • ora-14459 : missing GLOBAL keyword
  • ora-10270 : Debug shared cursors
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-07582 : spstp: ORA_SID has illegal value
  • ora-06315 : IPA: Invalid connect string
  • ora-24789 : start not allowed in recursive call
  • ora-36290 : (EIFMAKEF14) You cannot export object workspace object, because EIFVERSION is set to number. That version does not support dimensions of type NUMBER.
  • ora-00983 : cannot audit or noaudit SYS user actions
  • ora-24309 : already connected to a server
  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-31494 : could not activate a LogMiner session
  • ora-02830 : Segment could not be split - no free segments available
  • ora-39776 : fatal Direct Path API error loading table string
  • ora-00294 : invalid archivelog format specifier 'string'
  • ora-30045 : No undo tablespace name specified
  • ora-06122 : NETTCP: setup failure
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-27052 : unable to flush file data
  • ora-14623 : Value string does not exist in subpartition string
  • ora-07495 : spwat: lm_wait failed.
  • ora-27214 : skgfrsfe: file search failed
  • ora-31483 : cannot have spaces in the parameter string
  • ora-16198 : Timeout incurred on internal channel during remote archival
  • 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.