ORA-13764: Value "string" is illegal as a result percentage.

Cause : The user attempted to select data from a SQL Tuning Set using an invalid result percentage. The result percentage must be between 0 and 1.

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

Correct the result percentage value and retry the operation.

update : 23-08-2017

ORA-13764 - Value "string" is illegal as a result percentage.
ORA-13764 - Value "string" is illegal as a result percentage.

  • ora-01688 : unable to extend table string.string partition string by string in tablespace string
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-38427 : attribute string does not exist
  • ora-09950 : Unable to get server operating system privileges
  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-32113 : Null object passed
  • ora-16737 : the redo transport service for standby database "string" has an error
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-12467 : minimum label can contain a level only
  • ora-27468 : "string.string" is locked by another process
  • ora-31697 : aborting operation at process order number string
  • ora-02782 : Both read and write functions were not specified
  • ora-02705 : osnpol: polling of communication channel failed
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-31065 : Cannot modify read-only property [string]
  • ora-00260 : cannot find online log sequence string for thread string
  • ora-02778 : Name given for the log directory is invalid
  • ora-14291 : cannot EXCHANGE a composite partition with a non-partitioned table
  • ora-24399 : invalid number of connections specified
  • ora-24906 : invalid recepient attribute passed into OCI call
  • ora-29841 : invalid option for ALTER INDEXTYPE
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-35810 : (XSINPUTERR) The command has requested more input than was supplied in the command string.
  • ora-33305 : (DBVALID06) Note: Record number was allocated but not used. This can result in wasted space. (PS number)
  • ora-07747 : slemrd: $READ failure
  • ora-24763 : transaction operation cannot be completed now
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-33000 : (AGOPEN00) AGGMAP workspace object cannot be accessed because it was compiled by a more recent version of string.
  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • 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.