Chatta subito con l'assistenza
Chat con il supporto

SQL Optimizer for Oracle 10.0 - User Guide

Welcome to SQL Optimizer
About SQL Optimizer SQL Optimization Workflow New in This Release Additional Resources Database Privileges Database Privileges Script Connect to the Database Windows Layout Customize Toolbars Keyboard Shortcuts Support Bundle Register SQL Optimizer Check for Updates SQL Operations
ALL PARTITION ALTER INDEX AND EQUAL ANTI JOIN BITMAP AND BITMAP COMPACTION BITMAP CONSTRUCTION BITMAP CONVERSION BITMAP INDEX BITMAP JOIN INDEX UPDATE BITMAP JOIN INDEX UPDATE STATEMENT BITMAP KEY ITERATION BITMAP MERGE BITMAP MINUS BITMAP OR BUFFER SORT CARTESIAN JOIN COLLECTION ITERATOR CONCATENATION CONNECT BY CONNECT BY PUMP COUNT COUNT STOPKEY CREATE AS SELECT CUBE SCAN DDL STATEMENT DELETE DOMAIN INDEX FAST FULL INDEX SCAN FILTER FIRST ROWS FIXED INDEX FIXED TABLE FOR UPDATE FULL INDEX SCAN FULL INDEX SCAN DESCENDING FULL INDEX SCAN (MIN/MAX) HASH GROUP BY HASH GROUP BY PIVOT HASH JOIN HASH JOIN BUFFERED HASH PARTITION HASH UNIQUE INDEX INDEX BUILD NON UNIQUE INDEX RANGE SCAN INDEX RANGE SCAN DESCENDING INDEX RANGE SCAN (MIN/MAX) INDEX SAMPLE FAST FULL SCAN INDEX SKIP SCAN INDEX SKIP SCAN DESCENDING INDEX UNIQUE SCAN INLIST ITERATOR INLIST PARTITION INSERT INTERSECTION INTO INVALID PARTITION ITERATOR PARTITION LOAD AS SELECT MAT_VIEW ACCESS MAT_VIEW REWRITE ACCESS MERGE JOIN MINUS MULTI-TABLE INSERT NESTED LOOPS OUTER JOIN PARTITION PARTITION HASH EMPTY PARTITION LIST PARTITION RANGE PROJECTION PX BLOCK ITERATOR PX COORDINATOR PX ITERATOR PX PARTITION PX PARTITION HASH ALL PX PARTITION LIST ALL PX PARTITION RANGE ALL PX RECEIVE PX SEND RANGE PARTITION RECURSIVE EXECUTION RECURSIVE WITH PUMP REFERENCE MODEL REMOTE SELECT SEMI JOIN SEQUENCE SINGLE PARTITION SINGLE RANGE PARTITION SORT SORT AGGREGATE SORT GROUP BY SORT GROUP BY CUBE SORT GROUP BY NOSORT SORT GROUP BY ROLLUP SORT JOIN SORT ORDER BY SORT UNIQUE SQL MODEL TABLE ACCESS TABLE ACCESS BY GLOBAL INDEX ROWID TABLE ACCESS BY INDEX ROWID TABLE ACCESS BY LOCAL INDEX ROWID TABLE ACCESS BY ROWID TABLE ACCESS BY USER ROWID TABLE ACCESS CLUSTER TABLE ACCESS FULL TABLE ACCESS HASH TABLE ACCESS SAMPLE TABLE QUEUE TEMP TABLE GENERATION TEMP TABLE TRANSFORMATION UNION UNION ALL UNION ALL (RECURSIVE WITH) UNPIVOT UPDATE VIEW VIEW PUSHED PREDICATE WINDOW
Optimize SQL
Create Optimize SQL Sessions Open Optimizer SQL Sessions Rewrite SQL Generate Execution Plan Alternatives
Optimize Indexes Batch Optimize SQL Scan SQL Inspect SGA Analyze Impact Manage Plans Configure Options SQL Optimizer Tutorials About Us Legal Notices

Analyze Impact of Parameter Change

Step two. After selecting to analyze the impact of a database parameter change, specify the parameter changes.

To analyze the impact of a database parameter change

  1. If you have already created a new session, skip to 3. Otherwise, select Analyze Impact.
  2. Click .
  3. Now enter a session name, and select a database and schema.
  4. Enter or select parameter changes in the Compare with value column.
  5. After specifying the parameter changes, click to start collecting the SQL to evaluate.

 

Go to Step three. See Collect SQL and Run an Impact Analysis.

 

  

Related Topics

 

 

Compare Databases

Step two. If you selected to compare two different databases, specify the databases to compare.

