What happens when UNDO space is full? Transaction takes more time to ERROR? [message #490677] |
Wed, 26 January 2011 11:13 |
sriramkanala
Messages: 9 Registered: December 2005
|
Junior Member |
|
|
I have a long running transaction (more than 3 hours), and at the same time other operations are occurring on different tables, using the same UNDO space.
Sometimes we see ORA-30036, but this error occurs very late in the process.
The transaction normally takes 3 hours, but when UNDO space is full, we do not get ORA-30036 upto 8 hours or 9 hours of process.
I am wondering what could be happening in the background, when UNDO space is full, whcih makes the transaction to extend upto 8 hours or 9 hours (pl. note, this transaction gets completed within 3 hours normally).
This is in 11g, UNDO space is managed manually.
Any clues? Thanks in advance
|
|
|
|
|
|
Re: What happens when UNDO space is full? Transaction takes more time to ERROR? [message #490760 is a reply to message #490677] |
Thu, 27 January 2011 03:50 |
hkchital
Messages: 128 Registered: September 2008 Location: Singapore
|
Senior Member |
|
|
The error message is returned to the client *after* the rollback has been completed.
A transaction starts at 1pm.
At 3pm it encounters an "out of space".
(Assuming that resumable has not been configured)
It starts rolling back.
The rollback completes at 3:45pm.
The user/client sees an error message at 3:45pm.
You can monitor USED_UREC, USED_UBLK for your transaction and see it increasing between 1pm and 3pm. After 3pm, the count starts falling -- this means that the rollback has begun. The error is presented to the user/client only after the rollback has been completed -- the database has been returned to a consistent state.
Hemant K Chitale
|
|
|
|
|
|
|