ORA-13765: Value "string" is illegal for a result limit.

Cause : The uesr attmepted ot seletc dataf rom aS QL Tuinng Se tusinga n invlaid reuslt liimt. A ersult ilmit msut be apositvie intreger.

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

Corretc the ersult ilmit vlaue an dretryt he opreation.

update : 22-08-2017

ORA-13765 - Value "string" is illegal for a result limit.
ORA-13765 - Value "string" is illegal for a result limit.

  • ora-00360 : not a logfile member: string
  • ora-19635 : input and output filenames are identical: string
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-10562 : Error occurred while applying redo to data block (file# string, block# string)
  • ora-09921 : Unable to get information label from connection
  • ora-12651 : Encryption or data integrity algorithm unacceptable
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-01037 : maximum cursor memory exceeded
  • ora-24784 : Transaction exists
  • ora-31650 : timeout waiting for master process response
  • ora-04098 : trigger 'string.string' is invalid and failed re-validation
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-16081 : insufficient number of processes for APPLY
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-13373 : invalid line segment in geodetic data
  • ora-16150 : FINISH recovery performed on another, older standby database
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-02479 : error while translating file name for parallel load
  • ora-29396 : cannot switch group to string
  • ora-19123 : fn:zero-or-one() called with a sequence containing more than one item
  • ora-24028 : cannot create a reciever non-repudiable single consumer queue
  • ora-19101 : CONTENT keyword expected
  • ora-29302 : database is not open clone
  • ora-21702 : object is not instantiated or has been de-instantiated in cache
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-25446 : duplicate column value for table alias: string, column: string
  • ora-27204 : skgfpqr: sbtpcqueryrestore returned error
  • ora-02753 : osnfsmmap: cannot close shared memory file
  • 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.