RelationalDBDesign RelationalDBDesign 

Business Requirements   «Prev  Next»
Lesson 7Ongoing performance tuning
ObjectiveMonitor Oracle for exceptional conditions.

Ongoing Performance Tuning

In addition to monitoring Oracle for long-term tuning, you may also want to periodically monitor the database and report on exceptional conditions.

Immediate and non-immediate Remedy Problems

Here we find that there are two areas of Oracle performance.
  1. Immediate remedy problems: Those conditions that we can immediately address
  2. Non-immediate remedy problems: Those condition that we cannot fix until we have an opportunity to stop and re-start , or bounce the Oracle database
Below are some common immediate remedy and non-immediate remedy problems.
immediate and non-immediate remedy problems
immediate and non-immediate remedy problems
Note that even though conditions such as a table failing to extend, or a tablespace becoming full (immediate remedy problems) are not considered Oracle tuning topics, they have a direct impact on the performance of the Oracle database because they will cause severe response time slowdowns.

Maximizing your maintenance window

If you can only bounce your database once each week, then you only have one opportunity to change the init.ora parameters to improve tuning. Hence, problems that cannot be fixed immediately do not require immediate reporting. Most Oracle DBAs will check their performance and tuning database the day prior to the maintenance window (i.e. bouncing Oracle) to see what init.ora parameters may be changed.

The next lesson concludes this module.