Você está na página 1de 43

Statspack/AWR analysis

In stead of using ratios, such as the buffer cache hit ratio, or single figures taken out of context this
documents 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 of service time and wait
time.

The service time is the time spent by the CPU actively working on your request, and the wait time is
the 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 in
processing blocks in the buffer cache, scanning an index block for a certain value and getting your
requested 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 CPU
processing PL/SQL and you may wait for a lock or for Oracle to write data to the redo log file when you
do a commit.

The general idea behind this method is to identify in some detail what the components of the service
time and the wait time are and simply order these. The component at the top is the one that should be
the 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 reduce
my 20 second latch wait time”, if you are using 20 minutes of CPU processing SQL. A second
observation in the method is that tuning something that is taking long time can be done both by
reducing the time (such as using faster disks) or reducing the number of times (such as making fewer
disk reads). Hence, the steps involved in this method that we will refer to as time based tuning, are
simply:

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 of
executions

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 regularly
check in your STATSPACK output:

• Top 5 wait events (timed events)

• Load profile

• Instance efficiency hit ratios

• Wait events

• Latch waits

• 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 drop
from 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 for
OLTP, 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 you
why you are receiving the top 5 waits.

Tuning the top 25 buffer get and top 25 physical get queries has yielded system
performance gains of anywhere from 5 to 5000 percent. The SQL section of the
STATSPACK 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 your
buffer gets or disk reads.

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

The “sorts (disk)” statistic divided by the “sorts (memory)” should not be above 1–5
percent. If it is, you should increase the PGA_AGGREGATE_TARGET (or SORT_AREA_SIZE)
parameter in the initialization file (given that physical memory is available
to do this). Remember that the memory allocated for Sort_Area_Size is a per-user value
and PGA_AGGREGATE_TARGET is across all sessions.

Latches are like locks on pieces of memory (or memory buffers). If the latch hit ratio is
below 99 percent, there is a serious issue, since not even the lock to get memory
could 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 extended
period of time, the SHARED_POOL_SIZE is probably too small for your best system
performance. If the reloads are greater than 1 percent, this also points to a
SHARED_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 a
great place to find hot block and ITL issues, but it takes a lot of time and energy on the
part of an advanced DBA to pinpoint problems at this level.

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

Time Model Statistics
In 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 time
failed 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 of
database processing work.( see above table )

These statistics can be obtained by V$SESS_TIME_MODEL and V$SYS_TIME_MODEL Statistics
Views

The time model views differ from each other in that the V$SESS_TIME_MODEL view stores timing
information for individual sessions while the V$SYS_TIME_MODEL view provides information at
instance level. As a result, you won't find the column for SESSION_ID in the V$SYS_TIME_MODEL
view. In addition, V$SYS_TIME_MODEL records information historically from instance startup, so
don't be concerned if you add up all of the time spent by the current indiviudal sessions and it doesn't
match the DBTIME value in V$SYS_TIME_MODEL view. One last thing, use the timings as a relative
reference, 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 to
process all database calls. In fact, it describes the total database workload. DB time is calculated by
aggregating the CPU and all non-idle wait times for all sessions in the database after the last startup.

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

DB Time is the most important of the various Time Model Statistics, which break down the Service
component 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 the
total 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 session’s SQL
parse and processing times, session’s wait times, etc.

DB Time shows us 'the Oracle bit' that we might be able to tune. The goal of the DB Time
Performance 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 tuning
it to do less work, or increasing the efficiency of that work by reducing bottlenecks. Regardless of
howI you would have improved the performance of the query the end user's experience would have
improved..

.06 Logons: 0.42 User calls: 64.30 0.26 1. If > 100/second. • A Hard Parse occurs when a SQL statement is executed and is not currently in the shared pool.00 13.072.621.212K Load Profile: This important section shows important rates expressed in units of xxx per second and in units of xxx per transactions. Cache Sizes ~~~~~~~~~~~ Begin End ---------.07 2. CURSOR_SHARING initialization parameter should be potentially used or there may be a Shared Pool sizing problem.80 54.44 5.59 Sorts: 6.28 22.586. Load Profile ~~~~~~~~~~~~ Per Second Per Transaction --------------.” indicates increased DML (insert/update/delete) activity.” “block changes” and “% Blocks changed per Read:.96 Transactions: 1.67 Rollback per transaction %: 0.Cache Sizes : This shows the size of each SGA region after AMM has changed them.54 Parses: 16.00 Instance Efficiency Percentages ( hit ratios ) : With a target of 100%.99 Recursive Call %: 60.19 % Blocks changed per Read: 0.---------- Buffer Cache: 348M 340M Std Block Size: 8K Shared Pool Size: 128M 136M Log Buffer: 6.25 Executes: 27. these are high-level ratios for activity in the SGA. • An increase in “redo size.46 620.73 Physical writes: 6. This information can be compared to the original init.ora parameters at the end of the AWR report.17 Logical reads: 1.49 2.08 Hard parses: 3.364.02 5.73 14.47 Physical reads: 737.12 Rows per Sort: 59. --------------- Redo size: 3.65 Block changes: 16.

In-Memory Sort % of less than 95 percent in OLTP. I’ll discuss this further when we get to latch issues. Latch Hit % of less than 99 percent is usually a big problem. then could be a (hot)block(s) being contended for that should be found in the Buffer Wait Section. 80%+ have multiple executions.00 Buffer Hit %: 54.97 Redo NoWait %: 100. Library Hit % of less than 95 percent. In this case.77 Soft Parse %: 81.63 Execute to Parse %: 38.06 Shared Pool Statistics: This is a good summary of changes to the shared pool during the snapshot period. further investigation should be done as to the cause. 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). – 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. In an OLTP system. This is a ratio of hits on a request for a specific buffer where the buffer was immediately available in memory. which can be misleading indication of good performance.96 Parse CPU to Parse Elapsd %: 25. – 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). Finding the specific latch will lead you to solving this issue Instance Efficiency Percentages (Target 100%) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Buffer Nowait %: 99.85 % Non-Parse CPU: 91.00 Library Hit %: 86. – You must fix the problem (use bind variables or CURSOR_SHARING) and then appropriately size the shared pool. . Buffer Hit % of less than 95 percent. Setting the PGA_AGGREGATE_TARGET (or SORT_AREA_SIZE) initialization parameter effectively will eliminate this problem. – When this varies greatly one day to the next. If the ratio is low. – If you have unselective indexes that are frequently accessed. 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.67 Latch Hit %: 99. it will drive your hit ratio higher. Shows the percentage of the shared pool in use and the percentage of SQL statements that have been executed multiple times. you really don’t want to do disk sorts.Buffer NoWait % of less than 99 percent.85 In-memory Sort %: 100.

