ASH Report 解析

其他 2018-10-24 03:34:54 阅读次数: 0

 

ASH Report For EDADBT/edadbt

DB Name DB Id Instance Inst num Release RAC Host
EDADBT 1157804911 edadbt 1 12.2.0.1.0 NO p1edadb01t
CPUs SGA Size Buffer Cache Shared Pool ASH Buffer Size In-memory Area Size
4 9,632M (100%) 7,776M (80.7%) 884M (9.2%) Not Available 0.0M (0.0%)
  Sample Time Data Source
Analysis Begin Time: 05-Sep-18 12:00:00 DBA_HIST_ACTIVE_SESS_HISTORY
in AWR snapshot 4532
Analysis End Time: 05-Sep-18 23:59:59 DBA_HIST_ACTIVE_SESS_HISTORY
in AWR snapshot 4533
+ V$ACTIVE_SESSION_HISTORY
Elapsed Time: 720.0 (mins)  
Sample Count: 3,307  
Average Active Sessions: 0.77  
Avg. Active Session per CPU: 0.19  
Report Target: None specified  

ASH Report


Back to Top

Top Events

Back to Top

Top User Events

Event Event Class % Event Avg Active Sessions
CPU + Wait for CPU CPU 80.22 0.61
db file sequential read User I/O 11.10 0.08
db file parallel read User I/O 2.90 0.02
direct path read temp User I/O 1.57 0.01

这一部分是用户会话的等待事件的信息。列出了采样时段内数据库发生的显著用户等待！

Top Background Events

Event Event Class % Activity Avg Active Sessions
db file async I/O submit System I/O 1.15 0.01

Back to Top Events
Back to Top

Top Event P1/P2/P3 Values

Event % Event P1 Value, P2 Value, P3 Value % Activity Parameter 1 Parameter 2 Parameter 3
db file sequential read 11.19 "1","1449","1" 0.03 file# block# blocks
db file parallel read 2.90 "3","128","128" 0.82 files blocks requests
direct path read temp 1.57 "207","765696","64" 0.03 file number first dba block cnt
db file async I/O submit 1.15 "2004","0","0" 0.06 requests interrupt timeout

这部分信息显示了在抽样会话活动中占很高百分比的等待事件的参数值它通过总的等待时间(%Event)百分比进行排序后被显示.对于每一个等待事件p1,p2,p3的值与等待事件参数parameter

Load Profile

Back to Top

Top Service/Module

Service Module % Activity Action % Action
SYS$USERS UNNAMED 64.47 UNNAMED 64.47
edadbt JDBC Thin Client 32.30 UNNAMED 32.30
SYS$BACKGROUND UNNAMED 1.94 UNNAMED 1.94

这部分信息显示了在抽样会话活动中占很高百分比的服务和模块信息

Top Client IDs

No data exists for this section of the report.

这部分信息显示了在抽样会话活动中占很高百分比的客户端的id信息它是数据库会话中应用程序的特定标识符

Top SQL Command Types

  • 'Distinct SQLIDs' is the count of the distinct number of SQLIDs with the given SQL Command Type found over all the ASH samples in the analysis period
SQL Command Type Distinct SQLIDs % Activity Avg Active Sessions
PL/SQL EXECUTE 17 64.95 0.50
SELECT 81 17.72 0.14
INSERT 74 12.97 0.10

这部分信息显示了在抽样会话活动中占很高百分比的sql命令类型比如select或update

Top Phases of Execution

Phase of Execution % Activity Avg Active Sessions
SQL Execution 96.10 0.74
Java Execution 64.47 0.49

Back to Load Profile
Back to Top

Top SQL

Back to Top

Top SQL with Top Events

SQL ID FullPlanhash Planhash Sampled # of Executions % Activity Event % Event Top Row Source % RwSrc SQL Text
0sbv4vu4qscxu     1 21.08 CPU + Wait for CPU 21.08 ** Row Source Not Available ** 21.08 DECLARE job BINARY_INTEGER := ...
3mvuvwgyu1chg     1 21.08 CPU + Wait for CPU 21.08 ** Row Source Not Available ** 21.08 DECLARE job BINARY_INTEGER := ...
8kkrj1sdcak68     1 11.37 CPU + Wait for CPU 11.37 ** Row Source Not Available ** 11.37 DECLARE job BINARY_INTEGER := ...
6ykr736rxbadn     1 9.71 CPU + Wait for CPU 9.71 ** Row Source Not Available ** 9.71 DECLARE job BINARY_INTEGER := ...
c0z5w1ptawhmw 1988401559 570450625 103 3.18 CPU + Wait for CPU 2.48 INDEX - RANGE SCAN 2.48 SELECT COUNT(*) FROM CF_CHAMBE...

这部分安装sql的活动频度列出了前6位的sql语句。空值说明没有采样到数据。

Top SQL with Top Row Sources

