RE: baselines before moving to a new server
Date: Tue, 23 Dec 2008 18:20:17 -0500
Getting plans for the queries that constitute the bulk of your workload is useful, especially if a reasonable number of queries constitute the workload.
The tricky part is that queries that currently have good plans that may change to an inefficient plan in the move might not currently show up as much. So if you can keep your old server around for a while it can be very useful to get the plan for a query that has become a problem on the new server on the old environment.
Being able to relatively quickly slap a hint on a query that has gone south in the new environment or collect a column histogram or whatever can help stem the notion that the new environment is "no good." Then you can make more scientific case by case improvements divorced from the psychological link to the change in systems.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Ram Raman
Sent: Tuesday, December 23, 2008 5:32 PM To: ORACLE-L
Subject: baselines before moving to a new server
We will be moving to a new server in future. Before we make the move, I plan to take some snaps of awr during peak and reporitng hours at 30 min interval to compare the performance after the move. I have requested Unix admin to get snapshots of basic OS statistics like IO activity, CPU activity and memory usage. Is there anything else we need to consider. We will be moving to the same version of Oracle and application with a better capacity hardware.