cache small tables Free Buffer Increase the DB_CACHE_SIZE. Check application (trans. 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.95 Top 5 Timed Events: This is the most important section in the AWR report. Raw devices Top 5 Timed Events Avg %Total ~~~~~~~~~~~~~~~~~~ wait Call Event Waits Time (s) (ms) Time Wait . Add more or larger Redo Logs Log file sync Commit more records at a time.)– Increase initrans and/or maxtrans Buffer Busy Undo Header – Add rollback segments or areas Buffer Busy Undo block – Commit more (not too much) Larger rollback segments/areas. ------ Memory Usage %: 95. mgmt. use reverse key indexes.26 % Memory for SQL w/exec>1: 90. Parse and Latch data will help you to size the Shared Pool.12 76. The top 5 timed events section is showing you the top 5 contributors to DB Time. Shared Pool Statistics Begin End -----. Faster Redo Log disks. Latch Free Investigate the detail (Covered later) Enqueue . smaller blocks Wait Problem Potential Fix Buffer Busy Data Block (cont.) locking of tables Log Buffer Space Increase the Log Buffer. It shows the top wait events and can quickly show the overall database bottleneck. Faster disks for the Redo Logs Log File Switch Archive destination slow or full.HW Pre-allocate extents above high water mark Enqueue – TX Increase initrans and/or maxtrans on (transaction) the table or index Enqueue . shorten the checkpoint.• Combining this data with the Library.52 88.ST Use LMT’s or pre-allocate large extents Enqueue . tune the code Buffer Busy Segment Header – Add freelists or freelist groups (Use ASSM) Buffer Busy Data Block – Separate ‘hot’ data.19 % SQL with executions>1: 81.TM Index foreign keys.62 84.

----------. waits desc (idle events last) Avg %Time Total Wait wait Waits Event Waits -outs Time (s) (ms) /txn ---------------------------. and wait classes statistics.0 216 0 12.------ ---------- CPU time 2.338 71 1 2.-------------.0 log file sequential read 220 .912 .3 os thread startup 655 .0 52 3 0.3 log file sync 41.0 59 1 0.942.1 User I/O Backup: sbtbackup 20 72 3608 2.0 71 1 1.-----.millisecond .116 458 0 12.680 216 0 6.------- --------- db file scattered read 1. Wait Events DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> s .Class -----------------------------.680 .0 control file parallel write 16.0 458 0 41.019 .-----------.0 System I/O ------------------------------------------------------------- all non-idle wait times for all sessions Wait Events Statistics Section: This section shows a breakdown of the main wait events in the database including foreground and background database wait events as well as time model.9 User I/O db file sequential read 603.microsecond .9 Backup: sbtclose2 20 .centisecond .1 db file scattered read 1.1000000th of a second -> ordered by wait time desc.3 db file sequential read 603.----------. Wait Events: This AWR report section provides more detailed wait event information for foreground user processes which includes Top 5 wait events and many other wait events that occurred during the snapshot interval.0 57 2875 0.135 60.-----.8 Backup: sbtbackup 20 .116 .0 .0 log file parallel write 61.8 42 65 0.338 . service. operating system.0 23 102 0.0 72 3608 0. 100th of a second -> ms .942.second -> cs .0 Administra log file parallel write 61. 1000th of a second -> us .

0 SQL*Net message to client 2.334 .0 LGWR wait for redo copy 921 .0 2 528 0.0 latch: redo allocation 17 .0 0 2 0.0 0 8 0.0 Backup: sbtinfo2 20 .3 Backup: sbtremove2 10 .4 SQL*Net break/reset to clien 12.0 17 146 0.0 6 621 0.0 read by other session 17.257.927 .0 latch: checkpoint queue latc 8 .0 1 0 1.653 .0 1 19 0.0 0 49 0.0 4 9 0.049 .0 latch: shared pool 428 .109 .0 0 0 0.0 recovery area: computing obs 298 .0 SQL*Net more data to client 74.0 recovery area: computing bac 863 .0 16 1 0.0 SQL*Net more data from clien 11.5 direct path read temp 68.0 0 0 0.0 control file single write 200 .contention 30 .861 .0 1 203 0.0 RMAN backup & recovery I/O 78 .0 0 4 0.0 1 37 0.0 2 0 48.0 kksfbc child completion 8 100.0 17 3 0.0 16 821 0.0 2 268 0.0 2 5 0.6 switch logfile command 11 .0 12 13 0.0 latch: row cache objects 30 .3 11 1909 0.0 enq: WL .0 enq: CF .0 7 1 0.0 3 0 2.056 .0 0 1 0.0 1 36 0.0 latch: cache buffer handles 7 .0 log file switch completion 4 50.contention 6 33.0 control file sequential read 99.db file parallel write 5.0 0 0 .0 2 52 0.320 .0 7 0 0.2 latch: cache buffers chains 74 .1 latch free 47 .0 1 80 0.5 Backup: sbtwrite2 885 .713 .0 Log archive I/O 362 .0 13 0 1.0 direct path write temp 24.1 latch: library cache 116 .

0.0 0 0 0.0 0 13 0.0 Backup: sbtend 10 .0 0 2 0.0 undo segment extension 281 100.0 latch: library cache lock 1 .0 0 1 0.0 0 3 0.0 SQL*Net message to dblink 62 .0 flashback buf free by RVWR 22 .0 direct path write 187 .0 0 45 0.0 0 1 0.0 0 0 0.0 buffer busy waits 51 .0 library cache pin 13 .0 .0 0 8 0.0 0 5 0.0 enq: SQ .0 library cache load lock 16 .0 log file single write 22 .0 0 0 0.0 recovery area: computing app 10 .0 latch: object queue header o 2 .0 enq: TX .0 0 0 0.0 Backup: sbtinit 10 .0 0 0 0.0 SGA: allocation forcing comp 1 .0 Backup: sbtinit2 10 .0 0 5 0.0 db file parallel read 35 .0 0 12 0.0 0 1 0.0 0 1 0.0 0 0 0.0 0 47 0.index contention 4 .0 0 2 0.0 recovery area: computing dro 10 .contention 1 .0 rdbms ipc reply 62 .

0 single-task message 4 .0 0 8 0.-----.-----. Background Wait Events DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> ordered by wait time desc.0 latch: library cache pin 1 .0 0 53 0.----------.0 SGA: MMAN sleep for componen 173 73.502 13429 0.0 latch: redo writing 1 .0 ------------------------------------------------------------- Background Wait Events: This section is relevant to the background process wait events.324 .0 215 4883 0.1 33.171 99.-------------.1 jobq slave wait 12. 100th of a second -> ms .625 2927 0. 1000th of a second -> us .----------. waits desc (idle events last) Avg %Time Total Wait wait Waits Event Waits -outs Time (s) (ms) /txn ---------------------------.0 0 0 0.-------------.406 67 48.0 latch: cache buffers lru cha 4 .3 Streams AQ: waiting for time 312 55.0 class slave wait 44 100.022 .4 1 8 0.Wait Events DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> s .0 0 0 0.0 Streams AQ: qmn slave idle w 1.------- --------- log file parallel write 61.0 71 1 1.second -> cs .1000000th of a second -> ordered by wait time desc.0 latch: session allocation 1 .502 27306 0.0 0 0 0.410 .0 49 3 .0 38.3 control file parallel write 14.412 .029 105863 0.8 35.centisecond . waits desc (idle events last) Avg %Time Total Wait wait Waits Event Waits -outs Time (s) (ms) /txn ---------------------------.0 Streams AQ: qmn coordinator 2.257.8 38.0 0 0 0.0 SQL*Net message from client 2.0 SQL*Net message from dblink 62 .millisecond .0 151.867 50.------- --------- direct path read 187 .microsecond .0 0 0 0.

