Less 04 Oracle Performance Tuning:11g

Copyright 2008, Oracle. All rights reserved.
Defining Problems
Copyright 2008, Oracle. All rights reserved. 4 - 2
Objectives
After completing this lesson, you should be able to do the
following:
Identify performance issues
Set tuning priorities
Interpret tuning diagnostics
Tune for life cycle phase
Defining the Problem
Users
DBA
Monitor
Reports and files
Database
instance
Feedback
Limit the Scope
Where is the problem?
Application (SQL)
Instance
Operating system
Setting the Priority
Choose the problem that has the greatest impact:
Analyze system performance in terms of work done (CPU or
service time) versus time spent waiting for work (wait time).
Determine which component consumes the greatest amount
of time.
Drill down to tune that component, if appropriate.
Top Wait Events
Setting the Priority: Example
Time Model Statistics
Top SQL Reports
SQL by Elapsed Time
SQL by CPU Time
SQL by Executions
SQL by Buffer Gets
Common Tuning Problems
The most common tuning problems:
Inefficient or high-load SQL statements
Suboptimal use of Oracle Database by the application
Undersized memory structures
Concurrency issues
I/O issues
Database configuration issues
Short-lived performance problems
Degradation of database performance over time
Unexpected performance regression after environment
changes
Locking issues
Tuning Life Cycle Phases
An applications life cycle can be divided into different phases:
Application design and development
Testing: Database configuration
Deployment: Adding a new application to an existing
database
Production: Troubleshooting and tuning
Migration, upgrade, and environment changes
Tuning During the Life Cycle
Tuning can be divided into two classes:
Proactive (make it better, so it will not break)
Test scenarios.
Find the problem areas.
Resolve the problem.
Reactive (wait until it breaks, then fix it)
Monitor active instance.
Tune issues as needed.
Reactive
Proactive
Application Design and Development
The application can be tuned, even in the design and
development phases, by building and tuning test cases.
Check normalization against major functions.
Check data structures against access times.
Look at points where processes are serialized.
Tune the major reports.
Tune the high-volume processes.
Testing: Database Configuration
The testing phase allows tuning at a deeper level.
Check physical layout.
Monitor for resource contention.
Memory utilization
Locks
Disk hot spots
Test for resource exhaustion.
Deployment
Deployment of:
New application and database
Take baseline.
Monitor growth and performance.
New application in existing database
Take baseline before deployment.
Take baseline after deployment.
Compare baselines.
Production
Tuning is reactive. You need to know:
What has changed?
Where is the baseline?
Migration, Upgrade, and Environment Changes
1. Create a test system.
2. Capture a representative workload.
3. Execute the workload against the test system.
4. Collect statistics.
5. Reset the test system, make a change.
6. Execute the workload.
7. Capture statistics and compare.
ADDM Tuning Session
An ADDM tuning session follows the same procedure as a
manual tuning session, but combines steps.
ADDM Tuning Session Manual Tuning Session
Generate the ADDM report. Collect current statistics.
Compare current statistics with a previous set; look
up in a performance-issues knowledge base.
Define the problem and make recommendations.
Review the recommendations. Build a trial solution.
Implement the
recommendations.
Implement and measure the change.
Review the next ADDM report. Decide: Did the solution meet the goal?
Performance Versus Business Requirements
Factors that affect performance:
Frequent checkpointing
Performing archiving
Block check sums
Redundancy
Frequent backups of data files
Multiple control files
Multiple redo log members in a group
Security
Auditing
Encryption
Virtual Private Database/Fine Grained Access Control
Performance Tuning Resources
Oracle provides a large set of resources for problem solving.
Documentation
Metalink
Forums
Performance Service requests
Remote Diagnostics Report
Filing a Performance Service Request
File a performance service request.
Is the problem instance-wide or query specific?
Identify the root cause.
Provide Statspack or AWR reports, and OS statistics.
Provide Remote Diagnostics Agent (RDA) reports.
Provide SQL_TRACE reports.
RDA Report
Monitoring and Tuning Tool: Overview
Alert log
Trace files
Performance views
Optimizer statistics
SQL statistics
Base statistics
Histograms
Metrics
Service statistics
ASH
tkprof
trcsess
System statistics
Session statistics
Wait model
Time model
Alerts
ASH reports
Services
Monitoring and Tuning Tool: Overview

Statspack
AWR
EM performance
pages
Metric baseline
EM policies
ADDM
Advisors
Direct SGA monitor
Hang analyzer
Baselines
AWR baselines
Compare periods
Services
Summary
In this lesson, you should have learned how to:
Identify performance issues
Set tuning priorities
Interpret tuning diagnostics
Tune for life-cycle phase
Practice 4 Overview:
Identifying the Problem
This practice covers the following topics:
Identify an OS problem using EM

Less 04 Oracle Performance Tuning:11g

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Less 04 Oracle Performance Tuning:11g

Diunggah oleh

Hak Cipta:

Format Tersedia

Copyright 2008, Oracle. All rights reserved.

Anda mungkin juga menyukai