| undo fundamentals [message #172226] |
Mon, 15 May 2006 10:30  |
rkl1
Messages: 97
Registered: June 2005
|
Member |
|
|
Dear All: Here is something troubling me. For example, I have an undo Tablespace which is only 200M. Consider this is a new undo Tablespace which I made default for this experiment. Now I update a table and undo Tablespace (TS) grows up to 175M. After update complete, I commit it. The undo TS still shows that 175M storage. Now I run the same update statement and undo TS jumps to its maximum 200M but the update transaction completed. This means Oracle just write over what is in the undo TS and nothing wrong about it. Now when I query the undo TS and it shows that all 200M being taken. Does Oracle lives by putting a high water mark on undo TS like the Temp TS. Is there a way to shrink it.
thanks.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
