Re: Huge Archive generation causing instance to hang
From: Sriram Kumar <k.sriramkumar_at_gmail.com>
Date: Mon, 31 Dec 2012 09:41:32 +0800
Message-ID: <CAEq4C0cOv=4_dW4CP2Zns-9pj084eEOrofp2Us=znKCKD4-f4Q_at_mail.gmail.com>
Hi,
Not sure what version you are on. AWR might not directly indicate which segment caused high redo. if you have tuning and diagnostic license, you could query dba_hist_seg_stat for the time period to identify the segments with maximum block changes and then you could progressively drill down into dab_hist_sqlstat to identify the exact sql statements that caused the redo activity
Date: Mon, 31 Dec 2012 09:41:32 +0800
Message-ID: <CAEq4C0cOv=4_dW4CP2Zns-9pj084eEOrofp2Us=znKCKD4-f4Q_at_mail.gmail.com>
Hi,
Not sure what version you are on. AWR might not directly indicate which segment caused high redo. if you have tuning and diagnostic license, you could query dba_hist_seg_stat for the time period to identify the segments with maximum block changes and then you could progressively drill down into dab_hist_sqlstat to identify the exact sql statements that caused the redo activity
best regards
sriram kumar
On Mon, Dec 31, 2012 at 2:00 AM, Apps DBA <dbaorapps_at_gmail.com> wrote:
> Hi Gurus,
> I am a newbie in reading AWR and concluding the issue lies at some point.
> Would require your advice in knowing where the issue lies during my
> production hung due to high archive generation today? Basically, redo
> generation bumped up caused the alerting mechanism to fail resulting in
> instances hung state. Please help me in understanding and analyzing the AWR
> report.
>
> Thanks,
> RK
>
>
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Dec 31 2012 - 02:41:32 CET