Issue:
The database is not able to release UNDO space.
Findings:
a) Undo tablespace always shows 100% utilization
b) There is No error in the alert log
c) We have queried the v$undostat and we found the value of tuned_undo_retention is quite bigger than the undo_retention which is 54000
Solution:
Set "_smu_debug_mode= 33554432" in database
It should allow the expired segments to be released and re-used and you should see a drop in the number of unexpired segments.
There is no negative impact of using this parameter. Its the fixed value to specify its mode.
This mode helps auto tune of undo to work effectively and specially in such cases where max_query_length < tuned_undoretention, it helps alot.
The database is not able to release UNDO space.
Findings:
a) Undo tablespace always shows 100% utilization
b) There is No error in the alert log
c) We have queried the v$undostat and we found the value of tuned_undo_retention is quite bigger than the undo_retention which is 54000
Solution:
Set "_smu_debug_mode= 33554432" in database
It should allow the expired segments to be released and re-used and you should see a drop in the number of unexpired segments.
There is no negative impact of using this parameter. Its the fixed value to specify its mode.
This mode helps auto tune of undo to work effectively and specially in such cases where max_query_length < tuned_undoretention, it helps alot.
No comments:
Post a Comment