The course starts with an unknown database that requires tuning. The lessons will proceed through the steps a DBA will perform to acquire the information needed to identify problem areas, to diagnose common problems, and remedy those problems. The methodology used in the practices is primarily reactive. After configuring monitoring tools, and reviewing the available reports, the student will be presented with the Oracle architecture based on the SQL statement processing of SELECT and DML. The SQL tuning section assumes that the DBA has little or no ability to change the code. The DBA will influence the SQL performance with available tools. The DBA will be introduced to various methods of identifying the SQL statements that require tuning, and the diagnostic tools needed to find ways to change the performance. This will include the use of statistics, outlines, and profiles to influence the optimizer, adding and rebuilding indexes, and using the SQL Advisors. A major task of DBAâ€™s is to maintain SQL performance across changes. This course introduces the DB Replay, and SQL Performance Analyzer tools to help the DBA test and minimize the impact of change.
Instance tuning uses the same general method of observing a problem, diagnosing the problem, and implementing a solution. The instance tuning lessons cover the details of major tunable components and describe how you can influence the instance behavior. For each lesson, we will examine the relevant components of the architecture. The class only discusses the architecture to the level required to understand the symptoms and solutions. More detailed explanations are left to other courses, reference material, and the Oracle documentation.
The last lesson of this course is a recap of the best practices discovered in the previous lessons, and miscellaneous recommendations. The goal is to finish the course with a best practices list for students to take away.