ORA-13801: invalid value for SQLTUNE_CATEGORY parameter

Cause : An invalid Oracle identifier was used as the value of the parameter.

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

Specify the parameter conforming to the rules for Oracle identifiers.

update : 17-08-2017

ORA-13801 - invalid value for SQLTUNE_CATEGORY parameter
ORA-13801 - invalid value for SQLTUNE_CATEGORY parameter

  • ora-01547 : warning: RECOVER succeeded but OPEN RESETLOGS would get error below
  • ora-25179 : invalid PCTTHRESHOLD storage option value
  • ora-19300 : Error occurred in uri processingstring
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-12354 : secondary object being dropped
  • ora-38955 : Source platform string not cross platform compliant
  • ora-12652 : String truncated
  • ora-01026 : multiple buffers of size > 4000 in the bind list
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-26040 : Data block was loaded using the NOLOGGING option
  • ora-12046 : cannot use trusted constraints for refreshing remote MV
  • ora-38481 : ADT "string" is used for a dependent object.
  • ora-12056 : invalid REFRESH method
  • ora-26101 : tablespace # in file header is string rather than string for file string
  • ora-06575 : Package or function string is in an invalid state
  • ora-38773 : cannot add data file 'string' - file already part of database
  • ora-22061 : invalid format text [string]
  • ora-29517 : recursive resolution failed for a referenced class
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-21604 : property [string] is not a property of transient or value instances
  • ora-14036 : partition bound value too large for column
  • ora-14014 : maximum number of partitioning columns is 16
  • ora-01257 : cannot reuse database file string, unknown file size
  • ora-38504 : this operator not allowed with the configured attribute set
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-39601 : Hash key is required.
  • ora-29828 : invalid name for implementation type
  • ora-08429 : raw data has invalid digit in display type data
  • ora-13841 : SQL profile named string already exists for a different signature/category pair
  • 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.