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

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

  • ora-14013 : duplicate partition name
  • ora-32832 : failure string trying to acquire administration lock
  • ora-19602 : cannot backup or copy active file in NOARCHIVELOG mode
  • ora-07605 : szprv: $ASCTOID failure
  • ora-37176 : argument string is not valid for the sparsity advisor
  • ora-01101 : database being created currently mounted by some other instance
  • ora-22902 : CURSOR expression not allowed
  • ora-15129 : entry 'string' does not refer to a valid directory
  • ora-38305 : object not in RECYCLE BIN
  • ora-27125 : unable to create shared memory segment
  • ora-04080 : trigger 'string' does not exist
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-26522 : rpc execution error
  • ora-16765 : Redo Apply is unexpectedly online
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-12659 : Error received from other process
  • ora-01123 : cannot start online backup; media recovery not enabled
  • ora-25279 : dequeue as select not supported before 8.2
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-02855 : Number of requests is less than the number of slaves
  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • ora-30031 : the suspended (resumable) statement has been aborted
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-00267 : name of archived log file not needed
  • ora-32134 : Cannot assign LOBs
  • ora-12838 : cannot read/modify an object after modifying it in parallel
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-10946 : trace name context forever
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • 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.