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@xxxxxxxxx> 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 > > > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l