22234290 Awr Report Analysis

8/8/2019 22234290 Awr Report Analysis

1/43

Statspack/AWR analysis

In stead of using ratios, such as the buffer cache hit ratio, or single figures taken out of context thisdocuments shall focus on the following the equation:

response time = service time + wait time

R = S + W

which basically says that the response time perceived by the user consist ofservice timeand waittime.

The service time is the time spent by the CPU actively working on your request, and the wait time isthe time you spend waiting for some resource to respond or become available. When you e.g.execute a SQL statement that is doing some index lookup, the CPU time involved may be inprocessing blocks in the buffer cache, scanning an index block for a certain value and getting yourrequested row out of the data block. To do this, Oracle may have to read the data block from the disk,

which incurs a wait time until the disk responds. In more complex cases, you may spend CPUprocessing PL/SQL and you may wait for a lock or for Oracle to write data to the redo log file when youdo a commit.

The general idea behind this method is to identify in some detail what the components of the servicetime and the wait time are and simply order these. The component at the top is the one that should bethe first one to tune. As a result, you will not make conclusions like My buffer cache hit ratio is too low,so I better increase the cache, if I/O is not causing any trouble. And you will not say, I must reducemy 20 second latch wait time, if you are using 20 minutes of CPU processing SQL. A secondobservation in the method is that tuning something that is taking long time can be done both byreducing the time (such as using faster disks) or reducing the number of times (such as making fewerdisk reads). Hence, the steps involved in this method that we will refer to as time based tuning, aresimply:

1. Identify the service time and the wait time and the components of these

2. Order all time components

3. Start your tuning effort from the top of this list

4. For each entry in the list, either reduce the cost per execution, or the number ofexecutions

Remember to separate OLTP and Batch activity when you run STATSPACK, since they usually

generate different types of waits.

Since every system is different, the above list is a general list of things you should regularlycheck in your STATSPACK output:

Top 5 wait events (timed events)

Load profile

Instance efficiency hit ratios

Wait events

Latch waits


2/43

Top SQL

Instance activity

File I/O and segment statistics

Memory allocation

Buffer waits

Hit ratios are good indicators of the health of your system. A large increase or dropfrom day to day is an indicator of a major change that needs to be investigated.

Generally, buffer and library cache hit ratios should be greater than 95 percent forOLTP, but they could be lower for a data warehouse that genrally do many full table scans.

Tuning by wait events is one of the best possible reactive tuning methods.

The top 5 wait events reveal to you the largest issues on your system at the macro level.Rarely do they point you to a specific problem. Other parts of AWR will tell youwhy you are receiving the top 5 waits.

Tuning the top 25 buffer get and top 25 physical get queries has yielded systemperformance gains of anywhere from 5 to 5000 percent. The SQL section of theSTATSPACK report tells you which queries to potentially tune first.

The top 10 percent of your SQL statements should not be more than 10 percent of yourbuffer gets or disk reads.

If the free buffers inspected divided by the free buffer scans equals less than 1, theDB_CACHE_SIZE parameter may need to be increased.

The sorts (disk) statistic divided by the sorts (memory) should not be above 15percent. If it is, you should increase the PGA_AGGREGATE_TARGET (orSORT_AREA_SIZE)parameter in the initialization file (given that physical memory is availableto do this). Remember that the memory allocated for Sort_Area_Size is a per-user valueand PGA_AGGREGATE_TARGET is across all sessions.

Latches are like locks on pieces of memory (or memory buffers). If the latch hit ratio isbelow 99 percent, there is a serious issue, since not even the lock to get memorycould be gotten.

Segment statistics are a great way to pinpoint performance problem to a given table,index, or partition. Oracle 10gR2 contains many segment-level statistics in both the

AWR Report and STATSPACK.

If the PINHITRATIO is less than 95 percent when the report is run for an extendedperiod of time, the SHARED_POOL_SIZE is probably too small for your best systemperformance. If the reloads are greater than 1 percent, this also points to aSHARED_POOL_SIZE that is too small.

You do not set maxtrans in 10g (it defaults to 255).

Never go to the block level unless you absolutely have to go there. The block level is agreat place to find hot block and ITL issues, but it takes a lot of time and energy on thepart of an advanced DBA to pinpoint problems at this level.

The ADDM Report can be a helpful tuning utility, but ADDM is better used throughOracles Grid Control for maximum benefits.


3/43

Time Model StatisticsIn both Oracle 10.2 and Oracle 11.1 there are 19 time model statistics.

There are no differences between the time model statistics in the aforementioned versions.

The following table shows the 19 time model statistics in Oracle 11.1:

Name

background cpu time

background elapsed time

connection management call elapsed time

DB CPU

DB time

failed parse (out of shared memory) elapsed timefailed parse elapsed time

hard parse (bind mismatch) elapsed time

hard parse (sharing criteria) elapsed time

hard parse elapsed time

inbound PL/SQL rpc elapsed time

Java execution elapsed time

parse time elapsed

PL/SQL compilation elapsed time

PL/SQL execution elapsed time

repeated bind elapsed time

RMAN cpu time (backup/restore)

sequence load elapsed time

sql execute elapsed time

Time model statistics show the amount of CPU time that has been required to complete each type ofdatabase processing work.( see above table )

These statistics can be obtained by V$SESS_TIME_MODEL and V$SYS_TIME_MODEL StatisticsViews

The time model views differ from each other in that the V$SESS_TIME_MODEL view stores timinginformation forindividual sessions while the V$SYS_TIME_MODEL view provides information atinstance level. As a result, you won't find the column for SESSION_ID in the V$SYS_TIME_MODELview. In addition, V$SYS_TIME_MODEL records information historically from instance startup, sodon't be concerned if you add up all of the time spent by the current indiviudal sessions and it doesn'tmatch the DBTIME value in V$SYS_TIME_MODEL view. One last thing, use the timings as a relativereference, they may not add up exactly because of the way they are recorded by Oracle.

The most important time model statistic is DB time, which represents the total time spent by Oracle toprocess all database calls. In fact, it describes the total database workload. DB time is calculated byaggregating the CPU and all non-idle wait times for all sessions in the database after the last startup.


4/43

In other words DB time the total time spent by user processes either actively working or activelywaiting in a database call.

DB Time is the most important of the various Time Model Statistics, which break down the Servicecomponent of R = S + W into more detail.

From Oracle Slides on ASH we read :

Time spent in the Database by foreground sessions Includes CPU time, IO time and wait time Excludes idle wait time The lingua franca for performance analysis Database time is the total time spent by user processes either actively working or actively

waiting in a database call

Since it is an aggregate value, it is actually possible that the DB time statistic could be larger than thetotal instance runtime.

One common objective in Oracle performance tuning is the reduction of database workload or DB

time. This reduction can be achieved by minimizing specific components such as the sessions SQLparse and processing times, sessions wait times, etc.

DB Time shows us 'the Oracle bit' that we might be able to tune. The goal of the DB TimePerformance Method is to reduce the amount of DB Time taken to deliver the same results. So,how can we reduce DB Time here? By making the query run more quickly, whether it's through tuningit to do less work, or increasing the efficiency of that work by reducing bottlenecks. Regardless ofhowI you would have improved the performance of the query the end user's experience would haveimproved..
http://download.oracle.com/docs/cd/B19306_01/server.102/b28051/tdppt_method.htm#TDPPT008http://download.oracle.com/docs/cd/B19306_01/server.102/b28051/tdppt_method.htm#TDPPT008


