order Specify TRUE for Oracle to search for terms in the order you specify. The default is FALSE. For… → that have the order flag set differently. For example, Oracle might return different scores for the
Line 6 of the INSERT statement specifies values for the three purchase order attributes PONo, OrderDate → , and ShipDate. Only attribute values are given; no purchase order constructor is specified. You do … not need to explicitly specify a purchase order constructor to instantiate a purchase order … . If you omit a purchase order constructor, the system instantiates a purchase order automatically
Installing the Order Entry (OE) Schema and its Online Catalog (OC) Subschema → All scripts necessary to create this schema reside in $ORACLE_HOME/demo/schema/order_entry. You need to call only one script, oe_main.sql, to create all objects and load the data. Running oe_main.sql accomplishes the following tasks: Prompts for passwords and tablespace names used within the scripts Erases any previously installed OE schema Creates the user OE and grants the necessary privileges Connects
Values Ranked in the Same or the Opposite Order as the Values of Another Source → You can rank the values of a Source by sorting them in the same or the opposite order of the values … order as the Source named sortValue. Example 6-10 the values of a Source named base in the opposite … order as the Source named sortValue. Example 6-9 Ranking Values in the Same Order as Another Source … Opposite
Changing the Sort Order for All Characters with the Same Diacritic → This example shows how to change the sort order for characters with diacritics. You can do this by … after all characters containing a tilde. Verify the current sort order by choosing Canonical Rules … shows the Non-Spacing Characters screen. Figure 12-30 Changing the Sort Order for All Characters with … Secondary in the Paste
VTP-0110: In order to collect historical data, at least one data item non-key column must be selected. → Cause: An attempt was made to create a user-defined class with only one column in the class. This column is used as the key, resulting in no data items in the class. Action: Add at least one other data item to the class for collection.
Oracle Workflow Guide Release 2.6.2 → Contents Index Glossary Master Index Feedback
Oracle Workflow Guide Release 2.6.2 → Contents Index Glossary Master Index Feedback
Changing the Join Order → The Join Order of an explain plan tells the optimizer how to join multiple tables within a single … the join order by allowing you to drag and drop a table to another position or by selecting the Outline\\Join Order menu option.
ORA-22950 cannot ORDER objects without MAP or ORDER method → Cause: An object type must have a MAP or ORDER method defined for all comparisons other than … equality and inequality comparisons. Action: Define a MAP or ORDER method for the object type.
RMAN-20036 invalid record order → Cause: This is an internal error. Action: Contact Oracle Support Services.
How to Order this Manual → In North America, printed documentation is available for sale in the Oracle Store at http://oraclestore.oracle.com/ Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from http://www.oraclebookshop.com/ Other customers can contact their Oracle representative to purchase printed documentation. To download free release notes, installation documentation, white papers,
PLS-01424 Non-ANSI order of clauses → from clause must come first, and the clauses after it can appear in any order (with the addition of
ORA-00355 change numbers out of order → Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one. Action: Perform recovery with a good version of the log or perform time-based recovery up to the indicated time.
ORA-30487 ORDER BY not allowed here → Cause: DISTINCT functions and RATIO_TO_REPORT cannot have an ORDER BY clause.
ORA-22951 NULL returned by ORDER method → Cause: ORDER method used to compare two object values returned NULL which is not allowed. Action: Redefine the ORDER method to not return a NULL.
DRG-10839 invalid ORDER argument supplied to NEAR → Cause: An invalid value was supplied for ORDER argument to NEAR. Action: Provide a valid ORDER. Valid values are T, TRUE, F, FALSE (case insensitive).
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.
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-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-00523 ORDER methods must return an INTEGER. → Cause: An order member function was written such that it returns something other than an integer … type. Action: Rewrite the ORDER method such that it returns an integer type.
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.
ORA-29301 wrong DBMS_PITR package function/procedure order → Cause: The DBMS_PITR package function/procedure was called in an incorrect order. Action: Restart tablespace point-in-time recovery with a correct procedure.
ORA-30929 ORDER SIBLINGS BY clause not allowed here → Cause: ORDER SIBLINGS BY clause is specified in a query which doesn't have CONNECT BY clause … . Action: Remove ORDER SIBLINGS BY clause or add CONNECT BY clause.
Syntax → NEAR(( word1, word2,..., wordn ) [, max_span [, order]])
Queued Shipping (QS) Schema Scripts → This section shows the QS schema scripts in alphabetical order.
Descriptions of Solaris Event Tests → The Solaris 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.
Human Resources (HR) Schema Scripts → This section shows the HR schema scripts in alphabetical order.
Descriptions of HP-UX Event Tests → The HP-UX Event Tests are listed in alphabetical order.
Descriptions of IBM AIX Event Tests → The IBM AIX Event Tests are listed in alphabetical order.
Descriptions of Compaq Tru64 Event Tests → The Compaq Tru64 Event Tests are listed in alphabetical order.
Descriptions of Windows NT Event Tests → The Windows NT event tests are listed in alphabetical order.
Product Media (PM) Schema Scripts → This section shows the PM schema scripts in alphabetical order.
Descriptions of HTTP Server Event Tests → The HTTP Server event tests are listed in alphabetical order.
Descriptions of Database Event Tests → The Oracle Database Event Tests are listed in alphabetical order.
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.
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:
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-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.
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.
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