To compare databases

  1. If you have already created a new session, skip to 3. Otherwise, select Analyze Impact.
  2. Click .
  3. Select a database connection and schema to specify the Baseline Database Connection.
  4. Select a database connection and schema to specify the database to compare to the baseline.
  5. Click to start collecting the SQL to evaluate.

 

Go to Step three. See Collect SQL and Run an Impact Analysis.

 

  

Related Topics

Collect SQL and Run an Impact Analysis

 

 

Use Custom Scripts to Analyze Impact

Step two. If you selected to use a custom script to make database changes, specify the custom script details.

To use custom scripts to create a change for an Analyze Impact session

  1. If you have already created a new session, skip to 3. Otherwise, select Analyze Impact.
  2. Click .
  3. Now enter a session name, and select a database connection and schema.
  4. In the Pre-Script section, click to browse to and select a file for the prescript. After the prescript runs, SQL Optimizer retrieves each SQL statement's execution plan to be used as the post-change plan in the impact analysis.

    Note: Alternatively, you can use the script editor to compose a script.

  5. (optional) In the Post-Script section, click to browse to and select a file for the post-script. You can use the post-script to roll back the change created with the first script. Using a post-script is not required.

    Note: Alternatively, you can use the script editor to compose a script.

  6. After specifying the custom script details, click to start collecting the SQL to evaluate.

    Note: If you are not using a post-script, you can click Next->Select SQL after inputting the pre-script.

Go to Step three. See Collect SQL and Run an Impact Analysis.

 

Note: In the script editor, separate multiple commands with a semi-colon.

 

  

Related Topics

 

Collect SQL and Run Analysis

Step three, four, five. After specifying the criteria for the type of change you want to analyze, select the SQL workload or group of SQL statements on which to evaluate the change's impact. You can collect SQL from one of several different sources.

Step three.

Collect SQL

  1. Before collecting SQL, you must create an Analyze Impact session and specify a change to be analyzed.

    • If you have not created an Analyze Impact session, see About Analyze Impact.
    • If you have created an Analyze Impact session and specified the change details, click Next->Select SQL on the Change Details page.
  2. On the SQL page, select the source from which you want to collect SQL. Select from the following:

    • Oracle Automatic Workload Repository (AWR)
    • Oracle System Global Area (SGA)
    • Source code
  3. Next, define the SQL workload by specifying criteria for collecting SQL. Click one of the following for instructions.

  4. After specifying SQL criteria, click to start the collection process.

    Note: Click Cancel to return to the previous page and select a new SQL source type.

  5. SQL Optimizer collects the specified SQL statements. The SQL page opens displaying the list of SQL statements collected. You can review the SQL or run the analysis.

Step four.

Review collected SQL (optional)

  1. You can review or modify the list of SQL statements collected in the previous steps. Review the following for additional information:

    Pane / Button Description

    SQL Tuning Set Pane /

    SQL Workload Pane

    This pane displays the list of SQL in the workload.

    Include—To include a SQL statement in the optimize indexes process, select the checkbox in the Include column.

    SQL Text Pane This pane displays the SQL text of the selected SQL statement.
    Parsed Execution Plan Pane

    This pane displays the execution plan of the selected SQL statement.

    SQL Statistics—Select this tab to display statistics of the selected statement.

    Select to send your SQL to Optimize SQL or Batch Optimize SQL. Click the arrow for more options.

    Notes:

    • Click or Collected from Source to return to the SQL Collection page. (On the SQL Collection page, click Review SQL to go back to the SQL Review page.)
    • To collect a new SQL workload, return to the SQL Collection page and click Edit Criteria.

      Caution: If you click Edit Criteria, the SQL workload will be lost, as well as any analysis data already gathered for the current session.

Step five.

Run the impact analysis

  1. When you are satisfied with the SQL collected, click on the SQL page to run the impact analysis.

  2. When the analysis process is finished, one of the following will display, depending on the analysis results:

    • If an impact was found, the Impacts page displays. See Review Impact Analysis Results.
    • If the analysis determines that non of the specified SQL were impacted, the log page displays and reports "No impacted SQL found." You can click to run the impact analysis again (without modifying any criteria).

      Note: You can modify the change or the SQL collection criteria and then run a new analysis within the same session. To do this, select the SQL or Change Details tab and click Edit criteria.

      Caution: If you click Edit Criteria, the analysis results for the current session will be lost, as well as the SQL workload or the Change criteria for the current session.

Note: Click to stop the SQL collection or analysis process.

 

Go to Step six. Review Impact Analysis Results.

 

  

Related Topics

Review Impact Analysis Results

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione