Re: AWR Report

Hi,
Next time before restart the server that is hanging, don't forget to run a systemstate and ashdump.
I keep commands on had there:
http://blog.dbi-services.com/oracle-is-hanging-dont-forget-hanganalyze-and-systemstate/ Regards,
Franck.
Franck Pachot | Senior Consultant & Oracle Technology Leader | Oracle Certified Master 12*c* and Oracle ACE Director

On Mon, Jul 11, 2016 at 11:58 PM Kellyn Pot'Vin-Gorman <dbakevlar_at_gmail.com> wrote:

> Could I recommend running an ASH at the time of the incident? ASH is a
> great way to get a view of the environment at small units of time and to
> see what was going on at that time. ADDM and AWR do rely on snapshots,
> where ASH will run against the samples which are collected all the time.
>
> Hope this helps,
> Kellyn
>
> On Jul 11, 2016, at 1:55 PM, <fmhabash_at_gmail.com> <fmhabash_at_gmail.com>
> wrote:
>
> Whatever this query tells you
>
> select startup_time, min(snap_id), max(snap_id) from dba_hist_snapshot
> group by startup_time
>
> STARTUP_TIME MIN(SNAP_ID) MAX(SNAP_ID)
> ------------ ------------ ------------
> 7/8/2016 1:1 84508 84974
> 5/26/2016 7: 82251 84507
> 12/11/2015 4 80058 82250
>
>
> ----------------------------------------
> Thank you
>
> *From: *David Ramírez Reyes <dramirezr_at_gmail.com>
> *Sent: *Monday, July 11, 2016 3:06 PM
> *To: *'oracle-l_at_freelists.org' (oracle-l_at_freelists.org)
> <oracle-l_at_freelists.org>
> *Subject: *AWR Report
>
> Hello all,
>
> RHEL 5, 11g R2
>
> DB was hung at 10:15 am; am trying to get an AWR Report from 10 to 10:30
> am but the package failed because there was a shutdown in the midle (the DB
> was restarted to become online again).
>
> Do any know if there's a way to generate the AWR Report from 10:00 am to
> the time the last statistic was generated?
>
> The files are sequencial and does not let me get it:
>
> Using 3097553944 for database Id
> Using 1 for instance number
>
> Specify the number of days of snapshots to choose from
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Entering the number of days (n) will result in the most recent
> (n) days of snapshots being listed. Pressing <return> without
> specifying a number lists all completed snapshots.
>
> Enter value for num_days: 1
> Listing the last day's Completed Snapshots
> Snap
> Instance DB Name Snap Id Snap Started Level
> ------------ ------------ --------- ------------------ -----
> KMMMESV1P KMMMESV1 14356 11 Jul 2016 00:00 1
> 14357 11 Jul 2016 00:30 1
> 14358 11 Jul 2016 01:00 1
> 14359 11 Jul 2016 01:30 1
> 14360 11 Jul 2016 02:00 1
> 14361 11 Jul 2016 02:30 1
> 14362 11 Jul 2016 03:00 1
> 14363 11 Jul 2016 03:30 1
> 14364 11 Jul 2016 04:00 1
> 14365 11 Jul 2016 04:30 1
> 14366 11 Jul 2016 05:00 1
> 14367 11 Jul 2016 05:30 1
> 14368 11 Jul 2016 06:00 1
> 14369 11 Jul 2016 06:30 1
> 14370 11 Jul 2016 07:00 1
> 14371 11 Jul 2016 07:30 1
> 14372 11 Jul 2016 08:00 1
> 14373 11 Jul 2016 08:30 1
> 14374 11 Jul 2016 09:00 1
> 14375 11 Jul 2016 09:30 1
> 14376 11 Jul 2016 10:00 1
> 14377 11 Jul 2016 10:36 1
> 14378 11 Jul 2016 11:00 1
> 14379 11 Jul 2016 11:30 1
> 14380 11 Jul 2016 12:00 1
> 14381 11 Jul 2016 12:30 1
> 14382 11 Jul 2016 13:00 1
> 14383 11 Jul 2016 13:30 1
> 14384 11 Jul 2016 14:00 1
>
> Specify the Begin and End Snapshot Ids
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Enter value for begin_snap: 14376
> Begin Snapshot Id specified: 14376
> Enter value for end_snap: 14377
> End Snapshot Id specified: 14377
>
> declare
> *
> ERROR at line 1:
> ORA-20200: The instance was shutdown between snapshots 14376 and 14377
> ORA-06512: at line 42
>
>
>
> David Ramírez Reyes
> Profesión: Padre de Familia y DBA en mis ratos libres
> Profession: Parent and DBA in my spare time
>
>
>

--
http://www.freelists.org/webpage/oracle-l