AWR time model statistics vs SQL Statistics

Looking at an AWR report took on a unique snapshot interval, I note the following:

In time model statistics, DB time is listed as 161,47 seconds, with sql execute represents the time of 127,83 seconds.

When I DBA_HIST_SQLSTAT to queries on the same cliché and summarize all the elapsed_time_delta of each SQL stored in AWR, I find that it's 132,05 seconds, even after filtering of all PL/SQL (command_type 47) and each SQL with parsing_schema_name SYS.

If anything, I expect this sum less than that contained in the statistics of the model time, thinking that only the top n sql is included in DBA_HISSQLSTAT.

Does anyone know where my reasoning was an error?

KDeWeerd wrote:
Detailed analysis of an environment, trying to give meaning to all the numbers and to explain things to people doesn't make not easier if you can not all numbers that collects Oracle corresponding to some how.

Yes, I understand. Here you can not because the statistical statement have no knowledge of what what call. This is probably why Oracle introduced the chronological model: it gives information that you can't derive from other sources.

Any timed operation will be buffer at most 5 seconds of time data. This means that if a timed (such as the SQL execution) takes a long period of time to perform, the data published to this point of view lack maximum 5 seconds of the time accumulated for the operation.

Can't really make sense of interpretation which

means that the value may be missed for 5 seconds for each running of instruction.

Tags: Database