5/43


6/43

Buffer NoWait % of less than 99 percent. This is a ratio of hits on a request for a specific

buffer

where the buffer was immediately available in memory. If the ratio is low, then could be a

(hot)block(s) being contended for that should be found in the Buffer Wait Section.

Buffer Hit % of less than 95 percent. This is the ratio of hits on a request for a specific buffer

and the buffer was in memory instead of needing to do a physical I/O.

When this varies greatly one day to the next, further investigation should be done as to the

cause.

If you have unselective indexes that are frequently accessed, it will drive your hit ratio

higher, which can be misleading indication of good performance.

When you effectively tune your SQL and have effective indexes on your entire system, this

issue is not encountered as frequently and the hit ratio is a better performance indicator.

Library Hit % of less than 95 percent. A lower library hit ratio usually indicates that SQL is

being pushed out of the shared pool early (could be due to a shared pool that is too small).

A lower ratio could also indicate that bind variables are not used or some other issue is

causing SQL not to be reused (in which case a smaller shared pool may only be a band-aid

that will potentially fix a library latch problem which may result).

You must fix the problem (use bind variables or CURSOR_SHARING) and then

appropriately size the shared pool. Ill discuss this further when we get to latch issues.

In-Memory Sort % of less than 95 percent in OLTP. In an OLTP system, you really dont

want to do disk sorts. Setting the PGA_AGGREGATE_TARGET (or SORT_AREA_SIZE)initialization parameter

effectively will eliminate this problem.

Latch Hit % of less than 99 percent is usually a big problem. Finding the specific latch will

lead you to solving this issue

Instance Efficiency Percentages (Target 100%)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Buffer Nowait %: 99.97 Redo NoWait %: 100.00Buffer Hit %: 54.85 In-memory Sort %: 100.00

Library Hit %: 86.77 Soft Parse %: 81.63Execute to Parse %: 38.67 Latch Hit %: 99.96

Parse CPU to Parse Elapsd %: 25.85 % Non-Parse CPU: 91.06

Shared Pool Statistics:This is a good summary of changes to the sharedpool during the snapshot period.

Shows the percentage of the shared pool in use and the

percentage of SQL statements that have been executed

multiple times. In this case, 80%+ have multiple executions.


7/43

Combining this data with the Library, Parse and Latch data

will help you to size the Shared Pool.

Shared Pool Statistics Begin End

------ ------Memory Usage %: 95.52 88.19% SQL with executions>1: 81.12 76.26

% Memory for SQL w/exec>1: 90.62 84.95

Top 5 Timed Events: This is the most important section in the AWR report. Itshows the top wait events and can quickly show the overall database bottleneck.The top 5 timed events section is showing you the top 5 contributors to DB Time.

Wait Problem Potential Fix

Sequential Read Indicates many index reads tune the

code (especially joins)Scattered Read Indicates many full table scans tune

the code; cache small tables

Free Buffer Increase the DB_CACHE_SIZE;

shorten the checkpoint; tune the code

Buffer Busy Segment Header Add freelists or

freelist groups (Use ASSM)

Buffer Busy Data Block Separate hot data; use

reverse key indexes; smaller blocks

Wait Problem Potential Fix

Buffer Busy Data Block (cont.) Increase initrans

and/or maxtransBuffer Busy Undo Header Add rollback segments

or areas

Buffer Busy Undo block Commit more (not too

much) Larger rollback segments/areas.

Latch Free Investigate the detail (Covered later)

Enqueue - ST Use LMTs or pre-allocate large extents

Enqueue - HW Pre-allocate extents above high water

mark

Enqueue TX Increase initrans and/or maxtrans on

(transaction) the table or indexEnqueue - TM Index foreign keys; Check application

(trans. mgmt.) locking of tables

Log Buffer Space Increase the Log Buffer; Faster disks

for the Redo Logs

Log File Switch Archive destination slow or full; Add

more or larger Redo Logs

Log file sync Commit more records at a time; Faster

Redo Log disks; Raw devices

Top 5 Timed Events Avg %Total~~~~~~~~~~~~~~~~~~ wait CallEvent Waits Time (s) (ms) Time Wait


8/43

Class------------------------------ ------------ ----------- ------ ----------------CPU time 2,135 60.1db file scattered read 1,942,116 458 0 12.9User I/O

db file sequential read 603,680 216 0 6.1User I/OBackup: sbtbackup 20 72 3608 2.0Administralog file parallel write 61,338 71 1 2.0System I/O

-------------------------------------------------------------

all non-idle wait times for all sessions

Wait Events Statistics Section:This section shows a breakdown of the main waitevents in the database including foreground and background database wait eventsas well as time model, operating system, service, and wait classes statistics.

Wait Events: This AWR report section provides more detailed wait event information for foreground user processes which includes Top 5wait events and many other wait events that occurred during the snapshot interval.

Wait Events DB/Inst: SALESNET/SNET Snaps: 14507-14537-> s - second-> cs - centisecond - 100th of a second-> ms - millisecond - 1000th of a second-> us - microsecond - 1000000th of a second-> ordered by wait time desc, waits desc (idle events last)

Avg%Time Total Wait wait

WaitsEvent Waits -outs Time (s) (ms)/txn---------------------------- -------------- ------ ----------- ----------------db file scattered read 1,942,116 .0 458 041.3db file sequential read 603,680 .0 216 0

12.8Backup: sbtbackup 20 .0 72 36080.0log file parallel write 61,338 .0 71 11.3log file sync 41,912 .0 59 10.9Backup: sbtclose2 20 .0 57 28750.0control file parallel write 16,019 .0 52 30.3os thread startup 655 .8 42 650.0

log file sequential read 220 .0 23 1020.0


9/43

db file parallel write 5,109 .0 17 30.1latch: library cache 116 .0 17 1460.0Backup: sbtinfo2 20 .0 16 8210.0

direct path write temp 24,049 .0 16 10.5direct path read temp 68,713 .0 13 01.5Backup: sbtwrite2 885 .0 12 130.0enq: WL - contention 6 33.3 11 19090.0read by other session 17,861 .0 7 00.4SQL*Net break/reset to clien 12,320 .0 7 10.3Backup: sbtremove2 10 .0 6 621

0.0latch: shared pool 428 .0 4 90.0control file sequential read 99,927 .0 3 02.1latch free 47 .0 2 520.0latch: checkpoint queue latc 8 .0 2 2680.0log file switch completion 4 50.0 2 5280.0SQL*Net message to client 2,257,056 .0 2 048.0recovery area: computing obs 298 .0 2 50.0RMAN backup & recovery I/O 78 .0 1 190.0latch: cache buffer handles 7 .0 1 2030.0enq: CF - contention 30 .0 1 370.0latch: row cache objects 30 .0 1 360.0SQL*Net more data to client 74,653 .0 1 01.6switch logfile command 11 .0 1 800.0control file single write 200 .0 0 20.0Log archive I/O 362 .0 0 10.0kksfbc child completion 8 100.0 0 490.0SQL*Net more data from clien 11,334 .0 0 00.2latch: cache buffers chains 74 .0 0 40.0latch: redo allocation 17 .0 0 80.0recovery area: computing bac 863 .0 0 0

0.0LGWR wait for redo copy 921 .0 0 0


10/43

0.0buffer busy waits 51 .0 0 20.0rdbms ipc reply 62 .0 0 10.0Backup: sbtinit2 10 .0 0 8