SQL ID FullPlanHash PlanHash Sampled # of Executions % Activity Row Source % RwSrc Top Event % Event SQL Text
0sbv4vu4qscxu     1 21.08 ** Row Source Not Available ** 21.08 CPU + Wait for CPU 21.08 DECLARE job BINARY_INTEGER := ...
3mvuvwgyu1chg     1 21.08 ** Row Source Not Available ** 21.08 CPU + Wait for CPU 21.08 DECLARE job BINARY_INTEGER := ...
8kkrj1sdcak68     1 11.37 ** Row Source Not Available ** 11.37 CPU + Wait for CPU 11.37 DECLARE job BINARY_INTEGER := ...
6ykr736rxbadn     1 9.71 ** Row Source Not Available ** 9.71 CPU + Wait for CPU 9.71 DECLARE job BINARY_INTEGER := ...
c0z5w1ptawhmw 1988401559 570450625 103 3.18 INDEX - RANGE SCAN 3.18 CPU + Wait for CPU 2.48 SELECT COUNT(*) FROM CF_CHAMBE...

Back to Top SQL
Back to Top

Top SQL using literals

No data exists for this section of the report.

这部分列出了一些未绑定变量的sql。

Top Parsing Module/Action

No data exists for this section of the report.

Back to Top SQL
Back to Top

Complete List of SQL Text

SQL Id SQL Text
0sbv4vu4qscxu DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN tyne_job_util.run_job(289); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
3mvuvwgyu1chg DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN tyne_job_util.run_job(237); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
6ykr736rxbadn DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN tyne_job_util.run_job(230); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
8kkrj1sdcak68 DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN tyne_job_util.run_job(236); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
c0z5w1ptawhmw SELECT COUNT(*) FROM CF_CHAMBER_HST_T WHERE STEP_ID = :B6 AND GLASS_ID = :B5 AND EQUIP_ID = :B4 AND SUB_EQUIP_ID = :B3 AND GLASS_START_TIME BETWEEN :B2 AND :B1

这部分是列出了所有的sql语句。

Top PL/SQL Procedures

  • 'PL/SQL entry subprogram' represents the application's top-level entry-point(procedure, function, trigger, package initialization or RPC call) into PL/SQL.
  • 'PL/SQL current subprogram' is the pl/sql subprogram being executed at the point of sampling . If the value is 'SQL', it represents the percentage of time spent executing SQL for the particular plsql entry subprogram
PLSQL Entry Subprogram % Activity PLSQL Current Subprogram % Current
EDAAPP.TYNE_JOB_UTIL.RUN_JOB 64.47 SQL 64.47
EDAAPP.DS_CELL_DATA_FETCH_UTIL.FETCH_DATA 4.05 SQL 4.05
EDALDR.CF_PDS_LOADER.LOAD_CHAMBER_HST 3.99 SQL 3.99
EDALDR.CELL2_FILE_LOADER.LOAD_DATA 3.30 SQL 3.27
EDALDR.ARRAY_PDS_LOADER.LOAD_CHAMBER_HST 3.14 SQL 3.14


Back to Top

Top Java Workload

Module % Module Entry SQL ID % Activity
  64.47 0sbv4vu4qscxu 21.08
  64.47 3mvuvwgyu1chg 21.08
  64.47 8kkrj1sdcak68 11.37


Back to Top

Top Call Types

Call Type Count % Activity Avg Active Sessions
V8 Bundled Exec 1,025 30.99 0.24
LOGOFF 384 11.61 0.09


Back to Top

Top Sessions

Back to Top

Top Sessions

  • '# Samples Active' shows the number of ASH samples in which the session was found waiting for that particular event. The percentage shown in this column is calculated with respect to wall clock time and not total database activity.
  • 'XIDs' shows the number of distinct transaction IDs sampled in ASH when the session was waiting for that particular event
  • For sessions running Parallel Queries, this section will NOT aggregate the PQ slave activity into the session issuing the PQ. Refer to the 'Top Sessions running PQs' section for such statistics.
Sid, Serial# % Activity Event % Event User Program # Samples Active XIDs
18,33983 21.08 CPU + Wait for CPU 21.08 EDAAPP oracle@p1edadb01t (J001) 697/4,320 [ 16%] 0
407,40014 21.08 CPU + Wait for CPU 21.08 EDAAPP oracle@p1edadb01t (J000) 697/4,320 [ 16%] 0
220, 8484 11.37 CPU + Wait for CPU 11.37 EDAAPP oracle@p1edadb01t (J002) 376/4,320 [ 9%] 0
601, 9692 9.71 CPU + Wait for CPU 9.71 EDAAPP oracle@p1edadb01t (J003) 321/4,320 [ 7%] 0
405, 8989 3.21 CPU + Wait for CPU 2.60 EDALDR JDBC Thin Client 86/4,320 [ 2%] 84

这部分列出了活动最频繁的会话信息。这一部分为我们提供了非常有用的信息，那就是哪些进程活动频繁。我们通过这一部分获取到某个活动频繁的会话信息，可以通过使用ashrpti.sql来生成针对这个会话的ASH性能报告，或者可以使用sql_trace对这个会话进程跟踪。这样我们就能了解到当前这个会话正在做什么。

