D50317GC20 Lesson12

Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Using SQL Performance Analyzer

F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Objectives
After completing this lesson, you should be able to:
Identify the benefits of using SQL Performance Analyzer
Describe the SQL Performance Analyzer workflow phases
Use SQL Performance Analyzer to ascertain performance
gains following a database change
Use SQL Performance Analyzer to test the impact of
proposed changes
Oracle Database 11g: Performance Tuning 12 - 2
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Real Application Testing: Overview
SPA and Database Replay offer complementary solutions
SQL Performance Analyzer Database Replay
What is it? Predict SQL performance
deviations
Replay real database workload
on test system
What
Purpose?
Assess impact of change on SQL
response time
Assess impact of change on
workload throughput
How it works? Single, isolated execution of SQL Replay actual workload
When to use? Test application SQL to identify the
set of SQL statements with
changed performance
Comprehensive testing of all sub-
systems of the database server
using real production workload
Real Application Testing: Overview
SQL Performance Analyzer (SPA)
SPA is the tool of choice when you trying to identify SQL statements that will perform
differently, when a change is made at the database or OS level. SPA captures SQL statements
into a SQL tuning set from various sources, including the cursor cache, Automatic Workload
Repository (AWR), and existing SQL tuning sets (STS). The STS is analyzed by executing each
SQL statement in isolation. The order of execution depends on the order of the statement in the
tuning set. The STS includes bind variable, execution plan, and execution context information.
With SPA, you will execute the STS and capture performance statistics, make the change to the
system and execute the STS again, and then compare. SPA does not consider the impact that
SQL statements can have on each other.
Database Replay
When there are extensive changes such as OS, or database version, or when overall system
performance must tested, Database Replay is the preferred tool. Database Replay captures the
actual workload over a period of time, along with performance statistics. This workload is
processed for the target system and then replayed. The replay has options for speed of replay,
think time, maintaining the transaction order (synchronization) and others. After the workload
has been replayed, the performance statistics, data divergence, and errors can be compared to the
original capture or another replay session. AWR and Replay reports are available.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Real Application Testing: Use Cases
Real Application Testing is beneficial in the following use
cases:
Database upgrades
Implementation of tuning recommendations
Example: Accepting SQL profiles
Schema changes
Example: Adding indexes or materialized views
Statistics gathering
Database parameter changes
OS and hardware changes
Real Application Testing: Use Cases
The Real Application Testing option allows you to test the impact of database and OS change
including (but are not limited to) any of the following:
Database upgrades
Implementation of tuning recommendations
Schema changes
Statistics gathering
Database parameter changes
OS and hardware changes
SQL Performance Analyzer can be used to predict and prevent potential performance
problems for any database environment change that affects the structure of the SQL execution
plans. DBAs can use SQL Performance Analyzer to foresee SQL performance changes that
result from the preceding changes for even the most complex environments. As applications
evolve through the development life cycle, database application developers can test, for
example, changes to schemas, database objects, and rewritten applications to mitigate any
potential performance impact.
SPA enables the comparison of SQL performance statistics.
Database Replay can be used for the same change scenarios but tests the entire workload,
honoring transaction dependencies. Database Replay executes all statements including DML.
The entire workload is tested, including interactions and dependencies.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

