DataBase Performance ST04

1. Data Buffer
Data base buffer pool size
The size of the database buffer pool, which holds the database blocks in the working storage and
therefore, reduces time-consuming hard disk accesses.
Quality of database buffer pool
The quality specifies how high the percentage of the reads without hard disk
accesses from the total quantity of read accesses to the database buffer pool is. A
high value indicates a good sizing of the database buffer pool there.
Database buffer reads
The number of read accesses which could be satisfied directly (without hard disk
access from the database buffer pool.
Physical reads
!umber of database blocks read physically from the hard disk.
Physical writes
!umber of database blocks written physically to the hard disk.
Buffer busy waits
!umber of access conflicts on individual database blocks in the database buffer
pool. This conflict always occurs if a process is to access a block in a mode
incompatible with the current mode.
Buffer busy wait time
The time required for buffer busy waits.
2. Shared Pool
Dictionary cache size
Size of the dictionary buffer in KB. The dictionary buffer has the function to store Data Dictionary
information which is frequently required in the working storage which facilitates the access.
Quality of Data Dictionary cache
Quality of the Data Dictionary Cache in racle!. This "alue s#ecifies how frequently the $%C&'
Data Dictionary has to be accessed when #rocessing SQ& commands. (n the installed system) this
"alue should at least be *+,.
Getratio of SQL!" in #!$L"%
-it rate for the number of requests of ob.ects which are managed in the library cache of racle!. %
high "alue suggests a good sizing of the shared #ool.
Pinratio of SQL!" in #!$L"%
-it rate for the number of e/ecutions of ob.ects) which are managed in the library cache of racle!.
% high "alue indicates a good sizing of the shared #ool.
SQL area reloads &'( from )*librarycache
+. Lo, Buffers
!edo lo, buffer size
Size of the redo log buffer in KB. (n the redo log buffer) all changes to the database are logged.
!edo lo, buffer entries
The number of entries in the redo log buffer.
!edo lo, buffer allocation retries
0requency) with which a user #rocess could not allocate sufficient s#ace in the redo log buffer and
had to start a further attem#t. This case can then occur if the redo writer is working less efficiently
or if an e"ent occurs such as a logswitch.
llocation error rate of redo lo, buffer
The #ercentage of aborted allocation attem#ts 1allocation fault2 from the total quantity of entries in
the redo log buffer 1entries2.
!edo lo, space wait time &s( from )*sysstat
!edo lo, file problems &from )*lo,files(
3umber of redo log files4 in #arentheses5 number of redo log files with status 6(378S'6. S%9
recommends at least two redo log files. %ll files must be 6(378S'6. 0or further information see5
:;&<0(&' 1double click2
-. $alls
.ser calls
The number of user calls started for the database.
$ommits
The number of commits carried out 1finished transactions2.
!ollbac/s
The number of the e/ecuted rollbacks 1rolling back incom#lete transactions2.
!ecursi)e calls
3umber of recursi"e database calls. % high "alue indicates that information was frequently not
found in the dictionary buffer. The dictionary buffer may be sized too small or has been #arsed too
many times.
Parses
3umber of #arse runs. This number should be reduced by a##lication tuning if #ossible.
ratio of user to recursi)e calls in oracle % monitor
ratio of reads to user calls in 0racle %
1. 2ime Statistics
3. !edo Lo,,in,
!edo lo, writes
The number of write o#erations which were e/ecuted on the redo log file. % database background
#rocess) the logwriter) cyclically transfers the contents of the redo log buffer into the redo log file.
!edo lo, bloc/s written
3umber of blocks which were written into the redo log file.
!edo lo, latchin, time
The time which the logwriter #rocess needed to recei"e and release the necessary latches 1short=
term locks of data structures2 to the redo log.
!edo lo, write time
The time in milliseconds which was needed for writing to the redo log file.
!edo lo, write size
The number of >B which were written into the redo log file.
%. 2able Scan 4 5etches
Short table scans
3umber of read accesses to tables with a ma/imum size of ? database blocks.
Lon, table scans
3umber of read accesses to tables is larger than ? database blocks.
2able fetch by row 6D
The number of blocks which were read "ia the $@(D. The $@(D is a logical byte address which
identifies e"ery data record in the database and links it with the inde/ "alue.
2able fetch continued row
3umber of accesses to concatenated database blocks 1 row chaining 2. The number should be as
low as #ossible) otherwise) the affected tables should be reorganized.
7. S#!2S
Sort memory
The number of sorting o#erations which could be carried out in the memory .
Sort dis/
The number of sorting o#erations which were carried out on the hard disk in the tem#orary
segments #ro"ided for this. This is necessary if sorting o#erations cannot be handled com#letely in
the memory.
Sort rows
3umber of the lines which were sorted.