单实例，DML的时候耗时慢，附AWR。

xltxb

公司办公平台，今天在保存数据的时候要等待的时间大概在10秒左右，比较异常，以前都是点完保存在1秒内就保存成功了。检查网络和系统都是正常的，麻烦帮忙分析下，谢谢！

xifenfei

该awr报告周期太长，无参考意义

Snap Id        Snap Time        Sessions        Cursors/Session
Begin Snap:        9805        06-11月-14 00:00:43        33        10.4
End Snap:        9844        07-11月-14 15:00:15        36        8.5
Elapsed:                 2,339.55 (mins)                  
DB Time:                 111.82 (mins)                  

xltxb

分时段的附件

xifenfei

DB Name	DB Id	Instance	Inst num	Release	RAC	Host
ZKBR	1353673763	zkbr	1	10.2.0.3.0	NO	WIN-YKALZWHQ3EQ

	Snap Id	Snap Time	Sessions	Cursors/Session
Begin Snap:	9843	07-11月-14 14:00:02	32	8.8
End Snap:	9844	07-11月-14 15:00:15	36	8.5
Elapsed:		60.22 (mins)
DB Time:		3.57 (mins)

Report Summary

Cache Sizes

	Begin	End
Buffer Cache:	280M	280M	Std Block Size:	8K
Shared Pool Size:	436M	436M	Log Buffer:	6,928K

Load Profile

	Per Second	Per Transaction
Redo size:	1,263.02	5,215.40
Logical reads:	1,756.01	7,251.12
Block changes:	7.10	29.32
Physical reads:	0.22	0.89
Physical writes:	0.67	2.75
User calls:	7.91	32.66
Parses:	5.64	23.30
Hard parses:	0.70	2.88
Sorts:	3.72	15.35
Logons:	0.04	0.16
Executes:	9.46	39.08
Transactions:	0.24

% Blocks changed per Read:	0.40	Recursive Call %:	83.26
Rollback per transaction %:	3.66	Rows per Sort:	62.73

Instance Efficiency Percentages (Target 100%)

Buffer Nowait %:	100.00	Redo NoWait %:	100.00
Buffer Hit %:	99.99	In-memory Sort %:	100.00
Library Hit %:	91.34	Soft Parse %:	87.62
Execute to Parse %:	40.39	Latch Hit %:	100.00
Parse CPU to Parse Elapsd %:	92.28	% Non-Parse CPU:	89.26

Shared Pool Statistics

	Begin	End
Memory Usage %:	74.84	69.97
% SQL with executions>1:	87.24	78.02
% Memory for SQL w/exec>1:	87.00	73.92

Top 5 Timed Events

Event	Waits	Time(s)	Avg Wait(ms)	% Total Call Time	Wait Class
CPU time		133		61.9
control file sequential read	43,798	10	0	4.8	System I/O
db file sequential read	703	4	5	1.6	User I/O
control file parallel write	1,235	1	1	.6	System I/O
db file parallel write	1,433	0	0	.2	System I/O

我看了这几分awr，都是上述类似的情况，数据库负载非常低，从awr中无法看出来系统异常，你尝试收集那故障极端时间内的ash 看看是否有发现