SQL Performance Analyzer: Process
1. Capture SQL workload on production.
2. Transport the SQL workload to a test system.
3. Build before-change performance data.
4. Make changes.
5. Build after-change performance data.
6. Compare results from steps 3 and 5.
7. Tune regressed SQL.
SQL Performance Analyzer: Process
1. Gather SQL: In this phase, you collect the set of SQL statements that represent your SQL
workload on the production system. You can use SQL tuning sets or Automatic Workload
Repository (AWR) to capture the information to transport. Because AWR essentially
captures high-load SQLs, you should consider modifying the default AWR snapshot
settings and captured Top SQL to ensure that AWR captures the maximum number of SQL
statements. This ensures more complete SQL workload capture. You can also use the
filtering and ranking capabilities of the STS to change the SQL statements that are included.
2. Transport: Here you transport the resultant workload to the test system. The STS is
exported from the production system and the STS is imported into the test system.
3. Compute before-version performance: Before any changes take place, you execute the
SQL statements, collecting baseline information that is needed to assess the impact that a
future change might have on the performance of the workload. The information collected in
this stage represents a snapshot of the current state of the system workload and includes
performance data. In this phase you may test the SQL by executing the STS or you can have
the SPA task only generate the execution plans, without executing the statements.
4. Make a change: After you have the before-version data, you can implement your planned
change and start viewing the impact on performance.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s
SQL Performance Analyzer: Process (continued)

5. Compute after-version performance: This step takes place after the change is made in
the database environment. Each statement of the SQL workload executes again, collecting
the same information as captured in step 3.
6. Compare and analyze SQL Performance: After you have both versions of the SQL
workload performance data, you can carry out the performance analysis by comparing the
after-version data with the before-version data. The comparison is based on the execution
statistics, such as elapsed time, CPU time, and buffer gets.
7. Tune regressed SQL: At this stage, you have identified exactly which SQL statements may
cause performance problems when the database change is made. Here, you can use any of
the database tools to tune the system. For example, you can use SQL Tuning Advisor or
Access Advisor against the identified statements and then implement those
recommendations. Alternatively, you can seed SQL Plan Management (SPM) with plans
captured in step 3 to guarantee that the plans remain the same. After implementing any
tuning action, you should repeat the process to create a new after-version and analyze the
performance differences to ensure that the new performance is acceptable.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Capturing the SQL Workload
1. Create a SQL tuning set (STS) on the original system.
2. Create a staging table and pack the STS in it.
3. Export the staging table to the test system.
4. Unpack the staging table to the STS on the test system.
Capturing the SQL Workload
Capturing SQL workload is done by using SQL tuning sets (STS) and transporting it to the target
system. This workflow is briefly described in the slide. You can use either Enterprise Manager
wizards or the DBMS_SQLTUNE PL/SQL package.
With Oracle Database 11g, you access the SQL tuning sets page from the Performance tab in
Database Control.
The workload that you capture should reflect a representative period of time (in captured SQL
statements) that you wish to test under some changed condition. The following information is
captured in this process:
The SQL text
The execution context (including bind values, parsing schema, and compilation
environment), which contains a set of initialization parameters under which the statement is
executed
The execution frequency, which tells how many times the SQL statement has been executed
during the time interval of the workload
Normally the capture SQL happens on the production system to capture the workload running on
it. The performance data is computed later on the test system by the compute SQL performance
processes. SQL Performance Analyzer tracks the SQL performance of the same STS before and
after a change is made to the database.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Creating a SQL Performance Analyzer Task
Creating a SQL Performance Analyzer Task
With EM you can manage each component in the SQL Performance Analyzer process and report
the analysis result. EM Database Control and EM Grid Control have the same pages.
There are multiple paths to access the SQL Performance Analyzer page: from the Software and
Support tab of Database Control, from the Related Links section on any tab (select Advisor
Central > Advisors > SQL Performance Analyzer), or from the Performance tab in the
Additional Monitoring Links section.
SQL Performance Analyzer offers five workflows for you to test different scenarios:
Upgrade from 9i or 10.1: Test and analyze the effects of database upgrade from 9i or 10.1
on SQL Tuning Set performance.
Upgrade from 10.2 or 11g: Test and analyze the effects of database upgrade from 10.2 or
11g on SQL Tuning Set performance.
Parameter Change: Test and compare an initialization parameter change on SQL tuning
set performance. A SQL Performance Analyzer task is created and an initial trial run is
performed with the parameter set to the base value. A second trial run is performed with the
parameter set to the changed value. A replay trial comparison report is then run for the two
trials.
Exadata Simulation: Simulate the effects of an Exadata Storage Server installation on SQL
Tuning Set performance.
Guided Workflow: Create a SQL Performance Analyzer task and execute custom
experiments by using manually created replay trials.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

