Re: parsing puzzle

  • From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
  • To: Brandon.Allen@xxxxxxxxxxx
  • Date: Fri, 9 Apr 2010 14:51:40 -0500

That seems unlikely, the wait events are consistent.  However, If you want a
short term snapshot though, run this command:

exec dbms_workload_repository.create_snapshot

at whatever interval you want.

On Fri, Apr 9, 2010 at 2:22 PM, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx>wrote:

> Because they report instance-wide stats, they could be showing you wait
> events for processes that are completely unrelated to the problems you're
> trying to troubleshoot.  And also since they are (usually) at infrequent
> intervals, transient problems can easily be buried by other more persistent
> events.  For example, a session that hangs for 5 minutes blocked by another
> transaction's blocking lock - this 5 minute delay could be a major problem
> for some business critical function that you're trying to troubleshoot, but
> if you look at an AWR report over a 1 hour interval, those 5 minutes of
> waiting on the blocking lock/enqueue aren't likely to show up in your top
> wait events.
> Regards,
> Brandon
> -----Original Message-----
> From: Joe A-C [mailto:jwc7744@xxxxxxxxx]
> Why do you say that the AWR reports are likely to be misleading?
> Privileged/Confidential Information may be contained in this message or
> attachments hereto. Please advise immediately if you or your employer do not
> consent to Internet email for messages of this kind. Opinions, conclusions
> and other information in this message that do not relate to the official
> business of this company shall be understood as neither given nor endorsed
> by it.
> --

Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

Other related posts: