For example, has the operating system software, hardware, application software, or Oracle Database release been upgraded? Has more data been loaded into the system, or has the data volume or user population grown?Īt the end of this phase, you should have a good understanding of the symptoms. This may narrow the potential cause quickly. Identify what has changed since performance was acceptable. How much worse are the timings than when the program was running well? Find a consistently reproducible measure of the response time or job run time. This helps identify the extent of the problem and also acts as a measure for comparison when deciding whether changes implemented to fix the problem have actually made an improvement. Is the problem only evident during peak hours? Does performance deteriorate over the course of the day? Was the slowdown gradual (over the space of months or weeks) or sudden? Identify the time frame when the problem occurs.

What is affected by the slowdown? For example, is the whole instance slow? Is it a particular application, program, specific operation, or a single user?

What is the measure of acceptable performance? How many transactions an hour, or seconds, response time will meet the required performance level? The data gathered during this stage helps determine the next step to take and what evidence to examine. Without this understanding, it is virtually impossible to implement effective changes. It is vital to develop a good understanding of the purpose of the tuning exercise and the nature of the problem before attempting to implement a solution.

Wise disk cleaner 10.2.4