SQL Performance Analyzer: Tasks
SQL Performance Analyzer: Tasks
After you create your SQL Performance Analyzer task, it might take a long time for it to finish
depending on the number of statements that are contained in your SQL tuning set. While your
task is executing, you can click Refresh on the SQL Performance Analyzer page to update the
Last Run Status field. When you see Completed in the Status column for your task, the task is
complete.
After execution, you can click the link corresponding to the name of your task in the SQL
Performance Analyzer Tasks table. This directs you to the corresponding SQL Performance
Analyzer Task page.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Parameter Change
Parameter Change
Optimizer Upgrade Simulation
This page enables you to create a task that measures the performance impact on a SQL tuning
set when the database is upgraded from one version to another. In the example in the slide, the
simulated upgrade is done from 10.2.0.1 to 11.1.6 by setting the COMPATIBLE initialization
parameter. (You set COMPATIBLE as low as 8.0.0.)
To create an analysis task, you must specify the following details:
Enter the name of the task and (optionally) a description.
Specify the STS to use for this analysis. It must already be created.
Select a time limit from the Per-SQL Time Limit drop-down list to specify the time limit for
the execution of each SQL statement:
- UNLIMITED: There is no time limit for the execution of each SQL statement.
- EXPLAIN ONLY: The test plan is generated but not executed.
- CUSTOMIZE: You can customize the execution time limit.
Select the parameter you want to change. For this simulation, use the
optimizer_features_enable parameter.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s
Parameter Change (continued)

Select the optimizer versions to indicate the original version of the database and the new
version to which the database is being upgraded. Two replay trials are created. The first
captures STS performance with the original optimizer version, and the second uses the
targeted version.
Select the comparison metric to be used by SPA to evaluate the performance impact due to
the database upgrade.
Specify a schedule for the task.
Click Submit to start the analysis.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

