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
Alphabetical Listing of Hints → This section provides syntax and semantics for all hints in alphabetical order.
Sorting Query Results → Use the ORDER BY clause to order the rows selected by a query. Sorting by position is useful in the … following cases: To order by a lengthy select list expression, you can specify its position in the … ORDER BY clause rather than duplicate the entire expression. For compound queries containing set … operators
Object Values → Object values are compared using one of two comparison functions: MAP and ORDER. Both functions … TYPE for a description of MAP and ORDER methods and the values they return
INDEX_SS_ASC Hint → scans the index entries in ascending order of their indexed values. In a partitioned index, the results … are in ascending order within each partition. Each parameter serves the same purpose as in \"INDEX … Hint\". The default behavior for a range scan is to scan index entries in ascending order of their … indexed values, or in
INDEX_ASC Hint → entries in ascending order of their indexed values. Each parameter serves the same purpose as in … \"INDEX Hint\". The default behavior for a range scan is to scan index entries in ascending order of their … indexed values, or in descending order for a descending index. This hint does not change the … default order
INDEX_SS_DESC Hint → ascending, then Oracle scans the index entries in descending order of their indexed values. In a … partitioned index, the results are in descending order within each partition. For a descending index, this … hint effectively cancels out the descending order, resulting in a scan of the index entries in … ascending order.
INDEX_DESC Hint → , then Oracle scans the index entries in descending order of their indexed values. In a partitioned … index, the results are in descending order within each partition. For a descending index, this hint … effectively cancels out the descending order, resulting in a scan of the index entries in ascending … order.
10 SQL Statements: ALTER CLUSTER to ALTER JAVA → various types of SQL statements and then describes the first set (in alphabetical order) of SQL … statements. The remaining SQL statements appear in alphabetical order in Chapter 11 through Chapter 19
ORDERED Hint → in the order in which they appear in the FROM clause. Oracle recommends that you use the LEADING hint … requiring a join, the optimizer chooses the order in which to join the tables. You might want to … use the ORDERED hint to specify a join order if you know something that the optimizer does not know
INDEX_SS Hint → entries in ascending order of their indexed values. In a partitioned index, the results are in ascending … order within each partition. Each parameter serves the same purpose as in \"INDEX Hint\". For
CEIL → greater than or equal to the order total of a specified order: SELECT order_total, CEIL(order_total
NO_USE_MERGE Hint → example: SELECT /*+ NO_USE_MERGE(e d) */ * FROM employees e, departments d WHERE e.department_id = d.department_id ORDER BY d.department_id;
FIRST_VALUE → (ORDER BY salary ASC ROWS UNBOUNDED PRECEDING) AS lowest_sal FROM (SELECT * FROM employees WHERE … department_id = 90 ORDER BY employee_id); DEPARTMENT_ID LAST_NAME SALARY LOWEST_SAL … are ordered by employee_id in descending order, as in the next example, then the function returns a … different value: SELECT department_id, last_name,
ROWNUM Pseudocolumn → For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in … query, as in this example: SELECT * FROM employees WHERE ROWNUM If an ORDER BY clause follows ROWNUM … in the same query, then the rows will be reordered by the ORDER BY clause. The results can vary … depending on the way the
LAST_VALUE → salary: SELECT last_name, salary, hire_date, LAST_VALUE(hire_date) OVER (ORDER BY salary ROWS … department_id = 90 ORDER BY hire_date); LAST_NAME SALARY HIRE_DATE LV … descending order, as in the next example, then the function returns a different value: SELECT … last_name, salary, hire_date, LAST_VALUE(hire_date) OVER (ORDER
CUME_DIST → by CUME_DIST is >0 to SELECT CUME_DIST(15500,.05) WITHIN GROUP (ORDER BY salary, commission_pct … , salary, CUME_DIST() OVER (PARTITION BY job_id ORDER BY salary) AS cume_dist FROM employees WHERE
Lexical Conventions → ) FROM employees WHERE department_id = 30 ORDER BY last_name; SELECT last_name, salary * 12 … , MONTHS_BETWEEN( hire_date, SYSDATE ) FROM employees ORDER BY last_name; Case is insignificant in reserved words
ROW_NUMBER → , the query must ensure a deterministic sort order. You cannot use ROW_NUMBER or any other analytic … numbers to each row in order of employee's hire date: SELECT department_id, last_name, employee_id … , ROW_NUMBER() OVER (PARTITION BY department_id ORDER BY employee_id) AS emp_id FROM employees … (SELECT last_name, ROW_NUMBER()
IS ANY Condition → the illustration is_any_condition.gif The condition always returns a Boolean value of TRUE in order to … ) IGNORE NAV UNIQUE DIMENSION RULES UPSERT SEQUENTIAL ORDER ( s[ANY, 2000] = 0 ) ORDER BY country
FIRST → information on syntax, semantics, and restrictions of the ORDER BY clause and OVER clause Purpose FIRST … commission: SELECT department_id, MIN(salary) KEEP (DENSE_RANK FIRST ORDER BY commission_pct) \"Worst … \", MAX(salary) KEEP (DENSE_RANK LAST ORDER BY commission_pct) \"Best\" FROM employees GROUP BY … , department_id, salary,
Cartesian Products → specific pair, then the optimizer may choose a join order that avoids producing an intermediate Cartesian product.
Analytic Functions → are the last set of operations performed in a query except for the final ORDER BY clause. All joins … . Therefore, analytic functions can appear only in the select list or ORDER BY clause. Analytic … or ORDER BY clause. To filter the results of a query based on an analytic function, nest these … functions except PERCENTILE_CONT
PERCENT_RANK → argument expressions and the expressions in the ORDER BY clause of the aggregate match by position … with a salary of $15,500 and a commission of 5%: SELECT PERCENT_RANK(15000,.05) WITHIN GROUP (ORDER BY … (PARTITION BY department_id ORDER BY salary DESC) AS pr FROM employees ORDER BY pr, salary; DEPARTMENT_ID
PERCENTILE_DISC → percentile value. This expression must be constant within each aggregate group. The ORDER BY clause … P, PERCENTILE_DISC sorts the values of the expression in the ORDER BY clause and returns the value … (ORDER BY salary DESC) OVER (PARTITION BY department_id) \"Percentile_Disc\", CUME_DIST() OVER … (PARTITION BY department_id
LEADING Hint → joined first in the order specified because of dependencies in the join graph. If you specify two or
Restriction on the WAIT Clause → dept_total > (SELECT avg FROM avg_cost) ORDER BY department_name; DEPARTMENT_NAME DEPT_TOTAL … employees WHERE department_id = 30 ORDER BY last_name; The following statement selects the name, job … department_id = 30) ORDER BY last_name; The following statement selects from subqueries in the FROM clause … ORDER
CREATE TYPE BODY → either one MAP method or one ORDER method, regardless of how many MEMBER or STATIC methods you declare … . If you declare either a MAP or ORDER method, then you can compare object instances in SQL. If you do … MAP function can have no arguments other than the implicit SELF argument. ORDER MEMBER Clause … Specify ORDER
COVAR_POP → sample schema oe: SELECT product_id, supplier_id, COVAR_POP(list_price, min_price) OVER (ORDER BY … product_id, supplier_id) AS CUM_COVP, COVAR_SAMP(list_price, min_price) OVER (ORDER BY product_id … , supplier_id) AS CUM_COVS FROM product_information p WHERE category_id = 29 ORDER BY product_id
User-Defined Operators → condition of a WHERE clause, or in ORDER BY clauses and GROUP BY clauses. However, you must have EXECUTE
Condition Precedence → Precedence is the order in which Oracle Database evaluates different conditions in the same
Oracle Compliance with FIPS 127-2 → list 120 (Note 5) Sort specifications in ORDER BY clause 6 255 (Note 5) Length of ORDER BY column … in an ORDER BY clause. However, the sum of the sizes of all the expressions in either a GROUP BY … clause or an ORDER BY clause is limited to the size of an Oracle data block (specified by the
Model Expressions → left-hand side of the rule contains a FOR loop or an ORDER BY clause. The arguments in the OVER clause … -cell reference. When AUTOMATIC ORDER is specified in the model_rules_clause, a nested cell reference … DIMENSION RULES UPSERT SEQUENTIAL ORDER ( s[prod='Mouse Pad', year=2000] = s['Mouse Pad', 1998] + s … ['Mouse Pad', 1999],
RANK → each group. The constant argument expressions and the expressions in the ORDER BY clause of the … ,.05) WITHIN GROUP (ORDER BY salary, commission_pct) \"Rank\" FROM employees; Rank ---------- 105 … : SELECT RANK(15500) WITHIN GROUP (ORDER BY salary DESC) \"Rank of 15500\" FROM employees; Rank of 15500 … department_id, last_name,
How to Use Sequence Values → : Example This example adds a new order with the next order number to the master order table. It then … adds suborders with this number to the detail order table: INSERT INTO orders (order_id, order_date
ITERATION_NUMBER → RULES UPSERT SEQUENTIAL ORDER ITERATE(2) ( s['Mouse Pad', 2001 + ITERATION_NUMBER] = s['Mouse Pad … ', 1998 + ITERATION_NUMBER] ) ORDER BY country, prod, year; COUNTRY PROD YEAR S
PRESENTV → SEQUENTIAL ORDER ( s['Mouse Pad', 2001] = PRESENTV(s['Mouse Pad', 2000], s['Mouse Pad', 2000], 0 … ) ) ORDER BY country, prod, year; COUNTRY PROD YEAR S
VAR_POP → )) OVER (ORDER BY t.calendar_month_desc) \"Var_Pop\", VAR_SAMP(SUM(s.amount_sold)) OVER (ORDER BY
IS PRESENT Condition → ) MEASURES (sale s) IGNORE NAV UNIQUE DIMENSION RULES UPSERT SEQUENTIAL ORDER ( s['Mouse Pad', 2000] = CASE … WHEN s['Mouse Pad', 1999] IS PRESENT THEN s['Mouse Pad', 1999] ELSE 0 END ) ORDER BY country, prod
CV → ORDER ( s[FOR prod IN ('Mouse Pad', 'Standard Mouse'), 2001] = s[CV( ), 1999] + s[CV( ), 2000] ) ORDER