Home » RDBMS Server » Performance Tuning » ADDM Findings from OEM (10g Rel 2)
| ADDM Findings from OEM [message #308150] |
Fri, 21 March 2008 10:52 |
azeem87
Messages: 116
Registered: September 2005
Location: dallas
|
Senior Member |
|
|
Hi,
These are the few recommendation from OEM when i see ADDM finidings Report.
| Quote: |
A hot data block with concurrent read and write activity was found. The block belongs to segment "** UNAVAILABLE **.** UNAVAILABLE **" and is block 2343385 in file 51.
and this was the SQL statement it showed against that recommendation ,
Action :- Investigate application logic to find the cause of high concurrent read and write activity to the data present in this block.
Rationale The SQL statement with SQL_ID "3s0j88r1hxc6t" spent significant time on "buffer busy" waits for the hot block.
SQL Text> INSERT INTO TRNS_XN ( TRNS_ID, PROC_TIME_DT, TRNS_SEQ_NB, BAT_ID, GP_NB, LAST_UPDT_TS,... VALUES ( TRNS_SEQ.NEXTVAL, :B28 , :B27 , :B26 , :B25 , SYSDATE, :B24 , :B23 , :B22 , :B21 , :B20 , :B19 , :B18 , :B17 , UPPER(TRIM(:B16 )),
UPPER(TRIM(:B15 )), :B14 , :B13 , :B12 , :B11 , :B10 , :B9 , TRIM(:B8 ), :B7 , TRIM(:B6 ), NVL(:B5 ,0), :B4 , NVL(:B3 ,1), :B2 , :B1 ) RETURNING TRNS_ID INTO :O0 )
|
And Second Finding is this
| Quote: |
Wait event "ARCH wait on SENDREQ" in wait class "Network" was consuming significant database time.
|
It's an OLTP application.
Where exactly i could see more information on this , and what's the area where tuning can be done for this findings.
Thanks
[Updated on: Fri, 21 March 2008 11:24] Report message to a moderator |
|
|
|
Goto Forum:
Current Time: Fri Jun 28 10:19:19 CDT 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