0.0log file single write 22 .0 0 30.0library cache pin 13 .0 0 50.0enq: TX - index contention 4 .0 0 130.0latch: library cache lock 1 .0 0 470.0enq: SQ - contention 1 .0 0 450.0db file parallel read 35 .0 0 10.0

library cache load lock 16 .0 0 20.0direct path write 187 .0 0 00.0flashback buf free by RVWR 22 .0 0 10.0SGA: allocation forcing comp 1 .0 0 120.0SQL*Net message to dblink 62 .0 0 00.0latch: object queue header o 2 .0 0 50.0Backup: sbtinit 10 .0 0 10.0recovery area: computing dro 10 .0 0 00.0recovery area: computing app 10 .0 0 00.0Backup: sbtend 10 .0 0 00.0undo segment extension 281 100.0 0 00.0


11/43

Wait Events DB/Inst: SALESNET/SNET Snaps: 14507-14537-> s - second-> cs - centisecond - 100th of a second-> ms - millisecond - 1000th of a second-> us - microsecond - 1000000th of a second

-> ordered by wait time desc, waits desc (idle events last)


WaitsEvent Waits -outs Time (s) (ms)/txn---------------------------- -------------- ------ ----------- ----------------direct path read 187 .0 0 00.0latch: cache buffers lru cha 4 .0 0 00.0

latch: session allocation 1 .0 0 00.0latch: library cache pin 1 .0 0 00.0latch: redo writing 1 .0 0 00.0SQL*Net message from client 2,257,022 .0 151,406 6748.0Streams AQ: qmn slave idle w 1,410 .0 38,502 273060.0Streams AQ: qmn coordinator 2,867 50.8 38,502 134290.1jobq slave wait 12,171 99.8 35,625 29270.3Streams AQ: waiting for time 312 55.1 33,029 1058630.0class slave wait 44 100.0 215 48830.0SGA: MMAN sleep for componen 173 73.4 1 80.0SQL*Net message from dblink 62 .0 0 80.0single-task message 4 .0 0 530.0

-------------------------------------------------------------

Background Wait Events: This section is relevant to the background process wait events.

Background Wait Events DB/Inst: SALESNET/SNET Snaps: 14507-14537-> ordered by wait time desc, waits desc (idle events last)


WaitsEvent Waits -outs Time (s) (ms)/txn---------------------------- -------------- ------ ----------- ----------------

log file parallel write 61,324 .0 71 11.3control file parallel write 14,412 .0 49 3


12/43

0.3os thread startup 654 .8 42 650.0log file sequential read 118 .0 19 1650.0db file parallel write 5,109 .0 17 3

0.1latch: library cache 51 .0 13 2640.0db file sequential read 1,252 .0 4 30.0events in waitclass Other 1,050 .0 3 20.0db file scattered read 308 .0 2 60.0control file sequential read 14,475 .0 1 00.3Log archive I/O 168 .0 0 10.0

log file single write 22 .0 0 30.0buffer busy waits 17 .0 0 40.0latch: library cache lock 1 .0 0 470.0direct path write 187 .0 0 00.0log file sync 22 .0 0 10.0latch: shared pool 5 .0 0 50.0direct path read 187 .0 0 00.0latch: cache buffers chains 1 .0 0 00.0latch: redo writing 1 .0 0 00.0rdbms ipc message 200,220 70.2 453,573 22654.3pmon timer 14,319 100.0 38,625 26970.3Streams AQ: qmn slave idle w 1,410 .0 38,502 273060.0Streams AQ: qmn coordinator 2,867 50.8 38,502 134290.1smon timer 171 68.4 37,509 2193490.0Streams AQ: waiting for time 312 55.1 33,029 1058630.0SGA: MMAN sleep for componen 173 73.4 1 80.0

-------------------------------------------------------------

Time Model Statistics:Time mode statistics report how database-processing time is spent. This section contains detailed timing information onparticular components participating in database processing.

Time Model Statistics DB/Inst: SALESNET/SNET Snaps: 14507-14537


13/43

-> Total time in database user-calls (DB Time): 3552.1s-> Statistics including the word "background" measure background process

time, and so do not contribute to the DB time statistic-> Ordered by % or DB time desc, Statistic name

Statistic Name Time (s) % of DB Time

------------------------------------------ ------------------ ------------sql execute elapsed time 2,853.1 80.3DB CPU 2,134.9 60.1parse time elapsed 734.0 20.7hard parse elapsed time 296.6 8.3PL/SQL execution elapsed time 41.4 1.2connection management call elapsed time 37.4 1.1inbound PL/SQL rpc elapsed time 16.0 .4PL/SQL compilation elapsed time 8.7 .2hard parse (sharing criteria) elapsed time 3.8 .1RMAN cpu time (backup/restore) 1.5 .0hard parse (bind mismatch) elapsed time 1.4 .0sequence load elapsed time 1.4 .0

repeated bind elapsed time 0.8 .0failed parse elapsed time 0.1 .0DB time 3,552.1 N/Abackground elapsed time 837.7 N/Abackground cpu time 245.3 N/A

-------------------------------------------------------------

Wait Class DB/Inst: SALESNET/SNET Snaps: 14507-14537-> s - second-> cs - centisecond - 100th of a second-> ms - millisecond - 1000th of a second-> us - microsecond - 1000000th of a second-> ordered by wait time desc, waits desc


WaitsWait Class Waits -outs Time (s)(ms) /txn-------------------- ---------------- ------ ---------------- ----------------User I/O 2,656,828 .0 711 056.5System I/O 183,275 .0 168 13.9Administrative 996 .0 165 1660.0Concurrency 1,389 .4 65 470.0Commit 41,912 .0 59 10.9Other 2,317 .4 21 90.0Application 12,320 .0 7 10.3Network 2,343,105 .0 3 049.8Configuration 287 98.6 2 80.0

-------------------------------------------------------------


14/43

Operating System Statistics:The stress on the Oracle server isimportant, and this section shows the main external resources including I/O, CPU,

memory, and network usage.

Operating System Statistics DB/Inst: SALESNET/SNET Snaps: 14507-14537

Statistic Total-------------------------------- --------------------NUM_LCPUS 0NUM_VCPUS 0AVG_BUSY_TIME 1,064,680AVG_IDLE_TIME 2,892,203AVG_IOWAIT_TIME 115,713AVG_SYS_TIME 77,471AVG_USER_TIME 986,214BUSY_TIME 4,262,713

IDLE_TIME 11,572,894IOWAIT_TIME 466,792SYS_TIME 313,834USER_TIME 3,948,879LOAD 0OS_CPU_WAIT_TIME 5,107,000RSRC_MGR_CPU_WAIT_TIME 0PHYSICAL_MEMORY_BYTES 15,032,385,536NUM_CPUS 4NUM_CPU_CORES 2

Service Statistics:The service statistics section gives information about how

particular services configured in the database are operating.


15/43

Service Statistics DB/Inst: SALESNET/SNET Snaps: 14507-14537-> ordered by DB Time

PhysicalLogical

Service Name DB Time (s) DB CPU (s) ReadsReads-------------------------------- ------------ ------------ --------------------SYS$USERS 3,551.7 2,134.7 ####################SALESNET 0.0 0.0 00SYS$BACKGROUND 0.0 0.0 9,304728,468

-------------------------------------------------------------

Service Wait Class Stats DB/Inst: SALESNET/SNET Snaps: 14507-

14537-> Wait Class info for services in the Service Statistics section.-> Total Waits and Time Waited displayed for the following wait

