Interpreting BW Statistics

Is there any documentation of the meaning of the key figures in the BW statistics cubes?
I just want to report on how often a specific query is being run, not the performance of that query.
There must be an appropriate key figure for this in 0BWTC_C02, but there are so many of them that I don't know where to start.
Kate

You should have a Number of Navigations KF which would correspond to the number of queries run. 
ST03N in Expert Mode also provides this information, but it only has some predefined timeframes, e.g.
Today
1 day ago
2 days ago
This week
1 week ago
2 weeks ago
This month
1 month ago
2 months ago

Similar Messages

  • WAAS 4.1 - connection statistics

    Need help interpreting connection statistics.
    The GUI shows no values against 'Percentage Compression' and 'Effective Capacity' (as per attached .jpg's)
    Outputs of 'sh stat conn det' on both peer WAE's appear to show that the connection is fully optimised in both directions (as per attached .txt's).
    How can I calculate optimisation result for the CLI output?
    Thanks
    DG

    DG,
    The statistics show that the output bytes on the optimised connection are >= the input bytes from the original connection. So basically compression isn't buying you anything here.
    What type of traffic is this? Is it encrypted?
    Zach

  • What's the difference between "Analyze amplitude" and "Analyze Loudness statistics" ?

    Hello!
    I wanted to find out tracks's RMS and found these 2 variants of measuring:
    http://help.adobe.com/en_US/Audition/3.0/help.html?content=WS58a04a822e3e5010548241038980c 2c5-7f54.html
    http://help.adobe.com/en_US/Audition/3.0/help.html?content=WS58a04a822e3e5010548241038980c 2c5-7de9.html
    What's the difference between them? Because the result of measuring was varied.
    Regards,
    Roman

    [email protected] wrote:
    > Hello!
    > I wanted to find out tracks's RMS and found these 2 variants of
    > measuring:
    >
    This is the one you use to find a tracks rms.
    >
    This one is in the context of group normalizing and comes with frequency
    compensation.
    > What's the difference between them?
    You use the first if you want to know the average and rms levels of a track.
    I always use a rms window of 300 milliseconds because that was the VU
    integration time of old and because that fits the averaging window of the
    sense of hearing.
    > Because the result of measuring
    > was varied.
    Group normalizing interprets the statistics prior to presenting them, I have
    also wondered why there is not there an option that gives the same result as
    the analyze amplitude tool. Manually adjusting to the average with 300 ms
    rms window generally works better for me and my way of listening than the
    group tool, consequently I miss having the same options available there.
    However you should always remember to listen, because some atypical audio
    needs to be more quiet or slightly louder to sound right in some context.
    > Regards,
    > Roman
    Kind regards
    Peter Larsen

  • Performance tuning of BPEL processes in SOA Suite 11g

    Hi,
      We are working with a customer for performance tuning of SOA Suite 11g, one of the areas is to tune the BPEL processes. I am new to this and started out with stress testing Hello World process using SOAPUI tool. I would like help with the below topics -
    1. How do I interpret the statistics collected during stress testing? Do we have any benchmark set that can indicate that the performance is ok.
    2. Do we need to run stress tests for every BPEL process deployed?
    2. Is there any performance tuning strategy documentation available? Or can anybody share his/her experiences to guide me?
    Thanks in advance!
    Sritama

    1. How do I interpret the statistics collected during stress testing? Do we have any benchmark set that can indicate that the performance is ok.
    You need
    pay attention to:
    java heap usage vs java heap capacity
    java eden usage vs java eden capacity
    JDBC pool initial connections vs JDBC pool capacity connections
    if you are using linux: top
    if you are using aix: topas
    2. Do we need to run stress tests for every BPEL process deployed?
    yes, you need test each BPEL. You can use "Jmeter" tool.
    Download Jmeter from here: Apache JMeter - Apache JMeter™
    Other tools:
    jstat
    jstack
    jps -v
    Enterprise Manager
    WebLogic Console
    VisualVM
    JRockit Mission Control
    3. Is there any performance tuning strategy documentation available? Or can anybody share his/her experiences to guide me?
    I recommend "Oracle SOA Suite 11g Performance Tuning Cookbook" http://www.amazon.com/Oracle-Suite-Performance-Tuning-Cookbook/dp/1849688842/ref=sr_1_1?ie=UTF8&qid=1378482031&sr=8-1&keywords=oracle+soa+suite+11g+performance+tuning+cookbook

  • How to get details on swapped out processes?

    I am trying to get the details on some swapped out processes. Currently vmstat is showing 71 processes a swapped out:
    vmstat 3 3
    kthr      memory            page            disk          faults      cpu
    r b w   swap  free  re  mf pi po fr de sr vc vc vc --   in   sy   cs us sy id
    *0 0 6 5598448 512968 155 352 428 40 42 0 22 3 28 1 0 1982 3904 1905 7 14 79*
    *0 0 71 5091488 436568 0 4 0 0 0 0 0 0 1 0 0 976 1215 945 0 3 97*
    *0 0 71 5099088 440896 2 5 0 0 0 0 0 0 2 0 0 1004 1221 991 1 2 97*
    A search of the MOS knowledge base turned up Support Recommended doc 1009494.1 How to use DTrace and mdb to Interpret vmstat Statistics.
    The section titled "kthr: Swapped out Threads (w)" includes the following statements and commands:
    To see the kernel threads swapped out during the sample period:
    $ dtrace -q -n 'fbt::swapout_lwp:entry{ proc = (proc *)arg[0]->t_procp; printf("Lwp: %d of \t Proc: %s being swaped out\n",arg[0]->t_id, proc->p_user.u_comm);}'
    The vmstat output doesn't tell what processes are swapped out. Mdb(1) can be used to print swapped out processes:
    # echo "::walk thread myvar|::print kthread_t t_schedflag|::grep .==0x8|::eval <myvar=K|::print kthread_t t_procp|::print proc_t p_user.u_comm"|mdb -k
    The dtrace command does not pass edit:
    *dtrace -q -n 'fbt::swapout_lwp:entry{ proc = (proc *)arg[0]->t_procp; printf("Lwp: %d of \t Proc: %s being swaped out\n",arg[0]->t_id, proc->p_user.u_comm);}'*
    *dtrace: invalid probe specifier fbt::swapout_lwp:entry{ proc = (proc *)arg[0]->t_procp; printf("Lwp: %d of \t Proc: %s being swaped out\n",arg[0]->t_id, proc->p_user.u_comm);}: syntax error near ")"*
    The mdb command does not return any thing:
    *#echo "::walk thread myvar|::print kthread_t t_schedflag|::grep .==0x8|::eval <myvar=K|::print kthread_t t_procp|::print proc_t p_user.u_comm"|mdb -k*
    The server is running:
    uname -a
    SunOS rizzotest 5.10 Generic_142900-11 sun4v sparc SUNW,SPARC-Enterprise-T5220
    cat /etc/release
    Solaris 10 10/09 s10s_u8wos_08a SPARC
    Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
    Use is subject to license terms.
    Assembled 16 September 2009
    Thanks,
    GlenG

    Satellite M505-S4975
    There are some utilities that read SMART data from the log.
       Comparison of S.M.A.R.T. tools
    But, as Peter says, there is no way to tell when such a drive will fail. Best to replace it now.
    -Jerry

  • LIBTUX_CAT:541 + Memory Leaks

    Hi
    Tuxedo 11g (11.1.1.2.0) / Windows 2008 R2
    We have a number of third party supplied tuxedo servers which when the BBL kills and restarts them the following is noted in the ULOG.
    BBL.1168.8884.0: LIBTUX_CAT:541: WARN: Server ThirdParty_Grp/630 terminated
    I understand that this warning is given when the code exited a process without calling any Tuxedo exit routines.
    The memory on these same tuxedo servers grow quite large throughout the day and I was wondering if the poor practice of not calling Tuxedo exit routines are the root cause of the memory leaks.
    If so, what evidence/proof/test is there that we can use to ask the third party to correct the code?
    Thanks
    Edited by: cool.br33ze on 20-Mar-2013 04:43

    Hi,
    you can definitely search for one specific ATMI call, see
    http://docs.oracle.com/cd/E18050_01/tuxedo/docs11gr1/rf5/rf5.html#wp1529614
    for details regarding TMTRACE where there's an example of logging all calls to tpacall().
    As I'm not The Universal Master Of All RegExps I don't really know whether you can catch several different calls in the search expression.
    On another note, I'd try looking into the processing time of your services. I'd say it's more probable that you have a performance problem in general rather than a major bug in the services (if they never call tpreturn() not much work will be done at all...).
    What is the value for SVCTIMEOUT (that is trespassed every now and then)?
    If you can add a "-r" in CLOPT you'll get statistics from all services executed in that particular server written to the stderr file (that might be specified with the -e option).
    Using txrpt you can then get insight into the execution times for the services in question. If they are constantly near the SVCTIMEOUT you may need to adjust the SVCTIMEOUT. If they are varying very much you may need to check for locks in the database or other reasons for "spiky" behaviour.
    See
    http://docs.oracle.com/cd/E18050_01/tuxedo/docs11gr1/rf5/rf5.html#wp1003290
    for more info on what can be done in CLOPT in the ubbconfig (look for -r and -e options), and also
    http://docs.oracle.com/cd/E18050_01/tuxedo/docs11gr1/rfcm/rfcmd.html#wp1002357
    for more info on how to interpret the statistics that -r creates.
    It is fairly common to create own-written utilities for interpreting the stderr file, it's not really rocket science if you want to get for instance min and max values out of it, which, by the way, would make a nice enhancement to txrpt in the first place. Product Management: are you listening? :-)
    Hope this helps,
    /Per

  • SQL Server 2008 R2 - need help in interpreting output of statistics time on

    Hi,
    Could you please help me to understand how to interpres CPU and Elapsed time
    I ran a query that took  1h 23 min 52 sec to complete.
    My statistics time result hows the following:
    CPU time = 17407152 ms, elapsed time = 5018172 ms.
    Both well exceed 1h 23 min 52 sec if I consider ms to be milliseconds.
    Could you please help me to understand why such mismatch?
    Does ms actually mean milliseconds?
    Thanks,
    Andrei
    SSIS question

    Mostly the query is going for parallelism (running on multiple CPU) and that's why CPU time is more.
    5018172 ms
    5018.172 sec 
    83.6362 min
    1.393936667 hours
    1 hr 23 min (matching with wall clock)
    Balmukund Lakhani
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    | Facebook
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • Interpreting statistics

    Hi all,
    I'm interpreting the AWR report. On the "Shared Pool Advisory" section, I can see this:
    Shared Pool Size(M)     SP Size Factr     Est LC Time Saved Factr     Est LC Load Time (s) Est LC Load Time Factr
    816      0.89      1.00      9,647      1.07
    912      1.00      1.00      9,005      1.00
    1,008      1.11      1.06      1      0.00
    I'm interpreting if I increase the Shared Pool size to 1Gb, I can improve the load time from 9005 seg to only 1seg.
    Is it true? Is not too much difference to be true? And if I'm wrong, How I've to interpret it?
    Regards,
    dbajug

    You should have a Number of Navigations KF which would correspond to the number of queries run. 
    ST03N in Expert Mode also provides this information, but it only has some predefined timeframes, e.g.
    Today
    1 day ago
    2 days ago
    This week
    1 week ago
    2 weeks ago
    This month
    1 month ago
    2 months ago

  • Interpret DB Time in AWR statistics.....

    We are running multiple Oracle instances on the one database server, and are trying to measure the proportion of time that each instance uses, by analysing AWR reports.
    We are having trouble understanding the meaning of the "DB Time" statistic, near the top of the report. A sample is shown below:
    {color:#000000}Snap Id Snap Time Sessions Cursors/Session
    Begin Snap: 16777 20-Oct-08 00:00:34 687 5.8
    End Snap: 16945 27-Oct-08 00:00:13 667 .5
    Elapsed: 10,079.65 (mins)
    DB Time: 11,164.25 (mins)
    {color}
    The two snapshots are one week apart, so the "Elapsed Time" make sense - there are 10080 minutes in a week
    We are not sure how the "DB Time" can be 11,164 minutes?? Does this quantity relate to the number of processors/cores on the machine?
    Any help would be appreciated.
    Thanks
    Gavin

    Hi,
    DBTime is the time that is based on the number of sessions which are at the moment active and are doing some thing in the system. So if there are, for example, 3 sessions active and the instance is up from 30 minutes, the db time would be reported as 90 minutes. You may want to look at this doc link which explains it with a pic,
    http://download.oracle.com/docs/cd/B19306_01/server.102/b28051/tdppt_method.htm#CIHCDGCI
    The idea bascially is to find the area using this in the database where the maximum time is spent as its based on both, cpu and wait time. If we can reduce the wait time, that time can be used in doing some thing productive.
    Edit:
    I just remebered that Doug had written a very good piece of blogpost for the same topic. That would help in better understanding of it.
    http://oracledoug.com/serendipity/index.php?/archives/1429-Time-Matters-DB-Time.html
    HTH
    Aman....
    Edited by: Aman.... on Oct 27, 2008 12:19 PM

  • How to interprete Statspack report

    Hello all,
    I'm new in using statspack and i've tried to run it and gather the report but i can't interprete the result, i mean what can i do, the decisions after reading the report how to inteprete, what part of the result are the essential.
    Here is an extract of my statspack report. If someone can help me or any documentations online for this.
    STATSPACK report for
    DB Name DB Id Instance Inst Num Release OPS Host
    QLM3 1443332160 orcl 1 8.1.7.0.0 NO SRVUSINE
    Snap Id Snap Time Sessions
    Begin Snap: 1 03-Jan-07 15:48:53 57
    End Snap: 2 03-Jan-07 15:56:30 57
    Elapsed: 7.62 (mins)
    Cache Sizes
    ~~~~~~~~~~~
    db_block_buffers: 19200 log_buffer: 163840
    db_block_size: 8192 shared_pool_size: 128000000
    Load Profile
    ~~~~~~~~~~~~ Per Second Per Transaction
    Redo size: 8,232.78 22,941.34
    Logical reads: 11,853.51 33,030.82
    Block changes: 41.60 115.91
    Physical reads: 145.94 406.67
    Physical writes: 36.83 102.62
    User calls: 139.75 389.42
    Parses: 6.30 17.55
    Hard parses: 0.09 0.25
    Sorts: 2.23 6.23
    Logons: 0.82 2.29
    Executes: 87.97 245.13
    Transactions: 0.36
    % Blocks changed per Read: 0.35 Recursive Call %: 32.96
    Rollback per transaction %: 6.71 Rows per Sort: 104.37
    Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Buffer Nowait %: 100.00 Redo NoWait %: 99.90
    Buffer Hit %: 98.77 In-memory Sort %: 99.22
    Library Hit %: 99.83 Soft Parse %: 98.58
    Execute to Parse %: 92.84 Latch Hit %: 100.00
    Parse CPU to Parse Elapsd %: 57.07 % Non-Parse CPU: 100.00
    Shared Pool Statistics Begin End
    Memory Usage %: 88.80 88.08
    % SQL with executions>1: 35.12 35.45
    % Memory for SQL w/exec>1: 56.60 58.45
    Top 5 Wait Events
    ~~~~~~~~~~~~~~~~~ Wait % Total
    Event Waits Time (cs) Wt Time
    direct path write 13,024 13,301 38.64
    db file sequential read 17,592 8,103 23.54
    direct path read 13,514 7,199 20.91
    db file scattered read 3,231 2,085 6.06
    PX Deq: Txn Recovery Start 8 699 2.03
    Wait Events for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> cs - centisecond - 100th of a second
    -> ms - millisecond - 1000th of a second
    -> ordered by wait time desc, waits desc (idle events last)
    Avg
    Total Wait wait Waits
    Event Waits Timeouts Time (cs) (ms) /txn
    direct path write 13,024 0 13,301 10 79.4
    db file sequential read 17,592 0 8,103 5 107.3
    direct path read 13,514 0 7,199 5 82.4
    db file scattered read 3,231 0 2,085 6 19.7
    PX Deq: Txn Recovery Start 8 3 699 874 0.0
    db file parallel write 82 0 656 80 0.5
    log file parallel write 348 0 471 14 2.1
    control file parallel write 214 0 447 21 1.3
    log file sync 256 0 309 12 1.6
    control file sequential read 229 0 209 9 1.4
    log file switch completion 10 0 205 205 0.1
    Wait for stopper event to be 19 17 200 105 0.1
    SQL*Net break/reset to clien 74 0 191 26 0.5
    file open 1,587 0 122 1 9.7
    log buffer space 16 0 115 72 0.1
    buffer busy waits 11 0 36 33 0.1
    SQL*Net more data to client 3,459 0 35 0 21.1
    latch free 68 52 18 3 0.4
    file identify 8 0 8 10 0.0
    refresh controlfile command 10 0 6 6 0.1
    log file sequential read 4 0 4 10 0.0
    log file single write 8 0 3 4 0.0
    LGWR wait for redo copy 1 0 2 20 0.0
    PX Deq: Signal ACK 3 0 1 3 0.0
    PX Deq: Join ACK 5 0 0 0 0.0
    enqueue 5 0 0 0 0.0
    SQL*Net message from client 62,888 0 1,462,717 233 383.5
    PX Idle Wait 602 600 124,058 2061 3.7
    virtual circuit status 15 15 46,101 30734 0.1
    SQL*Net message to client 62,885 0 10 0 383.4
    SQL*Net more data from clien 12 0 1 1 0.1
    Background Wait Events for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> ordered by wait time desc, waits desc (idle events last)
    Avg
    Total Wait wait Waits
    Event Waits Timeouts Time (cs) (ms) /txn
    db file parallel write 82 0 656 80 0.5
    direct path read 542 0 546 10 3.3
    log file parallel write 348 0 471 14 2.1
    control file parallel write 214 0 447 21 1.3
    Wait for stopper event to be 19 17 200 105 0.1
    control file sequential read 176 0 194 11 1.1
    file open 1,485 0 50 0 9.1
    buffer busy waits 1 0 33 330 0.0
    db file scattered read 7 0 16 23 0.0
    direct path write 297 0 8 0 1.8
    file identify 8 0 8 10 0.0
    log file sequential read 4 0 4 10 0.0
    log file single write 8 0 3 4 0.0
    LGWR wait for redo copy 1 0 2 20 0.0
    PX Deq: Signal ACK 3 0 1 3 0.0
    db file sequential read 1 0 1 10 0.0
    PX Deq: Join ACK 5 0 0 0 0.0
    enqueue 1 0 0 0 0.0
    rdbms ipc message 1,221 427 134,286 1100 7.4
    pmon timer 149 148 45,558 3058 0.9
    smon timer 2 1 43,807 ###### 0.0
    SQL ordered by Gets for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Buffer Gets Threshold: 10000
    -> Note that resources reported for PL/SQL includes the resources used by
    all SQL statements called within the PL/SQL code. As individual SQL
    statements are also reported, it is possible and valid for the summed
    total % to exceed 100
    Buffer Gets Executions Gets per Exec % Total Hash Value
    887,405 3,544 250.4 16.4 8985785
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE > 0 AND GISEMENT_T
    YPE IN ( 'L','F' ) AND MVT_SITE_CODE = :b5
    887,405 3,544 250.4 16.4 739720993
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE != 'T' AND MVT_SITE_CODE = :b5
    885,540 3,531 250.8 16.3 203835771
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE < 0 AND GISEMENT_T
    YPE IN ( 'L','F' ) AND MVT_SITE_CODE = :b5
    885,540 3,531 250.8 16.3 3827568942
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE > 0 AND GISEMENT_T
    YPE IN ( 'T' ) AND GISEMENT_SITE_CODE = :b5
    885,410 3,544 249.8 16.3 667813037
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE < 0 AND GISEMENT_T
    YPE IN ( 'T' ) AND GISEMENT_SITE_CODE = :b5
    472,580 1 472,580.0 8.7 1418790643
    SELECT COUNT(*) FROM VAPS_APS_SORTIES WHERE MVT_DATE LIKE '%' AN
    D INVEST_NUMERO IS NULL and (CLE=:1)
    180,137 1 180,137.0 3.3 1562147089
    SELECT COUNT(*) FROM VPRF_PRF_ETAT_STOCKS
    110,321 443 249.0 2.0 2233067473
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4
    72,956 2 36,478.0 1.3 3376831664
    BEGIN statspack.snap; END;
    67,904 1 67,904.0 1.3 625421128
    INSERT INTO STATS$SQLTEXT ( HASH_VALUE,TEXT_SUBSET,PIECE,SQL_TEX
    T,ADDRESS,COMMAND_TYPE,LAST_SNAP_ID ) SELECT ST1.HASH_VALUE,SS.
    TEXT_SUBSET,ST1.PIECE,ST1.SQL_TEXT,ST1.ADDRESS,ST1.COMMAND_TYPE,
    SS.SNAP_ID FROM V$SQLTEXT ST1,STATS$SQL_SUMMARY SS WHERE SS.S
    NAP_ID = :b1 AND SS.DBID = :b2 AND SS.INSTANCE_NUMBER = :b3 A
    SQL ordered by Gets for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Buffer Gets Threshold: 10000
    -> Note that resources reported for PL/SQL includes the resources used by
    all SQL statements called within the PL/SQL code. As individual SQL
    statements are also reported, it is possible and valid for the summed
    total % to exceed 100
    Buffer Gets Executions Gets per Exec % Total Hash Value
    49,930 9,986 5.0 0.9 2352601327
    SELECT INSTR(:b1,'/') FROM DUAL
    26,262 1 26,262.0 0.5 2467990648
    SELECT PRF_CB_QUALITES.QUALITE_LIB, PRF_FICHEARTICLES.FSA_
    ARTICLE_CODE, PRF_CB_EMBALLAGES.EMB_LIBELLE, PRF_CB_CALIBR
    ES.CALIBRE_LIBELLE, PRF_CB_VARIETES.VARIETE_LIB, PRF_CF_ST
    OCKS.CF_CODE, PRF_CF_CHAMBREFROIDES.CF_LIBELLE, to_char(PR
    F_CF_STOCKS.MC_DATE_CONGELATION,'ddd') ||PRF_CF_STOCKS.MC_EQUIPE
    25,024 1 25,024.0 0.5 2687416176
    SELECT num_lot_cqi num_lot, date_congelation date_peche, equipe_
    congelation equipe_conditionnement, equipe_emballage FROM VCQI_P
    RF_CB_LOTS WHERE site_code = fcqi_parametre ('SITE_CODE', 0) AND
    quart_code like nvl(:1,'%') order by date_congelation desc
    24,952 1 24,952.0 0.5 2144314401
    SELECT DATE_CONGELATION,EQUIPE_CONGELATION,EQUIPE_EMBALLAGE FR
    OM VCQI_PRF_CB_LOTS WHERE NUM_LOT_CQI = :b1 AND QUART_CODE LIK
    E NVL(:b2,'%')
    21,644 3,542 6.1 0.4 3246828773
    SELECT SUM(NVL(ARTSTATGIS_QTE,0)) FROM APS_MVT_ARTICLE_GISEMEN
    T WHERE ARTICLE_ID = :b1 AND STATUT_CODE = :b2 AND REGIME = :
    b3 AND SITE_CODE = :b4
    6,714 3 2,238.0 0.1 1676564828
    SELECT ROWID,CLE,PBS_DATE,PBS_HEURE,IMPUTATION_CODE,SERVICE_CODE
    ,STATUT_CODE,REGIME,PBS_BONTRAVAIL,INVEST_NUMERO,UTIL_NUMERO_EME
    TTEUR,DDESORTIE_NUM_DDE,PBS_VALEUR,REFACTURER,REFACTURER_CODE,UT
    IL_NUMERO_DESTINATAIRE,OBSERVATION,IMPRIME_UNEFOIS,PBS_VALIDE,DA
    TE_VALIDATION,PBS_ENVOYE_MAGASIN,DATE_ENVOIMAG,PBS_GISEMENT_VALI
    6,714 3 2,238.0 0.1 2431929513
    SELECT COUNT(*) FROM APS_SORTIES_HDR WHERE (PBS_VALIDE='O') AND
    (PBS_ENVOYE_MAGASIN='O' )AND (PBS_GISEMENT_VALIDE='N')
    6,022 60 100.4 0.1 1010618514
    SELECT COUNT(*) FROM QRH_PNT_MOUVEMENTS WHERE STE_CODE = :1 AND
    (ANOMALIE!='0') AND (ANOMALIE!='1') AND (ANOMALIE!='2') AND (ANO
    MALIE!='3') AND (ANOMALIE!='21') AND (VALIDEE='N') AND (JOURNEE=
    TO_CHAR(:2,'dd/mm/yyyy')) AND (MATRICULE=:3) AND (SERVICE_CODE=:
    4) and (MATRICULE=:5) and (STE_CODE=:6)
    6,022 60 100.4 0.1 4067308175
    SELECT ROWID,VALIDEE,MATRICULE,ENTREE,SORTIE,REGUL,ORIGINE_POINT
    AGE,JUSTIFICATION_CODE,JUSTIFIEE,ANOMALIE,JOURNEE,SERVICE_CODE,S
    TE_CODE,UTIL_NUMERO_JUSTIFIER,UTIL_NUMERO_VALIDER,OK_PAIE,DATE_O
    K_PAIE FROM QRH_PNT_MOUVEMENTS WHERE STE_CODE = :1 AND (ANOMALIE
    !='0') AND (ANOMALIE!='1') AND (ANOMALIE!='2') AND (ANOMALIE!='3
    SQL ordered by Gets for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Buffer Gets Threshold: 10000
    -> Note that resources reported for PL/SQL includes the resources used by
    all SQL statements called within the PL/SQL code. As individual SQL
    statements are also reported, it is possible and valid for the summed
    total % to exceed 100
    Buffer Gets Executions Gets per Exec % Total Hash Value
    SQL ordered by Reads for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Disk Reads Threshold: 1000
    Physical Reads Executions Reads per Exec % Total Hash Value
    16,941 1 16,941.0 25.4 1418790643
    SELECT COUNT(*) FROM VAPS_APS_SORTIES WHERE MVT_DATE LIKE '%' AN
    D INVEST_NUMERO IS NULL and (CLE=:1)
    12,263 443 27.7 18.4 2233067473
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4
    6,699 3 2,233.0 10.0 2431929513
    SELECT COUNT(*) FROM APS_SORTIES_HDR WHERE (PBS_VALIDE='O') AND
    (PBS_ENVOYE_MAGASIN='O' )AND (PBS_GISEMENT_VALIDE='N')
    6,493 3 2,164.3 9.7 1676564828
    SELECT ROWID,CLE,PBS_DATE,PBS_HEURE,IMPUTATION_CODE,SERVICE_CODE
    ,STATUT_CODE,REGIME,PBS_BONTRAVAIL,INVEST_NUMERO,UTIL_NUMERO_EME
    TTEUR,DDESORTIE_NUM_DDE,PBS_VALEUR,REFACTURER,REFACTURER_CODE,UT
    IL_NUMERO_DESTINATAIRE,OBSERVATION,IMPRIME_UNEFOIS,PBS_VALIDE,DA
    TE_VALIDATION,PBS_ENVOYE_MAGASIN,DATE_ENVOIMAG,PBS_GISEMENT_VALI
    4,783 2 2,391.5 7.2 3376831664
    BEGIN statspack.snap; END;
    4,075 1 4,075.0 6.1 1762397322
    SELECT ROWID,MC_CODE,CB_QUALITE,CB_EMBALLAGE,CB_CALIBRE,CB_VARIE
    TE,TYPECH_CODE,TYPECH_LIBELLE,CF_CODE,CF_LIBELLE,MC_EQUIPE_CONDI
    TIONNEMENT,MC_DATE_CONGELATION,MC_EQUIPE_EMBALLAGE,MC_DATE_EMBAL
    LAGE,INC_CODE,INC_LIBELLE,PALETTE_CODE,TP_CODE,CB_ORIGINE_CODE,U
    SINE_CODE,LIEU_CODE,MC_ETAT,TP_LIBELLE,ORIGINE_LIBELLE,QUALITE_L
    3,455 1 3,455.0 5.2 2467990648
    SELECT PRF_CB_QUALITES.QUALITE_LIB, PRF_FICHEARTICLES.FSA_
    ARTICLE_CODE, PRF_CB_EMBALLAGES.EMB_LIBELLE, PRF_CB_CALIBR
    ES.CALIBRE_LIBELLE, PRF_CB_VARIETES.VARIETE_LIB, PRF_CF_ST
    OCKS.CF_CODE, PRF_CF_CHAMBREFROIDES.CF_LIBELLE, to_char(PR
    F_CF_STOCKS.MC_DATE_CONGELATION,'ddd') ||PRF_CF_STOCKS.MC_EQUIPE
    2,308 1 2,308.0 3.5 3874720143
    INSERT INTO STATS$SQL_SUMMARY ( SNAP_ID,DBID,INSTANCE_NUMBER,TEX
    T_SUBSET,SHARABLE_MEM,SORTS,MODULE,LOADED_VERSIONS,EXECUTIONS,LO
    ADS,INVALIDATIONS,PARSE_CALLS,DISK_READS,BUFFER_GETS,ROWS_PROCES
    SED,ADDRESS,HASH_VALUE,VERSION_COUNT ) SELECT :b1,:b2,:b3,SUBST
    R(SQL_TEXT,1,31),SHARABLE_MEM,SORTS,MODULE,LOADED_VERSIONS,EXECU
    2,295 1 2,295.0 3.4 3337740287
    INSERT INTO STATS$SQL_STATISTICS ( SNAP_ID,DBID,INSTANCE_NUMBER,
    TOTAL_SQL,TOTAL_SQL_MEM,SINGLE_USE_SQL,SINGLE_USE_SQL_MEM ) SEL
    ECT :b1,:b2,:b3,COUNT(1),SUM(SHARABLE_MEM),SUM(DECODE(EXECUTIONS
    ,1,1,0)),SUM(DECODE(EXECUTIONS,1,SHARABLE_MEM,0)) FROM V$SQLXS
    2,232 14 159.4 3.3 2819681083
    SELECT COUNT(*) FROM APS_SORTIES_HDR WHERE PBS_GISEMENT_VALIDE =
    'N' and (SERVICE_CODE=:1) and (PBS_VALIDE=:2)
    SQL ordered by Reads for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Disk Reads Threshold: 1000
    Physical Reads Executions Reads per Exec % Total Hash Value
    2,232 14 159.4 3.3 2856670560
    SELECT ROWID,CLE,IMPUTATION_CODE,SERVICE_CODE,STATUT_CODE,REGIME
    ,INVEST_NUMERO,PBS_BONTRAVAIL,REFACTURER,REFACTURER_CODE,ENTREE_
    NUMERO,PBS_DATE,PBS_HEURE,UTIL_NUMERO_EMETTEUR,UTIL_NUMERO_DESTI
    NATAIRE,OBSERVATION,PBS_VALIDE,DATE_VALIDATION,PBS_ENVOYE_MAGASI
    N,DATE_ENVOIMAG,DDESORTIE_NUM_DDE,PBS_VALEUR,IMPRIME_UNEFOIS,PBS
    1,168 1 1,168.0 1.8 1352033258
    SELECT PRF_CB_QUALITES.QUALITE_LIB, PRF_FICHEARTICLES.FSA_
    ARTICLE_CODE, PRF_CB_EMBALLAGES.EMB_LIBELLE, PRF_CB_CALIBR
    ES.CALIBRE_LIBELLE, PRF_CB_VARIETES.VARIETE_LIB, PRF_CF_ST
    OCKS.CF_CODE, PRF_CF_CHAMBREFROIDES.CF_LIBELLE, to_char(PR
    F_CF_STOCKS.MC_DATE_CONGELATION,'ddd') ||PRF_CF_STOCKS.MC_EQUIPE
    723 3 241.0 1.1 165227727
    SELECT ROWID,CLE,UTIL_NUMERO_VALIDE,VALIDPBS_DATE,VALIDPBS_HEURE
    FROM APS_SORTIES_VALIDATION WHERE (CLE=:1)
    685 3 228.3 1.0 3538988510
    SELECT COUNT(*) FROM APS_SORTIES_VALIDATION WHERE (CLE=:1)
    602 1 602.0 0.9 1562147089
    SELECT COUNT(*) FROM VPRF_PRF_ETAT_STOCKS
    390 15 26.0 0.6 3423685253
    INSERT INTO PRF_CF_ENTREES ( MC_CODE,CF_CODE,PALETTE_CODE,MC_ETA
    T,SYS_DATE_LECTEUR,TYPE_ENTREE ) VALUES ( :b1,:b2,:b3,SUBSTR(:b
    4,1,2),SYSDATE,'E' )
    372 6 62.0 0.6 2944582360
    SELECT COUNT(*) FROM QRH_FIP_AGENTS WHERE (QRH_FIP_AGENTS.AGE
    NT_MATRICULE = :b1 ) AND (QRH_FIP_AGENTS.SERVICE_CODE LIKE :b2
    ) AND (QRH_FIP_AGENTS.SERVICE_CODE IN (SELECT SERVICE_CODE FRO
    M SEC_QRH_ACCES_SERVICES WHERE STE_CODE = :b3 AND (ACCES_FICHE
    PERSONNEL = 'O'  AND POINTAGECONSULTATION = 'O' AND POINTAGE_
    352 15 23.5 0.5 836774746
    INSERT INTO PRF_CF_STOCKS ( MC_CODE,TP_CODE,CB_ORIGINE_CODE,USIN
    E_CODE,LIEU_CODE,CB_QUALITE,CB_EMBALLAGE,MARQUE_LIBELLE,CB_CALIB
    RE,CB_VARIETE,TYPECH_CODE,MC_DATE_CONGELATION,MC_EQUIPE_CONDITIO
    NNEMENT,MC_DATE_EMBALLAGE,MC_EQUIPE_EMBALLAGE,PALETTE_CODE,CF_CO
    DE,FSA_ARTICLE_CODE,MC_POIDS_KG,MC_ETAT,INC_CODE,BASSIN_CODE,MAR
    271 15 18.1 0.4 1991901539
    SELECT COUNT('X') FROM DUAL WHERE EXISTS (SELECT 'X' FROM
    PRF_LOTS_ENTREES WHERE NUMERO_LOT = :b1 AND TP_CODE = :b2 AND
    SQL ordered by Executions for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Executions Threshold: 100
    Executions Rows Processed Rows per Exec Hash Value
    9,986 9,986 1.0 2352601327
    SELECT INSTR(:b1,'/') FROM DUAL
    3,544 3,544 1.0 8985785
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE > 0 AND GISEMENT_T
    YPE IN ( 'L','F' ) AND MVT_SITE_CODE = :b5
    3,544 3,544 1.0 667813037
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE < 0 AND GISEMENT_T
    YPE IN ( 'T' ) AND GISEMENT_SITE_CODE = :b5
    3,544 3,544 1.0 739720993
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE != 'T' AND MVT_SITE_CODE = :b5
    3,542 3,542 1.0 3246828773
    SELECT SUM(NVL(ARTSTATGIS_QTE,0)) FROM APS_MVT_ARTICLE_GISEMEN
    T WHERE ARTICLE_ID = :b1 AND STATUT_CODE = :b2 AND REGIME = :
    b3 AND SITE_CODE = :b4
    3,531 3,531 1.0 203835771
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE < 0 AND GISEMENT_T
    YPE IN ( 'L','F' ) AND MVT_SITE_CODE = :b5
    3,531 3,531 1.0 3827568942
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4 AND MVT_TYPE = 'T' AND MVT_QUANTITE > 0 AND GISEMENT_T
    YPE IN ( 'T' ) AND GISEMENT_SITE_CODE = :b5
    629 629 1.0 3347504826
    SELECT COUNT('x') FROM DUAL WHERE EXISTS (SELECT 'x' FROM
    PRF_TB_AI WHERE CODE_AI = :b1 )
    586 586 1.0 830918687
    SELECT SYSDATE FROM DUAL
    494 494 1.0 2353080377
    INSERT INTO APS_ARCHIVE_STOCKS_DTL VALUES ( :b1,:b2,:b3,:b4,:b5,
    :b6 )
    444 444 1.0 431034241
    UPDATE APS_ARCHIVE_STOCKS SET ART_STAT_QTE_STOCK_SITE=:b1 WHERE
    PERIODE = :b2 AND ARTICLE_ID = :b3 AND STATUT_CODE = :b4 AND
    REGIME = :b5
    443 443 1.0 2233067473
    SELECT SUM(MVT_QUANTITE) FROM APS_MVT_MOUVEMENTS WHERE PERIOD
    SQL ordered by Executions for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Executions Threshold: 100
    Executions Rows Processed Rows per Exec Hash Value
    E > :b1 AND ARTICLE_ID = :b2 AND STATUT_CODE = :b3 AND REGIME
    = :b4
    442 442 1.0 4030231140
    INSERT INTO APS_ARCHIVE_STOCKS ( PERIODE,ARTICLE_ID,STATUT_CODE,
    REGIME,ART_STAT_QTE_STOCK,ART_STAT_QTE_STOCK_SITE,ART_STAT_PUMP,
    ART_STAT_PUMP_EURO,ART_STAT_PUMP_1 ) VALUES ( :b1,:b2,:b3,:b4,:
    b5,:b6,:b7,:b8, NULL )
    441 3,520 8.0 2193642303
    SELECT SITE_CODE FROM APS_LOC_SITES
    416 167 0.4 3549129673
    SELECT DISTINCT LIBELLE_PRODUIT FROM VCQI_PRF_CB_QC_PRODUITS
    WHERE TYPE_PRODUIT = :b1
    415 415 1.0 3105143149
    SELECT UTIL_NOM || DECODE(UTIL_PRENOM, NULL , NULL ,' ' || UTIL_
    PRENOM ) UTIL_NOM_PRENOM FROM COM_UTILISATEURS WHERE UTIL_NU
    MERO = :b1
    270 270 1.0 1045955060
    SELECT COUNT('X') FROM DUAL WHERE EXISTS (SELECT 'X' FROM
    PRF_GFR_BASSINS WHERE BASSIN_CODE = :b1 )
    235 235 1.0 2123798088
    SELECT COUNT('X') FROM DUAL WHERE EXISTS (SELECT 'X' FROM
    PRF_FICHEARTICLES WHERE FSA_ARTICLE_CODE = :b1 )
    218 217 1.0 2987457698
    SELECT NOM FROM SYS_CQI_SITE WHERE CODE = :b1
    213 213 1.0 1425443843
    update seq$ set increment$=:2,minvalue=:3,maxvalue=:4,cycle#=:5,
    order$=:6,cache=:7,highwater=:8,audit$=:9 where obj#=:1
    183 183 1.0 3529593353
    SELECT COUNT('X') FROM DUAL WHERE EXISTS (SELECT 'X' FROM
    PRF_GFR_BASSINS WHERE BASSIN_CODE = SUBSTR(:b1,2,3) )
    178 0 0.0 313510536
    select job from sys.job$ where next_date < sysdate and (field1
    = :1 or (field1 = 0 and 'Y' = :2)) order by next_date, job
    167 167 1.0 2542007726
    SELECT PRF_PARAM_VALEUR FROM PRF_MAHAVOKATRA_PARAMETRES WHERE
    PRF_PARAM_NOM = :b1
    144 144 1.0 1202015936
    SELECT CODE_AI,DESCRIPTION_AI,TYPE_AI,LONGUEUR_MAX FROM PRF_TB
    AI  WHERE CODEAI = :b1
    138 138 1.0 2840696239
    SELECT SEQ_PRF_MC_SERIE.Nextval FROM Dual
    SQL ordered by Executions for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> End Executions Threshold: 100
    Executions Rows Processed Rows per Exec Hash Value
    101 7 0.1 148923490
    SELECT COUNT(*) FROM APS_SORTIES_HDR WHERE (PBS_VALIDE='O') AND
    (PBS_ENVOYE_MAGASIN='O' )AND (PBS_GISEMENT_VALIDE='N') and (CLE=
    :1)
    101 7 0.1 2329028825
    SELECT ROWID,CLE,PBS_DATE,PBS_HEURE,IMPUTATION_CODE,SERVICE_CODE
    Instance Activity Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    Statistic Total per Second per Trans
    background checkpoints completed 4 0.0 0.0
    background checkpoints started 4 0.0 0.0
    background timeouts 620 1.4 3.8
    branch node splits 0 0.0 0.0
    buffer is not pinned count 4,838,419 10,587.4 29,502.6
    buffer is pinned count 15,660,264 34,267.5 95,489.4
    bytes received via SQL*Net from c 7,127,276 15,595.8 43,459.0
    bytes sent via SQL*Net to client 13,724,270 30,031.2 83,684.6
    calls to get snapshot scn: kcmgss 41,025 89.8 250.2
    calls to kcmgas 383 0.8 2.3
    calls to kcmgcs 145 0.3 0.9
    change write time 134 0.3 0.8
    cleanouts and rollbacks - consist 0 0.0 0.0
    cleanouts only - consistent read 3 0.0 0.0
    cluster key scan block gets 132 0.3 0.8
    cluster key scans 64 0.1 0.4
    commit cleanout failures: block l 2 0.0 0.0
    commit cleanout failures: buffer 0 0.0 0.0
    commit cleanout failures: callbac 3 0.0 0.0
    commit cleanout failures: cannot 0 0.0 0.0
    commit cleanouts 1,238 2.7 7.6
    commit cleanouts successfully com 1,233 2.7 7.5
    consistent changes 37 0.1 0.2
    consistent gets 5,342,340 11,690.0 32,575.2
    CPU used by this session 563,606,920 1,233,275.5 3,436,627.6
    CPU used when call started 16,475 36.1 100.5
    CR blocks created 32 0.1 0.2
    current blocks converted for CR
    cursor authentications 0 0.0 0.0
    data blocks consistent reads - un 37 0.1 0.2
    db block changes 19,010 41.6 115.9
    db block gets 74,714 163.5 455.6
    DBWR buffers scanned 11,292 24.7 68.9
    DBWR checkpoint buffers written 604 1.3 3.7
    DBWR checkpoints 4 0.0 0.0
    DBWR free buffers found 10,956 24.0 66.8
    DBWR lru scans 48 0.1 0.3
    DBWR make free requests 48 0.1 0.3
    DBWR summed scan depth 11,292 24.7 68.9
    DBWR transaction table writes 31 0.1 0.2
    DBWR undo block writes 223 0.5 1.4
    deferred (CURRENT) block cleanout 796 1.7 4.9
    DFO trees parallelized 0 0.0 0.0
    dirty buffers inspected 41 0.1 0.3
    enqueue conversions 59 0.1 0.4
    enqueue releases 1,608 3.5 9.8
    enqueue requests 1,627 3.6 9.9
    enqueue timeouts 21 0.1 0.1
    enqueue waits 0 0.0 0.0
    execute count 40,202 88.0 245.1
    free buffer inspected 43 0.1 0.3
    free buffer requested 50,071 109.6 305.3
    hot buffers moved to head of LRU 32,358 70.8 197.3
    immediate (CR) block cleanout app 3 0.0 0.0
    immediate (CURRENT) block cleanou 216 0.5 1.3
    index fast full scans (full) 197 0.4 1.2
    Instance Activity Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    Statistic Total per Second per Trans
    leaf node splits 43 0.1 0.3
    logons cumulative 376 0.8 2.3
    messages received 566 1.2 3.5
    messages sent 566 1.2 3.5
    no buffer to keep pinned count 361,161 790.3 2,202.2
    no work - consistent read gets 4,584,108 10,030.9 27,951.9
    opened cursors cumulative 2,903 6.4 17.7
    Parallel operations not downgrade 0 0.0 0.0
    parse count (hard) 41 0.1 0.3
    parse count (total) 2,879 6.3 17.6
    parse time cpu 109 0.2 0.7
    parse time elapsed 191 0.4 1.2
    physical reads 66,694 145.9 406.7
    physical reads direct 17,008 37.2 103.7
    physical writes 16,830 36.8 102.6
    physical writes direct 15,849 34.7 96.6
    physical writes non checkpoint 16,523 36.2 100.8
    pinned buffers inspected 0 0.0 0.0
    prefetched blocks 28,860 63.2 176.0
    prefetched blocks aged out before 104 0.2 0.6
    process last non-idle time 395,024,325 864,385.8 2,408,684.9
    PX local messages recv'd 3 0.0 0.0
    PX local messages sent 2 0.0 0.0
    queries parallelized 0 0.0 0.0
    recovery array reads 0 0.0 0.0
    recovery blocks read 0 0.0 0.0
    recursive calls 31,404 68.7 191.5
    recursive cpu usage 973 2.1 5.9
    redo blocks written 7,766 17.0 47.4
    redo buffer allocation retries 24 0.1 0.2
    redo entries 9,689 21.2 59.1
    redo log space requests 10 0.0 0.1
    redo log space wait time 205 0.5 1.3
    redo ordering marks 0 0.0 0.0
    redo size 3,762,380 8,232.8 22,941.3
    redo synch time 310 0.7 1.9
    redo synch writes 252 0.6 1.5
    redo wastage 83,944 183.7 511.9
    redo write time 798 1.8 4.9
    redo writer latching time 2 0.0 0.0
    redo writes 348 0.8 2.1
    rollback changes - undo records a 100 0.2 0.6
    rollbacks only - consistent read 32 0.1 0.2
    rows fetched via callback 152,467 333.6 929.7
    session connect time 395,024,325 864,385.8 2,408,684.9
    session logical reads 5,417,054 11,853.5 33,030.8
    session pga memory 1,198,867,080 2,623,341.5 7,310,165.1
    session pga memory max 1,252,931,128 2,741,643.6 7,639,824.0
    session uga memory 2,021,828 4,424.1 12,328.2
    session uga memory max 11,504,160 25,173.2 70,147.3
    sorts (disk) 8 0.0 0.1
    sorts (memory) 1,013 2.2 6.2
    sorts (rows) 106,560 233.2 649.8
    SQL*Net roundtrips to/from client 62,770 137.4 382.7
    summed dirty queue length 2 0.0 0.0
    switch current to new buffer
    Instance Activity Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    Statistic Total per Second per Trans
    table fetch by rowid 10,162,108 22,236.6 61,964.1
    table fetch continued row 5,568 12.2 34.0
    table scan blocks gotten 73,722 161.3 449.5
    table scan rows gotten 3,805,522 8,327.2 23,204.4
    table scans (direct read) 0 0.0 0.0
    table scans (long tables) 50 0.1 0.3
    table scans (rowid ranges) 0 0.0 0.0
    table scans (short tables) 12,550 27.5 76.5
    total file opens 1,587 3.5 9.7
    transaction rollbacks 0 0.0 0.0
    user calls 63,865 139.8 389.4
    user commits 153 0.3 0.9
    user rollbacks 11 0.0 0.1
    write clones created in backgroun 0 0.0 0.0
    write clones created in foregroun 27 0.1 0.2
    Tablespace IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by IOs (Reads + Writes) desc
    Tablespace
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    TEMP
    9,953 22 0.0 1.2 11,991 26 0 0.0
    APS_DATA_DYNA
    18,803 41 4.4 2.3 67 0 7 2.9
    TEMP1
    4,163 9 0.0 1.1 3,367 7 0 0.0
    APS_INDEX
    1,169 3 6.3 1.6 113 0 0 0.0
    PRF_DATA_DYNA
    290 1 13.7 10.2 105 0 2 5.0
    APS_DATA_STAT
    324 1 4.4 4.6 41 0 0 0.0
    TOOLS
    53 0 10.2 1.0 287 1 0 0.0
    PRF_INDEX
    133 0 6.7 1.0 88 0 1 0.0
    SYSTEM
    128 0 12.9 1.7 58 0 0 0.0
    RBS1
    17 0 10.6 1.0 158 0 1 330.0
    GRH_DATA_DYNA
    72 0 7.1 1.0 78 0 0 0.0
    RBS
    30 0 44.7 1.0 111 0 0 0.0
    GRH_INDEX
    38 0 8.2 1.0 46 0 0 0.0
    PRF_DATA_STAT
    53 0 11.5 2.2 3 0 0 0.0
    CQI_DATA_DYNA
    25 0 5.2 4.2 12 0 0 0.0
    CQI_INDEX
    28 0 5.0 1.0 9 0 0 0.0
    GRH_DATA_STAT
    23 0 5.2 8.0 3 0 0 0.0
    GTMAO_DATA_DYNA
    20 0 0.0 1.0 6 0 0 0.0
    COM_DATA_DYNA
    19 0 20.5 1.0 3 0 0 0.0
    COM_INDEX
    18 0 6.1 1.0 3 0 0 0.0
    RFG_INDEX
    9 0 0.0 1.0 9 0 0 0.0
    CQI_DATA_STAT
    13 0 3.8 1.0 3 0 0 0.0
    GFRP_DATA_DYNA
    9 0 0.0 1.0 6 0 0 0.0
    USERS
    9 0 0.0 1.0 6 0 0 0.0
    RFG_DATA_DYNA
    6 0 0.0 1.0 6 0 0 0.0
    GFRP_DATA_STAT
    6 0 0.0 1.0 3 0 0 0.0
    Tablespace IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by IOs (Reads + Writes) desc
    Tablespace
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    GFRP_INDEX
    6 0 0.0 1.0 3 0 0 0.0
    PRF_DATA_DYNA_ARCHIVE
    6 0 0.0 1.0 3 0 0 0.0
    PRF_INDEX_ARCHIVE
    6 0 0.0 1.0 3 0 0 0.0
    COM_DATA_STAT
    4 0 2.5 1.0 3 0 0 0.0
    BO_DATA
    3 0 0.0 1.0 3 0 0 0.0
    DRSYS
    3 0 0.0 1.0 3 0 0 0.0
    FSQ_DATA_DYNA
    3 0 0.0 1.0 3 0 0 0.0
    FSQ_DATA_STAT
    3 0 0.0 1.0 3 0 0 0.0
    FSQ_INDEX
    3 0 0.0 1.0 3 0 0 0.0
    GNS_DATA_DYNA
    3 0 0.0 1.0 3 0 0 0.0
    GTMAO_DATA_STAT
    3 0 0.0 1.0 3 0 0 0.0
    GTMAO_INDEX
    3 0 0.0 1.0 3 0 0 0.0
    INDX
    3 0 0.0 1.0 3 0 0 0.0
    RFG_DATA_STAT
    3 0 0.0 1.0 3 0 0 0.0
    SMQ_DATA_DYNA
    3 0 0.0 1.0 3 0 0 0.0
    SMQ_DATA_STAT
    3 0 0.0 1.0 3 0 0 0.0
    SMQ_INDEX
    3 0 0.0 1.0 3 0 0 0.0
    File IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by Tablespace, File
    Tablespace Filename
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    APS_DATA_DYNA F:\ORADATA\APS_DYNA_DF
    279 1 7.0 3.4 3 0 0
    F:\ORADATA\APS_DYNA_01.DF
    477 1 4.9 2.2 4 0 0
    F:\ORADATA\APS_DYNA_02.DF
    412 1 4.5 1.5 4 0 0
    F:\ORADATA\APS_DYNA_03.DF
    420 1 5.1 1.3 3 0 0
    F:\ORADATA\APS_DYNA_04.DF
    9 0 0.0 1.0 3 0 0
    F:\ORADATA\APS_DYNA_05.DF
    17 0 4.1 3.0 3 0 0
    F:\ORADATA\APS_DYNA_06.DF
    6,158 13 4.1 1.4 11 0 6 0.0
    F:\ORADATA\APS_DYNA_07.DF
    8,331 18 3.4 1.4 9 0 1 20.0
    F:\ORADATA\APS_DYNA_08.DF
    10 0 2.0 1.0 3 0 0
    G:\ORADATA\APS_DYNA_09.DF
    2,172 5 7.8 8.5 7 0 0
    G:\ORADATA\APS_DYNA_10.DF
    518 1 6.4 2.7 17 0 0
    APS_DATA_STAT F:\ORADATA\APS_STAT_DF
    324 1 4.4 4.6 41 0 0
    APS_INDEX F:\ORADATA\APS_IDX_003.DF
    10 0 0.0 1.0 13 0 0
    F:\ORADATA\APS_INDEX_DF
    117 0 8.2 1.0 18 0 0
    F:\ORADATA\APS_INDEX_DF02
    12 0 1.7 1.0 20 0 0
    F:\ORADATA\APS_INDEX_04.DF
    14 0 2.9 1.0 33 0 0
    F:\ORADATA\APS_INDEX_05.DF
    1,016 2 6.2 1.7 29 0 0
    BO_DATA F:\ORADATA\BO_DATA.DF
    3 0 0.0 1.0 3 0 0
    COM_DATA_DYNA E:\ORACLE\ORADATA\QLM3\COM_DATA_DYNA.ORA
    19 0 20.5 1.0 3 0 0
    COM_DATA_STAT E:\ORACLE\ORADATA\QLM3\COM_DATA_STAT.ORA
    4 0 2.5 1.0 3 0 0
    COM_INDEX F:\ORADATA\COM_INDEX.DF
    18 0 6.1 1.0 3 0 0
    CQI_DATA_DYNA G:\ORADATA\CQI_DATA_DYNA_01.DF
    25 0 5.2 4.2 12 0 0
    File IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by Tablespace, File
    Tablespace Filename
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    CQI_DATA_STAT G:\ORADATA\CQI_DATA_STAT_01.DF
    13 0 3.8 1.0 3 0 0
    CQI_INDEX G:\ORADATA\CQI_INDEX_01.DF
    28 0 5.0 1.0 9 0 0
    DRSYS E:\ORACLE\ORADATA\QLM3\DR01.DBF
    3 0 0.0 1.0 3 0 0
    FSQ_DATA_DYNA F:\ORADATA\FSQ_DYNA_DF
    3 0 0.0 1.0 3 0 0
    FSQ_DATA_STAT F:\ORADATA\FSQ_STAT_DF
    3 0 0.0 1.0 3 0 0
    FSQ_INDEX F:\ORADATA\FSQ_INDEX_DF
    3 0 0.0 1.0 3 0 0
    GFRP_DATA_DYNA G:\ORADATA\GFRP_DYNA_01.DF
    6 0 0.0 1.0 3 0 0
    H:\ORADATA\GFRP_DATA_DYNA
    3 0 0.0 1.0 3 0 0
    GFRP_DATA_STAT G:\ORADATA\GFRP_STAT_01.DF
    6 0 0.0 1.0 3 0 0
    GFRP_INDEX G:\ORADATA\GFRP_INDEX_01.DF
    6 0 0.0 1.0 3 0 0
    GNS_DATA_DYNA F:\ORADATA\GNS_DATA_DYNA_01.ORA
    3 0 0.0 1.0 3 0 0
    GRH_DATA_DYNA F:\ORADATA\GRH_DY_1.DF
    38 0 11.3 1.0 37 0 0
    F:\ORADATA\GRH_DY_2.DF
    3 0 0.0 1.0 5 0 0
    F:\ORADATA\GRH_DY_3.DF
    3 0 0.0 1.0 3 0 0
    F:\ORADATA\GRH_DY_4.DF
    13 0 6.2 1.0 18 0 0
    F:\ORADATA\GRH_DY_5.DF
    3 0 0.0 1.0 3 0 0
    F:\ORADATA\GRH_DY_6.DF
    3 0 0.0 1.0 3 0 0
    F:\ORADATA\GRH_DY_7.DF
    3 0 0.0 1.0 3 0 0
    H:\ORADATA\GRH_DY_8.DF
    3 0 0.0 1.0 3 0 0
    H:\ORADATA\GRH_DY_9.DF
    3 0 0.0 1.0 3 0 0
    GRH_DATA_STAT F:\ORADATA\GRH_ST_1.DF
    File IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by Tablespace, File
    Tablespace Filename
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    23 0 5.2 8.0 3 0 0
    GRH_INDEX F:\ORADATA\GRH_IDX.DF
    38 0 8.2 1.0 46 0 0
    GTMAO_DATA_DYNA F:\ORADATA\GTMAO_DATA_DYNA_01.DF
    10 0 0.0 1.0 3 0 0
    F:\ORADATA\GTM_DY_2.DF
    10 0 0.0 1.0 3 0 0
    GTMAO_DATA_STAT F:\ORADATA\GTMAO_DATA_STAT_01.DF
    3 0 0.0 1.0 3 0 0
    GTMAO_INDEX F:\ORADATA\GTMAO_INDEX_01.DF
    3 0 0.0 1.0 3 0 0
    INDX E:\ORACLE\ORADATA\QLM3\INDX01.DBF
    3 0 0.0 1.0 3 0 0
    PRF_DATA_DYNA E:\ORADATA\PRF_D14.DF
    29 0 10.3 1.0 12 0 0
    E:\ORADATA\PRF_D15.DF
    28 0 10.4 1.0 19 0 0
    E:\ORADATA\PRF_D16.DF
    89 0 31.9 26.9 9 0 0
    F:\ORADATA\PRF_D1.DF
    9 0 5.6 1.0 4 0 0
    F:\ORADATA\PRF_D10.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D11.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D12.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D13.DF
    26 0 7.7 7.2 3 0 2 5.0
    F:\ORADATA\PRF_D2.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D3.DF
    6 0 0.0 1.0 5 0 0
    F:\ORADATA\PRF_D4.DF
    15 0 4.0 1.0 10 0 0
    F:\ORADATA\PRF_D5.DF
    15 0 4.0 1.0 10 0 0
    F:\ORADATA\PRF_D6.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D7.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D8.DF
    6 0 0.0 1.0 3 0 0
    F:\ORADATA\PRF_D9.DF
    6 0 0.0 1.0 3 0 0
    G:\ORADATA\PRF_D17.DF
    File IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by Tablespace, File
    Tablespace Filename
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    16 0 7.5 13.3 3 0 0
    PRF_DATA_DYNA G:\ORADATA\PRF_D18.DF
    9 0 6.7 1.0 6 0 0
    PRF_DATA_DYNA_ARCHIVE H:\ORADATA\PRF_DATA_DYNA_ARCHIVE01.DF
    6 0 0.0 1.0 3 0 0
    PRF_DATA_STAT F:\ORADATA\PRF_ST1.DF
    53 0 11.5 2.2 3 0 0
    PRF_INDEX E:\ORADATA\PRF_IDX4.DF
    14 0 7.1 1.0 10 0 0
    E:\ORADATA\PRF_IDX5.DF
    13 0 3.8 1.0 10 0 0
    E:\ORADATA\PRF_IDX6.DF
    18 0 8.3 1.0 12 0 0
    E:\ORADATA\PRF_IDX7.DF
    10 0 2.0 1.0 3 0 0
    F:\ORADATA\PRF_IDX1.DF
    8 0 2.5 1.0 4 0 0
    F:\ORADATA\PRF_IDX2.DF
    11 0 3.6 1.0 11 0 0
    F:\ORADATA\PRF_IDX3.DF
    43 0 7.9 1.0 28 0 1 0.0
    H:\ORADATA\PRF_IDX8.DF
    16 0 10.6 1.0 10 0 0
    PRF_INDEX_ARCHIVE H:\ORADATA\PRF_INDEX_ARCHIVE_01.DF
    6 0 0.0 1.0 3 0 0
    RBS E:\ORACLE\ORADATA\QLM3\RBS01.DBF
    22 0 59.1 1.0 92 0 0
    E:\ORACLE\ORADATA\QLM3\RBS02.DBF
    8 0 5.0 1.0 19 0 0
    RBS1 E:\ORACLE\ORADATA\QLM3\RBS11.ORA
    3 0 0.0 1.0 18 0 1 330.0
    E:\ORACLE\ORADATA\QLM3\RBS12.ORA
    5 0 24.0 1.0 12 0 0
    E:\ORACLE\ORADATA\QLM3\RBS13.ORA
    9 0 6.7 1.0 128 0 0
    RFG_DATA_DYNA G:\ORADATA\RFG_DATA_DYNA_01.DF
    3 0 0.0 1.0 3 0 0
    G:\ORADATA\RFG_DATA_DYNA_02.DF
    3 0 0.0 1.0 3 0 0
    RFG_DATA_STAT G:\ORADATA\RFG_DATA_STAT_01.DF
    3 0 0.0 1.0 3 0 0
    RFG_INDEX G:\ORADATA\RFG_INDEX_01.DF
    3 0 0.0 1.0 3 0 0
    File IO Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->ordered by Tablespace, File
    Tablespace Filename
    Av Av Av Av Buffer Av Buf
    Reads Reads/s Rd(ms) Blks/Rd Writes Writes/s Waits Wt(ms)
    RFG_INDEX G:\ORADATA\RFG_INDEX_02.DF
    3 0 0.0 1.0 3 0 0
    G:\ORADATA\RFG_INDEX_03.DF
    3 0 0.0 1.0 3 0 0
    SMQ_DATA_DYNA F:\ORADATA\SMQ_DYNA_DF
    3 0 0.0 1.0 3 0 0
    SMQ_DATA_STAT F:\ORADATA\SMQ_STAT_DF
    3 0 0.0 1.0 3 0 0
    SMQ_INDEX F:\ORADATA\SMQ_INDEX_DF
    3 0 0.0 1.0 3 0 0
    SYSTEM E:\ORACLE\ORADATA\QLM3\SYSTEM01.DBF
    119 0 12.8 1.6 53 0 0
    E:\ORACLE\ORADATA\QLM3\SYSTEM02.DBF
    9 0 14.4 3.6 5 0 0
    TEMP E:\ORACLE\ORADATA\QLM3\TEMP01.DBF
    9,953 22 0.0 1.2 11,991 26 0
    TEMP1 H:\ORADATA\TEMP101.ORA
    4,163 9 0.0 1.1 3,367 7 0
    TOOLS E:\ORACLE\ORADATA\QLM3\TOOLS01.DBF
    3 0 0.0 1.0 27 0 0
    E:\ORACLE\ORADATA\QLM3\TOOLS02.DBF
    50 0 10.8 1.0 260 1 0
    USERS E:\ORACLE\ORADATA\QLM3\USERS01.DBF
    3 0 0.0 1.0 3 0 0
    E:\ORACLE\ORADATA\QLM3\USERS02.DBF
    6 0 0.0 1.0 3 0 0
    Buffer Pool Statistics for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> Pools D: default pool, K: keep pool, R: recycle pool
    Free Write Buffer
    Buffer Consistent Physical Physical Buffer Complete Busy
    P Gets Gets Reads Writes Waits Waits Waits
    D 50,061 0 49,675 981 0 0 11
    Buffer wait Statistics for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> ordered by wait time desc, waits desc
    Tot Wait Avg
    Class Waits Time (cs) Time (cs)
    undo header 1 33 33
    data block 10 3 0
    Rollback Segment Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->A high value for "Pct Waits" suggests more rollback segments may be required
    Trans Table Pct Undo Bytes
    RBS No Gets Waits Written Wraps Shrinks Extends
    0 24.0 0.00 0 0 0 0
    1 78.0 0.00 16,834 0 0 0
    2 84.0 0.00 29,374 0 0 0
    3 65.0 0.00 9,950 0 0 0
    4 67.0 0.00 14,278 0 0 0
    5 66.0 0.00 16,364 0 0 0
    6 64.0 0.00 6,144 0 0 0
    7 176.0 0.00 58,588 0 0 0
    8 69.0 0.00 23,158 0 0 0
    9 90.0 0.00 15,068 0 0 0
    10 64.0 0.00 9,776 0 0 0
    11 69.0 0.00 11,076 0 0 0
    12 298.0 0.34 647,830 2 0 0
    13 101.0 0.00 233,506 0 0 0
    Rollback Segment Storage for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->Optimal Size should be larger than Avg Active
    RBS No Segment Size Avg Active Optimal Size Maximum Size
    0 401,408 0 401,408
    1 4,186,112 540,690 4,194,304 4,186,112
    2 4,186,112 663,298 4,194,304 4,186,112
    3 4,186,112 536,369 4,194,304 4,186,112
    4 4,186,112 552,957 4,194,304 4,186,112
    5 4,186,112 566,795 4,194,304 4,186,112
    6 4,186,112 565,140 4,194,304 4,186,112
    7 4,186,112 524,103 4,194,304 4,186,112
    8 251,854,848 534,027 251,854,848
    9 48,447,488 630,996 48,447,488
    10 29,810,688 609,701 29,810,688
    11 21,823,488 531,386 21,823,488
    12 30,875,648 1,398,641 30,875,648
    13 15,720,448 4,922,485 20,963,328
    Latch Activity for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
    willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
    Pct Avg Pct
    Get Get Slps NoWait NoWait
    Latch Name Requests Miss /Miss Requests Miss
    active checkpoint queue latch 395 0.0 0
    cache buffer handles 118 0.0 0
    cache buffers chains 10,212,613 0.0 0.0 83,659 0.0
    cache buffers lru chain 88,174 0.0 0.4 0
    channel handle pool latch 18 0.0 23 0.0
    channel operations parent lat 36 0.0 23 0.0
    checkpoint queue latch 4,264 0.0 0
    dml lock allocation 1,219 0.0 0
    enqueue hash chains 3,289 0.0 0.0 0
    enqueues 5,614 0.0 0
    error message lists 9 0.0 0
    event group latch 18 0.0 0
    file number translation table 10 0.0 0
    job_queue_processes parameter 8 0.0 0
    ktm global data 3 0.0 0
    latch wait list 36 0.0 36 0.0
    library cache 287,494 0.1 0.2 92 0.0
    library cache load lock 46 0.0 0
    list of block allocation 774 0.0 0
    loader state object freelist 72 0.0 0
    longop free list 535 0.0 0
    messages 3,858 0.0 0.0 0
    multiblock read objects 11,104 0.0 0
    ncodef allocation latch 8 0.0 0
    parallel query alloc buffer 32 3.1 0.0 0
    parallel query stats 6 0.0 0
    parallel txn reco latch 3,083 0.0 0
    process allocation 18 0.0 18 0.0
    process group creation 41 0.0 0
    process queue 18 0.0 0
    process queue reference 2,886 0.0 14 0.0
    query server freelists 27 0.0 0
    query server process 4 0.0 4 0.0
    redo allocation 10,454 0.0 0.0 0
    redo writing 2,223 0.0 0
    row cache objects 38,374 0.0 0.0 12 0.0
    sequence cache 383 0.0 0
    session allocation 3,315 0.1 1.3 0
    session idle bit 128,781 0.0 0.0 0
    session switching 8 0.0 0
    session timer 149 0.0 0
    shared pool 19,330 0.0 0.2 0
    sort extent pool 172 0.0 0
    Token Manager 904 0.0 12 0.0
    transaction allocation 1,143 0.0 0
    transaction branch allocation 8 0.0 0
    undo global data 1,833 0.0 0
    user lock 66 0.0 0
    virtual circuit queues 22 0.0 0
    Latch Activity for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->"Get Requests", "Pct Get Miss" and "Avg Slps/Miss" are statistics for
    willing-to-wait latch get requests
    ->"NoWait Requests", "Pct NoWait Miss" are for no-wait latch get requests
    ->"Pct Misses" for both should be very close to 0.0
    Pct Avg Pct
    Get Get Slps NoWait NoWait
    Latch Name Requests Miss /Miss Requests Miss
    Latch Sleep breakdown for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> ordered by misses desc
    Get Spin &
    Latch Name Requests Misses Sleeps Sleeps 1->4
    cache buffers chains 10,212,613 224 9 217/5/2/0/0
    library cache 287,494 211 44 176/29/3/3/0
    cache buffers lru chain 88,174 20 8 16/0/4/0/0
    shared pool 19,330 9 2 8/0/1/0/0
    session allocation 3,315 3 4 1/1/0/1/0
    Latch Miss Sources for DB: QLM3 Instance: orcl Snaps: 1 -2
    -> only latches with sleeps are shown
    -> ordered by name, sleeps desc
    NoWait Waiter
    Latch Name Where Misses Sleeps Sleeps
    cache buffers chains kcbgtcr: kslbegin 0 7 9
    cache buffers chains kcbgtcr 0 2 0
    cache buffers lru chain kcbbiop: lru scan 0 8 0
    library cache kglic 0 24 2
    library cache kglhdgn: child: 0 18 8
    library cache kglget: child: KGLDSBYD 0 1 1
    library cache kglpnal: child: alloc spac 0 1 1
    session allocation ksuxds: KSUSFCLC not set 0 4 0
    shared pool kghfrunp: alloc: clatch no 0 2 0
    Dictionary Cache Stats for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->"Pct Misses" should be very low (< 2% in most cases)
    ->"Cache Usage" is the number of cache entries being used
    ->"Pct SGA" is the ratio of usage to allocated size for that cache
    Get Pct Scan Pct Mod Final Pct
    Cache Requests Miss Requests Miss Req Usage SGA
    dc_constraints 0 0 0 188 99
    dc_database_links 0 0 0 0 0
    dc_files 0 0 0 16 94
    dc_free_extents 26 23.1 9 0.0 19 2,072 99
    dc_global_oids 0 0 0 28 62
    dc_histogram_data 0 0 0 0 0
    dc_histogram_data_valu 0 0 0 0 0
    dc_histogram_defs 597 0.0 0 0 ###### 100
    dc_object_ids 3,481 0.0 0 0 4,068 100
    dc_objects 606 1.5 0 0 8,596 100
    dc_outlines 0 0 0 0 0
    dc_profiles 14 0.0 0 0 1 9
    dc_rollback_segments 394 0.0 0 0 15 54
    dc_segments 260 0.0 0 9 4,752 100
    dc_sequence_grants 104 0.0 0 0 169 92
    dc_sequences 183 0.0 0 169 36 86
    dc_synonyms 280 5.7 0 0 4,343 100
    dc_tablespace_quotas 33 0.0 0 9 18 23
    dc_tablespaces 2,965 0.0 0 0 45 78
    dc_used_extents 9 100.0 0 9 2,086 53
    dc_user_grants 2,213 0.0 0 0 109 93
    dc_usernames 289 0.0 0 0 131 99
    dc_users 2,790 0.0 0 0 209 95
    ifs_acl_cache_entries 0 0 0 0 0
    Library Cache Activity for DB: QLM3 Instance: orcl Snaps: 1 -2
    ->"Pct Misses" should be very low
    Get Pct Pin Pct Invali-
    Namespace Requests Miss Requests Miss Reloads dations
    BODY 22 0.0 21 0.0 0 0
    CLUSTER 0 0 0 0
    INDEX 0 0 0 0
    OBJECT 0 0 0 0
    PIPE 0 0 0 0
    SQL AREA 2,846 0.2 48,618 0.2 25 0
    TABLE/PROCEDURE 7,107 0.2 29,746 0.2 3 0
    TRIGGER 22 0.0 22 0.0 0 0
    SGA Memory Summary for DB: QLM3 Instance: orcl Snaps: 1 -2
    SGA regions Size in Bytes
    Database Buffers 157,286,400
    Fixed Size 75,804
    Redo Buffers 172,032
    Variable Size 185,597,952
    sum 343,132,188
    SGA breakdown difference for DB: QLM3 Instance: orcl Snaps: 1 -2
    Pool Name Begin value End value Difference
    java pool free memory 45,973,504 45,973,504 0
    java pool memory in use 4,030,464 4,030,464 0
    large pool free memory 614,400 614,400 0
    shared pool db_block_buffers 2,611,200 2,611,200 0
    shared pool db_block_hash_buckets 438,520 438,520 0
    shared pool db_files 370,988 370,988 0
    shared pool dictionary cache 21,129,860 21,141,516 11,656
    shared pool event statistics per ses 774,000 774,000 0
    shared pool fixed allocation callbac 640 640 0
    shared pool free memory 15,115,180 16,081,664 966,484
    shared pool joxlod: in ehe 91,888 91,888 0
    shared pool joxlod: in phe 37,284 37,284 0
    shared pool joxlod: init P 812 812 0
    shared pool joxs heap init 4,248 4,248 0
    shared pool KGFF heap 69,160 69,160 0
    shared pool KGK heap 19,236 19,236 0
    shared pool KQLS heap 8,262,784 8,225,444 -37,340
    shared pool library cache 29,124,008 29,099,824 -24,184
    shared pool miscellaneous 5,152,512 5,135,872 -16,640
    shared pool partitioning d 203,808 185,716 -18,092
    shared pool PLS non-lib hp 2,096 2,096 0
    shared pool PL/SQL DIANA 3,668,952 3,659,000 -9,952
    shared pool PL/SQL MPCODE 1,560,124 1,563,104 2,980
    shared pool PL/SQL PPCODE 19,460 19,460 0
    shared pool PX msg pool 46,572 46,572 0
    shared pool PX subheap 11,612 11,612 0
    shared pool sessions 485,100 485,100 0
    shared pool sql area 45,274,860 44,405,220 -869,640
    shared pool table columns 53,228 53,564 336
    shared pool table definiti 16,748 15,428 -1,320
    shared pool transaction_branches 368,000 368,000 0
    shared pool trigger defini 41,236 36,948 -4,288
    shared pool trigger inform 3,380 3,380 0
    shared pool trigger source 572 572 0
    shared pool type object de 1,600 1,600 0
    shared pool view columns d 1,072 1,072 0
    db_block_buffers 157,286,400 157,286,400 0
    fixed_sga 75,804 75,804 0
    log_buffer 163,840 163,840 0
    init.ora Parameters for DB: QLM3 Instance: orcl Snaps: 1 -2
    End value
    Parameter Name Begin value (if different)
    audit_trail TRUE
    background_dump_dest E:\oracle\admin\QLM3\bdump
    compatible 8.1.7.0
    control_files E:\oracle\oradata\QLM3\control01.
    cursor_sharing EXACT
    db_block_buffers 19200
    db_block_size 8192
    db_file_multiblock_read_count 32
    db_files 1024
    db_name QLM3
    distributed_transactions 500
    global_names FALSE
    instance_name ORCL
    java_pool_size 50000000
    job_queue_interval 10
    job_queue_processes 4
    large_pool_size 614400
    log_buffer 163840
    log_checkpoint_interval 5000
    log_checkpoint_timeout 0
    max_dump_file_size 10240
    max_enabled_roles 30
    mts_dispatchers (PROTOCOL=TCP)(PRE=oracle.aurora.
    open_cursors 1000
    open_links 4
    oracle_trace_collection_name
    os_authent_prefix
    parallel_max_servers 8
    processes 200
    query_rewrite_enabled TRUE
    query_rewrite_integrity TRUSTED
    remote_login_passwordfile EXCLUSIVE
    rollback_segments RBS10, RBS11, RBS12, RBS13, RBS14
    service_names QLM3
    shared_pool_size 128000000
    sort_area_retained_size 128000
    sort_area_size 128000
    timed_statistics TRUE
    user_dump_dest E:\oracle\admin\QLM3\udump
    utl_file_dir c:\utl_file
    End of Report.
    Thanks for your help.
    regards raitsarevo

    Hi
    I'm experienced any problem when our application run one transaction it becomes very slow, before it was speed and from yesterday it takes a lot of time to accomplish the transaction. That's why i analyze the problem with statspack and i've done also a trace. It's for my problem and for academic purpose too.
    Many thanks for your help.

  • How to interprete db_stats report for -m option

    Hi
    please help me to interprete the db_stats report (for -m option).
    What is the total number of pages created by DB? (It is "Current page count" or "The number of page allocations").
    what is " Total number of times hash chains searched for a page" , "Total number of hash chain entries checked for page" and " Requested pages found in the cache" ( we see really huge numbers there when XML file size is increased)
    Thanks,
    Santhosh

    Hi Santhosh,
    Here are some explanations on the memory pool (cache) statistics:
    - “The number of page allocations” (st_alloc)
         This accounts for the total number of page allocations made by BDB. We allocate pages in the memory pool when we create, open and rename a file in the memory pool, when we get a page from a database file, when we resize the memory pool, when we create and extend the free page list, etc. This value is grow-only.
    - “Current total page count” (st_pages)
         This represents the number of pages found in the cache (both clean, with non-updated content, and dirty, with updated content). So, this equals the sum of the “Current clean page count” (st_page_clean) and the “Current dirty page count” (st_page_dirty).
    - “Requested pages found in the cache” (st_cache_hit)
         This represents the total number of requests for database pages that were satisfied with pages existing in the memory pool. The percent value represents the cache hit rate, that is, how many requested pages were found in the cache, and it’s calculated using the formula “st_cache_hit / (st_cache_hit + st_cache_miss)”.
    - “Requested pages not found in the cache” (st_cache_miss)
         This is the total number of requested pages that were not served directly from cache and had to be read from disk. You can determine a miss rate value, using the following formula: “st_cache_miss / (st_cache_miss + st_cache_hit)”; or, you may substract the hit rate from 100%. A higher hit rate means a hotter cache; details on how to appropriately size the cache is here:
    http://www.oracle.com/technology/documentation/berkeley-db/db/ref/am_conf/cachesize.html
    - “Number of hash buckets used for page location” (st_hash_buckets)
         We organize and manage the cache buffer space using hash buckets; each hash bucket has a hash chain associated where its entries (hash chain entries) refer to buffers in the memory pool space. Thus, this value represents the number of hash buckets we’re using for administering pages in the memory pool.
    - “Total number of times hash chains searched for a page” (st_hash_searches)
         This value accounts for the total number of times we’ve inspected the hash chains when searching for a page in the cache (memory pool).
    - “Total number of hash chain entries checked for a page” (st_hash_examined)
         This value represents the total number of entries in cache’s hash bucket chains we’ve examined when looking for a page.
    When the container’s/database’s size increases, the number of pages that comprise the file will increase as well. The statistics you’ve mentioned are grow-only, so their values increase during the lifetime of the application.
    Let me know if this information is helpful and if you need further clarification.
    Regards,
    Andrei

  • Statistics Collection to a Table

    Hello,
    i need to gather statistics for few tables from a schema, to a separate table. Basically i have gather the stats into newly created table. my question is how can i do this? i know how to generate statistics using the dbms statspack, but do not have any idea of how to gather these statistics to a separate table>
    could any one shed some light here..
    Thanks..

    Hello,
    i created a table using the following dbms_stats package.
    BEGIN
    DBMS_STATS.create_stat_table (
    ownname => 'TEST',
    stattab => 'stats_table',
    tblspace => 'users');
    END;
    when this table created using the above script it created with the following columns.
    STATID VARCHAR2(30 BYTE),
    TYPE CHAR(1 BYTE),
    VERSION NUMBER,
    FLAGS NUMBER,
    C1 VARCHAR2(30 BYTE),
    C2 VARCHAR2(30 BYTE),
    C3 VARCHAR2(30 BYTE),
    C4 VARCHAR2(30 BYTE),
    C5 VARCHAR2(30 BYTE),
    N1 NUMBER,
    N2 NUMBER,
    N3 NUMBER,
    N4 NUMBER,
    N5 NUMBER,
    N6 NUMBER,
    N7 NUMBER,
    N8 NUMBER,
    N9 NUMBER,
    N10 NUMBER,
    N11 NUMBER,
    N12 NUMBER,
    D1 DATE,
    R1 RAW(32),
    R2 RAW(32),
    CH1 VARCHAR2(1000 BYTE)
    how can I interpret what column is for what? for example C1 to C5, N1 to N12 or R1, CH1 what do they mean?
    also will be able to get any info regarding the COst of the SQL statement that took to run? if not how can i obtain that info?
    Then I gathered statistics for one table to test.
    exec dbms_stats.gather_table_stats(ownname=>'TEST',
    estimate_percent=>10,
    statown=>'TEST',
    tabname=>'ord_receipts',
    stattab=>'STATS_TABLE',
    statid=>'TESTING');
    the data inserted into STATS_TABLE, but could not understand.
    I need to run these statistics on daily basis and save to a diffferent table daily . for example today is 01/01/2012 should have its own table for stats to collect and 01/02/2012 should have another table to collect the statistics.
    is there any way that i can dynamically incorporated when gathering the statistics, to create the STATS_TABLE concatanated with sysdate daily to analyze the statistics?
    Thanks..

  • Cgi statistics gathering under 6.1 and Solaris 9

    Hello all,
    is it possible to log for cgi requests the value for handling each of the time spent on the request?
    I see a lot of editable parameters in the 'Performance, Tuning and Scaling Guide' but can't figure out how to do that.
    Once in a thread I read "...enable statistics gathering, then add %duration% to your access log format line".
    I can't find the terminus %duration% in the guide, which parameter is taken?
    Regards Nick

    Hello elvin,
    thanks for your reply. Now I think I managed to let the webserver log the duration of a cgi request, but I'm unsure how to interpret the value eg. in the access log I get
    ..."GET /cgi/beenden.cgi ... Gecko/20040113 MultiZilla/1.6.3.1d" 431710"
    ..."GET /pic.gif ... Gecko/20040113 MultiZilla/1.6.3.1d" 670"
    so the last value corresponds to my %duration% in the magnus.conf.
    431710 ... in msec? - makes no sense
    670 ... in msec?
    The complete string in magnus.conf reads as follows:
    Init fn="flex-init" access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf
    -request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length% \"%Req->headers.user-agent%\" \%duration%\""Regards Nick

  • Interpreting show controllers ingressq capacity

    anyone enlighten me how i can interpret these values, i need to analyze any bottleneck on the CRS-3 8-10GbE slot.
    Following command is on the fabric managment documenation but no clear explanation on these values :
    http://www.cisco.com/en/US/docs/routers/crs/software/crs_r3.9/adv_system/command/reference/ar39fabr.html#wp1080588
    show controllers ingressq capacity 0 location 0/0/cpu0
    Mon Apr 15 12:37:42.274 QAT
    ingressq capacity table: Port Max capacity
    Table id: 0
    4       8       12      16      20      24      28      32     
    36      40      44      48      52      56      60      64     
    68      72      76      88      108     136     172     216    
    276     348     436     552     700     884     1116    1408   
    1780    2248    2836    3584    4528    5724    7228    9136   
    11540   14580   18420   23272   29404   37152   46936   59304  
    74924   94664   119600  151108  190916  241212  304756  385040 
    486472  614628  776548  981120  1239584 1566140 1978724 2500000
    Further if anyone point me some documention related to troubleshooting packet drops / PSE / Queue managment . 
    Thanks in Advance,
    Gobinath.

    Hi Gobinath,
    This is not a command to worry yourself with.You also do not need to worry about the fabric queues. The only thing you should concern youself with is if the fabric is working and if/where drops are occuring.
    Troubleshooting is pretty simple. Check for config and port level issues along with total fabric health and statistics. Next look at the port level to look for ingress drops, go to the ingressQ, S1, S2, S3 fabric ASICs (Rx and Tx), fabricQ, and finally the egress port.
    I am not sure what new documentation is on CCO but here is a rough idea as well as some of the general fabric commands. There are many more commands, and it is possible to track drops all the way through the fabric with some time and patience. Some drops are ok, note the large input/output amounts of good packets, and not all drops means packets are being dropped.
    http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.4/troubleshooting/guide/tr34fab.pdf
    show int
    show controller stats
    In admin mode
    show controllers fabric plane all detail
    show controllers fabric connectivity all
    show controllers fabric link health *Most helpful for CRS-MC
    show controllers fabric fsdb-pla rack 0
    show controllers fabric plane all statistics
    show controllers fabric plane statistics detail
    HTH,
    Sam Milstead
    CSE - XR TAC

  • MDX queries : BW statistics are inconsistents

    Hello,
    We are implementing BO on top of SAP BW 3.5.
    We had some major performance issues , and now we're tryning to investigate in detail.
    The queries were first launched on BO only, and afeterwards on SAP BW, using the transaction MDXTEST, we measured a similar amount of time.
    Now now want to have a closer look at the distribution of the time spent. (DB%,Frontend%;Network%, etc...)
    The problem is that when we have a look at transaction ST03 in BW analysis, the statistics of MDX
    queries are inconsistents :
    I've join a concrete example :
    The left column is a BO statistic executed on SAP using MDXTEST,
    The right column is a traditional BEX query.
    When I do the addition of the different time %(percent total) the results is 100 % for the Bex query ...and 44% for the MDX query.
    I know that many fixes for MDX have been delivered on BI.7, but what about 3.5, I searched the sap notes but I couldn't find any note descrybing this symptom, nor any fix for our BW release.
    Do you know how I should interpret thoses results, in other worlds, where ar the missing percentages in MDX queries ?
    thank you in advance for your help.
    Regards.
    InfoCube Name                                         Cube C      Cube C
    Name of Query                                Query A(BO)        Query B(BEX)
    Number of Navigation Steps                        1     1
    Total Runtime (s)                                       534,9     39,8
    Total Runtime / Navigation Step (s)     534,9     39,8
    Median of Total Runtime (s)                      534,9     39,8
    Initialization Time (s)                                        0,2     0,4
    Initialization Time / Total Runtime (%)     0,04     1,01
    Ø Initialization Time (s)                     0,2     0,4
    OLAP Runtime (s)                                    0,9     2,1
    OLAP Time / Total Runtime (%)                  0,17     5,28
    OLAP Runtime / Navigation Step (s)     0,9     2,1
    Database Runtime (s)                                  197,0     22,4
    Database Runtime / Total Runtime (%)     36,83     56,28
    DB Runtime per Navigation Step (s)     197,0     22,4
    Frontend Runtime (s)                                    33,9     4,8
    Frontend Runtime / Total Runtime (%)     6,34     12,06
    Frontend Time per Navigation Step (s)     33,9     4,8
    Master Data Runtime (s)                    5,6     10,1
    Master Data Time / Total Runtime (%)     1,05     25,38
    Ø Master Data Time per Navigation Step     5,6     10,1
    Number of records selected                  18620     899
    Number of Transferred Records                10037     629
    Ratio of Selected to Transferred Records     1,9     1,4
    Database Time per Selected Record (ms)     10,6     24,9
    Number of Cells                                       162060     7295
    Cells per Transferred Records                   16,1     11,6
    Number Formatted                                     0     72
    Ratio of Formattings to Number of Cells     0,0     0,0
    percent Total     :                     44,43% for MDX              and  100,01% as expected for BEX
    time                                             237,8     40,2
    Edited by: Raoul Shiro on Feb 5, 2009 6:54 PM

    Hi Raoul,
    in regards to the BW statistics values I would suggest you open a OSS case.
    in regards to the performance improvements - correct they are done for BI7 and the XI 3.1 release.
    Ingo

Maybe you are looking for

  • Can't Transfer Files/Folders To & Around iPod?

    Hello there. Whenever I go to move something to the iPod's hard drive, or try to move things around it, all I get is the circle with the strike through it (basically, I'm unable to do the task). What is going on? I just restored it a few hours ago, a

  • Creating Help pages

    I have designed a java program(GUI). There is a button that brings up a help page when clicked, like in microsoft word help. How do i create this help page.

  • Getting dump when you hire an emp in Development system

    Hi, We are getting an ABAP dump when we hires an emp in development system where as the dump is not coming in Quality system. Kindly suggest any config settings need to changed. Please find the dump below for reference:                               

  • Maximum Form Size/Length

    I have spent the past 4 days creating a new form. I am building my police department's background investigation packet with FormsCentral. It is, as you can imagine, a very lengthy form. I am on page 13/28 and received a warning saying that I have rea

  • Forwarding workitem to different user

    there is a workflow which is in error failed due to agent assignment but we need to forward the workitem to a new user after restarting workitem as the previous user got terminated . Can anyone please suggest how to do that