0 0 1 0.0 rdbms ipc message 200.029 105863 0.3 Log archive I/O 168 .0 0 3 0.0 1 0 0.0 log file sync 22 .0 Streams AQ: waiting for time 312 55.0 0 0 0.475 .867 50.502 27306 0.0 latch: shared pool 5 .0 latch: library cache lock 1 .252 .0 ------------------------------------------------------------- Time Model Statistics: Time mode statistics report how database- processing time is spent.0 4 3 0.4 37.0 db file scattered read 308 .0 17 3 0.0 events in waitclass Other 1.3 os thread startup 654 .319 100.0 0 4 0.109 .0 0 5 0.0 0 0 0.3 pmon timer 14.0 0 47 0.0 SGA: MMAN sleep for componen 173 73.1 latch: library cache 51 .3 Streams AQ: qmn slave idle w 1.625 2697 0.050 .0 0 0 0.0.0 buffer busy waits 17 . Time Model Statistics DB/Inst: SALESNET/SNET Snaps: 14507- 14537 .0 direct path write 187 .8 42 65 0.0 0 1 0.0 latch: cache buffers chains 1 .573 2265 4.0 log file single write 22 .0 3 2 0.502 13429 0.0 38.0 Streams AQ: qmn coordinator 2.0 log file sequential read 118 .4 1 8 0.1 smon timer 171 68.2 453.0 direct path read 187 .1 33.0 38.0 19 165 0.0 latch: redo writing 1 .0 db file parallel write 5.0 0 0 0.0 13 264 0.0 2 6 0.509 219349 0.410 .0 control file sequential read 14.0 db file sequential read 1. This section contains detailed timing information on particular components participating in database processing.220 70.8 38.

552.8 Configuration 287 98.4 65 47 0.------- --------- User I/O 2.4 .1 RMAN cpu time (backup/restore) 1.8 .853.6 8.9 60.second -> cs .389 .9 Other 2.0 Concurrency 1. 100th of a second -> ms .7 N/A background cpu time 245.0 failed parse elapsed time 0.microsecond .5 System I/O 183.0 repeated bind elapsed time 0.1s -> Statistics including the word "background" measure background process time.0 3 0 49.2 connection management call elapsed time 37.0 20.912 .3 N/A ------------------------------------------------------------- Wait Class DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> s .-> Total time in database user-calls (DB Time): 3552.-----.0 sequence load elapsed time 1.6 2 8 0.0 59 1 0.320 .2 hard parse (sharing criteria) elapsed time 3.4 PL/SQL compilation elapsed time 8.8 . Statistic name Statistic Name Time (s) % of DB Time -----------------------------------------.1000000th of a second -> ordered by wait time desc.1 N/A background elapsed time 837.3 PL/SQL execution elapsed time 41.5 .0 DB time 3.-----------------.4 .275 .105 .134.3 Network 2.4 1.828 .7 .656.7 hard parse elapsed time 296.---------------.0 711 0 56.0 165 166 0.1 80.---------------.4 21 9 0.1 parse time elapsed 734.4 1.millisecond .1 .0 ------------------------------------------------------------- .0 168 1 3.centisecond .0 7 1 0.0 Application 12.0 hard parse (bind mismatch) elapsed time 1.------------ sql execute elapsed time 2. 1000th of a second -> us .317 . and so do not contribute to the DB time statistic -> Ordered by % or DB time desc.0 Commit 41.343.3 DB CPU 2.1 inbound PL/SQL rpc elapsed time 16. waits desc Avg %Time Total Wait wait Waits Wait Class Waits -outs Time (s) (ms) /txn -------------------.9 Administrative 996 .0 .

713 AVG_SYS_TIME 77.572.107.214 BUSY_TIME 4.834 USER_TIME 3.262. and network usage.536 NUM_CPUS 4 NUM_CPU_CORES 2 Service Statistics: The service statistics section gives information about how particular services configured in the database are operating. memory. Operating System Statistics DB/Inst: SALESNET/SNET Snaps: 14507- 14537 Statistic Total -------------------------------.064. CPU.713 IDLE_TIME 11.879 LOAD 0 OS_CPU_WAIT_TIME 5.948.385. .-------------------- NUM_LCPUS 0 NUM_VCPUS 0 AVG_BUSY_TIME 1.032.792 SYS_TIME 313.680 AVG_IDLE_TIME 2.000 RSRC_MGR_CPU_WAIT_TIME 0 PHYSICAL_MEMORY_BYTES 15.894 IOWAIT_TIME 466.Operating System Statistics: The stress on the Oracle server is important. and this section shows the main external resources including I/O.203 AVG_IOWAIT_TIME 115.892.471 AVG_USER_TIME 986.

0 9. -> Total Waits and Time Waited displayed for the following wait classes: User I/O.134.0 0.--------.0 0.7 2.--------. Network -> Time Waited (Wt Time) in centisecond (100th of a second) Service Name ---------------------------------------------------------------- User I/O User I/O Concurcy Concurcy Admin Admin Network Network Total Wts Wt Time Total Wts Wt Time Total Wts Wt Time Total Wts Wt Time --------.--------.7 ########## ########## SALESNET 0.-----------. Administrative.--------- --------- SYS$USERS 2649410 68453 634 807 996 16509 2290987 265 SYS$BACKGROUND 7415 2612 750 5611 0 0 0 0 ------------------------------------------------------------- .-----------.0 0 0 SYS$BACKGROUND 0.Service Statistics DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> ordered by DB Time Physical Logical Service Name DB Time (s) DB CPU (s) Reads Reads -------------------------------.551.--------. Concurrency.304 728.--------.468 ------------------------------------------------------------- Service Wait Class Stats DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Wait Class info for services in the Service Statistics section.---------- ---------- SYS$USERS 3.

. • SQL Ordered by Elapsed Time: Includes SQL statements that took significant execution time during processing. ordered by important SQL execution metrics.SQL Section: This section displays top SQL. • SQL Ordered by CPU Time: Includes SQL statements that consumed significant CPU time during its processing. • 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 Sharable Memory: Includes SQL statements cursors which consumed a large amount of SGA shared pool memory. • SQL Ordered by Version Count: These SQLs have a large number of versions in shared pool for some reason. • SQL Ordered by Parse Calls: These SQLs experienced a high number of reparsing operations.

