Sorry about the cross/multi post guys. Chastiment duly accepted!
I will try to answer all posts in this response.
1.. Data is pulled from one server to another in the daily batch process
but the process to which I refer does not include any external file
processing
2.. The decision to change the disks and NICs was management's.
3.. The database layout change was necessary as the SAN was reallocated
and a SCSI array assigned in its stead. (I know, this is another cause for
concern ...)
4.. Operating system is W2k with SP4 and Oracle 9.2.0.4.0
5.. I am analyzing the trace file (with TKPROF) and reviewing the
STATSPACK output file
Tony
"Tony" <trindata_at_bellsouth.net> wrote in message
news:Ildlf.19132$wi2.16460_at_bignews1.bellsouth.net...
> After devoting a great deal of effort to tune a particular batch process
> some physical changes were made to our environment. The result is that
> our
> batch job now takes twice the amount of time to execute (7 hours instead
> of
> 3.5!)..
>
>
>
> The changes made were as follows:
>
> 1.. 1 GB Nics were replaced by 100 MB cards
> 2.. 15k rpm smaller drives were replaced by larger 10k rpm drives
> 3.. Disk layouts were changed to make use of the larger drives
> Other than that, the application has not been changed. The operating
> system
> and Oracle release have not been upgraded either. I am trying to make a
> case for returning the environment to its previous state (Nics and drive
> speed) while collecting information using in-house tools such as
> Statspack,
> TKPROF etc. In the absence of detailed analysis of the previous runs (3.5
> hours) what can I use to highlight the negative impact of the changes made
> to our environment?
>
>
Received on Tue Dec 06 2005 - 17:00:10 CST
