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 OPTIMIZER_MODE


1 to 20 of 24 results. Previous page Prev  Next next page


Database Reference, 12c Release 1 (12.1)

OPTIMIZER_MODE

1.189 OPTIMIZER_MODEProperty Description Parameter type String Syntax OPTIMIZER_MODE = { FIRST_ROWS_[1 | 10 | 100 … Modifiable in a PDB Yes Basic No OPTIMIZER_MODE establishes the default behavior for choosing an optimization

Database SQL Tuning Guide, 12c Release 1 (12.1)

Influencing the Optimizer

Choosing an Optimizer GoalOPTIMIZER_MODE initialization parameter, you can set the following optimizer goals: Best throughput (default … ) When you set the OPTIMIZER_MODE value to ALL_ROWS, the database uses the least amount of resources … application is running. Best response time When you set the OPTIMIZER_MODE value to FIRST_ROWS_ n, the … SQL*Plus

Database Administrator's Guide, 12c Release 1 (12.1)

Developing Applications for a Distributed Database System

33.4.3 Using Hintsthe Environment Set the OPTIMIZER_MODE initialization parameter to establish the default behavior … OPTIMIZER_MODE parameter in the initialization parameter file Setting it at session level by issuing … the OPTIMIZER_MODE initialization parameter in the parameter file and for configuring your system to

Database SQL Tuning Guide, 12c Release 1 (12.1)

Improving Real-World Performance Through Cursor Sharing

Minimize Session-Level Changes to the Optimizer EnvironmentEXEC:emp_id:= 110; ALTER SESSION SET OPTIMIZER_MODE = FIRST_ROWS; SELECT salary FROM hr.employees

Database SQL Tuning Guide, 12c Release 1 (12.1)

Glossary

optimizer goalThe prioritization of resource usage by the optimizer. Using the OPTIMIZER_MODE initialization

Database Data Warehousing Guide, 12c Release 1 (12.1)

Refreshing Materialized Views

Recommended Initialization Parameters for Parallelismshould be less than HASH_AREA_SIZE. OPTIMIZER_MODE should equal all_rows. Remember to analyze all

Database Data Warehousing Guide, 12c Release 1 (12.1)

Basic Query Rewrite for Materialized Views

Ensuring that Query Rewrite Takes Effectparameter OPTIMIZER_MODE to ALL_ROWS, FIRST_ROWS, or FIRST_ROWS_ n. See Initialization Parameters for

Database Error Messages, 12c Release 1 (12.1)

QSM-00501 to QSM-03287

QSM-01002: no query rewrite when OPTIMIZER_MODE is rule basedCause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE. Action: Change the optimizer mode using the OPTIMIZER_MODE parameter.

Database Data Warehousing Guide, 12c Release 1 (12.1)

Basic Query Rewrite for Materialized Views

Initialization Parameters for Query Rewrite: OPTIMIZER_MODE = ALL_ROWS (default), FIRST_ROWS, or FIRST_ROWS_ n With OPTIMIZER_MODE set to FIRST_ROWS, the

Database SQL Tuning Guide, 12c Release 1 (12.1)

SQL Processing

SQL OptimizationOPTIMIZER_MODE=ALL_ROWS; ALTER SYSTEM FLUSH SHARED_POOL; # optimizer environment 1 SELECT * FROM sh.sales; ALTER … SESSION SET OPTIMIZER_MODE=FIRST_ROWS; # optimizer environment 2 SELECT * FROM sh.sales; ALTER

Database Reference, 12c Release 1 (12.1)

QUERY_REWRITE_ENABLED

1.224 QUERY_REWRITE_ENABLEDDatabase SQL Tuning Guide and \" OPTIMIZER_MODE \" for information on cost-based optimization

Database Error Messages, 12c Release 1 (12.1)

QSM-00501 to QSM-03287

QSM-01202: query rewrite not possible when OPTIMIZER_MODE is set to rule basedCause: Query rewrite did not occur because the OPTIMIZER_MODE was set to RULE. Action: Change the optimizer mode using the OPTIMIZER_MODE parameter.

Database SQL Tuning Guide, 12c Release 1 (12.1)

Influencing the Optimizer

About Optimizer Initialization Parametersparameter were set to false. You can view the report by using DBMS_XPLAN.DISPLAY_CURSOR. OPTIMIZER_MODE

Database Reference, 12c Release 1 (12.1)

Modifiable Parameters

1.4.2 Modifiable ParametersOPTIMIZER_MODE OPTIMIZER_USE_INVISIBLE_INDEXES OPTIMIZER_USE_PENDING_STATISTICS … OPTIMIZER_INDEX_CACHING OPTIMIZER_INDEX_COST_ADJ OPTIMIZER_INMEMORY_AWARE OPTIMIZER_MODE

Database SQL Tuning Guide, 12c Release 1 (12.1)

Influencing the Optimizer

Guidelines for Join Order Hints… See Also: Oracle Database Reference to learn about OPTIMIZER_MODE

Database Reference, 12c Release 1 (12.1)

Parameters by Functional Category

1.4.1 Parameters by Functional CategoryOPTIMIZER_MODE OPTIMIZER_SECURE_VIEW_MERGING OPTIMIZER_USE_PENDING_STATISTICS

Database Reference, 12c Release 1 (12.1)

V$SQL_SHARED_CURSOR

9.62 V$SQL_SHARED_CURSOR|N ) Parameter OPTIMIZER_MODE mismatch (for example, all_rows versus first_rows_1) PX_MISMATCH

Database Reference, 12c Release 1 (12.1)

V$SQLAREA

9.67 V$SQLAREAof this SQL statement COMMAND_TYPE NUMBER Oracle command type definition OPTIMIZER_MODE VARCHAR2(10

Database Reference, 12c Release 1 (12.1)

V$SQLAREA_PLAN_HASH

9.68 V$SQLAREA_PLAN_HASHbehalf of this SQL statement COMMAND_TYPE NUMBER Oracle command type definition OPTIMIZER_MODE

Database Reference, 12c Release 1 (12.1)

DBA_HIST_SQLSTAT

5.60 DBA_HIST_SQLSTATthe query given by the optimizer OPTIMIZER_MODE VARCHAR2(10)   Mode under which the SQL statement is