classes: User I/O, Concurrency, Administrative, Network-> Time Waited (Wt Time) in centisecond (100th of a second)

Service Name----------------------------------------------------------------User I/O User I/O Concurcy Concurcy Admin Admin NetworkNetworkTotal Wts Wt Time Total Wts Wt Time Total Wts Wt Time Total Wts WtTime--------- --------- --------- --------- --------- --------- ------------------SYS$USERS2649410 68453 634 807 996 16509 2290987

265SYS$BACKGROUND

7415 2612 750 5611 0 0 00

-------------------------------------------------------------


16/43

SQL Section:This section displays top SQL, ordered by important SQLexecution metrics.

SQL Ordered by Elapsed Time: Includes SQL statements that took significant execution time duringprocessing.

SQL Ordered by CPU Time: Includes SQL statements that consumed significant CPU time during itsprocessing.

SQL Ordered by Gets: These SQLs performed a high number of logical reads while retrieving data.

SQL Ordered by Reads: These SQLs performed a high number of physical disk reads while retrieving data.

SQL Ordered by Parse Calls: These SQLs experienced a high number of reparsing operations.

SQL Ordered by Sharable Memory: Includes SQL statements cursors which consumed a large amountof SGA shared pool memory.

SQL Ordered by Version Count: These SQLs have a large number of versions in shared pool for somereason.


17/43

SQL ordered by Elapsed Time DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Resources reported for PL/SQL code includes the resources used by allSQL

statements called by the code.-> % Total DB Time is the Elapsed Time of the SQL statement divided

into the Total Database Time multiplied by 100

Elapsed CPU Elap per % TotalTime (s) Time (s) Executions Exec (s) DB Time SQL Id

---------- ---------- ------------ ---------- ------- -------------56 18 3 18.6 1.6 2v48tvxsbus8d

Module: namgr.EXEselect transaction_id, assignedto, action_status, tran_loggeddate,tran_status,level3caseno, callid, onholdreason from crm_action_vw where tran_status ='OPEN' AND code = 'TECHEN' AND action_statusin('ASSIGNED','ACCEPTED','ONHOLD')

46 43 7,009 0.0 1.3 09bcp82ffxh72Module: JDBC Thin ClientSELECT NULL AS table_cat, t.owner AS table_schem, t.table_name AStable_name, t.column_name AS column_name, DECODE (t.data_type, 'CHAR', 1, 'VARCHAR2', 12, 'NUMBER', 3, 'LONG', -1, 'DATE', 93, 'RAW', -3, 'LONG RAW', -4, 1111) AS data_type, t.data_type AS t