SQL Performance Analyzer Task Page
SQL Performance Analyzer Task Page
A SQL Performance Analyzer task allows you to execute a specific SQL tuning set under
changed environmental conditions. After you execute the task, you can assess the impact of
these changes on the performance of the SQL tuning set. The Comparison Report is useful in
assessing the impact of the changed environmental conditions on the performance of the
specified SQL tuning set.
From this page, you can also perform the following:
Create a trial to test the performance of a SQL tuning set under a specific environment.
Click SQL Replay Trial. Refer to the Guided Workflow page for detailed information about
creating a replay trial.
Run a trial comparison to compare the differences between the replay trials that have been
created so far. A comparison report is generated for each replay trial run.
Click Run SQL Trial Comparison. Refer to the Guided Workflow page for detailed
information about running a replay trial comparison.
Click the eyeglass icon in the Comparison Report column to view the trial comparison
report for your task.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Comparison Report
Comparison Report
Use the SQL Performance Analyzer Task Result page to see the replay trial comparison report.
The following general details are displayed:
Task details such as name, owner, and description of the task
Name and owner of the SQL tuning set
Total number of SQL statements and any SQL statements with errors. Click the SQL
Statements With Errors link to access the Errors table.
The replay trials being compared and the comparison metric being used
In addition to these details, you can view the following:
Projected Workload [Comparison Metric]: This chart shows the projected workload for
each replay trial based on the comparison metric along with the improvement, regression,
and overall impact. Click the impact links to drill down to the complete list of SQL
statements in each category.
SQL Statement Count: This chart shows the number of SQL statements that have
improved, regressed, or not changed performance based on the comparison metric. The
colors of the bars indicate whether the plan changed between the two trial runs. Click the
links or the data buckets to access the SQL Statement Count Details page, where you can
see a list of SQL statements, and then click a SQL ID to access the SQL details.
Top 10 SQL Statements Based on Impact on Workload table: This table allows you to
click a specific SQL ID to drill down to the corresponding SQL Details page.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Comparison Report SQL Detail
Comparison Report (continued)
On the SQL Details page, you can view the SQL statements and a line-by-line comparison
between each replay trial run for each statistic. You can also find the execution plan for each
trial.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Tuning Regressing Statements
From the SQL Performance Analyzer Task Result page, you can directly tune all regressing
statements by invoking SQL Tuning Advisor. To do so, click the Run SQL Tuning Advisor
button to access the Schedule SQL Tuning Task page, where you can specify the tuning task
name and a schedule.
When you are finished, click OK. This creates a new tuning task that analyzes all regressing
statements found by SQL Performance Analyzer.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Tuning Regressing Statements (continued)
After the SQL tuning task is created, you return to the SQL Performance Analyzer Task Results
page, where you can see that you now have a SQL Tune report associated with your
performance analysis in the Recommendations Section.
You can also access the SQL Tuning Results page directly from the SQL Performance Analyzer
Task page by clicking the eyeglass icon in the SQL Tune Report column of the Replay Trial
Comparisons section for your trial comparison. The SQL Tune Report shows you the
Recommendations table that lists all recommendations for regressing statements.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Tuning Regressed SQL Statements
BEGIN
DBMS_SQLTUNE.CREATE_TUNING_TASK(
spa_task_name => 'MYSPA',
spa_compare_exec => 'MYCOMPEXEC');
END;
/
You can also create a SQL tuning task using the
DBMS_SQLTUNE.CREATE_TUNING_TASK function to tune
regressed SQL statements reported by the SQL Performance
Analyzer:
Tuning Regressed SQL Statements
After reviewing the SQL Performance Analyzer report, you should tune any regressed SQL
statements that are identified after comparing the SQL performance. If there are a large number
of SQL statements that appear to have regressed, try to identify the root cause and make system-
level changes to rectify the problem.
If only a few SQL statements have regressed, consider using the SQL Tuning Advisor to
implement a point solution for them. Create a SQL tuning task for the SQL Performance
Analyzer execution by using the DBMS_SQLTUNE.CREATE_TUNING_TASK function. The
CREATE_TUNING_TASK function has the following parameters:
SPA_TASK_NAME: Name of the SQL Performance Analyzer task
SPA_TASK_OWNER: Owner of the specified SQL Performance Analyzer task. If
unspecified, this parameter will default to the current user.
SPA_COMPARE_EXEC: Execution name of the compare performance trial for the specified
SQL Performance Analyzer task. If unspecified, this parameter defaults to the most recent
execution of the COMPARE PERFORMANCE type for the given SQL Performance Analyzer
task.
After tuning the regressed SQL statements, test your changes by using SQL Performance
Analyzer. Run a new SQL trial on the test system, followed by a second comparison (between
this new SQL trial and the first SQL trial) to validate your results. Once SQL Performance
Analyzer shows that performance has stabilized, you can implement the changes.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Preventing Regressions
Preventing Regressions
Instead of using SQL Tuning Advisor to tune your regressing statements, you can also prevent
regressions by using the SQL plan baselines. You can do so from the SQL Performance
Analyzer Task Result page by clicking the Create SQL Plan Baselines button.
Note: For more information about SQL plan baselines, refer to the SQL Performance
Management lesson.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Parameter Change Analysis
Parameter Change Analysis
Use the Parameter Change page to create a task that allows you to test the performance impact
on a SQL tuning set when the value of the initialization parameter is changed. This option is
very useful because it is difficult to forecast whether changing the parameter value will have a
positive or negative impact.
To create a task, do the following:
1. Enter the name of the task and a description.
2. Click the Select icon and select a SQL tuning set from the list.
3. Select the creation method.
4. Select the Per-SQL Time Limit from the list to specify the time limit for the execution of
each SQL statement.
5. Click the Select icon to select an initialization parameter from the list.
6. Specify the current value (Base Value) and the new value (Changed Value) for the
initialization parameter.
7. Select the comparison metric that will be used to evaluate the performance impact due to
the change.
8. Specify the schedule for the task.
After the task has been created, an initial trial run is performed with the initialization parameter
set to the base value. A second trial run is performed with the initialization parameter set to the
changed value. Finally, a replay trial comparison report is generated for the two trials with the
specified comparison metric.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Guided Workflow Analysis
Guided Workflow Analysis
You can use the Guided Workflow page to define a sequence of steps to execute a two-trial SQL
Performance Analyzer test. The steps are as follows:
1. Create a SQL Performance Analyzer task based on a SQL tuning set.
2. Create a trial in the initial environment: Any changes to the trial environment that affect the
STS must be made manually before the replay trial is executed. These trials may include
changing initialization parameters, gathering optimizer statistics, and creating indexes.
3. Create the SQL trial using the changed environment: You can now create the second SQL
trial using the changed environment by specifying all the necessary information.
Performance differences between the trials are attributed to the environmental differences.
4. Create the trial comparison using trials from previous steps. This allows you to assess the
performance impact on the STS when each replay trial is executed.
5. View the trial comparison report: You can now generate the replay trial comparison report.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