I_IDOC_TIMESTAMP. broken BOOLEAN : = FALSE. SGA_SIZ E.5 gmp51k9qhajrs .I_IN TENGC ODE. 3. tran_status. -4. DECODE (t.'ACCEPTED'. onholdreason from crm_action_vw where tran_status = 'OP EN' AND code = 'TECHEN' AND action_status in('ASSIGNED'. BEGIN SELECT SYS_CONTEXT('USERENV'.I_Q UOTEV 38 29 30 1.table_name AS table_name.I_CUSTOMERREF.I_PRERECDL OC. next_date DATE := :mydate.I_SENGCODE.0 1. SGA_SIZE_FACTOR. SGA_SIZE.'ONHOLD') 46 43 7. t. instance_number. IF broken THEN :b := 1.I_GRADE.9 6gvch1xu9ca3g DECLARE job BINARY_INTEGER := :job.6 2v48tvxsbus8d Module: namgr. 'CH AR'. :instance_number.---------.I_RECDDATE.I_VERSION.009 0. action_status.I_SENGNAME. 1.data_type AS t 44 36 6.------.---------.0 1. t.I_EQSTATUS.I_ TRACKERCODE.SET_IDENTIFIER(v_u ser_identifier).6 1.-----------. 21 6 11. 'VARCHAR2'. 'LONG'. :dbi d. tran_loggeddate. 1111) AS data_type.I_BU_REF. :mydate := next_date . END IF. callid. 18 1 1 18.2 2cj1bzhruawfa Module: JDBC Thin Client INSERT INTO SAPIF_QUOTECOPIES (I_IDOC_NO.3 0. DBMS_SESSION.owner AS table_schem. assignedto. 'LONG RAW'.EXE select transaction_id. END. ESTD_DB_TIME.I_INTENGNAME. -1.SQL ordered by Elapsed Time DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code. 93. END.3 09bcp82ffxh72 Module: JDBC Thin Client SELECT NULL AS table_cat.I_BU.I_TE LNO. BEGIN EMD_MAINTENANCE. ESTD_PHYSICAL_R EADS from v$sga_target_advice 33 9 297 0.1 bunssq950snhf insert into wrh$_sga_target_advice (snap_id.data_type.210 0. 12.I_CONTACTNAME.column_name AS column_name. 'SES SION_USER') INTO v_user_identifier FROM dual. ELSE :b := 0. 'RAW '.I_QUOTENO. level3caseno. dbid.I_ACCNO. SGA_SIZE_FACTOR.I_ORDERDATE. -3. ESTD_PHYSICAL_READS) select :snap_id.I_ORDERNO.EXECUTE_EM_DBMS_JOB_PROCS(). 'NUMBER'.------------- 56 18 3 18.I_ACCNAME. -> % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100 Elapsed CPU Elap per % Total Time (s) Time (s) Executions Exec (s) DB Time SQL Id ---------.1 0. t. 'DATE'.459 0.6 946nc1uuwvu4n DECLARE v_user_identifier varchar2(20). ESTD_DB_TIME.I_REQDDATE.I_VALIDTODATE. t.I_CONTACTCODE.3 1.0 0.

2 0. allowphone. phone.LOGGEDDATE FROM CRM_TRANSACTION INNER JOIN CRM_TRA 14 1 1. substr(notes. contact_no.ACCOUNTNUMBER.LASTNAME . fax. estd_physical_reads from v$db_cache_advice where id = '3' 12 8 14 0. log geddate loggeddate.8 0.TRANSACTION_ID.FIRSTNAME.COMPANYNAME. job_code. status. estd_physical_read_time. CRM_TRANSACTION_VW.50) notes. transaction_id.EXE select code. callid callid. CRM_TRANS ACTION_VW. CRM_TRANSACTION_VW. CRM_TRANSACTION_VW. TEMPFIELD1.3 3qa6dxrc98tmy Module: nHTTP. status status. transaction_id t ransaction_id.CRM_TRANSACTION. accountnumber.079 0.EXE select accountnumber.CONTACT_NO. recordnumber recordnumber from crm_transaction where upper( accou 11 7 76 0. donotfax from (select accountnumb . pref_contact_method_code. mobile.Module: namgr. allowmail. CRM_TRANSACTION. pref_contact_method. last_name.4 aykvshm7zsabd select size_for_estimate. r ecordnumber from (select code code. so urce_table. job_de sc. CRM_TRANSACTION. email. allowemail.0 0. callid. CRM_TRANSACTION. size_factor * 100 f.3 02b1z9pttr658 Module: nHTTP. accountnumber accountnumber.EXE SELECT CRM_TRANSACTION. title. first_name. notes.1. loggeddate.COMPANYNAME.

------------- er accountnumber. contact_no contact_no. -> % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100 Elapsed CPU Elap per % Total Time (s) Time (s) Executions Exec (s) DB Time SQL Id ---------.-----------.---------. las ------------------------------------------------------------- .---------.------. title title.SQL ordered by Elapsed Time DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code. first_name first_name.

I_ACCNAME. :dbi d.column_name AS column_name. IF broken THEN :b := 1. assignedto. -4. callid. 12.I_PRERECDL OC.EXE select transaction_id.EXECUTE_EM_DBMS_JOB_PROCS().I_CUSTOMERREF.3 09bcp82ffxh72 Module: JDBC Thin Client SELECT NULL AS table_cat. ESTD_PHYSICAL_READS) select :snap_id. 'LONG RAW'.I_EQSTATUS.I_VERSION. callid callid.89 1.------.I_CONTACTNAME. dbid. broken BOOLEAN : = FALSE. 93.I_IDOC_TIMESTAMP. -3.SQL ordered by CPU Time DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.'ONHOLD') 9 33 297 0. SGA_SIZ E. substr(notes.01 1. t.009 0. level3caseno.I_ORDERNO.-----------.98 1. t. status status.I_CONTACTCODE.I_VALIDTODATE. transaction_id t .1 bunssq950snhf insert into wrh$_sga_target_advice (snap_id.2 2cj1bzhruawfa Module: JDBC Thin Client INSERT INTO SAPIF_QUOTECOPIES (I_IDOC_NO. SGA_SIZE_FACTOR.01 1. 8 12 14 0. onholdreason from crm_action_vw where tran_status = 'OP EN' AND code = 'TECHEN' AND action_status in('ASSIGNED'.I_BU. 'VARCHAR2'. status. 'NUMBER'.I_BU_REF. log geddate loggeddate. SGA_SIZE.I_QUOTENO.I_RECDDATE. SGA_SIZE_FACTOR.I_IN TENGC ODE.I_GRADE.9 6gvch1xu9ca3g DECLARE job BINARY_INTEGER := :job.1. callid.I_SENGCODE. notes.I_ACCNO. t.---------. ESTD_PHYSICAL_R EADS from v$sga_target_advice 18 56 3 5.table_name AS table_name.459 0. DECODE (t.6 2v48tvxsbus8d Module: namgr. -> % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100 CPU Elapsed CPU per % Total Time (s) Time (s) Executions Exec (s) DB Time SQL Id ---------. BEGIN EMD_MAINTENANCE. t.I_ORDERDATE. ESTD_DB_TIME. END IF.60 0.'ACCEPTED'. :mydate := next_date . transaction_id.I_INTENGNAME. 3. END.I_REQDDATE.data_type AS t 36 44 6.I_ TRACKERCODE. loggeddate. 'DATE'. -1.----------. 'LONG'. 1111) AS data_type.03 0. accountnumber accountnumber. tran_loggeddate. ELSE :b := 0. 'CH AR'.EXE select code.I_TE LNO. 1. ESTD_DB_TIME.owner AS table_schem.------------- 43 46 7.50) notes. accountnumber.data_type.I_SENGNAME. r ecordnumber from (select code code. next_date DATE := :mydate. :instance_number. action_status. tran_status.I_Q UOTEV 29 38 30 0. 'RAW '.3 3qa6dxrc98tmy Module: nHTTP. instance_number.

distkey.09 0.town.00 0.i.custo mer_category.i.nvl( 7 11 76 0.pctf ree$.type#.i.EXE SELECT companyname.ransaction_id.phone.00 0.1).3 54cjjrxy34pyh Module: nHTTP.initrans.indmethod#.i.nvl(i.i.i. 'SES SION_USER') INTO v_user_identifier FROM dual.i.userfieldg. recordnumber recordnumber from crm_transaction where upper( accou 7 10 8.774 0. mobile. donotfax from (select accountnumb er accountnumber.block#.dblkkey .i.property.1). DBMS_SESSION. pref_contact_method_code.file#.degree. BEGIN SELECT SYS_CONTEXT('USERENV'.dataobj#.cl ufac.i.256). allowemail.09 0.maxtrans.pctthres$.rowcnt. job_de sc. fax. contact_no contact_no. allowmail. title.i.i. phone.nvl(i.0) .lblkkey. title title.i.userfieldm FROM cqs_snet_accounts_vw WHERE (upper( acco untnumber ) like 'SAL012%') ORDER BY companyname DESC 6 21 11. first_name first_name.6 946nc1uuwvu4n DECLARE v_user_identifier varchar2(20).i.i.EXE select accountnumber.unicols.trunccnt. first_name. last_name.nvl(c. pref_contact_method.i.i. job_code.3 02b1z9pttr658 Module: nHTTP.samplesize.postcode.3 7ng34ruy5awxq select i.i.ts#.i. las 7 11 77 0.userfield1.obj#.accountnumber.i.210 0.mod(i.i.blevel. email.flags.i. allowphone.intcols. contact_no.ins tance s.i.i.cols.leafcnt.SET_IDENTIFIER(v_u . so urce_table.userfield2.analyzetime.

SQL ordered by CPU Time DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.-----------. ------------------------------------------------------------- .----------. END.------------- ser_identifier).---------.------. -> % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100 CPU Elapsed CPU per % Total Time (s) Time (s) Executions Exec (s) DB Time SQL Id ---------.

userfieldm FROM cqs_snet_accounts_vw WHERE (upper( acco untnumber ) like 'SAL012%') ORDER BY companyname DESC 257.-------. -> Total Buffer Gets: 64.05 10. allowemail. first_name first_name.-----------. loggeddate. fax. donotfax from (select accountnumb er accountnumber.972 -> Captured SQL account for 16. callid callid.table_name AS table_name.I_CONTACTCODE. 93.64 09bcp82ffxh72 Module: JDBC Thin Client SELECT NULL AS table_cat. accountnumber.custo mer_category.I_IDOC_TIMESTAMP. substr(notes.I_ACCNO. log .owner AS table_schem.userfield1. t.I_BU_REF. title title. 'LONG RAW'.I_SENGNAME.I_ TRACKERCODE.data_type AS t 900.userfield2. phone.EXE select code. pref_contact_method_code.data_type. 'NUMBER'.84 3qa6dxrc98tmy Module: nHTTP.I_SENGCODE.I_QUOTENO.266 7. contact_no. status.94 54cjjrxy34pyh Module: nHTTP.273. contact_no contact_no. t.I_VERSION. las 255.86 43. -4.-----.394. 'VARCHAR2'.8 0.147.I_ACCNAME.89 2cj1bzhruawfa Module: JDBC Thin Client INSERT INTO SAPIF_QUOTECOPIES (I_IDOC_NO.postcode.SQL ordered by Gets DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.I_VALIDTODATE. 1111) AS data_type. notes.4 7.column_name AS column_name.43 11.44 02b1z9pttr658 Module: nHTTP. -3.I_CUSTOMERREF. allowphone.I_BU. 3. 12.8 42. job_de sc.EXE SELECT companyname.4 8.I_EQSTATUS.009 535.--------- ------------- 3. title. last_name.293. r ecordnumber from (select code code. DECODE (t.9% of Total Gets CPU Elapsed Buffer Gets Executions per Exec %Total Time (s) Time (s) SQL Id -------------.phone. pref_contact_method.I_GRADE.I_Q UOTEV 330.I_IN TENGC ODE.I_REQDDATE.town.-----------.1 0.1. allowmail.I_ORDERNO. t. t. transaction_id.4 35.I_RECDDATE.I_PRERECDL OC.5 7. job_code. 'RAW '.userfieldg.accountnumber.70 45. 'CH AR'.12 11. email.I_INTENGNAME. 'LONG'.3 5. 'DATE'.4 1.620 77 4.752.I_ORDERDATE.50) notes.6 0.993 76 3.EXE select accountnumber.562 6. first_name.823 14 18. mobile. callid.I_TE LNO. 1.459 139. -1. so urce_table.I_CONTACTNAME.

END IF.spare2 from icol$ where obj#=:1 109."LOGGEDBY" "Logged_By" from "SALESNET". onholdreason from crm_action_vw where tran_status = 'OP EN' AND code = 'TECHEN' AND action_status in('ASSIGNED'.53 1.2 1. status status.638 6 18.439.1 1. assignedto.2 0.16 6.47 33.588 4."CRM_TR ANSACTION" "CRM_TRANSACTION" order by "Logged_By" asc nulls last 106.18 219rt7uzd6j34 Module: BIBusTKServerMain.56 53saa2zkr6wc3 select intcol#.2 4. END. ELSE :b := 0. broken BOOLEAN : = FALSE.7 0.nvl(pos#. tran_loggeddate. callid.675 19. transaction_id t ransaction_id. action_status.317 23.8 0. :mydate := next_date . IF broken THEN :b := 1.319 3 35.64 6769wyy3yf66f select pos#.EXE select transaction_id. next_date DATE := :mydate.intcol#.EXECUTE_EM_DBMS_JOB_PROCS(). recordnumber recordnumber from crm_transaction where upper( accou 159.67 2v48tvxsbus8d Module: namgr.0).273.838 297 538.col#.geddate loggeddate.0) from ccol$ where con#=:1 ------------------------------------------------------------- . accountnumber accountnumber.nvl(spare1.0 0.'ONHOLD') 94.spare1.bo#.'ACCEPTED'.exe select distinct "CRM_TRANSACTION".4 0. tran_status.col#.2 17.2 9.03 6gvch1xu9ca3g DECLARE job BINARY_INTEGER := :job.439 5. BEGIN EMD_MAINTENANCE. 126. level3caseno.66 55.20 1.

147.0 17. status. recordnumber recordnumber from crm_transaction where upper( accou 73. transaction_id t ransaction_id. notes. r ecordnumber from (select code code."LOGGEDBY" "Logged_By" from "SALESNET". recordnumber recordnumber from crm_transaction where upper( accou 87.3 1. accountnumber accountnumber. tran_loggeddate.3 4. substr(notes.8 0. accountnumber. status.391 4 16. status status.097. loggeddate. callid.1.16 6.EXE select code. onholdreason from crm_action_vw where tran_status = 'OP EN' AND code = 'TECHEN' AND action_status in('ASSIGNED'.84 3qa6dxrc98tmy Module: nHTTP.18 219rt7uzd6j34 Module: BIBusTKServerMain. action_status. transaction_id.794 -> Captured SQL account for 9. status status.EXE select code. assignedto.4 0.EXE select code. callid callid. level3caseno. accountnumber. tran_status. loggeddate.3 2. callid.43 11. r ecordnumber from (select code code.'ONHOLD') 226. notes. status.107 3 99. callid. callid.1.702. loggeddate. log geddate loggeddate. log geddate loggeddate. accountnumber. accountnumber accountnumber.09 3.802 5 17.92 3.'ACCEPTED'.50) notes. substr(notes.01 a0t3v0f069rgb Module: nHTTP.-------.199.----------.66 55. status status.--------- ------------- 299.068 14 16.1. transaction_id.2% of Total Reads CPU Elapsed Physical Reads Executions per Exec %Total Time (s) Time (s) SQL Id -------------.------------. callid callid.178."CRM_TR ANSACTION" "CRM_TRANSACTION" order by "Logged_By" asc nulls last 64.2 2. transaction_id t .SQL ordered by Reads DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Total Disk Reads: 29.8 8.7 0.7 0.50) notes.75 6u1f3nky542fr Module: nHTTP. notes. log geddate loggeddate. r ecordnumber from (select code code.67 2v48tvxsbus8d Module: namgr.exe select distinct "CRM_TRANSACTION". accountnumber accountnumber.560. substr(notes. transaction_id t ransaction_id.-----. callid callid.EXE select transaction_id.50) notes. transaction_id.198 6 12.

rlock from (select code code.0 0. recordnumber. tran_loggeddate. recordnumber rec 59. recordnumber. transaction_id transaction_id. notes.2 1.14 6uah25bcnz4s9 Module: nHTTP.EXE select code.EXE select code. tran_loggeddate. checkedout.1. tran_loggeddate.2 1.50) notes. callid.81 9. accountnumber.845 2 30. recordnumber rec 59.0 0. substr(notes. recordnumber. substr(notes. recordnumber rec 60. rlock from (select code code.66 2.70 2. recordnumber rec . accountnumber.5 0. rlock from (select code code.622.50) notes. substr(notes.2 1.592 2 29.796.EXE select code. callid callid. tran_status. notes. accountnumber. accountnumber accountnumber.749.1. recordnumber.498 2 29.75 2.22 5n6x02qbpfqm7 Module: nHTTP. transaction_id transaction_id. tran_status tran_stat us.73 b758gugh6wrvd Module: nHTTP.1. callid callid. tran_loggeddate. tran_status tran_stat us. accountnumber. tran_status tran_stat us. transac tion_id. callid. tran_loggeddate tran_loggeddate. transaction_id transaction_id.50) notes. callid callid. tran_status. transaction_id transaction_id. callid. accountnumber accountnumber.5 0. substr(notes. notes.2 1. tran_status. transac tion_id. recordnumber recordnumber from crm_transaction where upper( accou 61.32 4wsjqsfss2u2p Module: nHTTP. accountnumber accountnumber. accountnumber accountnumber. tran_loggeddate tran_loggeddate. checkedout.422.50) notes.245 2 30.1. transac tion_id. tran_loggeddate tran_loggeddate. rlock from (select code code. transac tion_id. tran_status tran_stat us. tran_status. checkedout. callid. notes. callid callid. checkedout.EXE select code. tran_loggeddate tran_loggeddate.ransaction_id.

checkedout.--------- ------------- 59. substr(notes. tran_loggeddate. tran_loggeddate tran_loggeddate. notes. callid callid. transaction_id transaction_id.50) notes.------------. recordnumber rec ------------------------------------------------------------- .15 5qudsshx7hgs2 Module: nHTTP.178. callid.0 0.-----.736.----------.EXE select code. transac tion_id. rlock from (select code code.-------. recordnumber.73 2.SQL ordered by Reads DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Total Disk Reads: 29.2% of Total Reads CPU Elapsed Physical Reads Executions per Exec %Total Time (s) Time (s) SQL Id -------------. accountnumber accountnumber. tran_status tran_stat us.2 1.1.472 2 29. tran_status. accountnumber.794 -> Captured SQL account for 9.

scale.----------- ------------- 32.--------------. BEGIN SELECT SYS_CONTEXT('USERENV'.694 1.nvl(deflength.scale.00 0.139 27.0.0.210 1. range_preds = range_preds + decode(bitand(:flag.00 0.0 .1).- 127/*MAXSB1MINAL*/).00 53saa2zkr6wc3 select intcol#.length.180.4).588 27.079.scale.4 0.00 6769wyy3yf66f select pos#.0).scale.2).p roper .7 0.col_usage$ set equality_preds = equality_preds + decode(bitan d(:flag.00 0.472 0.210 11.6 0.0.default$.00 0.183.0).00 0.0).00 0h6b2sajwb74n select privilege#.179.00 946nc1uuwvu4n DECLARE v_user_identifier varchar2(20).spare1.decode(type#.0.nvl(spare1."XTRASECURITY" FROM "SALESNET ". nonequijoin_preds = nonequijoin_preds + decode(bitand(:flag.0.106 2.rowid.4 0.scale.intcol#. 10.1).00 0.182.col#.col#.-------------.s cale.733 1.intcol#.139 1.0 0.00 3fwypqz13krwu Module: MSACCESS.1). 11.bo#."USERSEC" WHERE "USERKEY" = :1 AND "TABLENAME" = :2 23.231.181.level from sysauth$ connect by grantee#=prior privilege# and p rivilege#>0 start with grantee#=:1 and privilege#>0 27.nvl(pos#.605 17.00 0k8522rmdzg4k select privilege# from sysauth$ where (grantee#=:1 or grantee#=1) and privilege# >0 9.1).0.446 -> Captured SQL account for 30.001 29.00 3c1kubcdjnppq update sys.717 13.00 0.517 18.0 0."FIELDSEC".0) from ccol$ where con#=:1 13. equijoin_preds = equijoin_preds + decode(bitand(:flag .EXE SELECT "USERKEY".1). 'SES SION_USER') INTO v_user_identifier FROM dual.9 0."TABLENAME". END.scale.0).spare2 from icol$ where obj#=:1 19.null$.510 165.178.00 83taa7kaw59c1 select name.0.439 39.---------.SET_IDENTIFIER(v_u ser_identifier).col#.00 0.SQL ordered by Executions DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Total Executions: 1.2."SECURITY".nvl(sc ale. DBMS_SESSION.1% of Total CPU per Elap per Executions Rows Processed Rows per Exec Exec (s) Exec (s) SQL Id -----------.segcol#.type#.nvl(precision#.703 1.0 0.fixedstorage.8).

cl ufac.maxtrans.i.degree.i.i.00 0.249 8.0).i.property.dataobj#.leafcnt.lblkkey.i.rowcnt.ty.i.spare1. nvl(charsetid.i.distkey.638 2.nvl(i.nvl(i.i.ts#.i.obj#.nvl(spare3.0) .pctthres$.analyzetime.nvl( 8.cols.mod(i.initrans.i.249 1.7 0.256).00 0.type#.pctf ree$.nvl(c. 'SESSION_USER') FROM DUAL ------------------------------------------------------------- .0) from col$ wh 8.i.i.i.0).i.774 23.i.samplesize.i.i.i.i.i.block#.00 7ng34ruy5awxq select i.i.indmethod#.ins tance s.i.dblkkey .flags.1).i.1).nvl(charsetform.trunccnt.file#.blevel.00 g8skttwyjx17y Module: JDBC Thin Client SELECT SYS_CONTEXT('USERENV'.unicols.spare2.0 0.intcols.

7% of Total % Total Parse Calls Executions Parses SQL Id -----------. 'VARCHAR2'. 'LONG RAW'. DECODE (t.250 8. t. -1.I_ACCNAME.210 11.I_VERSION.684 0.517 4.I_VALIDTODATE.' NLS_CALENDAR= 'GREGORIAN' NLS_DAT E_FORMAT= 'DD-MON-RR' NLS_DATE_LANGUAGE= 'ENGLISH' NLS_COMP= 'B 7.363 1.I_ORDERNO.I_ACCNO.210 1.I_IDOC_TIMESTAMP.055 -> Captured SQL account for 29.006 7.365 7.I_ TRACKERCODE. t.--------.249 1.I_CUSTOMERREF.data_type.EXE SELECT VALUE FROM V$NLS_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET' 7.I_QUOTENO.98 2cj1bzhruawfa Module: JDBC Thin Client INSERT INTO SAPIF_QUOTECOPIES (I_IDOC_NO.682 5. 10..I_BU_REF.I_BU.002 10.86 asvzxj61dc5vs select timestamp. flags from fixed_obj$ where obj#=:1 . 1111) AS data_type.column_name AS column_name.data_type AS t 6. 'DATE'. -4.51 0k8522rmdzg4k select privilege# from sysauth$ where (grantee#=:1 or grantee#=1) and privilege# >0 8.table_name AS table_name.I_CONTACTCODE.459 0.I_RECDDATE. DBMS_SESSION. 'SESSION_USER') FROM DUAL 7. 12.69 946nc1uuwvu4n DECLARE v_user_identifier varchar2(20).------------- 32.06 09bcp82ffxh72 Module: JDBC Thin Client SELECT NULL AS table_cat. 'RAW '.I_TE LNO. t.-----------.I_PRERECDL OC.I_IN TENGC ODE.owner AS table_schem.I_SENGNAME.25 g8skttwyjx17y Module: JDBC Thin Client SELECT SYS_CONTEXT('USERENV'. -3.I_INTENGNAME.457 6.I_CONTACTNAME.I_SENGCODE.I_EQSTATUS.I_GRADE.I_REQDDATE. 'NUMBER'.I_ORDERDATE. 93. 1.level from sysauth$ connect by grantee#=prior privilege# and p rivilege#>0 start with grantee#=:1 and privilege#>0 11.365 1.11 18m93d30zw6mb Module: nHTTP. BEGIN SELECT SYS_CONTEXT('USERENV'. 'LONG'. 3.517 32.363 7.I_Q UOTEV 5. t. 'SES SION_USER') INTO v_user_identifier FROM dual.11 3n58uzvnuw2hj Module: namgr.009 1. 'CH AR'.EXE ALTER SESSION SET NLS_LANGUAGE= 'ENGLISH' NLS_TERRITORY= 'UNITED KINGDOM' NLS_CURRENCY= '#' NLS_ISO_CURRENCY= 'UNITED KINGDOM' NLS_NUMERIC_CHARACTERS= '. END.001 1.SET_IDENTIFIER(v_u ser_identifier).SQL ordered by Parse Calls DB/Inst: SALESNET/SNET Snaps: 14507- 14537 -> Total Parse Calls: 662.91 0h6b2sajwb74n select privilege#.

Instance Activity Stats (Thread Activity): This report section reports a log switch activity statistic.994 4. Instance Activity Stats (Absolute Values): This section contains statistics that have absolute values not derived from end and start snapshots.columns.993 0. . ------------------------------------------------------------- Instance Activity Stats: This section contains statistical information describing how the database operated during the snapshot period. ------------------------------------------------------------- SQL ordered by Version Count DB/Inst: SALESNET/SNET Snaps: 14507- 14537 No data exists for this section of the report. 4.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.75 8swypbbr0m372 select order#.

-------------- ------------- CPU used by this session 168.0 0.9 0.260 4.2 OS Page faults 112.2 CR blocks created 499 0.3 OS Signals received 0 0.0 background checkpoints completed 11 0.870 100.0 .4 OS Page reclaims 3.2 47.9 18.0 0.767.6 CPU used when call started 151.580.6 0.0 background checkpoints started 11 0.8 SMON posted for undo segment shr 14 0.327 35.749.405.148 3.294 626.9 OS Involuntary context switches 866.371 4.3 SQL*Net roundtrips to/from dblin 62 0.0 OS System time used 22.0 DBWR undo block writes 12.0 0.962.0 DBWR transaction table writes 1.9 4.7 57.0 0.407.0 0.514 21.6 OS Integral unshared data size 24.0 526.866.948.0 application wait time 685 0.1 OS Voluntary context switches 2.164 56.511.107.155 0.520 13.7 DBWR checkpoint buffers written 33.610 0.675.3 3.7 DBWR checkpoints 11 0.099 0.0 0.593 3.9 2.225.121 68.717.799.0 Commit SCN cached 0 0.0 0.0 0.3 OS Integral shared text size 134.8 11.0 DB time 1.4 OS Maximum resident set size 541.0 0.0 active txn count during cleanout 1.5 OS User time used 194.8 3.-----------------.689 2.0 0.0 Cached Commit SCN referenced 0 0.478 0.0 0.425 0.3 0.6 2.4 29.0 0.2 84.Instance Activity Stats DB/Inst: SALESNET/SNET Snaps: 14507- 14537 Statistic Total per Second per Trans -------------------------------.0 SQL*Net roundtrips to/from clien 2.

0 commit cleanouts 143.863 0.1 commit txn count during cleanout 581 0.863 0.673 34.632 1.7 0.821 325.270.0 concurrency wait time 6.764 12.consis 153 0.349 0.336 0.0 buffer is not pinned count 12.733.0 cleanouts only .240 0.6 7.1 commit batch/immediate requested 5.0 28.0 0.6 calls to kcmgas 74.5 0.1 commit cleanout failures: block 0 0.0 0.2 0.0 0.6 3.2 cluster key scans 922.0 cluster key scan block gets 2.410 0.1 commit immediate performed 5.0 branch node splits 0 0.353 3.0 commit batch/immediate performed 5.consistent read 43 0.6 commit batch performed 4 0.1 .7 bytes received via SQL*Net from 366.4 calls to get snapshot scn: kcmgs 1.0 0.462 3.6 3.0 commit cleanout failures: callba 106 0.0 0.0 0.2 0.7 568.0 0.9 1.2 0.0 0.0 commit batch requested 4 0.155 0.2 bytes received via SQL*Net from 28.1 change write time 1.6 bytes sent via SQL*Net to client 504.0 commit cleanout failures: buffer 3 0.321 0.345.803.360 65.091 9.826 23.394 3.859 0.number of ktugct call 1.1 commit cleanouts successfully co 143.592.2 0.3 bytes sent via SQL*Net to dblink 20.3 buffer is pinned count 26.859 0.0 0.589 675.728.0 0.4 10.756.0 0.0 cleanout .5 55.807.0 cleanouts and rollbacks .1 commit immediate requested 5.6 calls to kcmgcs 2.background timeouts 140.9 274.3 19.2 0.737.893.1 0.6 3.

286 1.514.consistent changes 505 0.605.101.examination 4.0 consistent gets 63.7 87.929 103.0 0.3 .3 1.351.2 consistent gets .

2 heap block compress 5.6 index fast full scans (full) 789 0.2 43.0 13.1 hot buffers moved to head of LRU 577.-----------------.863 14.0 0.5 deferred (CURRENT) block cleanou 81.243 15.686 16.0 0.0 0.368 0.1 0.5 db block gets 633.0 db block changes 633.1 0.242 0.2 enqueue releases 603.351.514.505 52.9 index scans kdiixs1 1.0 0.3 1.0 db block gets from cache 633.686 16.0 free buffer inspected 29.138 732.064 0.7 dirty buffers inspected 3.992.Instance Activity Stats DB/Inst: SALESNET/SNET Snaps: 14507- 14537 Statistic Total per Second per Trans -------------------------------.0 flashback log writes 2.0 free buffer requested 28.304 0.0 0.1 1.965.0 0.802 734.226 15.0 0.2 0.2 618.4 42.1 frame signature mismatch 0 0.0 enqueue waits 39 0.1 enqueue conversions 9.-------------- ------------- consistent gets direct 0 0.7 0.2 cursor authentications 29.691 2.1 616.181 16.0 0.0 index fetch by key 2.5 db block gets direct 0 0.7 0.065.6 12.168 0.429 50.0 immediate (CURRENT) block cleano 28.8 enqueue requests 603.0 13.3 12.3 immediate (CR) block cleanout ap 196 0.286 1.6 data blocks consistent reads .605.0 execute count 1.446 27.u 505 0.1 0.8 enqueue timeouts 18 0.3 12.3 23.079.386 0.4 .047.0 consistent gets from cache 63.0 13.

6 57.4 physical read total multi block 1.095.303 667.448 6.0 physical write IO requests 46.7 opened cursors cumulative 682.055 16.7 1.418.3 0.0 parse count (hard) 121.920 6.257 1.178.0 logons cumulative 11.6 physical reads direct (lob) 0 0.455 68.7 562.680.0 616.611.7 physical reads cache 28.239.0 0.1 parse time cpu 19.7 1.446.0 55.3 messages received 66.5 0.0 physical reads direct 215.197.4 parse time elapsed 73.0 0.1 2.3 0.5 620.0 lob reads 11.103.965 17.131 5.leaf node 90-10 splits 232 0.714.183 0.257 1.3 0.805 1.940 0.649 3.7 14.6 5.0 0.2 1.032.0 no work .3 14.0 0.963.131.0 lob writes unaligned 451 0.4 5.6 physical read bytes 239.7 41.259.0 0.777.6 physical read IO requests 2.217.476 732.318 5.965.794 737.8 physical reads 29.232 0.0 0.0 physical reads direct temporary 215.4 4.942 1.078 0.4 messages sent 66.8 physical read total bytes 241.2 physical reads prefetch warmup 0 0.0 0.517 49.0 .275 1.4 no buffer to keep pinned count 0 0.2 physical reads cache prefetch 26.979.4 physical read total IO requests 2.0 leaf node splits 414 0.consistent read gets 57.0 0.6 parse count (total) 662.7 1.044.5 parse count (failures) 32 0.4 4.2 lob writes 451 0.041.9 1.085.222 66.6 physical reads for flashback new 10.

432.307.158 4.4 physical write total bytes 3.754.7 44.792 52.731.448 94.4 79.physical write bytes 2.087.0 3.404.380.329.4 .7 physical write total IO requests 159.

0 0.2 0.8 physical writes non checkpoint 234.268 3.undo records 5.0 84.0 prefetched blocks aged out befor 4 0.0 redo ordering marks 9.3 redo log space requests 4 0.886 5.-----------------.3 redo write time 7.0 0.072.903 0.1 6.8 0.0 0.6 physical writes from cache 39.0 redo entries 340.6 7.2 1.4 4.2 0.568.0 0.9 5.321 0.017.0 0.0 0.385 5.2 redo writer latching time 11 0.331 2.0 0.568 8.1 .3 rollback changes .141 2.2 redo synch time 6.0 redo buffer allocation retries 3 0.224 0.7 redo blocks written 281.550 7.3 1.-------------- ------------- physical write total multi block 87.676 455.Instance Activity Stats DB/Inst: SALESNET/SNET Snaps: 14507- 14537 Statistic Total per Second per Trans -------------------------------.1 recursive cpu usage 33.0 physical writes direct temporary 215.198 5.9 physical writes 254.954.750 0.0 process last non-idle time 39.586.4 4.801 6.8 recursive calls 3.2 redo size 121.6 physical writes direct (lob) 0 0.1 prefetch warmup blocks aged out 0 0.0 redo writes 61.4 383.2 0.4 5.9 redo wastage 18.416 1.0 0.1 0.305 1.538 1.6 1.096 0.2 0.0 pinned buffers inspected 2.5 2.4 physical writes direct 215.0 0.0 redo log space wait time 216 0.281 0.598 100.1 redo synch writes 89.

6 session connect time 0 0.5 user calls 2.0 0.0 sorts (memory) 237.800.461.976 28.270.814.385.546 0.5 1.rollbacks only .3 total number of times SMON poste 54 0.7 table scans (long tables) 3.539 1.0 0.8 9.643 35.995 1.530.121.7 session pga memory 984.041.621.364.056 1.3 session uga memory max 5.023.312 1.224.981 64.1 table fetch continued row 32.024.6 126.133.952.233.147.206 10.0 0.084 49.139.2 898.5 user commits 46.951 1.0 user rollbacks 56 0.742.972 1.965.7 23.471.8 1.943.3 user I/O wait time 71.7 20.2 0.9 shared hash latch upgrades .0 5.154.563.1 0.970.992 6.wai 3.956 29.922.no 1.528 66.8 41.2 session uga memory 2.0 session cursor cache hits 428.2 24.480.892.0 0.0 .0 summed dirty queue length 4.2 362.1 undo change vector size 42.3 1.7 session pga memory max 1.4 29.2 1.0 rows fetched via callback 1.0 0.863 0.504 150.126.0 transaction rollbacks 5.620.755 0.080 0.0 table scan rows gotten 1.5 shared hash latch upgrades .224.6 944.consistent read 343 0.8 0.1 session logical reads 64.0 0.9 298.1 0.1 0.0 0.067.167 430.154 0.7 sql area purged 0 0.7 table scan blocks gotten 44.912 0.376.1 sorts (rows) 14.967.048 24.5 55.0 table fetch by rowid 17.1 table scans (short tables) 60.172 354.1 switch current to new buffer 1.1 sorts (disk) 8 0.8 54.

onepass 33 0.multipass 8 0.7 .0 0.0 workarea executions .workarea executions .0 workarea executions .optimal 174.0 0.876 4.4 3.

0 ------------------------------------------------------------- .Instance Activity Stats DB/Inst: SALESNET/SNET Snaps: 14507- 14537 Statistic Total per Second per Trans -------------------------------.0 0.-------------- ------------- write clones created in backgrou 0 0.-----------------.0 write clones created in foregrou 1 0.0 0.

and PGA Memory Advisory.398 opened cursors current 117 91 logons current 29 63 ------------------------------------------------------------- Instance Activity Stats . Latch Activity: This section shows details about latch statistics. 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: .--------- log switches (derived) 11 1.Instance Activity Stats . Buffer Pool Advisory PGA Aggr Summary: PGA Aggr Target Stats.-----------------.--------------. shared pool. Enqueue Activity: This important section shows how enqueue operates in the database. data file. Tablespace IO Stats File IO Stats Buffer Pool Statistics Advisory Section: This section show details of the advisories for the buffer. Shared Pool Advisory Java Pool Advisory Buffer Wait Statistics: This important section shows buffer cache waits statistics. Latches are a lightweight serialization mechanism that is used to single- thread access to internal Oracle structures.648 135.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.Thread ActivityDB/Inst: SALESNET/SNET Snaps: 14507- -> Statistics identified by '(derived)' come from sources other than SYSSTAT Statistic Total per Hour -------------------------------. Enqueues are special internal structures which provide concurrent access to various database resources. Undo Segment Stats: This section shows detailed history information about undo segment activity. Undo Segment Summary: This section gives a summary about how undo segments are used by the database. PGA and Java pool. and includes buffer pool statistics.00 ------------------------------------------------------------- I/O Section: This section shows the all important I/O activity for the instance and shows I/O activity by tablespace. PGA Aggr Target Histogram.

Library Cache Activity: Includes library cache statistics describing how shared library objects are managed by Oracle.ora Parameters: This section shows the original init. Segments by Row Lock Waits: Includes segments that had a large number of row locks on their data. init. Dictionary Cache Stats: This section exposes details about how the data dictionary cache is operating. Segments by Logical Reads: Includes top segments which experienced high number of logical reads. .ora parameters for the instance during the snapshot period. SGA Memory Summary: This section provides summary information about various SGA regions. Segments by Physical Reads: Includes top segments which experienced high number of disk physical reads. The contention for ITL can be reduced by increasing INITRANS storage parameter of the table. Segments by Buffer Busy Waits: These segments have the largest number of buffer waits caused by their data blocks. Segments by ITL Waits: Includes segments that had a large contention for Interested Transaction List (ITL).