Problemm for quary slow running

Question

hi all,
i do have a problem...i am using oracle database 10g rel 2 enterprise edition on solaris .Some of the quary from sql client runs smooth normally.but today some of then running very slow.i got awr and addm.c The perticular quary that taking lot of time is....
*1>select idtr_broc_code, sum(idtr_val)/10000000 from import_dtr where idtr_rpt_date between '01-APR-10' and '31-DEC-10' and substr(idtr_cty_cons, 3, 3)='187' group by idtr_broc_code order by idtr_broc_code .*
now i am giving the addm report ...
FINDING 1: 56% impact (1052 seconds)
Individual database segments responsible for significant user I/O wait were
found.
RECOMMENDATION 1: Segment Tuning, 31% benefit (582 seconds)
ACTION: Run "Segment Advisor" on TABLE *"FTSSDEV.EXPORT_DTR*" with object
id 53014.
RELEVANT OBJECT: database object with id 53014
ACTION: Investigate application logic involving I/O on TABLE
"FTSSDEV.EXPORT_DTR" with object id 53014.
RELEVANT OBJECT: database object with id 53014
RATIONALE: The I/O usage statistics for the object are: 8 full object
scans, 5198937 physical reads, 11923 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "gsvs1ybcp476p" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID gsvs1ybcp476p
select sum(EDTR_VAL) from export_dtr
where EDTR_SLDT between '01-apr-2009' and '31-mar-2010'
RATIONALE: The SQL statement with SQL_ID "25ankjpssqcj6" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 25ankjpssqcj6
RATIONALE: The SQL statement with SQL_ID "2hfu33hbrdr72" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 2hfu33hbrdr72
RATIONALE: The SQL statement with SQL_ID "71vdzkq9j2j1q" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 71vdzkq9j2j1q
RATIONALE: The SQL statement with SQL_ID "b5ww83x3qf8s8" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID b5ww83x3qf8s8
select edtr_broc_code, sum(edtr_val)/10000000 from export_dtr
where edtr_sldt between '01-APR-10' and '31-DEC-10'
and substr(edtr_cty_code,3,3)='187'
group by edtr_broc_code
order by edtr_broc_code
RECOMMENDATION 2: Segment Tuning, 14% benefit (266 seconds)
ACTION: Run "Segment Advisor" on TABLE "FTSSDEV.IMPORT_DTR" with object
id 53220.
RELEVANT OBJECT: database object with id 53220
ACTION: Investigate application logic involving I/O on TABLE
"FTSSDEV.IMPORT_DTR" with object id 53220.
RELEVANT OBJECT: database object with id 53220
RATIONALE: The I/O usage statistics for the object are: 3 full object
scans, 1389746 physical reads, 119 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "3k7qjrwwqu1gt" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 3k7qjrwwqu1gt
select idtr_broc_code, sum(idtr_val)/10000000 from import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by idtr_broc_code
order by idtr_broc_code
RATIONALE: The SQL statement with SQL_ID "c68ts7wh4nq3q" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID c68ts7wh4nq3q
SELECT COUNT(IDTR_VAL),SUM(IDTR_VAL),COUNT(IDTR_QTY),SUM(IDTR_QTY)
FROM IMPORT_DTR WHERE idtr_amy_msft = :1 and idtr_itchs = :2 and
idtr_cty_cons = :3 order by
idtr_itchs,substr(idtr_cty_cons,3,3),idtr_seq_no
RATIONALE: The SQL statement with SQL_ID "bf1g8zdfr9bu6" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID bf1g8zdfr9bu6
SELECT COUNT(IDTR_VAL),SUM(IDTR_VAL),COUNT(IDTR_QTY),SUM(IDTR_QTY)
FROM IMPORT_DTR WHERE idtr_amy_msft = :1 and idtr_itchs = :2 order
by idtr_itchs,substr(idtr_cty_cons,3,3),idtr_seq_no
RECOMMENDATION 3: Segment Tuning, 8.1% benefit (153 seconds)
ACTION: Run "Segment Advisor" on TABLE "FTSSDEV.EXP_BRC" with object id
53046.
RELEVANT OBJECT: database object with id 53046
ACTION: Investigate application logic involving I/O on TABLE
"FTSSDEV.EXP_BRC" with object id 53046.
RELEVANT OBJECT: database object with id 53046
RATIONALE: The I/O usage statistics for the object are: 38 full object
scans, 1871936 physical reads, 1957 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "71vdzkq9j2j1q" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 71vdzkq9j2j1q
RECOMMENDATION 4: Segment Tuning, 2.7% benefit (51 seconds)
ACTION: Investigate application logic involving I/O on INDEX
"FTSSDEV.IDTR_CTY_CONS_IDX" with object id 56342.
RELEVANT OBJECT: database object with id 56342
RATIONALE: The I/O usage statistics for the object are: 0 full object
scans, 21347 physical reads, 22 physical writes and 0 direct reads.
RATIONALE: The SQL statement with SQL_ID "c68ts7wh4nq3q" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID c68ts7wh4nq3q
SELECT COUNT(IDTR_VAL),SUM(IDTR_VAL),COUNT(IDTR_QTY),SUM(IDTR_QTY)
FROM IMPORT_DTR WHERE idtr_amy_msft = :1 and idtr_itchs = :2 and
idtr_cty_cons = :3 order by
idtr_itchs,substr(idtr_cty_cons,3,3),idtr_seq_no
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(64% impact [1205 seconds])
FINDING 2: 36% impact (681 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 17% benefit (327 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"9749w96kkmuju".
RELEVANT OBJECT: SQL statement with SQL_ID 9749w96kkmuju and
PLAN_HASH 3254866456
UPDATE EXP_BRC SET E_PORT_ORDER = :B4 , E_PRT_DESC = :B3 WHERE
E_PORT_CODE = :B2 AND E_AMY_BRC = :B1
RATIONALE: SQL statement with SQL_ID "9749w96kkmuju" was executed 34
times and had an average elapsed time of 8.5 seconds.
RECOMMENDATION 2: SQL Tuning, 7.4% benefit (139 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cy02xtwqtbw1c".
RELEVANT OBJECT: SQL statement with SQL_ID cy02xtwqtbw1c and
PLAN_HASH 475583467
UPDATE EXPORT_DTR SET EDTR_GROSS_WT = NVL(:1 , EDTR_GROSS_WT )
,EDTR_PORT = NVL(:1 , EDTR_PORT ) ,EDTR_ITCHS = NVL(:1 , EDTR_ITCHS )
,EDTR_CTY_CODE = NVL(:1 , EDTR_CTY_CODE ) ,EDTR_VAL = NVL(:1 ,
EDTR_VAL ) ,EDTR_QTY = NVL(:1 , EDTR_QTY ) ,EDTR_BROC_CODE =
DECODE(:1 , NULL , EDTR_BROC_CODE , '99' ) WHERE EDTR_SEQ_NO =
:1 AND ( ( TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'MM' ) ) =
TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'RRRR' ) )
= TO_NUMBER (:1 ) ) OR ( TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT , 'MM'
) ) = TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT ,
'RRRR' ) ) = TO_NUMBER (:1 ) ) )
RATIONALE: SQL statement with SQL_ID "cy02xtwqtbw1c" was executed 30069
times and had an average elapsed time of 0.0029 seconds.
RECOMMENDATION 3: SQL Tuning, 6.9% benefit (129 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"3k7qjrwwqu1gt".
RELEVANT OBJECT: SQL statement with SQL_ID 3k7qjrwwqu1gt and
PLAN_HASH 728549793
select idtr_broc_code, sum(idtr_val)/10000000 from import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by idtr_broc_code
order by idtr_broc_code
RATIONALE: SQL statement with SQL_ID "3k7qjrwwqu1gt" was executed 2
times and had an average elapsed time of 58 seconds.
RECOMMENDATION 4: SQL Tuning, 6.3% benefit (120 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"gsvs1ybcp476p".
RELEVANT OBJECT: SQL statement with SQL_ID gsvs1ybcp476p and
PLAN_HASH 3481633577
select sum(EDTR_VAL) from export_dtr
where EDTR_SLDT between '01-apr-2009' and '31-mar-2010'
RATIONALE: SQL statement with SQL_ID "gsvs1ybcp476p" was executed 2
times and had an average elapsed time of 52 seconds.
RECOMMENDATION 5: SQL Tuning, 4.7% benefit (88 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7xph3c32acw08".
RELEVANT OBJECT: SQL statement with SQL_ID 7xph3c32acw08 and
PLAN_HASH 2314778580
select substr(idtr_cty_cons,3,3), sum(idtr_val)/10000000 from
import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by substr(idtr_cty_cons,3,3)
RATIONALE: SQL statement with SQL_ID "7xph3c32acw08" was executed 1
times and had an average elapsed time of 79 seconds.
FINDING 3: 30% impact (558 seconds)
The SGA was inadequately sized, causing additional I/O or hard parses.
RECOMMENDATION 1: DB Configuration, 30% benefit (558 seconds)
ACTION: Increase the size of the SGA by setting the parameter
"sga_target" to 2688 M.
ADDITIONAL INFORMATION:
The value of parameter "sga_target" was "1536 M" during the analysis
period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(64% impact [1205 seconds])
FINDING 4: 19% impact (361 seconds)
Individual SQL statements responsible for significant user I/O wait were
found.
RECOMMENDATION 1: SQL Tuning, 7.4% benefit (139 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cy02xtwqtbw1c".
RELEVANT OBJECT: SQL statement with SQL_ID cy02xtwqtbw1c and
PLAN_HASH 475583467
UPDATE EXPORT_DTR SET EDTR_GROSS_WT = NVL(:1 , EDTR_GROSS_WT )
,EDTR_PORT = NVL(:1 , EDTR_PORT ) ,EDTR_ITCHS = NVL(:1 , EDTR_ITCHS )
,EDTR_CTY_CODE = NVL(:1 , EDTR_CTY_CODE ) ,EDTR_VAL = NVL(:1 ,
EDTR_VAL ) ,EDTR_QTY = NVL(:1 , EDTR_QTY ) ,EDTR_BROC_CODE =
DECODE(:1 , NULL , EDTR_BROC_CODE , '99' ) WHERE EDTR_SEQ_NO =
:1 AND ( ( TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'MM' ) ) =
TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'RRRR' ) )
= TO_NUMBER (:1 ) ) OR ( TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT , 'MM'
) ) = TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT ,
'RRRR' ) ) = TO_NUMBER (:1 ) ) )
RATIONALE: SQL statement with SQL_ID "cy02xtwqtbw1c" was executed 30069
times and had an average elapsed time of 0.0029 seconds.
RATIONALE: Average time spent in User I/O wait events per execution was
0.0026 seconds.
RECOMMENDATION 2: SQL Tuning, 6.9% benefit (129 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"3k7qjrwwqu1gt".
RELEVANT OBJECT: SQL statement with SQL_ID 3k7qjrwwqu1gt and
PLAN_HASH 728549793
select idtr_broc_code, sum(idtr_val)/10000000 from import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by idtr_broc_code
order by idtr_broc_code
RATIONALE: SQL statement with SQL_ID "3k7qjrwwqu1gt" was executed 2
times and had an average elapsed time of 58 seconds.
RATIONALE: Average time spent in User I/O wait events per execution was
44 seconds.
RECOMMENDATION 3: SQL Tuning, 6.3% benefit (120 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"gsvs1ybcp476p".
RELEVANT OBJECT: SQL statement with SQL_ID gsvs1ybcp476p and
PLAN_HASH 3481633577
select sum(EDTR_VAL) from export_dtr
where EDTR_SLDT between '01-apr-2009' and '31-mar-2010'
RATIONALE: SQL statement with SQL_ID "gsvs1ybcp476p" was executed 2
times and had an average elapsed time of 52 seconds.
RATIONALE: Average time spent in User I/O wait events per execution was
35 seconds.
RECOMMENDATION 4: SQL Tuning, 4.6% benefit (87 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"2j4wgybgmsq78".
RELEVANT OBJECT: SQL statement with SQL_ID 2j4wgybgmsq78 and
PLAN_HASH 3886674073
select substr(edtr_cty_code,3,3), sum(edtr_val)/10000000 from
export_dtr
where edtr_sldt between '01-APR-10' and '31-DEC-10'
and substr(edtr_cty_code,3,3)='187'
group by substr(edtr_cty_code,3,3)
RATIONALE: SQL statement with SQL_ID "2j4wgybgmsq78" was executed 1
times and had an average elapsed time of 78 seconds.
RATIONALE: Average time spent in User I/O wait events per execution was
61 seconds.
RECOMMENDATION 5: SQL Tuning, 3.3% benefit (62 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"bf1g8zdfr9bu6".
RELEVANT OBJECT: SQL statement with SQL_ID bf1g8zdfr9bu6 and
PLAN_HASH 2952524195
SELECT COUNT(IDTR_VAL),SUM(IDTR_VAL),COUNT(IDTR_QTY),SUM(IDTR_QTY)
FROM IMPORT_DTR WHERE idtr_amy_msft = :1 and idtr_itchs = :2 order
by idtr_itchs,substr(idtr_cty_cons,3,3),idtr_seq_no
RATIONALE: SQL statement with SQL_ID "bf1g8zdfr9bu6" was executed 41
times and had an average elapsed time of 1.5 seconds.
RATIONALE: Average time spent in User I/O wait events per execution was
1.4 seconds.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(64% impact [1205 seconds])
FINDING 5: 9.2% impact (173 seconds)
Cluster multi-block requests were consuming significant database time.
RECOMMENDATION 1: SQL Tuning, 7.8% benefit (146 seconds)
ACTION: Investigate the SQL statement with SQL_ID "71vdzkq9j2j1q" for
possible performance improvements. Look for an alternative plan that
does not use object scans.
RELEVANT OBJECT: SQL statement with SQL_ID 71vdzkq9j2j1q
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Inter-instance messaging was consuming significant database
time on this instance. (11% impact [209 seconds])
SYMPTOM: Wait class "Cluster" was consuming significant database
time. (11% impact [209 seconds])
FINDING 6: 9.2% impact (173 seconds)
Global Cache Service Processes (LMSn) in other instances were not processing
requests fast enough.
RECOMMENDATION 1: DB Configuration, 9.2% benefit (173 seconds)
ACTION: Increase throughput of the Global Cache Service (LMSn)
processes. Increase the number of Global Cache Service processes by
increasing the value of the parameter "gcs_server_processes".
Alternatively, if the host is CPU bound consider increasing the OS
priority of the Global Cache Service processes.
RATIONALE: The value of parameter "gcs_server_processes" was "2" during
the analysis period.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Inter-instance messaging was consuming significant database
time on this instance. (11% impact [209 seconds])
SYMPTOM: Wait class "Cluster" was consuming significant database
time. (11% impact [209 seconds])
FINDING 7: 9% impact (169 seconds)
SQL statements responsible for significant inter-instance messaging were found
RECOMMENDATION 1: SQL Tuning, 17% benefit (327 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"9749w96kkmuju".
RELEVANT OBJECT: SQL statement with SQL_ID 9749w96kkmuju and
PLAN_HASH 3254866456
UPDATE EXP_BRC SET E_PORT_ORDER = :B4 , E_PRT_DESC = :B3 WHERE
E_PORT_CODE = :B2 AND E_AMY_BRC = :B1
RATIONALE: SQL statement with SQL_ID "9749w96kkmuju" was executed 34
times and had an average elapsed time of 8.5 seconds.
RATIONALE: Average time spent in Cluster wait events per execution was
3.2 seconds.
RECOMMENDATION 2: SQL Tuning, 7.4% benefit (139 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"cy02xtwqtbw1c".
RELEVANT OBJECT: SQL statement with SQL_ID cy02xtwqtbw1c and
PLAN_HASH 475583467
UPDATE EXPORT_DTR SET EDTR_GROSS_WT = NVL(:1 , EDTR_GROSS_WT )
,EDTR_PORT = NVL(:1 , EDTR_PORT ) ,EDTR_ITCHS = NVL(:1 , EDTR_ITCHS )
,EDTR_CTY_CODE = NVL(:1 , EDTR_CTY_CODE ) ,EDTR_VAL = NVL(:1 ,
EDTR_VAL ) ,EDTR_QTY = NVL(:1 , EDTR_QTY ) ,EDTR_BROC_CODE =
DECODE(:1 , NULL , EDTR_BROC_CODE , '99' ) WHERE EDTR_SEQ_NO =
:1 AND ( ( TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'MM' ) ) =
TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_BRC , 'RRRR' ) )
= TO_NUMBER (:1 ) ) OR ( TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT , 'MM'
) ) = TO_NUMBER (:1 ) AND TO_NUMBER (TO_CHAR (EDTR_AMY_MSFT ,
'RRRR' ) ) = TO_NUMBER (:1 ) ) )
RATIONALE: SQL statement with SQL_ID "cy02xtwqtbw1c" was executed 30069
times and had an average elapsed time of 0.0029 seconds.
RATIONALE: Average time spent in Cluster wait events per execution was
0.00021 seconds.
RECOMMENDATION 3: SQL Tuning, 6.3% benefit (120 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"gsvs1ybcp476p".
RELEVANT OBJECT: SQL statement with SQL_ID gsvs1ybcp476p and
PLAN_HASH 3481633577
select sum(EDTR_VAL) from export_dtr
where EDTR_SLDT between '01-apr-2009' and '31-mar-2010'
RATIONALE: SQL statement with SQL_ID "gsvs1ybcp476p" was executed 2
times and had an average elapsed time of 52 seconds.
RATIONALE: Average time spent in Cluster wait events per execution was
6.2 seconds.
RECOMMENDATION 4: SQL Tuning, 4.7% benefit (88 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"7xph3c32acw08".
RELEVANT OBJECT: SQL statement with SQL_ID 7xph3c32acw08 and
PLAN_HASH 2314778580
select substr(idtr_cty_cons,3,3), sum(idtr_val)/10000000 from
import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by substr(idtr_cty_cons,3,3)
RATIONALE: SQL statement with SQL_ID "7xph3c32acw08" was executed 1
times and had an average elapsed time of 79 seconds.
RATIONALE: Average time spent in Cluster wait events per execution was
32 seconds.
RECOMMENDATION 5: SQL Tuning, 3.4% benefit (64 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"21b7t3t31uwv7".
RELEVANT OBJECT: SQL statement with SQL_ID 21b7t3t31uwv7 and
PLAN_HASH 747082824
INSERT INTO EXP_GRP_ADD_TEMP(ID, ITC2, ITC4, ITC6, ITC8, GRP) SELECT
ROWID, SUBSTR(EDTR_ITCHS,1,2), SUBSTR(EDTR_ITCHS,1,4),
SUBSTR(EDTR_ITCHS,1,6), EDTR_ITCHS, EDTR_BROC_CODE FROM EXPORT_DTR
WHERE TO_CHAR(EDTR_AMY_BRC,'DD-MM-YYYY') = :B3 AND EDTR_BROC_CODE =
'99' AND EDTR_TOD BETWEEN :B2 AND :B1
RATIONALE: SQL statement with SQL_ID "21b7t3t31uwv7" was executed 1
times and had an average elapsed time of 61 seconds.
RATIONALE: Average time spent in Cluster wait events per execution was 8
seconds.
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Cluster" was consuming significant database time.
(11% impact [209 seconds])
FINDING 8: 2.4% impact (45 seconds)
Wait event "Streams AQ: qmn coordinator waiting for slave to start" in wait
class "Other" was consuming significant database time.
RECOMMENDATION 1: Application Analysis, 2.4% benefit (45 seconds)
ACTION: Investigate the cause for high "Streams AQ: qmn coordinator
waiting for slave to start" waits. Refer to Oracle's "Database
Reference" for the description of this wait event.
RECOMMENDATION 2: Application Analysis, 2.4% benefit (45 seconds)
ACTION: Investigate the cause for high "Streams AQ: qmn coordinator
waiting for slave to start" waits in Service "SYS$BACKGROUND".
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "Other" was consuming significant database time.
(4.8% impact [90 seconds])
FINDING 9: 2.1% impact (40 seconds)
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
RECOMMENDATION 1: SQL Tuning, 6.9% benefit (129 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"3k7qjrwwqu1gt".
RELEVANT OBJECT: SQL statement with SQL_ID 3k7qjrwwqu1gt and
PLAN_HASH 728549793
select idtr_broc_code, sum(idtr_val)/10000000 from import_dtr
where idtr_rpt_date between '01-APR-10' and '31-DEC-10'
and substr(idtr_cty_cons,3,3)='187'
group by idtr_broc_code
order by idtr_broc_code
RATIONALE: SQL statement with SQL_ID "3k7qjrwwqu1gt" was executed 2
times and had an average elapsed time of 58 seconds.
RATIONALE: Average CPU used per execution was 19 seconds.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ADDITIONAL INFORMATION
Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.
The analysis of I/O performance is based on the default assumption that the
average read time for one database block is 10000 micro-seconds.
An explanation of the terminology used in this report is available when you
run the report with the 'ALL' level of detail.
Now its showing that ..the particular quary..need segment tuning.But how should i approach to tune this problem.

Answer 1

Apparently if you're able to run ADDM, you must have something like Grid Control.
On the main page of each database, there is a link called "Segment Advisor".
Behind this link there is a page, with all segment recommendation of that perticular database.
Also check if the table has correct indexes, statistics, etc..etc..
HTH
FJFranken