RE: Drop Index takes longer in Prod than in Test
- From: "Khemmanivanh, Somckit" <somckit.khemmanivanh@xxxxxxxxxxxxxxxx>
- To: "David Sharples" <davidsharples@xxxxxxxxx>
- Date: Wed, 13 Sep 2006 11:42:20 -0700
The main issue with tracing is that there are many concurrently loads
during the time period -- tracing would produce massive amounts of
data...
I was thinking of looking at v$session_wait start to start with?
Statspack is a good start as well!
Thanks!
________________________________
From: David Sharples [mailto:davidsharples@xxxxxxxxx]
Sent: Wednesday, September 13, 2006 11:32 AM
To: Khemmanivanh, Somckit
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Drop Index takes longer in Prod than in Test
look at statspack for the affected time period, see if anything pops
out.
Else you are stuck with tracing - i dont seem the problem in enabling
it, multi tiered isnt a problem, just start a trace at the database
level
On 13/09/06, Khemmanivanh, Somckit
<somckit.khemmanivanh@xxxxxxxxxxxxxxxx> wrote:
The index drops can sometimes take minutes in prod -- whereas as
test of the same drop, in the test environment, takes seconds. Now
minutes might not seem like much, but there are many indexes so the
times add up.
Other related posts:
