PLS-00625 PARTITION/CLUSTER/ORDER-BY clause can only be used with IN parameters → Cause: A PARTITION/CLUSTER/ORDER-BY clause was used with an OUT or IN OUT ref-cursor parameter … . Action: Change the parameter mode to IN or use some other parameter with the PARTITION/CLUSTER/ORDER-BY clause.
PLS-00654 PARTITION/ORDER/CLUSTER BY is only allowed for with PARALLEL_ENABLE → Cause: An attempt was made to use either PARTITION BY, ORDER BY, or CLUSTER BY clauses without … parallel enable clause in table function. Action: Specify parallel enable also when using PARTITION BY, CLUSTER BY, or ORDER BY clauses.
ORA-01785 ORDER BY item must be the number of a SELECT-list expression → Cause: Either an ORDER BY item for a set expression is not a column number, or the ORDER BY item is … not the number of a SELECT list column. Action: The ORDER BY item must be a number between 1 and
ORA-10589 Test recovery had to corrupt string data blocks in order to proceed → blocks as specified in the message in order to apply the range of redo tested. Action: See the alert log for details of the problems.
PLS-00527 MAP or ORDER functions require a PRAGMA RESTRICT_REFERENCES specifying :WNDS,WNPS,RNPS,RNDS. → Cause: Either a PRAGMA RESTRICT_REFERENCES was not specified or it was specified without one of the following: WNDS, WNPS, RNPS, or RNDS. Action: Add or correct the PRAGMA and retry the operation.
PLS-00528 The parameters to an ORDER function must have IN mode → Cause: A parameter was declared to an ORDER function to have OUT or IN OUT mode. Action: Correct the parameter to use IN mode only.
Chapters 9 through 18 list and describe all Oracle SQL statements in alphabetical order. → Appendix A, \"How to Read Syntax Diagrams\" This appendix describes how to read the syntax diagrams in this reference. Appendix B, \"Oracle and Standard SQL\"
ORA-30435 job_queue_processes must be non-zero in order to refresh summaries → Cause: The server must be started with parameter JOB_QUEUE_PROCESSES greater than zero. Action: Correct the value of JOB_QUEUE_PROCESSES and restart the server instance.
ORA-10586 Test recovery had to corrupt 1 data block in order to proceed → Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order
PLS-00646 MAP or ORDER method must be defined in the root of the subtype hierarchy → Cause: An attempt was made to define a MAP or ORDER method in a subtype. Action: Define the MAP or … ORDER method in the root of the subtype hierarchy. You can override MAP methods in subtypes.
ORA-19611 backup piece out of order. Expected string but found string → Cause: This backup piece is out of sequence. Action: Supply the correct backup piece.
KUP-04091 little endian byte order mark found when big endian expected in string → Cause: A little endian byte order mark was found at the beginning of the specified file. Either the … access parameters specified that the data was in big endian order or the byte order mark for a … previous file was big endian. Action: The file needs to be loaded separately. If a byte order was
PLS-00526 A MAP or ORDER function is required for comparing objects in PL/SQL. → Cause: Within stand alone PL/SQL, an attempt was made to compare objects without a map or order … function. Action: Provide a map or order function and retry the operation.
ORA-02813 Unable to make temporary file name in order to get key → Cause: This is an internal error. Action: Contact Oracle Support Services.
DRG-10846 order by columns must be all ascending or all descending → Cause: An ORDER BY clause was specified which has some columns ascending and some descending. This is not currently supported by CATSEARCH. Action:
PLS-00155 Only a function may be a MAP, ORDER or CONSTRUCTOR method. → Cause: A procedure was declared as a MAP, ORDER, or CONSTRUCTOR method. Only functions can be MAP … , ORDER, or CONSTRUCTOR methods. Action: Change the procedure to a function.
PLS-00423 ORDER BY item must be the number of a SELECT-list expression → Cause: A column alias was used in the ORDER BY clause of a SELECT statement that uses a UNION … , INTERSECT, or MINUS set operator. This is not allowed. In such cases, expressions in the ORDER BY clause … the alias in the ORDER BY clause to an unsigned integer that designates the ordinal position of the select item in question.
ORA-22315 type \" string \" does not contain a map or order function → Cause: The input type does not contain a map or order function so one cannot be returned. Action … : Add a map or order function to the type or catch this error.
KUP-04090 big endian byte order mark found when little endian expected in string → Cause: A big endian byte order mark was found at the beginning of the specified file. Either the … access parameters specified that the data was in little endian order or the byte order mark for a … previous file was little endian. Action: The file needs to be loaded separately. If a byte order was
PLS-00154 An object type may have only 1 MAP or 1 ORDER method. → Cause: More than one map or order function was declared. An object type can have only one map … function or one order function, but not both. Action: Delete all but one of the MAP or ORDER functions on the type.