Oracle 10 Gb use ASH to generate performance report

Report Content: TOP wait event, top SQL, top SQL command type, TOP Session content.

Specific implementation methods:
SQL> @ $ Oracle_HOME/rdbms/admin/ashrpt. SQL

Current Instance
~~~~~~~~~~~~~~~~

DB Id DB Name Inst Num Instance
-------------------------------------------
631770879 ORA10 1 ora10

 

Specify the Report Type
~~~~~~~~~~~~~~~~~~~~~~~
Enter 'html' for an html report, or 'text' for plain text
Ults to 'html'
Enter value for report_type: text -- type of the report file generated by the input

Type Specified: text

Instances in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~

DB Id Inst Num DB Name Instance Host
--------------------------------------------------------
* 631770879 1 ORA10 ora10 linux

Ults to current database

Using database id: 631770879

Ults to current instance

Using instance number: 1

ASH Samples in this Workload Repository schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~

Oldest ASH sample available: 12-Mar-08 12:22:57 [10246 mins in the past]
Latest ASH sample available: 19-Mar-08 15:05:08 [4 mins in the past]

Specify the timeframe to generate the ASH report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~
Enter begin time for report:

-- Valid input formats:
-- To specify absolute begin time:
-- [MM/DD [/YY] HH24: MI [: SS]
-- Examples: 02/23/03 14:30:15
-- 14:30:15, 02/23
-- 14:30:15
-- 14: 30
-- To specify relative begin time: (start with '-' sign)
-- [HH24:] MI
-- Examples:-(SYSDATE-1 Hr 15 Mins)
---25 (SYSDATE-25 Mins)

Defaults to-15 mins
Enter value for begin_time: -- input Start Time
Report begin time specified:

Enter duration in minutes starting from begin time:
Defaults to SYSDATE-begin_time
Press Enter to analyze till current time
Enter value for duration: 20 -- Enter the time interval for Statistics
Report duration specified: 20

Using 19-Mar-08 14:40:00 as report begin time
Using 19-Mar-08 15:00:00 as report end time

Specify Slot Width (using ashrpti. SQL) for 'activity Over time' section
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- Explanation:
-- In the 'Activity Over time' section of the ASH report,
-- The analysis period is divided into smaller slots
-- And top wait events are reported in each of those slots.

-- Default:
-- The analysis period will be automatically split upto 10 slots
-- Complying to a minimum slot width
-- 1 minute, if the source is V $ ACTIVE_SESSION_HISTORY or
-- 5 minutes, if the source is DBA_HIST_ACTIVE_SESS_HISTORY.

Specify Slot Width in seconds to use in the 'Activity Over time' section:
Defaults to a value as fig:
Slot Width specified:

Specify Report Targets (using ashrpti. SQL) to generate the ASH report
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- Explanation:
-- ASH Report can accept "Report Targets ",
-- Like a participant SQL statement, or a participant SESSION,
-- To generate the report on. If one or more report targets are
-- Specified, then the data used to generate the report will only be
-- The ASH samples that pertain to ALL the specified report targets.

-- Default:
-- If none of the report targets are specified,
-- Then the target defaults to all activity in the database instance.

Specify SESSION_ID (eg: from V $ SESSION. SID) report target:
Defaults to NULL:
SESSION report target specified:

Specify SQL _ID (eg: from V $ SQL. SQL _ID) report target:
Defaults to NULL: (% and _ wildcards allowed)
SQL report target specified:

Specify WATI_CLASS name (eg: from V $ EVENT_NAME.WAIT_CLASS) report target:
[Enter 'cpu 'to ststigate CPU usage]
Defaults to NULL: (% and _ wildcards allowed)
WAIT_CLASS report target specified:

Specify SERVICE_HASH (eg: from V $ ACTIVE_SERVICES.NAME_HASH) report target:
Defaults to NULL:
SERVICE report target specified:

Specify MODULE name (eg: from V $ SESSION. MODULE) report target:
Defaults to NULL: (% and _ wildcards allowed)
MODULE report target specified:

Specify ACTION name (eg: from V $ SESSION. ACTION) report target:
Defaults to NULL: (% and _ wildcards allowed)
ACTION report target specified:

Specify CLIENT_ID (eg: from V $ SESSION. CLIENT_IDENTIFIER) report target:
Defaults to NULL: (% and _ wildcards allowed)
CLIENT_ID report target specified:

EXT
----
. Txt

 

Specify the Report Name
~~~~~~~~~~~~~~~~~~~~~~~
The default report file name is ashrpt_20170319_1500.txt. To use this name,
Press <return> to continue, otherwise enter an alternative.
Enter value for report_name: -- press Enter here or change the file name.

Using the report name ashrpt_20170319_1500.txt

Summary of All User Input
-------------------------
Format: TEXT
DB Id: 631770879
Inst num: 1
Begin time: 19-Mar-08 14:40:00
End time: 19-Mar-08 15:00:00
Slot width: Default
Report targets: 0
Report name: ashrpt_20170319_1500.txt

The report is as follows:

Oracle @ linux:/SERVER/soft> cat ashrpt_20170319_1500.txt

ASH Report For ORA10/ora10

DB Name DB Id Instance Inst Num Release RAC Host
---------------------------------------------------------------------
ORA10 631770879 ora10 1 10.2.0.1.0 NO linux

CPUs SGA Size Buffer Cache Shared Pool ASH Buffer Size
----------------------------------------------------------------------------
1 160 M (100%) 72 M (45.0%) 68 M (42.5%) 2.0 M (1.3%)

Analysis Begin Time: 19-Mar-08 14:40:00
Analysis End Time: 19-mar-08 15:00:00
Elapsed Time: 20.0 (mins)
Sample Count: 29
Average Active Sessions: 0.02
Avg. Active Session per CPU: 0.02
Report Target: None specified

Top User Events DB/Inst: ORA10/ora10 (Mar 19)

Avg Active
Event Class % Activity Sessions
----------------------------------------------------------------------
CPU + Wait for CPU 51.72 0.01
Db file sequential read User I/O 6.90 0.00
Null event Other 6.90 0.00
-------------------------------------------------------------

Top Background Events DB/Inst: ORA10/ora10 (Mar 19)

Avg Active
Event Class % Activity Sessions
----------------------------------------------------------------------
CPU + Wait for CPU 17.24 0.00
OS thread startup Concurrency 17.24 0.00
Activity Over Time DB/Inst: ORA10/ora10 (Mar 19)
-> Analysis period is divided into smaller time slots
-> Top 3 events are reported in each of those slots
-> 'Slot count' shows the number of ASH samples in that Slot
-> 'Event count' shows the number of ASH samples waiting
That event in that slot
-> '% Event' is 'event count' over all ASH samples in the analysis period

Slot Event
Slot Time (Duration) Count Event Count % Event
-------------------------------------------------------------------------
14:40:00 (2.0 min) 15 CPU + Wait for CPU 14 48.28
Db file sequential read 1 3.45
14:42:00 (2.0 min) 5 CPU + Wait for CPU 3 10.34
OS thread startup 2 6.90
14:44:00 (2.0 min) 3 db file sequential read 1 3.45
Null event 1 3.45
OS thread startup 1 3.45
14:46:00 (2.0 min) 3 OS thread startup 2 6.90
CPU + Wait for CPU 1 3.45
14:50:00 (2.0 min) 1 CPU + Wait for CPU 1 3.45
14:56:00 (2.0 min) 1 CPU + Wait for CPU 1 3.45
14:58:00 (2.0 min) 1 null event 1 3.45
-------------------------------------------------------------
End of Report

Note: The ASH information is based on V $ SESSION. sampling is performed once per second to record the event waiting for the Active SESSION. You can access the relevant information in the V $ ACTIVE_SESSION_HISOTRY view.

For more information about Oracle, see Oracle topics page http://www.bkjia.com/topicnews.aspx? Tid = 12