SQL Performance Analyzer: PL/SQL Example
1. Create a tuning task.
2. Execute the task to collect the before-change data.
3. Generate the before-change report.
exec :tname:= dbms_sqlpa.create_analysis_task( -
sqlset_name => 'MYSTS', -
task_name => 'MYSPA');
exec dbms_sqlpa.execute_analysis_task(task_name => :tname, -
execution_type => 'TEST EXECUTE', -
execution_name => 'before');
select dbms_sqlpa.report_analysis_task(
task_name => :tname,-
type=>'text',
section=>'summary') FROM dual;
The general example in the slide shows you how to use the DBMS_SQLPA package to invoke
SQL Performance Analyzer to access the SQL performance impact of some changes. You could
easily adapt this example to run your own analysis.
1. Create the tuning task to run SQL Performance Analyzer.
2. Execute the task once to build the before-change performance data. With this call, you can
specify various parameters, some of which are:
- Set the execution_type parameter in either of the following ways: Set to
EXPLAIN PLAN to generate explain plans for all SQL statements in the SQL
workload. Set to TEST EXECUTE to execute all SQL statements in the SQL
workload. The procedure executes only the query part of the DML statements to
prevent side effects to the database or user data. When TEST EXECUTE is specified,
the procedure generates execution plans and execution statistics.
- Specify execution parameters by using the execution_params parameter that
needs to be specified as dbms_advisor.arglist(name,value,). The
time_limit parameter specifies the global time limit to process all SQL statements
in a SQL tuning set before timing out. The local_time_limit parameter
specifies the time limit to process each SQL statement in a SQL tuning set before
timing out.
3. Produce the before-change report (special settings for report: set long 100000,
longchunksize 100000, and linesize 90).
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

4. Execute the after-changes task.
5. Generate the after-changes report.
6. Compare the two executions.
7. Generate the comparison report.
exec dbms_sqlpa.execute_analysis_task(task_name => :tname, -
execution_type => 'TEST EXECUTE', -
execution_name => 'after');
select dbms_sqlpa.report_analysis_task(task_name => :tname,
type=>'text', section=>'summary') FROM dual;
exec dbms_sqlpa.execute_analysis_task(task_name => :tname,-
execution_type => 'COMPARE PERFORMANCE');
select dbms_sqlpa.report_analysis_task(task_name => :tname,
type=>'text', section=>'summary') FROM dual;
SQL Performance Analyzer: PL/SQL Example (continued)
After you make the change to your test instance.
4. Execute the task again after making the changes
5. Generate the after-changes report.
6. Compare the two executions using the following command as a pattern and substituting
parameters to suit your needs:
BEGIN
DBMS_SQLPA.EXECUTE_ANALYSIS_TASK(
task_name => :tname,
execution_type => 'compare performance',
execution_params => dbms_advisor.arglist(
'execution_name1', 'before',
'execution_name2', 'after',
'comparison_metric', 'buffer_gets'));
END;
7. Generate the analysis report.
Note: For more information about the DBMS_SQLPA package, see the Oracle Database PL/SQL
Packages and Types Reference Guide.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

