Performance Tuning - Now You are the V8 Expert
Richard J. Niemiec
Version8 of the Oracle database has brought on a whole new level of issues for the DBA. While the queries for tuning thedatabase and individual queries has not changed much, the data retrieved by these queries has changed and must beanalyzed for partitioned tables and other cost-based optimizer functions. This paper will serve to give you the individualqueries to be successful. These excerpts come from the book, Oracle Performance Tuning Tips and Techniques (OraclePress (900 pages): ISBN 0-07-882434-6
is a symphony and you are the conductor with an opportunity to create aworld class performance. As with an orchestra, there are many different sections that must be coordinated with perfection if you are to succeed. Each chapter in the book represents a section of the orchestra which must be tuned. A single query (asingle note) or a poorly configured init.ora (the violin section) can be the cymbals (the ad-hoc query user) that will crash atan inopportune time to bring your system to its knees. The key to tuning often comes down to how effectively you can tunethe database memory and single problem queries. This paper will touch on as much as possible, but the book is 900 pageswith much more of a solution to tuning Oracle7, Oracle8 and Oracle8i.
What will be Covered (Goals for tuning):
Have enough memory allocated to Oracle -
The first goal should be to get enough memory (from your physicalhardware) allocated to “key” Oracle parameters. We will look at how to see what the current settings of a given system areset to and also look at the “key” parameters: DB_BLOCK_BUFFERS, SHARED_POOL_SIZE, andSORT_AREA_SIZE.
Goal#2: Get the data loaded into memory -
Once you have enough memory allocated to Oracle, the focus must shift toensuring that the most important information is getting into memory and staying there. We will look at using x$bh andusing the ‘cache’ parameter of ‘alter table...’ to investigate this area.
Goal#3: Find queries that are clogging memory and causing I/O -
Finding problem areas is, at times, the most difficult problem. We will investigate a method for easily identifying the bottlenecks by using v$sqlarea.
Goal#4: Tune the Problem Queries -
Tuning the problem queries could easily encompass an entire training course. I willfocus on the a couple of key areas: What you need to know before you tune my system, using the Parallel Query Option andgeneral tuning tips.