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 : 23-04-2017
ORA-13802

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

  • ora-39162 : Transportable tablespace job require privileges
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-28656 : incomplete attribute specification
  • ora-30344 : number of child cols different from number of parent level cols
  • ora-02826 : Illegal block size
  • ora-09201 : sfcopy: error copying file
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-12500 : TNS:listener failed to start a dedicated server process
  • ora-12044 : invalid CREATE MATERIALIZED VIEW LOG option
  • ora-22913 : must specify table name for nested table column or attribute
  • ora-29507 : query derived from USING clause found zero or many rows
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-01989 : role 'string' not authorized by operating system
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-34348 : (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
  • ora-13129 : HHCODE column string not found
  • ora-15092 : I/O request size string is not a multiple of logical block size string
  • ora-01489 : result of string concatenation is too long
  • ora-34722 : (NLSCHARSET05) CAUTION: Character data loss in character set conversion from string to string
  • ora-12535 : TNS:operation timed out
  • ora-06555 : this name is currently reserved for use by user SYS
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-19505 : failed to identify file "string"
  • ora-16658 : unobserved Fast-Start Failover configuration
  • ora-14287 : cannot REBUILD a partition of a Composite Range partitioned index
  • ora-32408 : materialized view log on "string"."string" already has new values
  • 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.