Re: STATSPACK in 10g

From: Kellyn Pedersen <>
Date: Tue, 9 Feb 2010 20:58:49 -0800 (PST)
Message-ID: <>

Since I have always upgraded to 10.2 so fast I made other DBA's head's spin and I have had the combined hourly statspack/AWR scenario running in multiple 10g environments, my money is on 10.1 for the bug... :)


  • On Tue, 2/9/10, Greg Rahn <> wrote:

From: Greg Rahn <> Subject: Re: STATSPACK in 10g
Date: Tuesday, February 9, 2010, 4:12 PM

In early releases of 10.1 or 10.2 (cant quite recall) there were bugs related to running both AWR and STATSPACK that could cause contention for certain latches in the sql area.  This was exacerbated by the fact that both snapshots ran at exactly the same time; at the top of the hour.  Thus it was advised not to run both of them.  I believe that these bugs have been all resolved in 11g.

On Tue, Feb 9, 2010 at 10:07 AM, Kellyn Pedersen <> wrote:
> "You have to use AWR and disable STATSPACK. "
> Why do you have to disable statspack if you are licensed for AWR?  I had both running at a previous company.  I preferred the AWR reports, being the new DBA and the other DBA was into his statspack reports, (I work with him again here at I-behavior, so he's since converted to AWR... :))  The snapshot ID's are completely different for each, use different views and I never had them interfere with each other in anyway in regards to reporting purposes...
> Please elaborate, I'm curious... Thanks!

Greg Rahn

Received on Tue Feb 09 2010 - 22:58:49 CST

Original text of this message