Top Blocking Sessions

No data exists for this section of the report.

这一部分列举了被阻塞的会话信息。

Top Sessions running PQs

No data exists for this section of the report.

这部分信息显示了哪些在抽样会话活动中占很高百分比的正处于等待的并行查询

Top Objects/Files/Latches

Back to Top

Top DB Objects

  • With respect to Application, Cluster, User I/O, buffer busy waits and In-Memory DB events only.
  • Tablespace name is not available for reports generated from the root PDB of a consolidated database.
Object ID % Activity Event % Event Object Name (Type) Tablespace
86272 2.15 db file sequential read 2.15 EDASYS.CELL_DEFECT_T_PK.P_180801 (INDEX PARTITION) EDASYS_DATA_L
112261 1.66 direct path read temp 1.57 EDAAPP.EDATOOL_DATA06_S (TABLE) SYSTEM
86275 1.54 db file sequential read 1.54 EDASYS.CELL_DEFECT_T_PK.P_180901 (INDEX PARTITION) EDASYS_DATA_L
82334 1.33 db file sequential read 1.06 EDASYS.ARRAY_GLASS_HST_T.P_180801 (TABLE PARTITION) EDASYS_DATA_M
82028 1.03 db file parallel read 1.03 EDASYS.ARRAY_CHAMBER_HST_T_PK.P_180801 (INDEX PARTITION) EDASYS_INDEX_M

Back to Top Objects/Files/Latches
Back to Top

Top DB Files

No data exists for this section of the report.

这部分信息显示了在抽样会话活动中占访问量很高百分比的数据库文件

Top Latches

No data exists for this section of the report.

这部分信息显示了在抽样会话活动中占很高百分比的闩锁信息
闩锁是一种简单低级别串行化机制用来保护sga中的共享数据结构.比如闩锁保护当前访问数据库和缓冲区缓存中数据块结构的用户列表.当维护或查找这些结构时服务器或后台进程请求持有闩锁的时间是非常短暂的.闩锁的实现依赖于操作系统特别是一个进程等待获取一个闩锁多长时间.

Activity Over Time

  • 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 for that event in that slot
  • '% Event' is 'Event Count' over all ASH samples in the analysis period
Slot Time (Duration) Slot Count Event Event Count % Event
12:00:00 (20.0 min) 452 CPU + Wait for CPU 399 12.07

12:00:00 (20.0 min)

452

 db file sequential read 20 0.60

12:00:00 (20.0 min)

452

 direct path read temp 12 0.36
12:20:00 (70.0 min) 2,114 CPU + Wait for CPU 1,774 53.64

12:20:00 (70.0 min)

2114

 db file sequential read 182 5.50

12:20:00 (70.0 min)

2114

 db file parallel read 59 1.78
13:30:00 (70.0 min) 741 CPU + Wait for CPU 509 15.39

13:30:00 (70.0 min)

741

 db file sequential read 168 5.08

13:30:00 (70.0 min)

741

 db file parallel read 35 1.06

这部分列举了各种等待的细粒度显示。
这一部分是ash报告信息最丰富的一部分.这部分信息对于长时间周期的ash报告来说因为在分析期间它提供了关于活动和工作负载概要深层次的详细信息.activity over time会被分成10个时段.每个时段的大小基于分析所持续的时间.第一个和最后一个时段是奇怪.所有内部时段是相等的大小它们可以相互比较.例如,如果分析时间持续10分钟那么所有的时段将会是每个一分钟.然后如果分析时间持续9分30秒,那么外部的时段可能是每个15秒内部的时段可能每个1分钟
特定时段中每个时段包含的信息如下:

列                               描述
slot time(持续时间)      时段的持续时间
solt count                  在时段中抽样会话的数量
event                          在时段中顶级的三个等待事件
event count                ash抽样等待的等待事件的数量
%event                       ash抽样等待的等待事件在整个分析期间所占的百分比


当比较内部时段时,通过识别异常的event count和slot count列执行一个倾斜分析.event count列的异常指示了在抽样会话中等待的等待事件数量增加了.slot count列的异常指示活动的会自豪感增加了,因为ash数据只从活动会话中进持抽样说明数据库的

猜你喜欢

转载自blog.csdn.net/MyySophia/article/details/82423117
今日推荐
周排行
Leetcode简单题61~80
解决zookeeper磁盘IO高的问题
多线程相关方法详解
Maven-setting.xml文件详解
Maven 项目的 classpath 理解
渊亭科技大数据笔试题
配置JVM内存分配
计算机网络个人学习笔记 （三）网络层 ：第三部分 连载
js中两个等号(==)和三个等号(===)的区别
用C程序自动打开电脑上的程序
每日归档
更多
2024-09-18(0)
2024-09-17(0)
2024-09-16(0)
2024-09-15(0)
2024-09-14(0)
2024-09-13(0)
2024-09-12(0)
2024-09-11(0)
2024-09-10(0)
2024-09-09(0)

代码天地 © 2018 codetd.com

境外服务器   最新电视剧2022