Tuning Steps

First steps to identify performance problems on your Oracle Database

– Look for objects statistics (they might be up-to-date for all objects)

– Get the bottlenecks with Wait Events

– Look for non-reentrant SQL (literals values inside SQL from v$sql)

– Get advices concerning memories structures

Advanced steps to identify performance problems on your Oracle Database

– Install Statspack and get hourly snapshots

– Analyze report for peak times activity

– Get the bottlenecks with Wait Events

– Find objects that the most used; try to put them in the “keep cache”

– See if large-table full-table scans can be removed with well-placed indexes

– Look for non-shared cursors

2 thoughts on “Tuning Steps

  1. Nilesh

    Thanks for Step if you share the sql tool which you used like (script) plus scenario then it will good and will appreciate your help and it will new learning experience for us.

  2. Maurice(Rese) Lewis

    My apologies Vincent. This may be somewhat off-topic.

    Would an Oracle « ora-08103 object no longer exists » error qualify as a reportable database error event?

    Sadly, I do not have access to the production server and therefore cannot examine the alert.log or the locations of possible trace files.

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *

Ce site utilise Akismet pour réduire les indésirables. En savoir plus sur comment les données de vos commentaires sont utilisées.