44 36 6,459 0.0 1.2 2cj1bzhruawfaModule: JDBC Thin ClientINSERT INTO SAPIF_QUOTECOPIES(I_IDOC_NO,I_IDOC_TIMESTAMP,I_ACCNO,I_ACCNAME,I_TELNO,I_QUOTENO,I_VERSION,I_BU_REF,I_BU,I_EQSTATUS,I_SENGCODE,I_SENGNAME,I_INTENGCODE,I_INTENGNAME,I_RECDDATE,I_REQDDATE,I_VALIDTODATE,I_ORDERDATE,I_PRERECDLOC,I_TRACKERCODE,I_CONTACTCODE,I_CONTACTNAME,I_ORDERNO,I_CUSTOMERREF,I_GRADE,I_QUOTEV

38 29 30 1.3 1.1 bunssq950snhfinsert into wrh$_sga_target_advice (snap_id, dbid, instance_number, SGA_SIZE, SGA_SIZE_FACTOR, ESTD_DB_TIME, ESTD_PHYSICAL_READS) select :snap_id,:dbid, :instance_number, SGA_SIZE, SGA_SIZE_FACTOR, ESTD_DB_TIME,ESTD_PHYSICAL_READS from v$sga_target_advice

33 9 297 0.1 0.9 6gvch1xu9ca3gDECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; brokenBOOLEAN := FALSE; BEGIN EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS(); :mydate :=next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;

21 6 11,210 0.0 0.6 946nc1uuwvu4nDECLARE v_user_identifier varchar2(20); BEGIN SELECT SYS_CONTEXT('USERENV','SESSION_USER') INTO v_user_identifier FROM dual;DBMS_SESSION.SET_IDENTIFIER(v_user_identifier); END;

18 1 1 18.3 0.5 gmp51k9qhajrs


18/43

Module: namgr.EXESELECT CRM_TRANSACTION.ACCOUNTNUMBER, CRM_TRANSACTION_VW.COMPANYNAME,CRM_TRANSACTION_VW.CONTACT_NO, CRM_TRANSACTION_VW.FIRSTNAME,CRM_TRANSACTION_VW.LASTNAME,CRM_TRANSACTION.TRANSACTION_ID, CRM_TRANSACTION.COMPANYNAME,

CRM_TRANSACTION.TEMPFIELD1, CRM_TRANSACTION.LOGGEDDATE FROM CRM_TRANSACTION INNER JOINCRM_TRA

14 1 1,079 0.0 0.4 aykvshm7zsabdselect size_for_estimate, size_factor * 100 f,estd_physical_read_time, estd_physical_readsfrom v$db_cache_advice where id = '3'

12 8 14 0.8 0.3 3qa6dxrc98tmyModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, r

ecordnumber from (select code code, callid callid, substr(notes,1,50)notes, loggeddate loggeddate, status status, accountnumber accountnumber,transaction_id transaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

11 7 76 0.2 0.3 02b1z9pttr658Module: nHTTP.EXEselect accountnumber, contact_no, title, first_name, last_name, job_code,job_desc, pref_contact_method_code, pref_contact_method, phone, email, mobile,fax, source_table, allowphone, allowmail, allowemail, donotfax from (selectaccountnumb


19/43

SQL ordered by Elapsed Time DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Resources reported for PL/SQL code includes the resources used by allSQL



Elapsed CPU Elap per % TotalTime (s) Time (s) Executions Exec (s) DB Time SQL Id

---------- ---------- ------------ ---------- ------- -------------er accountnumber, contact_no contact_no, title title, first_namefirst_name, las

-------------------------------------------------------------


20/43

SQL ordered by CPU Time DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Resources reported for PL/SQL code includes the resources used by allSQL



CPU Elapsed CPU per % TotalTime (s) Time (s) Executions Exec (s) DB Time SQL Id

---------- ---------- ------------ ----------- ------- -------------43 46 7,009 0.01 1.3 09bcp82ffxh72

Module: JDBC Thin ClientSELECT NULL AS table_cat, t.owner AS table_schem, t.table_name AStable_name, t.column_name AS column_name, DECODE (t.data_type, 'CHAR', 1, 'VARCHAR2', 12, 'NUMBER', 3, 'LONG', -1, 'DATE', 93, 'RAW', -3, 'LONG RAW', -4, 1111) AS data_type, t.data_type AS t

36 44 6,459 0.01 1.2 2cj1bzhruawfa

Module: JDBC Thin ClientINSERT INTO SAPIF_QUOTECOPIES(I_IDOC_NO,I_IDOC_TIMESTAMP,I_ACCNO,I_ACCNAME,I_TELNO,I_QUOTENO,I_VERSION,I_BU_REF,I_BU,I_EQSTATUS,I_SENGCODE,I_SENGNAME,I_INTENGCODE,I_INTENGNAME,I_RECDDATE,I_REQDDATE,I_VALIDTODATE,I_ORDERDATE,I_PRERECDLOC,I_TRACKERCODE,I_CONTACTCODE,I_CONTACTNAME,I_ORDERNO,I_CUSTOMERREF,I_GRADE,I_QUOTEV

29 38 30 0.98 1.1 bunssq950snhfinsert into wrh$_sga_target_advice (snap_id, dbid, instance_number, SGA_SIZE, SGA_SIZE_FACTOR, ESTD_DB_TIME, ESTD_PHYSICAL_READS) select :snap_id,:dbid, :instance_number, SGA_SIZE, SGA_SIZE_FACTOR, ESTD_DB_TIME,ESTD_PHYSICAL_READS from v$sga_target_advice

18 56 3 5.89 1.6 2v48tvxsbus8dModule: namgr.EXEselect transaction_id, assignedto, action_status, tran_loggeddate,tran_status,level3caseno, callid, onholdreason from crm_action_vw where tran_status ='OPEN' AND code = 'TECHEN' AND action_statusin('ASSIGNED','ACCEPTED','ONHOLD')

9 33 297 0.03 0.9 6gvch1xu9ca3gDECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; brokenBOOLEAN := FALSE; BEGIN EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS(); :mydate :=next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;

8 12 14 0.60 0.3 3qa6dxrc98tmyModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, recordnumber from (select code code, callid callid, substr(notes,1,50)notes, log

geddate loggeddate, status status, accountnumber accountnumber,transaction_id t


21/43

ransaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

7 10 8,774 0.00 0.3 7ng34ruy5awxqselecti.obj#,i.ts#,i.file#,i.block#,i.intcols,i.type#,i.flags,i.property,i.pctf

ree$,i.initrans,i.maxtrans,i.blevel,i.leafcnt,i.distkey,i.lblkkey,i.dblkkey,i.clufac,i.cols,i.analyzetime,i.samplesize,i.dataobj#,nvl(i.degree,1),nvl(i.instances,1),i.rowcnt,mod(i.pctthres$,256),i.indmethod#,i.trunccnt,nvl(c.unicols,0),nvl(

7 11 76 0.09 0.3 02b1z9pttr658Module: nHTTP.EXEselect accountnumber, contact_no, title, first_name, last_name, job_code,job_desc, pref_contact_method_code, pref_contact_method, phone, email, mobile,fax, so

urce_table, allowphone, allowmail, allowemail, donotfax from (selectaccountnumber accountnumber, contact_no contact_no, title title, first_namefirst_name, las

7 11 77 0.09 0.3 54cjjrxy34pyhModule: nHTTP.EXESELECTcompanyname,accountnumber,town,postcode,phone,userfield2,userfieldg,customer_category,userfield1,userfieldm FROM cqs_snet_accounts_vw WHERE(upper( accountnumber ) like 'SAL012%') ORDER BY companyname DESC

6 21 11,210 0.00 0.6 946nc1uuwvu4nDECLARE v_user_identifier varchar2(20); BEGIN SELECT SYS_CONTEXT('USERENV','SESSION_USER') INTO v_user_identifier FROM dual;DBMS_SESSION.SET_IDENTIFIER(v_u


22/43

SQL ordered by CPU Time DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Resources reported for PL/SQL code includes the resources used by allSQL



CPU Elapsed CPU per % TotalTime (s) Time (s) Executions Exec (s) DB Time SQL Id

---------- ---------- ------------ ----------- ------- -------------ser_identifier); END;

-------------------------------------------------------------


23/43

SQL ordered by Gets DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Resources reported for PL/SQL code includes the resources used by allSQL

statements called by the code.-> Total Buffer Gets: 64,147,972

-> Captured SQL account for 16.9% of Total

Gets CPU ElapsedBuffer Gets Executions per Exec %Total Time (s) Time (s) SQL

Id-------------- ------------ ------------ ------ -------- ----------------------

3,752,266 7,009 535.3 5.8 42.70 45.6409bcp82ffxh72Module: JDBC Thin ClientSELECT NULL AS table_cat, t.owner AS table_schem, t.table_name AStable_name, t.column_name AS column_name, DECODE (t.data_type, 'CHAR', 1, 'VARCHAR2', 12, 'NUMBER', 3, 'LONG', -1, 'DATE', 93, 'RAW

', -3, 'LONG RAW', -4, 1111) AS data_type, t.data_type AS t

900,562 6,459 139.4 1.4 35.86 43.892cj1bzhruawfaModule: JDBC Thin ClientINSERT INTO SAPIF_QUOTECOPIES(I_IDOC_NO,I_IDOC_TIMESTAMP,I_ACCNO,I_ACCNAME,I_TELNO,I_QUOTENO,I_VERSION,I_BU_REF,I_BU,I_EQSTATUS,I_SENGCODE,I_SENGNAME,I_INTENGCODE,I_INTENGNAME,I_RECDDATE,I_REQDDATE,I_VALIDTODATE,I_ORDERDATE,I_PRERECDLOC,I_TRACKERCODE,I_CONTACTCODE,I_CONTACTNAME,I_ORDERNO,I_CUSTOMERREF,I_GRADE,I_QUOTEV

330,620 77 4,293.8 0.5 7.05 10.9454cjjrxy34pyhModule: nHTTP.EXESELECTcompanyname,accountnumber,town,postcode,phone,userfield2,userfieldg,customer_category,userfield1,userfieldm FROM cqs_snet_accounts_vw WHERE(upper( accountnumber ) like 'SAL012%') ORDER BY companyname DESC

257,993 76 3,394.6 0.4 7.12 11.4402b1z9pttr658Module: nHTTP.EXEselect accountnumber, contact_no, title, first_name, last_name, job_code,job_desc, pref_contact_method_code, pref_contact_method, phone, email, mobile,fax, source_table, allowphone, allowmail, allowemail, donotfax from (selectaccountnumber accountnumber, contact_no contact_no, title title, first_namefirst_name, las

255,823 14 18,273.1 0.4 8.43 11.843qa6dxrc98tmyModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, r

ecordnumber from (select code code, callid callid, substr(notes,1,50)notes, log


24/43

geddate loggeddate, status status, accountnumber accountnumber,transaction_id transaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

159,838 297 538.2 0.2 9.47 33.03

6gvch1xu9ca3gDECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; brokenBOOLEAN := FALSE; BEGIN EMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS(); :mydate :=next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;

126,317 23,439 5.4 0.2 1.53 1.646769wyy3yf66fselect pos#,intcol#,col#,spare1,bo#,spare2 from icol$ where obj#=:1

109,638 6 18,273.0 0.2 4.16 6.18219rt7uzd6j34

Module: BIBusTKServerMain.exeselect distinct "CRM_TRANSACTION"."LOGGEDBY" "Logged_By" from"SALESNET"."CRM_TRANSACTION" "CRM_TRANSACTION" order by "Logged_By" asc nulls last

106,319 3 35,439.7 0.2 17.66 55.672v48tvxsbus8dModule: namgr.EXEselect transaction_id, assignedto, action_status, tran_loggeddate,tran_status,level3caseno, callid, onholdreason from crm_action_vw where tran_status ='OPEN' AND code = 'TECHEN' AND action_statusin('ASSIGNED','ACCEPTED','ONHOLD')

94,675 19,588 4.8 0.1 1.20 1.5653saa2zkr6wc3select intcol#,nvl(pos#,0),col#,nvl(spare1,0) from ccol$ where con#=:1

-------------------------------------------------------------


25/43

SQL ordered by Reads DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Total Disk Reads: 29,178,794-> Captured SQL account for 9.2% of Total

Reads CPU Elapsed

Physical Reads Executions per Exec %Total Time (s) Time (s) SQLId-------------- ----------- ------------- ------ -------- ----------------------

299,107 3 99,702.3 1.0 17.66 55.672v48tvxsbus8dModule: namgr.EXEselect transaction_id, assignedto, action_status, tran_loggeddate,tran_status,level3caseno, callid, onholdreason from crm_action_vw where tran_status ='OPEN' AND code = 'TECHEN' AND action_statusin('ASSIGNED','ACCEPTED','ONHOLD')

226,068 14 16,147.7 0.8 8.43 11.843qa6dxrc98tmyModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, recordnumber from (select code code, callid callid, substr(notes,1,50)notes, loggeddate loggeddate, status status, accountnumber accountnumber,transaction_id transaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

87,802 5 17,560.4 0.3 2.92 3.756u1f3nky542frModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, recordnumber from (select code code, callid callid, substr(notes,1,50)notes, loggeddate loggeddate, status status, accountnumber accountnumber,transaction_id transaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

73,198 6 12,199.7 0.3 4.16 6.18219rt7uzd6j34Module: BIBusTKServerMain.exeselect distinct "CRM_TRANSACTION"."LOGGEDBY" "Logged_By" from"SALESNET"."CRM_TRANSACTION" "CRM_TRANSACTION" order by "Logged_By" asc nulls last

64,391 4 16,097.8 0.2 2.09 3.01a0t3v0f069rgbModule: nHTTP.EXEselect code, callid, notes, loggeddate, status, accountnumber,transaction_id, recordnumber from (select code code, callid callid, substr(notes,1,50)notes, loggeddate loggeddate, status status, accountnumber accountnumber,

transaction_id t


26/43

ransaction_id, recordnumber recordnumber from crm_transaction whereupper( accou

61,245 2 30,622.5 0.2 1.66 2.225n6x02qbpfqm7Module: nHTTP.EXE

select code, callid, notes, tran_loggeddate, tran_status, accountnumber,transaction_id, recordnumber, checkedout, rlock from (select code code, callidcallid,substr(notes,1,50) notes, tran_loggeddate tran_loggeddate, tran_statustran_status, accountnumber accountnumber, transaction_id transaction_id,recordnumber rec

60,845 2 30,422.5 0.2 1.81 9.73b758gugh6wrvdModule: nHTTP.EXEselect code, callid, notes, tran_loggeddate, tran_status, accountnumber,

transaction_id, recordnumber, checkedout, rlock from (select code code, callidcallid,substr(notes,1,50) notes, tran_loggeddate tran_loggeddate, tran_statustran_status, accountnumber accountnumber, transaction_id transaction_id,recordnumber rec

59,592 2 29,796.0 0.2 1.70 2.324wsjqsfss2u2pModule: nHTTP.EXEselect code, callid, notes, tran_loggeddate, tran_status, accountnumber,transaction_id, recordnumber, checkedout, rlock from (select code code, callidcallid,substr(notes,1,50) notes, tran_loggeddate tran_loggeddate, tran_statustran_status, accountnumber accountnumber, transaction_id transaction_id,recordnumber rec

59,498 2 29,749.0 0.2 1.75 2.146uah25bcnz4s9Module: nHTTP.EXEselect code, callid, notes, tran_loggeddate, tran_status, accountnumber,transaction_id, recordnumber, checkedout, rlock from (select code code, callidcallid,substr(notes,1,50) notes, tran_loggeddate tran_loggeddate, tran_statustran_status, accountnumber accountnumber, transaction_id transaction_id,recordnumber rec


27/43


28/43

SQL ordered by Executions DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Total Executions: 1,079,446-> Captured SQL account for 30.1% of Total

CPU per Elap per

Executions Rows Processed Rows per Exec Exec (s) Exec (s) SQLId------------ --------------- -------------- ---------- ------------------------

32,517 18,472 0.6 0.00 0.000h6b2sajwb74nselect privilege#,level from sysauth$ connect by grantee#=prior privilege#and privilege#>0 start with grantee#=:1 and privilege#>0

27,139 27,139 1.0 0.00 0.003fwypqz13krwuModule: MSACCESS.EXE

SELECT "USERKEY","TABLENAME","SECURITY","FIELDSEC","XTRASECURITY" FROM"SALESNET"."USERSEC" WHERE "USERKEY" = :1 AND "TABLENAME" = :2

23,439 39,703 1.7 0.00 0.006769wyy3yf66fselect pos#,intcol#,col#,spare1,bo#,spare2 from icol$ where obj#=:1

19,588 27,733 1.4 0.00 0.0053saa2zkr6wc3select intcol#,nvl(pos#,0),col#,nvl(spare1,0) from ccol$ where con#=:1

13,717 13,694 1.0 0.00 0.003c1kubcdjnppqupdate sys.col_usage$ set equality_preds = equality_preds + decode(bitand(:flag,1),0,0,1), equijoin_preds = equijoin_preds + decode(bitand(:flag,2),0,0,1), nonequijoin_preds = nonequijoin_preds +decode(bitand(:flag,4),0,0,1), range_preds = range_preds + decode(bitand(:flag,8),0,0,1),

11,210 11,210 1.0 0.00 0.00946nc1uuwvu4nDECLARE v_user_identifier varchar2(20); BEGIN SELECT SYS_CONTEXT('USERENV','SESSION_USER') INTO v_user_identifier FROM dual;DBMS_SESSION.SET_IDENTIFIER(v_user_identifier); END;

10,001 29,106 2.9 0.00 0.000k8522rmdzg4kselect privilege# from sysauth$ where (grantee#=:1 or grantee#=1) andprivilege#>0

9,510 165,605 17.4 0.00 0.0083taa7kaw59c1selectname,intcol#,segcol#,type#,length,nvl(precision#,0),decode(type#,2,nvl(scale,-127/*MAXSB1MINAL*/),178,scale,179,scale,180,scale,181,scale,182,scale,183,s

cale,231,scale,0),null$,fixedstorage,nvl(deflength,0),default$,rowid,col#,proper


29/43

ty, nvl(charsetid,0),nvl(charsetform,0),spare1,spare2,nvl(spare3,0) fromcol$ wh

8,774 23,638 2.7 0.00 0.007ng34ruy5awxqselect

i.obj#,i.ts#,i.file#,i.block#,i.intcols,i.type#,i.flags,i.property,i.pctfree$,i.initrans,i.maxtrans,i.blevel,i.leafcnt,i.distkey,i.lblkkey,i.dblkkey,i.clufac,i.cols,i.analyzetime,i.samplesize,i.dataobj#,nvl(i.degree,1),nvl(i.instances,1),i.rowcnt,mod(i.pctthres$,256),i.indmethod#,i.trunccnt,nvl(c.unicols,0),nvl(

8,249 8,249 1.0 0.00 0.00g8skttwyjx17yModule: JDBC Thin ClientSELECT SYS_CONTEXT('USERENV', 'SESSION_USER') FROM DUAL

-------------------------------------------------------------


30/43

SQL ordered by Parse Calls DB/Inst: SALESNET/SNET Snaps: 14507-14537-> Total Parse Calls: 662,055-> Captured SQL account for 29.7% of Total

% Total

Parse Calls Executions Parses SQL Id------------ ------------ --------- -------------32,517 32,517 4.91 0h6b2sajwb74n

select privilege#,level from sysauth$ connect by grantee#=prior privilege#and privilege#>0 start with grantee#=:1 and privilege#>0

11,210 11,210 1.69 946nc1uuwvu4nDECLARE v_user_identifier varchar2(20); BEGIN SELECT SYS_CONTEXT('USERENV','SESSION_USER') INTO v_user_identifier FROM dual;DBMS_SESSION.SET_IDENTIFIER(v_user_identifier); END;

10,002 10,001 1.51 0k8522rmdzg4kselect privilege# from sysauth$ where (grantee#=:1 or grantee#=1) andprivilege#>0

8,250 8,249 1.25 g8skttwyjx17yModule: JDBC Thin ClientSELECT SYS_CONTEXT('USERENV', 'SESSION_USER') FROM DUAL

7,365 7,365 1.11 3n58uzvnuw2hjModule: namgr.EXESELECT VALUE FROM V$NLS_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET'

7,363 7,363 1.11 18m93d30zw6mbModule: nHTTP.EXEALTER SESSION SET NLS_LANGUAGE= 'ENGLISH' NLS_TERRITORY= 'UNITED KINGDOM'NLS_CURRENCY= '#' NLS_ISO_CURRENCY= 'UNITED KINGDOM'NLS_NUMERIC_CHARACTERS= '.,' NLS_CALENDAR= 'GREGORIAN' NLS_DATE_FORMAT= 'DD-MON-RR' NLS_DATE_LANGUAGE= 'ENGLISH' NLS_COMP= 'B

7,006 7,009 1.06 09bcp82ffxh72Module: JDBC Thin ClientSELECT NULL AS table_cat, t.owner AS table_schem, t.table_name AStable_name, t.column_name AS column_name, DECODE (t.data_type, 'CHAR', 1, 'VARCHAR2', 12, 'NUMBER', 3, 'LONG', -1, 'DATE', 93, 'RAW', -3, 'LONG RAW', -4, 1111) AS data_type, t.data_type AS t

6,457 6,459 0.98 2cj1bzhruawfaModule: JDBC Thin ClientINSERT INTO SAPIF_QUOTECOPIES(I_IDOC_NO,I_IDOC_TIMESTAMP,I_ACCNO,I_ACCNAME,I_TELNO,I_QUOTENO,I_VERSION,I_BU_REF,I_BU,I_EQSTATUS,I_SENGCODE,I_SENGNAME,I_INTENGCODE,I_INTENGNAME,I_RECDDATE,I_REQDDATE,I_VALIDTODATE,I_ORDERDATE,I_PRERECDLOC,I_TRACKERCODE,I_CONTACTCODE,I_CONTACTNAME,I_ORDERNO,I_CUSTOMERREF,I_GRADE,I_QUOTEV

5,682 5,684 0.86 asvzxj61dc5vs

select timestamp, flags from fixed_obj$ where obj#=:1


31/43

4,994 4,993 0.75 8swypbbr0m372select order#,columns,types from access$ where d_obj#=:1

-------------------------------------------------------------

SQL ordered by Sharable Memory DB/Inst: SALESNET/SNET Snaps: 14507-

14537

No data exists for this section of the report.-------------------------------------------------------------

SQL ordered by Version Count DB/Inst: SALESNET/SNET Snaps: 14507-14537

No data exists for this section of the report.-------------------------------------------------------------

Instance Activity Stats: This section contains statistical information describing how the database operated during the snapshot period.

Instance Activity Stats (Absolute Values): This section contains statistics that have absolute values not derived from end andstart snapshots.

Instance Activity Stats (Thread Activity): This report section reports a log switch activity statistic.


32/43

Instance Activity Stats DB/Inst: SALESNET/SNET Snaps: 14507-14537

Statistic Total per Second perTrans-------------------------------- ------------------ --------------

-------------CPU used by this session 168,371 4.33.6CPU used when call started 151,148 3.83.2CR blocks created 499 0.00.0Cached Commit SCN referenced 0 0.00.0Commit SCN cached 0 0.00.0DB time 1,407,799,327 35,580.429,948.7

DBWR checkpoint buffers written 33,478 0.90.7DBWR checkpoints 11 0.00.0DBWR transaction table writes 1,099 0.00.0DBWR undo block writes 12,425 0.30.3OS Integral shared text size 134,749,593 3,405.62,866.6OS Integral unshared data size 24,767,294 626.0526.9OS Involuntary context switches 866,514 21.918.4OS Maximum resident set size 541,107,520 13,675.811,511.2OS Page faults 112,689 2.92.4OS Page reclaims 3,962,870 100.284.3OS Signals received 0 0.00.0OS System time used 22,610 0.60.5OS User time used 194,260 4.94.1OS Voluntary context switches 2,717,121 68.757.8SMON posted for undo segment shr 14 0.00.0SQL*Net roundtrips to/from clien 2,225,164 56.247.3SQL*Net roundtrips to/from dblin 62 0.00.0active txn count during cleanout 1,155 0.00.0application wait time 685 0.00.0background checkpoints completed 11 0.00.0

background checkpoints started 11 0.00.0


33/43

background timeouts 140,394 3.63.0branch node splits 0 0.00.0buffer is not pinned count 12,893,821 325.9274.3

buffer is pinned count 26,733,589 675.7568.7bytes received via SQL*Net from 366,807,091 9,270.67,803.2bytes received via SQL*Net from 28,349 0.70.6bytes sent via SQL*Net to client 504,728,764 12,756.410,737.3bytes sent via SQL*Net to dblink 20,240 0.50.4calls to get snapshot scn: kcmgs 1,345,673 34.028.6calls to kcmgas 74,632 1.9

1.6calls to kcmgcs 2,155 0.10.1change write time 1,321 0.00.0cleanout - number of ktugct call 1,336 0.00.0cleanouts and rollbacks - consis 153 0.00.0cleanouts only - consistent read 43 0.00.0cluster key scan block gets 2,592,360 65.555.2cluster key scans 922,826 23.319.6commit batch performed 4 0.00.0commit batch requested 4 0.00.0commit batch/immediate performed 5,863 0.20.1commit batch/immediate requested 5,863 0.20.1commit cleanout failures: block 0 0.00.0commit cleanout failures: buffer 3 0.00.0commit cleanout failures: callba 106 0.00.0commit cleanouts 143,462 3.63.1commit cleanouts successfully co 143,353 3.63.1commit immediate performed 5,859 0.20.1commit immediate requested 5,859 0.20.1commit txn count during cleanout 581 0.00.0concurrency wait time 6,410 0.2

0.1


34/43

consistent changes 505 0.00.0consistent gets 63,514,286 1,605.31,351.2consistent gets - examination 4,101,929 103.787.3


35/43



-------------consistent gets direct 0 0.00.0consistent gets from cache 63,514,286 1,605.31,351.2cursor authentications 29,168 0.70.6data blocks consistent reads - u 505 0.00.0db block changes 633,181 16.013.5db block gets 633,686 16.013.5

db block gets direct 0 0.00.0db block gets from cache 633,686 16.013.5deferred (CURRENT) block cleanou 81,691 2.11.7dirty buffers inspected 3,242 0.10.1enqueue conversions 9,064 0.20.2enqueue releases 603,226 15.312.8enqueue requests 603,243 15.312.8enqueue timeouts 18 0.00.0enqueue waits 39 0.00.0execute count 1,079,446 27.323.0flashback log writes 2,304 0.10.1frame signature mismatch 0 0.00.0free buffer inspected 29,047,802 734.2618.0free buffer requested 28,965,138 732.1616.2heap block compress 5,368 0.10.1hot buffers moved to head of LRU 577,863 14.612.3immediate (CR) block cleanout ap 196 0.00.0immediate (CURRENT) block cleano 28,386 0.70.6index fast full scans (full) 789 0.00.0index fetch by key 2,065,505 52.243.9

index scans kdiixs1 1,992,429 50.442.4


36/43

leaf node 90-10 splits 232 0.00.0leaf node splits 414 0.00.0lob reads 11,183 0.30.2

lob writes 451 0.00.0lob writes unaligned 451 0.00.0logons cumulative 11,940 0.30.3messages received 66,257 1.71.4messages sent 66,257 1.71.4no buffer to keep pinned count 0 0.00.0no work - consistent read gets 57,239,942 1,446.7

1,217.7opened cursors cumulative 682,965 17.314.5parse count (failures) 32 0.00.0parse count (hard) 121,649 3.12.6parse count (total) 662,055 16.714.1parse time cpu 19,078 0.50.4parse time elapsed 73,805 1.91.6physical read IO requests 2,611,222 66.055.6physical read bytes 239,032,680,448 6,041,259.45,085,044.4physical read total IO requests 2,714,455 68.657.8physical read total bytes 241,197,777,920 6,095,979.65,131,103.4physical read total multi block 1,965,517 49.741.8physical reads 29,178,794 737.5620.7physical reads cache 28,963,476 732.0616.2physical reads cache prefetch 26,418,303 667.7562.0physical reads direct 215,318 5.44.6physical reads direct (lob) 0 0.00.0physical reads direct temporary 215,131 5.44.6physical reads for flashback new 10,232 0.30.2physical reads prefetch warmup 0 0.00.0physical write IO requests 46,275 1.2

1.0


37/43


38/43



-------------physical write total multi block 87,141 2.21.9physical writes 254,801 6.45.4physical writes direct 215,385 5.44.6physical writes direct (lob) 0 0.00.0physical writes direct temporary 215,198 5.44.6physical writes from cache 39,416 1.00.8

physical writes non checkpoint 234,886 5.95.0pinned buffers inspected 2,224 0.10.1prefetch warmup blocks aged out 0 0.00.0prefetched blocks aged out befor 4 0.00.0process last non-idle time 39,538 1.00.8recursive calls 3,954,598 100.084.1recursive cpu usage 33,321 0.80.7redo blocks written 281,550 7.16.0redo buffer allocation retries 3 0.00.0redo entries 340,568 8.67.3redo log space requests 4 0.00.0redo log space wait time 216 0.00.0redo ordering marks 9,281 0.20.2redo size 121,568,268 3,072.52,586.2redo synch time 6,096 0.20.1redo synch writes 89,331 2.31.9redo wastage 18,017,676 455.4383.3redo write time 7,750 0.20.2redo writer latching time 11 0.00.0redo writes 61,305 1.61.3

rollback changes - undo records 5,903 0.20.1


39/43

rollbacks only - consistent read 343 0.00.0rows fetched via callback 1,154,956 29.224.6session connect time 0 0.00.0

session cursor cache hits 428,206 10.89.1session logical reads 64,147,972 1,621.31,364.7session pga memory 984,922,048 24,892.720,952.7session pga memory max 1,126,530,976 28,471.723,965.2session uga memory 2,620,270,461,528 66,224,139.555,742,133.3session uga memory max 5,967,233,504 150,814.6126,943.5shared hash latch upgrades - no 1,970,084 49.8

41.9shared hash latch upgrades - wai 3,912 0.10.1sorts (disk) 8 0.00.0sorts (memory) 237,992 6.05.1sorts (rows) 14,041,172 354.9298.7sql area purged 0 0.00.0summed dirty queue length 4,755 0.10.1switch current to new buffer 1,154 0.00.0table fetch by rowid 17,023,167 430.2362.1table fetch continued row 32,546 0.80.7table scan blocks gotten 44,376,539 1,121.6944.0table scan rows gotten 1,385,800,643 35,024.429,480.7table scans (long tables) 3,080 0.10.1table scans (short tables) 60,995 1.51.3total number of times SMON poste 54 0.00.0transaction rollbacks 5,863 0.20.1undo change vector size 42,224,312 1,067.2898.3user I/O wait time 71,056 1.81.5user calls 2,563,981 64.854.5user commits 46,951 1.21.0user rollbacks 56 0.0

0.0


40/43


41/43



-------------write clones created in backgrou 0 0.00.0write clones created in foregrou 1 0.00.0

-------------------------------------------------------------


42/43

Instance Activity Stats - Absolute ValuesDB/Inst: SALESNET/SNET Snaps:14507-> Statistics with absolute values (should not be diffed)

Statistic Begin Value End Value-------------------------------- --------------- ---------------

session cursor cache count 56,648 135,398opened cursors current 117 91logons current 29 63

-------------------------------------------------------------

Instance Activity Stats - Thread ActivityDB/Inst: SALESNET/SNET Snaps:14507--> Statistics identified by '(derived)' come from sources other thanSYSSTAT

Statistic Total per Hour-------------------------------- ------------------ ---------log switches (derived) 11 1.00

-------------------------------------------------------------

I/O Section: This section shows the all important I/O activity for the instance and shows I/O

activity by tablespace, data file, and includes buffer pool statistics.

Tablespace IO Stats

File IO Stats

Buffer Pool Statistics

Advisory Section: This section show details of the advisories for the buffer, shared pool,

PGA and Java pool.Buffer Pool Advisory

PGA Aggr Summary: PGA Aggr Target Stats; PGA Aggr Target Histogram; and PGA Memory Advisory.

Shared Pool Advisory

Java Pool Advisory

Buffer Wait Statistics: This important section shows buffer cache waits statistics.

Enqueue Activity: This important section shows how enqueue operates in the database. Enqueues are special internal structures whichprovide concurrent access to various database resources.

Undo Segment Summary: This section gives a summary about how undo segments are used by the database.

Undo Segment Stats: This section shows detailed history information about undo segment activity.

Latch Activity: This section shows details about latch statistics. Latches are a lightweight serialization mechanism that is used to single-thread access to internal Oracle structures.

Latch Sleep Breakdown

Latch Miss Sources

Parent Latch Statistics

Child Latch Statistics

Segment Section: This report section provides details about hot segments using the following criteria:


43/43

Segments by Logical Reads: Includes top segments which experienced high number of logical reads.

Segments by Physical Reads: Includes top segments which experienced high number of disk physical reads.

Segments by Buffer Busy Waits: These segments have the largest number of buffer waits caused by their datablocks.

Segments by Row Lock Waits: Includes segments that had a large number of row locks on their data.

Segments by ITL Waits: Includes segments that had a large contention for Interested Transaction List (ITL). Thecontention for ITL can be reduced by increasing INITRANS storage parameter of the table.

Dictionary Cache Stats: This section exposes details about how the data dictionary cache is operating.

Library Cache Activity: Includes library cache statistics describing how shared library objects are managed by Oracle.

SGA Memory Summary: This section provides summary information about various SGA regions.

init.ora

Parameters: This section shows the originalinit.ora

parameters for the instanceduring the snapshot period.

22234290 Awr Report Analysis

Documents

Transcript of 22234290 Awr Report Analysis