SQL Performance Analyzer:
Data Dictionary Views
Modified views in Oracle Database 11g:
DBA{USER}_ADVISOR_TASKS: Displays details about the
analysis task
DBA{USER}_ADVISOR_FINDINGS: Displays analysis
findings
New views in Oracle Database 11g:
DBA{USER}_ADVISOR_EXECUTIONS: Lists metadata
information for task execution
DBA{USER}_ADVISOR_SQLPLANS: Displays the list of SQL
execution plans
DBA{USER}_ADVISOR_SQLSTATS: Displays the list of SQL
compilation and execution statistics
SQL Performance Analyzer: Data Dictionary Views
DBA{USER}_ADVISOR_TASKS: Displays details about the advisor task created to
perform an impact analysis of a system environment change
DBA{USER}_ADVISOR_FINDINGS: Displays analysis findings. The advisor generates
four types of findings: performance regression, symptoms, errors, and informative
messages.
DBA{USER}_ADVISOR_EXECUTIONS: Lists metadata information for a task execution.
SQL Performance Analyzer creates a minimum of three executions to perform a change
impact analysis on a SQL workload: one execution to collect performance data for the
before-change version of the workload, the second execution to collect data for the after-
change version of the workload, and a final execution to perform the actual analysis.
DBA{USER}_ADVISOR_SQLPLANS: Displays the list of all SQL execution plans (or
those owned by the current user)
DBA{USER}_ADVISOR_SQLSTATS: Displays the list of SQL compilation and execution
statistics (or those owned by the current user)
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s
Answer: b
The SQL Performance Analyzer will show the performance difference of individual SQL
statements. You would use Database Replay to find the overall performance change.
Quiz
The SQL Performance Analyzer will show the overall
performance change you can expect when changing
environments.
a. True
b. False
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Summary
In this lesson, you should have learned how to:
Identify the benefits of using SQL Performance Analyzer
Describe the SQL Performance Analyzer workflow phases
Use SQL Performance Analyzer to ascertain performance
gains following a database change
Use SQL Performance Analyzer to test the impact of
proposed changes
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

Practice 12: Overview
This practice covers using SQL Performance Analyzer with
Enterprise Manager to create a SQL tuning set (STS) and
analyze it after changing the environment.
F
u
n
m
i

A
l
a
p
a
f
u
j
a

(
f
u
n
m
i
a
l
a
p
a
f
u
j
a
@
l
l
o
y
d
s
b
a
n
k
i
n
g
c
o
m
)

h
a
s

a
n
o
n
-
t
r
a
n
s
f
e
r
a
b
l
e

l
i
c
e
n
s
e

t
o

u
s
e

t
h
i
s

S
t
u
d
e
n
t

G
u
i
d
e
U
n
a
u
t
h
o
r
i
z
e
d

r
e
p
r
o
d
u
c
t
i
o
n

o
r

d
i
s
t
r
i
b
u
t
i
o
n

p
r
o
h
i
b
i
t
e
d

C
o
p
y
r
i
g
h
t

2
0
1
3
,

O
r
a
c
l
e

a
n
d
/
o
r

i
t
s

a
f
f
i
l
i
a
t
e
s

D50317GC20 Lesson12

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

D50317GC20 Lesson12

Enviado por

Direitos autorais:

Formatos disponíveis

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Using SQL Performance Analyzer

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

SQL Performance Analyzer: Process (continued)

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Parameter Change (continued)

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Copyright 2010, Oracle and/or its affiliates. All rights reserved.

Você também pode gostar