Re: AWR Sample Report

From: raja <dextersunil_at_gmail.com>
Date: Tue, 25 Nov 2008 05:03:44 -0800 (PST)
Message-ID: <1046232a-6815-4745-be1b-46c1f70b0866@z27g2000prd.googlegroups.com>

Hi,

I have also another information which would help to solve the problem along with the AWR Report.
From the advisor tables, i got the following information ( these were the findings made by oracle ) :

Application Analysis :

---

Wait event "Backup: sbtwrite2" in wait class "Administrative"
Wait event "Data file init write" in wait class "User I/O"
Wait event "enq: CF - contention" in wait class "Other"
Wait event "enq: JI - contention" in wait class "Other"
Wait event "enq: TC - contention" in wait class "Other"
Wait event "inactive session" in wait class "Other"
Wait event "SQL*Net more data from dblink" in wait class "Network"
Wait event "wait for a undo record" in wait class "Other"

Waits on event "log file sync" while performing COMMIT and ROLLBACK operations

I will check over the above wait events also and get back to you.

Waits on event "log file sync" while performing COMMIT and ROLLBACK operations - i think we should not use more commits in the application, to solve this problem.

I hope most of the above mentioned wait events were due to the Backup activity that has been taken place ( This was also present in the AWR Report).
I have consolidated the above wait events ( data was taken for 2 months )
So the problem with the database should be mostly with the backup activity only.
Correct ?

With Regards,
Raja. Received on Tue Nov 25 2008 - 07:03:44 CST