Pgina 1 de 4
AWR & Statspack Report
Analyzer
Your report never leaves your PC, keeping your information confidential.
Note: This tool will NOT accept HTML-formatted AWR reports.
Please generate a plain text AWR report using the awrrpt.sql command:
root> $ORACLE_HOME/rdbms/admin/awrrpt.sql
WORKLOAD REPOSITORY report for
DB Name
DB Id
Instance
Inst Num Startup
Time
Release
RAC
------------ ----------- ------------ -------- -------------
Analyze
Database Info
DB ID
3717058888
Fri Mar 13 2015 10:52:19 GMT+0100 (Hora estndar romance)
Instance
Release
RAC
Host
HERMES
11.2.0.3.0
NO
undefined
Elapsed:
60.05 (min)
3,603 (sec)
DB Time:
23.02 (min)
1,381 (sec)
Cache:
880 MB
Block Size:
8,192 bytes
Transactions: 0.2 per second
Performance Summary
Physical Reads:
5/sec
MB per second:
0.04 MB/sec
Physical Writes:
35/sec
MB per second:
0.27 MB/sec
Single-block Reads:
4.97/sec
Avg wait:
2.18 ms
Multi-block Reads:
0.01/sec
Avg wait:
0 ms
Tablespace Reads:
5/sec
http://burleson-dba.com/SP/
Writes:
18/sec
13/03/2015
Pgina 2 de 4
Top 5 Events
Event
Percentage of Total Timed Events
DB CPU
91.6%
log file sync
8.7%
db file sequential read
2.8%
SQL*Net message to client
.2%
direct path read
.1%
Tablespace I/O Stats
Tablespace
Read/s Av Rd(ms) Blks/Rd Writes/s Read% % Total IO
INDEX_HERMES
3.2
16
13%
78.61%
DATOS_HERMES
1.2
71%
16.68%
UNDOTBS1
0%
2.81%
SYSAUX
0.9
1.5
56%
1.65%
Load Profile
Logical reads:
3,723/s
Parses:
0.8/s
Physical reads:
5/s
Hard parses:
Physical writes:
35/s
Transactions:
Rollback per transaction:
?%
0/s
0.2/s
Buffer Nowait:
100%
100%
0 Recommendations:
Instance Efficiency
Buffer Hit:
99.86%
In-memory Sort:
Library Hit:
99.99%
Latch Hit:
99.98%
Memory Usage:
88.53%
Memory for SQL:
96.82%
0 Recommendations:
Wait Events
Event
Waits
Wait Time (s)
Avg Wait (ms)
Waits/txn
log file sync
20,126
120
23.2
http://burleson-dba.com/SP/
13/03/2015
Pgina 3 de 4
db file sequential read
17,905
39
20.7
1,720,047
1,986.2
direct path read
189
10
0.2
log buffer space
398
0.0
SQL*Net more data from cli
462
0.5
SQL*Net more data to clien
506
0.6
30
0.0
undo segment extension
0.0
Disk file operations I/O
63
0.1
SQL*Net message to client
db file scattered read
1 Recommendations:
You have a high value for log file sync waits at 23.2 per transaction. Check to ensure that your
application does frequent commits and consider moving your redo log files to the Write
Accelerator. Also consider increasing your log_buffer size.
Instance Activity Stats
Statistic
Total
per Second
per Trans
consistent gets
5,439,414
1,509.7
6,281.1
consistent gets - examination
2,734,365
758.9
3,157.5
db block changes
4,084,752
1,133.7
4,716.8
execute count
1,652,059
458.5
1,907.7
parse count (hard)
48
0.0
0.1
parse count (total)
2,940
0.8
3.4
19,570
5.4
22.6
516
0.1
0.6
127,934
35.5
147.7
511
0.1
0.6
22,803
6.3
26.3
9,061
2.5
10.5
0.0
0.0
107,194
29.8
123.8
table fetch continued row
0.0
0.0
table scans (long tables)
0.0
0.0
table scans (short tables)
50,995
14.2
58.9
0.0
0.0
physical reads
physical reads direct
physical writes
physical writes direct
redo writes
session cursor cache hits
sorts (disk)
sorts (memory)
workarea executions - onepass
2 Recommendations:
You have high update activity with 1,133.7 db block changes per second. The DB block changes
are a rough indication of total database work. This statistic indicates (on a per-transaction level)
the rate at which buffers are being dirtied and you may want to optimize your database writer
http://burleson-dba.com/SP/
13/03/2015
Pgina 4 de 4
(DBWR) process. You can determine which sessions and SQL statements have the highest db
block changes by querying the v$session and v$sessatst views.
You have high small table full-table scans, at 14.2 per second. Verify that your KEEP pool is
sized properly to cache frequently referenced tables and indexes. Moving frequently-referenced
tables and indexes to SSD or the WriteAccelerator will significantly increase the speed of smalltable full-table scans.
SQL Statistics
Click here to see all SQL data
Buffer Pool Advisory
Current:
13,624 disk reads
Optimized:
10,559 disk reads
Improvement:
22.5% fewer
The Oracle buffer cache advisory utility indicates 13,624 disk reads during the sample interval.
Oracle estimates that doubling the data buffer size (by increasing db_cache_size) will reduce disk
reads to 10,559, a 22.5% decrease.
Init.ora Parameters
Parameter
Value
db_block_size
8,192
db_32k_cache_size
512MB
session_cached_cursors
500
_optimizer_cost_model
choose
cursor_sharing
exact
2 Recommendations:
You are not using your KEEP pool to cache frequently referenced tables and indexes. This may
cause unnecessary I/O. When configured properly, the KEEP pool guarantees full caching of
popular tables and indexes. Remember, an average buffer get is often 100 times faster than a disk
read. Any table or index that consumes > 10% of the data buffer, or tables & indexes that have >
50% of their blocks residing in the data buffer should be cached into the KEEP pool. You can
fully automate this process using scripts.
Consider setting your optimizer_index_caching parameter to assist the cost-based optimizer. Set
the value of optimizer_index_caching to the average percentage of index segments in the data
buffer at any time, which you can estimate from the v$bh view.
http://burleson-dba.com/SP/
13/03/2015
