Metrics "Database Time Spent Waiting (%)" is at 0 for event class

I am getting following warnings ,may anyone expalin it to me
Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Configuration"
Metrics "Database Time Spent Waiting (%)" is at .40757 for event class "Network"
Metrics "Database Time Spent Waiting (%)" is at .40757 for event class "Cluster"

You should have a look into Database Performance Guide.
This metrics shows how much time your database is spending on waiting for wait events of folowing classes
Best Regards
Krystian Zieja / mob

Similar Messages

  • Metrics "Database Time Spent Waiting (%) is ar 100 for event class "Applica

    Metrics "Database Time Spent Waiting (%) is ar 100 for event class "Application".
    i get this error in database. help me regarding this error.

    Streams AQ: qmn coordinator idle wait     31     16     42598     1374.12     425976281     989870553     2723168908     6     Idle
    Streams AQ: qmn slave idle wait     15     0     41599     2773.27     415990747     1830121438     2723168908     6     Idle
    Streams AQ: waiting for messages in the queue     83     83     41478     499.73     414776290     3955192389     2723168908     6     Idle
    jobq slave wait     134     131     39906     297.8     399055017     782339817     2723168908     6     Idle
    Streams AQ: waiting for time management or cleanup tasks     7     4     3778     539.71     37779540     3702640206     2723168908     6     Idle
    class slave wait     3     3     1499     499.54     14986144     1055154682     2723168908     6     Idle
    Streams AQ: qmn coordinator waiting for slave to start     2     1     500     249.95     4999066     1565566389     1893977003     0     Other
    LGWR wait for redo copy     1     0     0     0     1     4266849434     1893977003     0     Other

  • Metrics "Database Time Spent Waiting (%)" is at ... for event class "Commit

    Hi guys
    I'm getting this warning every 20 minutes from Enterprise Manager 10g: Metrics "Database Time Spent Waiting (%)" is at 67.62891 for event class "Commit". My database is an Oracle 10g 10.2.0.4 (Linux x84_64) with dataguard, one physical and one standby networked at 100Mbit. I have 3 groups of 50M redo log with a low volume of transaction for now. Here are some metrics numbers:
    SQL> select sum(seconds_in_wait),event from v$session_wait group by event;
    SUM(SECONDS_IN_WAIT) EVENT
    121210 SQL*Net message from client
    0 Streams AQ: waiting for messages in the queue
    18 wait for unread message on broadcast channel
    6 LNS ASYNC end of log
    30 jobq slave wait
    37571 rdbms ipc message
    384 smon timer
    35090 pmon timer
    I tune the my listerners for Dataguard using the documentation. I don't know what to tune anymore, is someone has a clue.
    Thanks,
    Chris

    cprieur wrote:
    Metrics "Database Time Spent Waiting (%)" is at 67.62891 for event class "Commit"
    I'am also getting this message at a regular time:
    Metrics "Database Time Spent Waiting (%)" is at 64.09801 for event class "Network"
    The report, I was sent only to indicate the time spent on: SQL*Net message from client
    I believe that these metrics are explained here (near the bottom of the page):
    http://download.oracle.com/docs/cd/B19306_01/em.102/b25986/oracle_database.htm
    There are only two wait events in the Commit class (on 11.1.0.7):
    log file sync
    enq: BB - 2PC across RAC instances
    log file sync waits happen when sessions issue a COMMIT or ROLLBACK. Sessions will wait on this event until LGWR completes its writes to the redo logs (LGWR will likely wait on the event log file parallel wriite while waiting for the write to complete). I believe that your DataGuard configuration may contribute to the long waits experienced by LGWR, and it may be made worse by the network connection.
    http://download.oracle.com/docs/cd/B28359_01/server.111/b28294.pdf
    "Maximum availability - This protection mode provides the highest level of data protection that is possible without compromising the availability of a primary database. Transactions do not commit until all redo data needed to recover those transactions has been written to the online redo log and to at least one standby database."
    So, if Maximum availability is configured, the sessions will have to wait for the redo to be applied to the remote database.
    At the system-wide level you will almost always be able to ignore the SQL*Net message from client wait events. At the session level this wait event has a more significant meaning - the client computer is not actively waiting on a response from the database instance - the client is either sitting idle, or performing client-side processing.
    Sybrand, if he joins this thread, will likely be able to provide a more complete answer regarding DataGuard's contribution to the Commit wait class.
    Charles Hooper
    IT Manager/Oracle DBA
    K&M Machine-Fabricating, Inc.

  • Waiting (%)     Metrics "Database Time Spent Waiting (%)" is at 69.64818 for event class "Commit"

    Hi,
    Can any one help me on this warning, i got this warning on ORACLE ENTERPRISE MANAGER
    Waits by Wait Class
    Database Time Spent Waiting (%)
    Metrics "Database Time Spent Waiting (%)" is at 69.64818 for event class "Commit"
    Below are our environment details:
    RDBMS: 10.2.0.4
    Oracle E-Business suite: 12.0.6
    OS: Oracle Sun 10
    Please suggest.
    Thank you.

    Please see the following docs.
    How to Disable Alerts for The Database Time Spent Waiting (%) Metric? (Doc ID 1500074.1)
    "Database Time Spent Waiting (%)" at 100 for Event Class "Other" when Database is not Under Load (Doc ID 1526552.1)
    Thanks,
    Hussein

  • Metrics "Database Time Spent Waiting (%)" is at 23,02268 for event class "C

    Hi,
    on 10g,
    I have this alerte in DB control home page :
    Metrics "Database Time Spent Waiting (%)" is at 23,02268 for event class "Commit"
    Should I do any action/correction ?
    Thank you.

    user522961 wrote:
    Thank you.
    Here is the result :
    SQL> select sid, event, p1, p2, p3 from v$session_wait where event not in ('SQL*Net message from client', 'rdbms ipc message', 'pipe get', 'PL/SQL lock timer',
    'pmon timer');
    SID EVENT                                                                    P1         P2      P3
    163 jobq slave wait                                                           0          0       0
    165 Streams AQ: waiting for messages in the queue                          8808  875118900       5
    166 SQL*Net message to client                                        1413697536          1       0
    167 wait for unread message on broadcast channel                      865275080  865241852       0
    169 Streams AQ: qmn slave idle wait                                           0          0       0
    170 Streams AQ: waiting for time management or cleanup tasks                  0          0       0
    179 Streams AQ: qmn coordinator idle wait                                     0          0       0
    194 smon timer                                                              300          0       0
    8 rows selected.Regards.As per above result, it seems there was no critical wait event or something occurs during frequent commits.
    If you know which application or batch processing caused this, for the best result, you should rerun this query during that workload.

  • Metrics "Database Time Spent Waiting (%)" is at 83.25965 for event class

    Hello,
    when i log into em console, i have alert below,
    "Metrics "Database Time Spent Waiting (%)" is at 83.25965 for event class "Commit"
    so, what do i need to do? i have no idea about this,
    is it a critical error? is there any solution?
    thank you
    Ugur

    Ugur MIHCI wrote:
    Hello,
    when i log into em console, i have alert below,
    "Metrics "Database Time Spent Waiting (%)" is at 83.25965 for event class "Commit"
    so, what do i need to do? i have no idea about this,
    is it a critical error? is there any solution?
    thank you
    UgurProbably what you would want to do in this case is to first determine which wait events are in that event class:
    {code}
    SELECT
    NAME
    FROM
    V$EVENT_NAME
    WHERE
    WAIT_CLASS='Commit';
    NAME
    log file sync
    enq: BB - 2PC across RAC instances
    {code}
    If you are not using RAC, the second of the above wait events probably does not apply. Next, you need to determine what the "log file sync" wait means, so you might do a Google search of the Oracle documentation. Assume that you are using Oracle Database 10.2.0.x - you would then search for:
    {code}
    site:download.oracle.com "log file sync" 102
    {code}
    In my search, the first link was a page from the Oracle Database Performance Tuning Guide:
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/instance_tune.htm
    That page contained the following quote:
    "log file sync
    General area: I/O, over- committing
    Possible cause: Slow disks that store the online logs, Un-batched commits
    Look for: Check the disks that house the online redo logs for resource contention. Check the number of transactions (commits + rollbacks) each second, from V$SYSSTAT."
    Excessive waits for log file sync may also be caused by lack of available CPU time - an overloaded CPU.
    Charles Hooper
    Co-author of "Expert Oracle Practices: Oracle Database Administration from the Oak Table"
    http://hoopercharles.wordpress.com/
    IT Manager/Oracle DBA
    K&M Machine-Fabricating, Inc.

  • "Database Time Spent Waiting (%)" alerts

    Hi all,
    I have noticed the following alert trace pattern, occurring at the top of every hour :
    Metrics "Database Time Spent Waiting (%)" is at 0 for event class "Other"
    Metrics "Database Time Spent Waiting (%)" is at 100 for event class "Other"
    I have also noticed somewhat of a performance hit client-side, but what I would really like to know is what exactly do these alert levels, and occurring at this 0-100 pattern, mean ?
    Thanks in advance.

    I think you should focus on monitoring of Target Availability
    Take a look at http://oemgc.wordpress.com/2007/07/11/configuration-of-metrics-in-oracle-enterprise-manager/
    which is a post on my Blog. Here I have a description of how you could do this.
    The Bog contains several other postings on this subject
    Regards
    Rob

  • Database Time Spent Waiting (%)

    In My RAC 11.2.0.2.2, I have the following warnings in the dba_outstanding_alerts,
    How to clean them? I don't have Diagnostic Pack licensed for this environment; it's a test environment; I just have a basic license
    REASON
    METRIC_VALUE MESSAGE_TYPE TO_CHAR(CREATION_TIME,'DD-MON
    HOST_ID
    Metrics "Database Time Spent Waiting (%)" is at 34.11247 for event class "Concurrency"
      34.1124716 Warning      15-JUL-2011 17:49:32
    db03
    Metrics "Database Time Spent Waiting (%)" is at 76.9712 for event class "Other"
      76.9712048 Warning      15-JUL-2011 17:53:00
    db02

    Please read How To Clear An Alert http://blogs.oracle.com/oem/entry/how_to_clear_an_alert.

  • Database Time Spent waiting issue

    Hi;
    I got this message in OEM:
    Metrics "Database Time Spent Waiting (%)" is at 62.00034 for event class "Other", under category Waits by Wait Class.
    When I hit over the message and then go to Additional Advice, under Impact(%) I got the message:
    ADDM did not find any problems during this period
    And under Informational Findings the message is:
    There was no significant database activity to run the ADDM.
    I am seeing this message in the last 3 days, however, apparently there's not problem. But the message still is there. My doubt is, is this a problem to watch? How can I delete this message?
    thanks for your advice
    Regards
    Al

    "SQL*Net message from client" event wait time is accumulated while your clients are idling (doing nothing but keeping the connection open.) If you have no apparent performance issues, this event can be safely ignored.
    Regards,
    Vladimir M. Zakharychev

  • Database Time Spent Waiting (%) for Concurrency

    Oracle 11g 11.1.0.6 Standard Edition
    Windows 2003 Server SP2
    I have recently begun building a development database. Enterprise Manager has popped up the following message Metrics "Database Time Spent Waiting (%)" is at 85.20092 for event class "Concurrency" but it won't show me any further info as I don't have access to the Database Diagnostic Pack.
    Is there any other way to investigate this metric alert?

    Oracle 11g 11.1.0.6 Standard Edition
    Windows 2003 Server SP2
    I have recently begun building a development
    database. Enterprise Manager has popped up the
    following message Metrics "Database Time Spent
    Waiting (%)" is at 85.20092 for event class
    "Concurrency" but it won't show me any further
    info as I don't have access to the Database
    Diagnostic Pack.
    Is there any other way to investigate this metric
    alert?You might start by looking at the wait events at the system level. Monitor the changes in the wait events at the system level when response time is poor. Keep the time delta between the start and end captures short, possibly 5 to 15 minutes. Start by executing a SQL statement such as this (possibly capture the output in a file or an application such as Excel):
    SELECT
    FROM
      V$SYSTEM_EVENT;You may notice that there is a column named WAIT_CLASS returned by the above query, so you might use that column to restrict the rows returned by the query.
    Wait 5-15 minutes, and then repeat the query. Subtract the values from the first execution for TOTAL_WAITS, TOTAL_TIMEOUTS, and TIME_WAITED from the second execution for the same wait events. Check the Oracle Performance Tuning manual for the meaning of the wait events, and how to address problems that are found.
    Charles Hooper
    IT Manager/Oracle DBA
    K&M Machine-Fabricating, Inc.

  • Database Time Spent Waiting (%) for event Commit

    I have a 10G R2 database that has started to report this alert every minute.
    Metrics "Database Time Spent Waiting (%)" is at 61.25661 for event class "Commit"
    I have not changed any metric configuration and the really weird thing to me is that the database is completely idle. I am having difficulty finding good documentation on the Metrics and alerts. I read something that seemed related and it said the commit class has only one alert and that is for redo log write confirmation. There are no users other than myself connected to this database and I am just monitoring with the EM. Any ideas?
    -Tim

    Update...
    The IBM rep said he could send someone over for $1500 day. Right. So I read over the DS4300 manuals again but nothing really stood out. However I thought it would be worth noting that when the write cache was turned 'off' for the logical with the redo logs the 'log file sync' wait event would stay below the warning threshold (50%) and average about 18%. With the write cache 'on' the wait event would always be above the warning threshold. Performance of the database overall is still degraded with either setting. I am going into production with the redo on a local mirror. Additionally I tested segment sizes of 64 ,32, and 16kb. The 16kb did not effect the 'log file sync' waits but proves to be excellent for transaction performance overall.
    -Tim

  • Explanation Database Time Spent Waiting (%)

    Dear DBA's
    i would like to ask the meaning for this statements
    *(Metrics "Database Time Spent Waiting (%)" is at 61.01392 for event class "Commit")*
    *(Metrics "Database Time Spent Waiting (%)" is at 99.48281 for event class "Network")*
    *(Metrics "Database Time Spent Waiting (%)" is at 48.36914 for event class "Other")*
    i often get this error on my OEM alerts
    could some one say me why this wait is happening and what should i do to resolve this time wait.
    Thanks and regards
    Raja...
    Edited by: [email protected] on Apr 6, 2010 5:59 AM

    Hi,
    These are database waits for different reasons. Network waits could be due to excessive waits on due to slow network. Other waits can be for different reasons. Majority of the waits falling in the other catagory are idle waits.
    Run AWR report on your database to find specific issues.
    HTH

  • Database Time Spent Waiting (%): Wait Class Other nearly 100% all the time

    Don't understand why OEM is reporting that Database Time Spent Waiting (%): Wait Class Other is nearly 100% all the time. Database 10.1.0.4 just installed on Linux(RHEL4AS) and nobody use it for now except OEM and me for admin purpose.
    Any clue for that problem ?
    Regards
    Nicolas

    Seems like you are not the first to see this kind of behaviour.
    I've found another similar thread on metalink. I can't say the answer is terribly helpful, but thought you might be interested anyway:
    From: Jose Ramón Tourón 14-Sep-07 08:34
    Subject: Database Time Spent Waiting (%) at 100 in event class Commit
    RDBMS Version: Oracle 10g r2
    Operating System and Version: Suse Enterprise Linux 10
    Error Number (if applicable):
    Product (i.e. SQL*Loader, Import, etc.): database core
    Product Version: 10gR2
    Database Time Spent Waiting (%) at 100 in event class Commit
    Hi everyone, yesterday we create a new database instance with dbca, the creation process was ok, and the two instances are running ok, database stops and starts without any problem, and listeners are ok. In the enterprise manager of this new instance we found this message:
    Database Time Spent Waiting (%) at 100 in event class Commit, this event happend every 1 or 2 minutes sometimes at 100, the next 40%, the next 98, ... and so on.
    Do you know what's happend in this instance?
    Thanks in advance to everyone
    Santiago Pérez
    From: Oracle, Helmut Pfau 14-Sep-07 12:52
    Subject: Re : Database Time Spent Waiting (%) at 100 in event class Commit
    From Oracle Database Reference Manual:
    Commit
    This wait class only comprises one wait event - wait for redo log write confirmation after a commit (that is, 'log file sync')
    So you can't write fast enough into your log files.
    Did you check the frequency of log switches?
    From: Metalink TCS User Group TCS Uruguay 14-Sep-07 15:52
    Subject: Re : Database Time Spent Waiting (%) at 100 in event class Commit
    Hi José! Please don't get anxious because of this: Wait time must be SOMEWHERE, there's a saying "An OLTP DB is only as fast as its redo logs", but if you are not having any performance problem you don't need to do anything special.
    You say you've just created the DB. Now make it DO something: put it to the test by simulating production conditions as closely as you can, and after some hours ask the users whether there is some problem. If there is, take a look at the wait statistics... you'll probably see many other top events before this one!
    Bruno abate_at_adinet.com.uy

  • How to get the total time spent by a Portal User for a given Date?

    Hello,
    We need to develop a Daily Audit Track Report that displays
    the Users logged into our System for a given day and the total login duration in Hours( should include all the
    Login-Logouts of a given date).
    While Portal30_SSO.WWSSO_AUDIT_LOG_TABLE$ can help me get the Users login to Portal for a day, there is no Login/Logout periods in it.
    Any help would be appreciated.
    Thanks
    Madhav

    You may want to consult with the view WWLOG_ACTIVITY_LOGS. Not sure how your environment is configured, but ours includes two WWLOG_ACTIVITY_LOG tables (1 & 2). These tables purge themselves based on your configuration. In other words, Portal will log activity in WWLOG_ACTIVITY_LOG1$ for a certain period of time, then switch to WWLOG_ACTIVITY_LOG2$ while purging the first one. You can specify the purge timetable in the Adminster tab of the Admin page (under Global Settings). If you just key on just 1 log table, you're logs may someday go blank.
    The actions used are 'login' and 'logout'. You can link the actions using the key_1 and key_2 columns of the view. From our current experience, Portal does not account for users that simply close the browser. In other words, we have not been able to get a log event for the action 'logout' for the same key_2 value if someone does this.

  • How to Tune EM Metric Alert "Average Users Waiting Count"?

    We have been getting below EM alert frequently , How can tune/fix this issue?
    Metric=Average Users Waiting Count
    Wait Class=Concurrency
    Severity=Warning
    Message=Metrics "Average Users Waiting Counts" is at 84.66522 for event class "Concurrency"

    Have a look at this to understand the Metrics first.
    Average Users Waiting Count
    <br>
    Oracle Database FAQs
    </br>

Maybe you are looking for