 Poor Insert Performance after table truncation was interupted [message #284681] |
Fri, 30 November 2007 09:33  |
williamhwh
Messages: 1
Registered: November 2007
Location: Kuala Lumpur
|
Junior Member |
|
|
We have a OLAP database and loading activities is performed by operator. Unfortunately, she mistakenly truncate the wrong table but halfway, she cancel the job. Now, the monthly loading activity has degrades/hang until 1 row(or none) per second.
It is a 17GB table and one of the partition is holding up 14GB (64MB extents). All our tablespace is using ASSM. The problem is we do not know what causes the slow insert.
1) Could it be fragmentation? How can check for tablespace fragmentation?
2) I have searched some bugs from Metalink but the bugs seems doesn't apply to my case where I did not get any ORA-600 error.
Bug 3279497 - Interupted (Ctrl-C) TRUNCATE can corrupt ASSM table
Bug 3610777 - Excessive CPU from INDEX insert into ASSM index segment
3) Is there any possible buffer chain latches issue? How can I verify it?
Any suggestion/advice will be helpful. Thanks a lot!
William Ha
|
|
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
