You are using an outdated browser. Please upgrade to the latest version for the best experience.
How do I narrow my search results?

After you submit your search query:

  1. On the Refine Search results page, select one or more categories of products or services from the left sidebar.
  2. 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
Results for hint


1 to 20 of 473 results. Previous page Prev  Next next page
Results per page:   20  | 40 | 60


Database SQL Language Reference, 12c Release 1 (12.1)

Comments

APPEND HintDescription of the illustration ''append_hint.gif'' The APPEND hint instructs the optimizer to use … default in serial mode. In serial mode, direct path can be used only if you include the APPEND hint … only if you specify the NOAPPEND hint. The decision whether the INSERT will go parallel or not is … independent of the APPEND

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

INDEX_ASC HintDescription of the illustration ''index_asc_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::=, indexspec::= ) The INDEX_ASC hint instructs the optimizer to use an index scan for … \"INDEX Hint\". The default behavior for a range scan is to scan index entries in ascending order of … their indexed values, or

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

INDEX_SS_DESC HintHint\", tablespec::=, indexspec::= ) The INDEX_SS_DESC hint instructs the optimizer to perform an … hint effectively cancels out the descending order, resulting in a scan of the index entries in … ascending order. Each parameter serves the same purpose as in the \"INDEX Hint\". For example: SELECT

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NOAPPEND HintDescription of the illustration ''noappend_hint.gif'' The NOAPPEND hint instructs the optimizer to

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_INDEX HintDescription of the illustration ''no_index_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::=, indexspec::= ) The NO_INDEX hint instructs the optimizer not to use one or more … FROM employees WHERE employee_id > 200; Each parameter serves the same purpose as in \"INDEX Hint … \" with the following modifications:

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_INDEX_SS HintDescription of the illustration ''no_index_ss_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::=, indexspec::= ) The NO_INDEX_SS hint instructs the optimizer to exclude a skip … \"NO_INDEX Hint\". See Also: Oracle Database SQL Tuning Guide for information on index skip scans

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_INMEMORY_PRUNING HintNote: The NO_INMEMORY_PRUNING hint is available starting with Oracle Database 12 c Release 1 … Block in a Hint\", tablespec::= ) The NO_INMEMORY_PRUNING hint disables pruning of in-memory queries.

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_NATIVE_FULL_OUTER_JOIN HintDescription of the illustration ''no_native_foj_hint.gif'' The NO_NATIVE_FULL_OUTER_JOIN hint … , the full outer join is executed as a union of left outer join and anti-join. See Also: NATIVE_FULL_OUTER_JOIN Hint

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_PUSH_SUBQ HintDescription of the illustration ''no_push_subq_hint.gif'' (See \"Specifying a Query Block in a Hint … \" ) The NO_PUSH_SUBQ hint instructs the optimizer to evaluate nonmerged subqueries as the last step

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_UNNEST HintDescription of the illustration ''no_unnest_hint.gif'' (See \"Specifying a Query Block in a Hint\" ) Use of the NO_UNNEST hint turns off unnesting.

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

PUSH_SUBQ HintDescription of the illustration ''push_subq_hint.gif'' (See \"Specifying a Query Block in a Hint … \" ) The PUSH_SUBQ hint instructs the optimizer to evaluate nonmerged subqueries at the earliest … significantly, then evaluating the subquery earlier can improve performance. This hint has no effect

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

PX_JOIN_FILTER HintDescription of the illustration ''px_join_filter_hint.gif'' This hint forces the optimizer to use parallel join bitmap filtering.

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

USE_NL HintThe USE_NL hint instructs the optimizer to join each specified table to another row source with a … ''use_nl_hint.gif'' (See \"Specifying a Query Block in a Hint\", tablespec::= ) The USE_NL hint … the following example, where a nested loop is forced through a hint, orders is accessed through a full … = h.order_id;

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

CLUSTER HintDescription of the illustration ''cluster_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::= ) The CLUSTER hint instructs the optimizer to use a cluster scan to access the … specified table. This hint applies only to tables in an indexed cluster.

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

CURSOR_SHARING_EXACT HintCURSOR_SHARING initialization parameter. The CURSOR_SHARING_EXACT hint instructs the optimizer to … switch this behavior off. When you specify this hint, Oracle executes the SQL statement without any attempt to replace literals with bind variables.

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

DRIVING_SITE HintDescription of the illustration ''driving_site_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::= ) The DRIVING_SITE hint instructs the optimizer to execute the query at a … different site than that selected by the database. This hint is useful if you are using distributed query … hint, then

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

FULL HintDescription of the illustration ''full_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::= ) The FULL hint instructs the optimizer to perform a full table scan for the specified … WHERE clause. The employees table has alias e in the FROM clause, so the hint must refer to the table … by its alias rather than

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

MERGE HintDescription of the illustration ''merge_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::= ) The MERGE hint lets you merge views in a query. If a view's query block contains a … = v.department_id AND e1.salary > v.avg_salary ORDER BY e1.last_name; When the MERGE hint is used without an

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

NO_USE_CUBE HintDescription of the illustration ''no_use_cube_hint.gif'' (See \"Specifying a Query Block in a Hint … \", tablespec::= ) The NO_USE_CUBE hint instructs the optimizer to exclude cube joins when joining

Database SQL Language Reference, 12c Release 1 (12.1)

Comments

PQ_DISTRIBUTE HintHint\", tablespec::= ) The PQ_DISTRIBUTE hint instructs the optimizer how to distribute rows among