Segment Tuning --- TablePartition [message #328784] |
Sun, 22 June 2008 15:45 |
visva4u3
Messages: 1 Registered: June 2008
|
Junior Member |
|
|
Hi,
There is an insert query running on the server, which is running from long ( more than 5 hours).
I ran the addm report
According to that there are recommendations to run sql tuning on the sql --- I ran sqltrpt.sql and as per the recommendations created indexes.
There is one more recommendation in the addm report,
Segment Tuning,
This is the recommendation from addm report.
FINDING 5: 37% impact (6257 seconds)
------------------------------------
Individual database segments responsible for significant user I/O wait were
found.
RECOMMENDATION 1: Segment Tuning, 18% benefit (3139 seconds)
ACTION: Investigate application logic involving I/O on TABLE PARTITION
"AP.AP_LIABILITY_BALANCE.SYS_P207" with object id 192903.
RELEVANT OBJECT: database object with id 192903
RATIONALE: The I/O usage statistics for the object are: 177 full object
scans, 338429 physical reads, 0 physical writes and 338177 direct
reads.
RATIONALE: The SQL statement with SQL_ID "gf8z8j899wabt" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID gf8z8j899wabt
Now I want to know, how to run this Segment tuning on TABLE PARTITION ---- AP_LIABILITY_BALANCE.
I would be thankful, if some one help me out in running segment tuning.It would be great if you give me the detailed steps.
Thanks
visva
|
|
|
|
Re: Segment Tuning --- TablePartition [message #330282 is a reply to message #328784] |
Sat, 28 June 2008 15:19 |
Kriptas
Messages: 118 Registered: June 2008
|
Senior Member |
|
|
your table have partitions?
your table have indexes?
it is insert too long, or select too long?
5 hours it is lots of time, on a good server you must working with tables containing 100 000 000 000 rows... ?
maybe there is some problems in select?
|
|
|