Similar Questions

  • AWR TIME STATISTICS

    Hello everyone,

    I need an answer everything into question of my mind.

    I have an example of awr report and I wonder on below...

    How is it 'execute sql elapsed time' and "DB CPU" are both is greater than the total duration of DB. Or the sum of all statisctics are greate than the total duration of DB.

    I knew that TIME DB = DB CPU + sql execute elapsed time + analysis elapsed time...

    But all of them are greater than 100, how and why.

    Statistics name time (s) per cent of the time Total of DB

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

    DB time 124 564

    Execute SQL time elapsed 95 118 853

    DB 27 033 22 CPU

    analysis time elapsed 12 15 552

    12-14-868 elapsed hard analysis

    elapsed time of bottom 6 7 804

    hard analysis (sharing criteria) elapsed ti 4 5 198

    me



    PL/SQL 3 3 272 elapsed execution

    time 2 2 546 background cpu



    Statistics name time (s) per cent of the time Total of DB

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

    hard analysis (bind incompatibility) passed 1 1 672

    PL/SQL compilation elapsed 1 1 050

    elapsed time of connection management call 178 0

    sequence of time charge 141 0

    Time cpu RMAN (backup/restore) 38 0

    repeated bind passed 13-0

    could not parse elapsed 3 0

    entering the time of PL/SQL rpc 0 0

    881931 wrote:
    Thank you my friend,

    I saw this response drinking I did not understand, Tom explained sql out of time, but I want to learn "why all are 100% grater."

    Thank you very much

    The simple reason why the statistics add up to more than 100% is because the statistics are not designed to be added together in the way that you add statistics. Statistics of time DB is just the CPU and wait event total time for the sessions of the user, so it was a logical choice as a divider for all statistics. Most of the time model statistics contributes to the statistic of time DB, but there is overlap between the statistics - for example, time CPU DB is required to run SQL statements (these two are listed statistics). Also included in the report of statistics that are not components of the statistics of time DB, as background the elapsed time, time background and RMAN (backup/restore) time cpu - cpu but the report still divides these statistics of statistics of time DB, probably just so that you have a common point of reference.

    Time model statistics should be seen in a tree that represents the parent relationships and the child between the statistics. The following article shows the directory structure and how you would interpret the statistics:
    http://hoopercharles.WordPress.com/2010/01/13/working-with-Oracle-time-model-data/

    If you take another look at your statistics:

    Statistic Name                           Time (s) Percent of Total DB Time
    ---------------------------------------- -------- ------------------------
    DB time                                   124,564
    sql execute elapsed time                  118,853                       95
    DB CPU                                     27,033                       22
    parse time elapsed                         15,552                       12
    hard parse elapsed time                    14,868                       12
    background elapsed time                     7,804                        6
    hard parse (sharing criteria) elapsed ti    5,198                        4
    PL/SQL execution elapsed time               3,272                        3
    background cpu time                         2,546                        2
    hard parse (bind mismatch) elapsed time     1,672                        1
    PL/SQL compilation elapsed time             1,050                        1
    connection management call elapsed time       178                        0
    sequence load elapsed time                    141                        0
    RMAN cpu time (backup/restore)                 38                        0
    repeated bind elapsed time                     13                        0
    failed parse elapsed time                       3                        0
    inbound PL/SQL rpc elapsed time                 0                        0
    

    You can make certain assumptions as follows:
    27 033 CPU seconds spent doing the work for user sessions. Because 124 564 seconds are indicated by the statistics of time DB, you can determine that about 124 564-27 033 seconds were spent in the events of waiting for user sessions. Sessions spent 15 552 seconds, the analysis of the SQL statements (note that some time CPU would be also consumed during analysis) and 14 868 seconds of this hard time parsing SQL statements, so sessions consume 15 552-14 868 seconds soft analysis of SQL statements. 14 868 seconds past hard analysis, 5 198 seconds were caused by sharing criteria and that 14 868-5 198 seconds were probably due to the unique SQL statements being submitted to the database. And so on.

    Charles Hooper
    Co-author of "Expert Oracle practices: Oracle Database Administration of the Oak Table.
    http://hoopercharles.WordPress.com/
    IT Manager/Oracle DBA
    K & M-making Machine, Inc.

  • Calculation of the time wall of a SQL query.

    Hello

    While trying to discover the time of running a SQL query (wall time) I read in one place that CPU_TIME/EXECUTIONS of v$ SQLAREA, is the precise runtime we can come close to.

    I can't use "set timing on ' or 'DBMS_UTILITY. GET_TIME' that I need to extract the execution time of the story because the query will be drawn to an end, and I need to know how long it took to DB level and compare it with the end time before calculating the % of time used in the DB level total.

    Maybe another way to track sessions and the user TKPORPOF but now I donot want to take the help of the ADMINISTRATOR at this initial stage.

    Is CPU_TIME/EXECUTIONS of v$ SQLAREA where (SQL_TEXT) AS "SELECT... OF... %'; should be enough?

    user2925917, yes as Brian already answered your understanding as posted above seems correct.  Except in the case where there has been only a running query you will download an average time.  The problem with averages is that one or two unusual executions that can skew the average, but in most cases the average will be probably fairly accurate.

    - -

    HTH - Mark D Powell.

  • Time of execution of SQL statements

    Is there a way to see the time of the last sql instructions? (as the TOAD request viewer)

    Without having to execute the statement as a script and use "set timing on."

    Kind regards

    Carsten

    We show the run down by the exit time

    You can also see the query execution times in the historical Panel SQL

  • is their any option to make its contribution to the time of execution in SQL

    is their any option to make its contribution to the time of execution in SQL instead of &

    Waran wrote:
    When to use & symbol to make his contribution in SQL queries. is their another way to provide the same.

    Yes, you can use a whole set to use any other symbol you like.

    SQL> select '&input' from dual;
    Enter value for input: Test1
    old   1: select '&input' from dual
    new   1: select 'Test1' from dual
    
    'TEST
    -----
    Test1
    
    SQL> set define "#"
    SQL> select '#input' from dual;
    Enter value for input: Test2
    old   1: select '#input' from dual
    new   1: select 'Test2' from dual
    
    'TEST
    -----
    Test2
    

    If this is not what you mean, please explain what you do and where you need to run SQL and the version of the database, like everyone else, it's important.

  • How to know the execution time of query in sql plus

    Hello

    I want to know the duration of execution of query in sql more accompanied by statistics

    I say time is set on;
    Set autotrace on;
    Select * view where usr_id = "abcd";


    If the result is 300 lines it scrolls up until all the rows are retrieved and finally gives me the run time in 40 seconds, or 1 minute... (it is after all records scrolls)

    but when I run it in Toad he gives 350 milli seconds...

    I want to see the execution time in sql how to proceed

    client and database server 11g is g 10

    concerning
    REDA

    In sqlplus you can do set autotrace traces to suppress the display of the selected lines.

    John

  • AWR: Time CPU = 0, % of time Total DB > 0

    Hello!

    I use * 10.2.0.5 *, AWR I see next statistical operation in one of my report:
    SQL ordered by Elapsed Time
    CPU Time   ... % Total DB Time
     0                            12.21
    Please explain, how is it possible
    DB-time does not time CPU here?

    Thank you and best regards,
    Pavel

    Published by: Pavel on April 18, 2012 04:17

    Hello

    for explanation of time CPU and DB, please visit http://savvinov.com/2012/04/06/awr-reports-interpreting-cpu-usage/.

    In your case, I think that the numbers is not reliable due to errors of instrumentation (for example, I saw 0 time processor in an extremely overloaded system).

    Best regards
    Nikolai

  • Concatinate date and time models

    Hello

    I have a problem.

    In forms 6i, I have two columns of data base no:

    1st is the Date format (exact)

    2nd is the time format (HH24:MI:SS)

    Now, I want to combine these two in 3rd fild who is date/time format (exact HH24:MI:SS).

    I tried this approach:

    Select to_date (to_char(:field1,'dd.mm.yyyy'): double to_char(:field2,'HH24:MI:SS');)

    ORA: 01850

    I also tried various other optios I found on the net but all I get are variations to errors ora 01850.

    Help, please!

    Thank you!

    994543 wrote:

    The two responses gives always the error: ora-01858

    Is there another way... I mean I didn't event know what to post here to help solve this problem.

    When I tried the solution answer was almost identical to what you guys posted here.

    You must post the values of Field1 and Field2. If they contain the values in the format that you specified then the solution should work without any fault. Here is an example

    SQL > var field1 varchar2 (10)

    SQL > varchar2 (8) var field2

    "SQL > exec: field1: = October 30, 2013.

    PL/SQL procedure successfully completed.

    "SQL > exec: field2: = 23:59 min 59 s.

    PL/SQL procedure successfully completed.

    SQL > alter session set nls_date_format = ' DD. MM YYYY HH24:MI:SS';

    Modified session.

    SQL > select to_date(:field1 ||) ' ' || : field2, ' JJ. MM YYYY HH24:MI:SS) double dt;

    DT
    -------------------
    30.10.2013 23:59:59

    SQL >

  • Help with time operations invloving the SQL query

    I created 2 tables in my SQL. One is the user_info_table table that stores the connection time and time zone of login for each user. The other is the post_table that stores user postid, who makes the post time post and time zone for each message.
    CREATE TABLE user_info
    (
    user_id VARCHAR(20), 
    login_date DATE,
    login_time_zone VARCHAR(20),
    PRIMARY KEY (user_id)
    );
    CREATE TABLE post_table
    (
    post_id VARCHAR(20),  
    user_id VARCHAR(20), 
    datepost DATE,  
    time_zone VARCHAR(20),
    PRIMARY KEY (post_id),
    FOREIGN KEY (user_id) REFERENCES user_info(user_id) ON DELETE CASCADE
    ) ;
    Some examples of data for my paintings is as below.
    INSERT INTO user_info VALUES( 'u1', to_date('9/17/2009 20:00','MM/DD/YYYY mi:ss'), -2 );
    INSERT INTO user_info VALUES( 'u2', to_date('9/17/2009 19:55','MM/DD/YYYY mi:ss'), -4 );
    
    INSERT INTO post_table VALUES( 'p1', 'u1', to_date('9/17/2009 20:50','MM/DD/YYYY mi:ss'), 6 );
    INSERT INTO post_table VALUES( 'p2', 'u2', to_date('9/17/2009 20:30','MM/DD/YYYY mi:ss'), -5 );
    INSERT INTO post_table VALUES( 'p3', 'u2', to_date('9/18/2009 6:00','MM/DD/YYYY mi:ss'), 2 );
    INSERT INTO post_table VALUES( 'p4', 'u1', to_date('9/17/2009 21:00','MM/DD/YYYY mi:ss'), -3 );
    I need to write a SQL query which - is the user whose time difference between the time of the connection and the last time when he or she wrote a post is the smallest. I need to consider the time zones here as well.

    I am not sure if time_zone must be of type VARCHAR or TIMESTAMP then have created as a VARCHAR in my paintings.

    Someone help me please to form this query.

    PS: How can I tags < code > user in this forum to write sql statements.

    Published by: user11994430 on October 9, 2009 17:59

    You can do this by adding a clause of "HAVING" as shown below. However, with your test defined data it returns ZERO rows because for all users of the MAX (DATEPOST) IS LESS than MAX (LOGIN_DATE)

    SELECT     USER_ID
    FROM
    (
         SELECT     USER_ID
         ,     DENSE_RANK() OVER (ORDER BY POST_LOGIN_DIFF) RNK
         FROM
         (
              SELECT     USER_INFO.USER_ID
              ,     MAX(DATEPOST) - MAX(LOGIN_DATE) AS POST_LOGIN_DIFF
              FROM     USER_INFO
              JOIN     POST_TABLE     ON POST_TABLE.USER_ID = USER_INFO.USER_ID
              GROUP BY USER_INFO.USER_ID
              HAVING      MAX(DATEPOST) > MAX(LOGIN_DATE)
         )
    )
    WHERE RNK = 1
    
  • Modeling of a SQL result

    Hello! I have a Sql that returns
    col1 col2 col3 col4 col5
    1 1 0 1
    1 0 1 1
    0 1 B 0 0
    1 1 0 0
    0 1 B 0 0

    Assuming that the sentence: Select col1, col2, col3, col4 col5 table

    How I model the sentence to get this result:

    col1 col2 col3 col4 col5
    4 1 1 2
    B 0 0 1 0

    The columns col3, col4 y col5 are obtained by adding the result of each line. col1 and col2 is the only value that is displayed.

    Thanks in advance

    Search SELECT, GROUPBY, SUM... in the documentation, you

    http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/statements_10002.htm#i2065646
    http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/statements_10002.htm#i2182483
    http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/functions163.htm#i89126

    and then tell us please what you don't understand

  • Can I use session variables in data model BI publisher SQL query?

    Hi Experts,

    We apply security at the level of the BI Publisher 11g data.

    In OBIEE we do so using session variables, so I wanted to just ask if we can use the same session variables in BI Publisher as well
    That is, we can include a where clause in the SQL for the sample data as

    Where ORG_ID = @{biServer.variables ['NQ_SESSION.]} {[INV_ORG']}

    I would like to know your opinion on this.

    PS: We implement security EBS r12 in BI Publisher.

    Thank you

    Read this-> OBIEE 11 g: error: "[nQSError: 23006] the session variable, NQ_SESSION.» LAN_INT, has no definition of value. "When you create a SQL query using the session NQ_SESSION variable. LAN_INT in BI Publisher [ID 1511676.1]

    Follow the ER - BUG: 13607750 -NEED TO be able TO SET up a SESSION IN OBIEE VARIABLE AND use it IN BI PUBLISHER

    HTH,
    SVS

  • Same link several times variable using dynamic SQL

    Salvation;
    I have a query that uses the variable even several times, is there a way I could just use that variable only once and it will take several times.
    Request is;
    run immediately "SELECT count (*) x WHERE MONTH_ID =: VOMNTH_ID"
    UNION
    SELECT count (*) FROM Y WHERE MONTH_ID =: VOMNTH_ID
    Union
    SELECT count (*) FROM WHERE MONTH_ID = z: VOMNTH_ID ' help months1, month1, months1
    What I don't want only once to provide months1.
    Your help is appreciated.
    PKM
    execute immediate
      'with p as (select :vmonth_id pmon from dual)
    SELECT count(*) FROM x,p WHERE MONTH_ID = p.pmon
    UNION
    SELECT count(*) FROM Y,p WHERE MONTH_ID = p.pmon
    union
    SELECT count(*) FROM z,p WHERE MONTH_ID =p.pmon '
    using month1;
    

    HTH

    Nigel cordially

  • PerfMon statement drive dramatic increase in access to Oracle starting times

    Hello

    My Oracle 10 g (10.2.0.4) server is hosted on a windows 2003 server.
    The data files are stored on a disk RAID1 on a dedicated partition array: currently 30 free concerts on 180, that shouldn't be a concern unless I am mistaken, because the data files have been created in the form of 10 GB of files with no automatic growth. I add a new data file whenever I need more space for my tables (alerts when 80% used).

    Since 2 days I feel a loss of theatrical representation:
    The EM console reports nothing special (no alarm storage-related) outside the need for a more paged memory.
    I have a reorg when segmentation Adviser suggests.
    My the optimizer statistics are calculated by the default scheduled task.

    The strange thing I noticed is that as soon as I start the database, there is a huge disk activity increase even if no request at all is submitted to the database.
    PerfMon reports current length of queue of > 1000 disc and disc > 3000 ms access time

    CPU is 2% of the activity on the 4-CPU server.
    I have a lot of spare memory (currently 3 used on the 16 GB).

    It is a server dev for ETL processes, there is very little simultaneous connections.

    Any suggestion is welcome.

    AWR report is available here
    http://min.us/mqnXQhd5Z

    Published by: user10799939 on March 22, 2012 09:30
    
    Cache Sizes
    ~~~~~~~~~~~                       Begin        End
                                 ---------- ----------
                   Buffer Cache:     1,296M     1,296M  Std Block Size:         8K
               Shared Pool Size:       160M       160M      Log Buffer:    14,364K 
    
    Load Profile
    ~~~~~~~~~~~~                            Per Second       Per Transaction
                                       ---------------       ---------------
                      Redo size:            460,955.72 ;         2,477,358.63
                  Logical reads:              3,392.16 ;            18,230.80
                  Block changes:              6,451.93 ;            34,675.22
                 Physical reads:                  2.92 ;                15.67
                Physical writes:                394.52 ;             2,120.28
                     User calls:                  1.69 ;                 9.08
                         Parses:                  3.31 ;                17.81
                    Hard parses:                  0.17 ;                 0.90
                          Sorts:                  1.32 ;                 7.09
                         Logons:                  0.06 ;                 0.31
                       Executes:                  7.01 ;                37.68
                   Transactions:                  0.19 
    
      % Blocks changed per Read:  190.20 ;   Recursive Call %:    96.23
    Rollback per transaction %:    0.30 ;      Rows per Sort:    14.41 
    
    Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                Buffer Nowait %:   99.98 ;      Redo NoWait %:   99.86
                Buffer  Hit   %:   99.92 ;   In-memory Sort %:  100.00
                Library Hit   %:   96.30 ;       Soft Parse %:   94.96
             Execute to Parse %:   52.74 ;        Latch Hit %:   99.07
    Parse CPU to Parse Elapsd %:    0.35 ;    % Non-Parse CPU:   99.30 
    
    Shared Pool Statistics        Begin    End
                                  ------  ------
                 Memory Usage %:   75.48 ;  75.51
        % SQL with executions>1:   79.92 ;  85.03
      % Memory for SQL w/exec>1:   77.07 ;  70.09 
    
    Top 5 Timed Events                                         Avg %Total
    ~~~~~~~~~~~~~~~~~~                                        wait   Call
    Event                                 Waits    Time (s)   (ms)   Time Wait Class
    ------------------------------ ------------ ----------- ------ ------ ----------
    db file sequential read               9,052      17,688   1954   51.3 ;  User I/O
    log file switch (checkpoint in        5,303       4,649    877   13.5 Configurat
    log file switch completion            4,245       4,023    948   11.7 Configurat
    wait for a undo record               32,393       3,531    109   10.3 ;     Other
    db file parallel write               18,771       3,437    183   10.0 System I/O 
    

    haven't seen as much waiting on average. For example, 877ms for "log file switch" is above the threshold. And other events waiting too...

    
    Time Model Statistics                DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> Total time in database user-calls (DB Time): 34446.5s
    -> Statistics including the word "background" measure background process
       time, and so do not contribute to the DB time statistic
    -> Ordered by % or DB time desc, Statistic name 
    
    Statistic Name                                       Time (s) % of DB Time
    ------------------------------------------ ------------------ ------------
    sql execute elapsed time                              4,008.5 ;        11.6
    parse time elapsed                                      352.9 ;         1.0
    hard parse elapsed time                                 352.7 ;         1.0
    PL/SQL compilation elapsed time                         120.1 ;          .3
    DB CPU                                                   61.8 ;          .2
    failed parse elapsed time                                21.3 ;          .1
    PL/SQL execution elapsed time                             8.0 ;          .0
    connection management call elapsed time                   0.0 ;          .0
    hard parse (sharing criteria) elapsed time                0.0 ;          .0
    repeated bind elapsed time                                0.0 ;          .0
    hard parse (bind mismatch) elapsed time                   0.0 ;          .0
    DB time                                              34,446.5 ;         N/A
    background elapsed time                              14,889.7 ;         N/A
    background cpu time                                      39.0 ;         N/A
              ------------------------------------------------------------- 
    
    Wait Class                            DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> s  - second
    -> cs - centisecond -     100th of a second
    -> ms - millisecond -    1000th of a second
    -> us - microsecond - 1000000th of a second
    -> ordered by wait time desc, waits desc 
    
                                                                      Avg
                                           %Time       Total Wait    wait     Waits
    Wait Class                      Waits  -outs         Time (s)    (ms)      /txn
    -------------------- ---------------- ------ ---------------- ------- ---------
    User I/O                       10,515     .1           17,785    1691      15.8
    Configuration                  10,186   79.5 ;           8,865     870      15.3
    System I/O                     27,619     .0            8,774     318      41.6
    Other                          57,768   98.3 ;           6,915     120      87.0
    Commit                          2,634   88.6 ;           2,481     942       4.0
    Concurrency                     2,847   75.4 ;           2,240     787       4.3
    Application                       219    2.3 ;              23     105       0.3
    Network                         4,790     .0                0       0       7.2
              ------------------------------------------------------------- 
    

    once seen it yet, there is an expectation very strong user IO

    
    Wait Events                          DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> s  - second
    -> cs - centisecond -     100th of a second
    -> ms - millisecond -    1000th of a second
    -> us - microsecond - 1000000th of a second
    -> ordered by wait time desc, waits desc (idle events last) 
    
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    ---------------------------- -------------- ------ ----------- ------- ---------
    db file sequential read               9,052     .0      17,688    1954      13.6
    log file switch (checkpoint           5,303   78.0 ;      4,649     877       8.0
    log file switch completion            4,245   89.2 ;      4,023     948       6.4
    wait for a undo record               32,393   99.8 ;      3,531     109      48.8
    db file parallel write               18,771     .0       3,437     183      28.3
    wait for stopper event to be         24,203   99.8 ;      2,634     109      36.5
    log file sync                         2,634   88.6 ;      2,481     942       4.0
    control file sequential read          7,356     .0       2,431     330      11.1
    buffer busy waits                     2,513   83.1 ;      2,173     865       3.8
    log file parallel write                 520     .0       1,566    3012       0.8
    control file parallel write             840     .0       1,334    1588       1.3
    rdbms ipc reply                         172   91.3 ;        330    1916       0.3
    enq: CF - contention                    309   23.0 ;        268     867       0.5
    log buffer space                        638   28.5 ;        192     301       1.0
    enq: PS - contention                     52   23.1 ;         71    1362       0.1
    db file scattered read                  113     .0          67     590       0.2
    os thread startup                        76   77.6 ;         63     834       0.1
    reliable message                         57   78.9 ;         50     878       0.1
    enq: RO - fast object reuse              22   22.7 ;         23    1038       0.0
    latch free                              537     .0          16      30       0.8
    Streams AQ: qmn coordinator               3  100.0 ;         15    5005       0.0 
    

    Overrides

    
    Background Wait Events               DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> ordered by wait time desc, waits desc (idle events last) 
    
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    ---------------------------- -------------- ------ ----------- ------- ---------
    db file parallel write               18,772     .0       3,437     183      28.3
    events in waitclass Other            24,367   99.5 ;      3,010     124      36.7
    control file sequential read          6,654     .0       2,333     351      10.0
    log file parallel write                 520     .0       1,566    3012       0.8
    control file parallel write             840     .0       1,334    1588       1.3
    buffer busy waits                       899   94.2 ;        884     984       1.4
    log file switch (checkpoint             206   82.0 ;        185     898       0.3
    os thread startup                        76   77.6 ;         63     834       0.1
    log file switch completion               46   93.5 ;         45     982       0.1
    log buffer space                        158   31.0 ;         12      77       0.2
    db file sequential read                  62     .0           7     111       0.1
    db file scattered read                   20     .0           6     318       0.0
    direct path read                        660     .0           5       7       1.0
    log file sequential read                 66     .0           4      65       0.1
    log file single write                    66     .0           1      16       0.1
    enq: RO - fast object reuse               2     .0           0      38       0.0
    latch: cache buffers chains               3     .0           0       6       0.0
    direct path write                       660     .0          -5      -8       1.0
    rdbms ipc message                     9,052   87.5 ;     21,399    2364      13.6
    pmon timer                            1,318   90.4 ;      3,562    2703       2.0
    Streams AQ: qmn coordinator             633   97.6 ;      3,546    5602       1.0
    Streams AQ: waiting for time             77   61.0 ;      3,449   44795       0.1
    PX Deq: Join ACK                         21     .0           0       0       0.0 
    

    Once again exceeded

    
    Tablespace IO Stats                  DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> 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)
    -------------- ------- ------ ------- ------------ -------- ---------- ------
    UNDOTBS1
               914       0 ######     1.0 ;   1,368,515      383      2,534  863.2
    MDMREF_INDICES
             6,918       2 ######     1.0 ;      11,086        3          0    0.0
    SYSAUX
               626       0 ######     1.1 ;       1,804        1          0    0.0
    SYSTEM
               850       0 ######     1.7 ;         296        0          0    0.0
    MDMREF_DATA
               293       0  712.3 ;    1.0 ;         274        0          0    0.0
    MDMPRJ_ODS
               198       0   72.1 ;    1.0 ;         198        0          0    0.0
    FEU_VERT
                33       0   61.5 ;    1.0 ;          33        0          0    0.0
    USERS
                33       0   31.5 ;    1.0 ;          33        0          0    0.0
              ------------------------------------------------------------- 
    

    Now have a serious look. AV Dr (ms). For a value of tablespace cannot event now enter the window that's why its display #.

    According to the recommendation of the oracle Av Rd (ms) should not be greater than 20, if his will on 20 so its considered to be a problem with the IO subsystem. But as its seen in your case its passing.

    Now the question on my side
    Did configuration changes?
    I suggest you undo these changes as soon as possible and to communicate with the storage admin guys...

    Hope this helps

  • Chronological model

    I need help to understand time model statistics and wait events, I understand that statistical model time is divided into two trees, one for the background processing carried out by the database instance itself and one for the foreground treatment (treatment performed on behalf of an application). In the foreground tree are the time for treatment, measurement process that do not expect. My question is:

    All measures in the foreground process tree is a part of the time processor, for example, if I see a DB CPU TIME of 4.4% and an elapsed time of sql in the 90s, I can't assume it's 90% 4.4% and the rest of the DB spend their waiting time?

    I know that the statistics of time DB indicates the duration of treatment accumulated elapsed time of not-idle sessions.

    The image you posted is from book Chris Antognini ALBUMS - do you have a copy? The answer to your question is in the paragraphs following the figures.

    Example:

    • From time to time DB's CPU
    • From time to time DB is SQL execute elapsed time
    • From time to time DB is PL/SQL execution elapsed

    BUT you can simply add the three components together because

    • Some of the DB CPU comes from the SQL execute elapsed time
    • Some of the DB CPU comes the duration of execution of PL/SQL
    • etc.

    In order to do not you talk about 90% or 4.4% - maybe that 4.4 percent is CPU used in the treatment of PL/SQL and a bit of it is used in the SQL - you can't tell of this set of statistics.

    Concerning

    Jonathan Lewis

  • Difference between CPU DB and DB times

    Hello

    What is the difference between CPU DB and DB AWR report?

    BR,
    REDA

    For a session, with a view to the db, a session can be one of three things:

    1 work (i.e. on the CPU or waiting for CPU)

    2. pending a not-idle event

    3 idle

    > 1DB CPU is the CPU time. It means only ACTIVELY work on CPU. Queue TIME is not included.

    Queue time is not included - it is the CPU or waiting to get the CPU (which the db has no knowledge of)

    > In 10 Minute intervals with four CPU, is the Maximum DB CPU 40 Minutes?

    Fix.

    > It says that time DB = includes time CPU + IO time + queue time

    E/s time is measured in queue time - file db scattered reading, sequential reading of file db, etc, etc.

    > Why has separated?

    Don't know. Perhaps to clarify the absoluately then IO is included in DB times

    > Is it possbile to split TIME CPU? As the analysis etc... What display you give him?

    See time model statistics

    > in a given interval, where can I find NO idle timeout in AWR?

    Top 5 + Foreground wait Class + waiting in the foreground events

Maybe you are looking for

  • Write to the file of text formatting issues

    My apologies if I touch on a topic that is discussed elsewhere.  I have two questions, which seems to be related, I'll have to overcome the difficulties.  I date of blood collection, converting it to a temperature and then writes the timestamp, tempe

  • All Progammically DTR, DSR, and RTS to CTS?

    I am trying to contact an extech with Labview power Analyzer.  Recording of data and all thier software cable work.  According to the manual.  I need to bind the RTS to CTS and DTR, DSR. I try to use the Visa controls.  Series of visa, Visa Read and

  • How can I programmatically draw new circles on an image control

    Hi, I'm fairly new LV and programming in general. I'm creating a program to get better. In this program, I have balls bouncing around on an image control. I use a table to keep track of the ball position (x, y) and the other to follow their speed. I

  • Black runs

    XP, fs9 my tracks are black, I do not see the shadow of the planes. Is it possible to recover?

  • How can I update the video card driver

    video card How do I see what I've got the video card. Windows xp pro tried playind a new game and all I get is square and lines where should be the graphixs and letters.