How do I narrow my search results?
After you submit your search query:
- On the Refine Search results page, select one or more categories of products or services from the left sidebar.
- Then for a category with search results, click Select to choose your product and release filters, and then click OK.
For search queries that contain multiple words, surround the query with quotes, and then resubmit your query. Example: "database cloud service"
How do I find the documentation for my product or service?
From the home page, click the technology categories for your products or services. If you do not know which category to pick, try the following features:
- Click the Find a product tab and search for your product or service.
- Click Browse All Products & Services at the bottom of the home page to view an alphabetical listing of products and services.
- Apple Safari: Version 6
- Google Chrome: Version 29 and later
- Mozilla Firefox: Version 24 and later
- Microsoft Internet Explorer: Version 9 and later
ORA-30485 missing ORDER BY expression in the window specification → Cause: Either the ORDER BY expression is mandatory for this function, or there is an aggregation group without any ORDER by expression.
PLS-00650 invalid type for PARTITION/CLUSTER/ORDER BY clause → Cause: An attempt was made to use an invalid type for either PARTITION BY, ORDER BY, or CLUSTER BY clauses. Action: Use legal, allowed types.
ORA-02282 duplicate or conflicting ORDER/NOORDER specifications → Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified. Action: Remove one of the conflicting specifications and try again.
QSM-02044 ORDER BY clause in materialized view → Cause: The capability in question is not supported when the materialized view includes an ORDER BY clause. Action: Remove the ORDER BY clause.
Syntax → NEAR(( word1, word2,..., wordn ) [, max_span [, order]])
Descriptions of Solaris Event Tests → The Solaris event tests are listed in alphabetical order.
Product Media (PM) Schema Scripts → This section shows the PM schema scripts in alphabetical order.
Human Resources (HR) Schema Scripts → This section shows the HR schema scripts in alphabetical order.
Descriptions of HTTP Server Event Tests → The HTTP Server event tests are listed in alphabetical order.
Descriptions of Linux Event Tests → The Linux event tests are listed in alphabetical order.
Sales History (SH) Schema Scripts → This section shows the SH schema scripts in alphabetical order.
Descriptions of Database Event Tests → The Oracle Database Event Tests are listed in alphabetical order.
Descriptions of Windows NT Event Tests → The Windows NT event tests are listed in alphabetical order.
Descriptions of IBM AIX Event Tests → The IBM AIX Event Tests are listed in alphabetical order.
Queued Shipping (QS) Schema Scripts → This section shows the QS schema scripts in alphabetical order.
Descriptions of Compaq Tru64 Event Tests → The Compaq Tru64 Event Tests are listed in alphabetical order.
Descriptions of HP-UX Event Tests → The HP-UX Event Tests are listed in alphabetical order.
getSortOrder → public java.lang.String getSortOrder() throws AQException This method gets the sort order that is used. Returns The sort order used
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-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-01409 NOSORT option may not be used; rows are not in ascending order → only be used for indexes on groups of rows that already are in ascending order. For non-unique indexes … ascending order may not be. If you create an index NOSORT, and two of the rows in the table have the … these addresses are not in ascending order, the ROWIDs are not either. Since these ROWIDs are … considered part of the index
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-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.
ORA-02813 Unable to make temporary file name in order to get key → Cause: This is an internal error. Action: Contact Oracle Support Services.
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-00521 ORDER methods must be declared with 1 (one) parameter in addition to (optional) SELF. → Cause: An order member function was declared without the user-specified parameter. Order member … second parameter is added by the user and must declare an order method which must be the same type as
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.
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-14303 partitions or subpartitions are not in the right order → ordered differently from the DDL order of partitions or subpartitions. Action: Re-order the partitions … or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement.
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.
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"
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
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:
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-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.
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-00524 The parameter type in an ORDER method must be the containing object type. → Cause: An order member function was declared without the user- specified parameter. Order member … second parameter is added by the user and must declare an order method which must be the same type as
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.