Inspect SGA retrieves executed SQL statements from Oracle's System Global Area or currently running SQL statements from Oracle's open cursor. Once you retrieve the statements, Inspect SGA displays the statements and their run time statistics so you can identify resource intensive statements in your database environment.
Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.
To retrieve a previously executed SQL statement
Select the Inspect SGA tab in the main window.
Note: To retrieve previously executed SQL statements, you must have privileges to view SYS.V_$SQLAREA and either SYS.V_$SQLTEXT_WITH_NEWLINES or SYS.V_$SQLTEXT.
Click to select a group or click to create a new group in the Group list.
Click . The Add Inspect SGA Job wizard displays.
Complete the following fields in the wizard:
|General Information Page||Description|
|Select the Executed SQL from SQL Area option.|
|Collecting Criteria Page||Description|
|Select the Top n records option and enter the number of records to display.|
Click and select the statistic to use to extract SQL statements if you are not displaying all records.
Note: A large SGA increases processing time.
|Collection Time Page||Description|
|Select the Start collecting when you click the Inspect button option.|
Click to retrieve the SQL statements and run time statistics.
Select a statement that requires optimization in the SQL Statistics pane and click to send to Batch Optimize SQL or click the arrow beside and select an option.
Tip: You can add an Inspect SGA job in Batch Optimize to optimize all the SQL statements in the collection.
Use Analyze Impact to evaluate the impact that a change can have on a group of SQL statements or a SQL workload. The types of changes Analyze Impact will allow you to evaluate include: the addition of indexes and changes to database parameters. You can also run a comparison of two different databases that run the same application.
You can collect the SQL workload from one of several sources: source code, an Oracle Automatic Workload Repository (AWR), or the Oracle System Global Area (SGA).
To perform an impact analysis
Specify the remaining index criteria for the selected index. Review the following for additional information:
|Index Type||Select an index type.|
|Advanced Options||Click to select from additional options for the selected index.|
|Select to add key compression. If you select Compress Key, you must also include the number of columns to compress in the Columns field.|
Click the edit link beside Module. Notice that all available modules (for the selected schema) display in the graph. You can filter the SQL to collect by selecting a particular module or you can select all to collect SQL from all modules.
Note: Use the mouse pointer to hover over a bar in the graph to display a descriptive tooltip containing SQL workload details to help you select a workload.
When the analysis process is finished, one of the following will display, depending on the analysis results:
If the analysis determines that non of the specified SQL were impacted, the log page displays and reports "No impacted SQL found."
Tip: Use and to navigate back and forth between the pages of a tab.
You can analyze the impact of new indexes on your SQL statement's execution plans before you physically create the indexes on your database. You can create indexes in Optimize SQL or Optimize Indexes and then send the index or indexes to Analyze Impact to evaluate the impact on your SQL workload.
Use the Optimize SQL module to generate index alternatives for a single SQL statement. Or use the Optimize Indexes module to generate index alternatives for a SQL workload or group of SQL statements.
To send indexes to Analyze Impact from Optimize SQL
Generate index alternatives using the Index Generation feature in Optimize SQL.
Select the virtual index alternative you want to use for the analysis in the Alternatives pane in Optimize SQL.
Click in Optimize SQL. A new Analyze Impact session opens.
The Indexing Change Details page is populated with the new index that you sent from the Optimize SQL session. Use this page to modify the index, if necessary.
To send indexes to Analyze Impact from Optimize Indexes
Outline Management displays stored outlines deployed using SQL Rewrite mode in Optimize SQL.
To manage outlines
Select the Manage Plans tab in the main window.
Tip: Select the Show Manage Plans checkbox on the Manage Plans options page to display the Manage Plans tab in the main window.
Click Manage Plans. The Create a New Manage Plans Session window displays.
Select a connection to use.
Select the Outlines Management tab.
Select a category in the Category/Outline pane.
You can delete or rename the selected category.
Select a stored outline from the category node.
You can move, rename, or reset the Used Flag on the selected stored outline.
© 2019 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité