| FULL status of rollback segment 18 set. [message #161484] |
Sun, 05 March 2006 06:22  |
lanawee
Messages: 2
Registered: March 2006
|
Junior Member |
|
|
Hi,
We have a problem with our UAT instance. The db alert log shows :
Sun Mar 5 13:20:15 2006
Restarting dead background process QMN0
QMN0 started with pid=90
Sun Mar 5 14:10:53 2006
>>> WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! pid=88
Sun Mar 5 16:55:53 2006
Failure to extend rollback segment 18 because of 28 condition
FULL status of rollback segment 18 set.
Pls help; where should I start from? Now I cannot connect to the database if using apps user. Been searching metalink but not very sure what to do.
Thank you very much in advance.
Lana
|
|
|
|
|
|
| Re: FULL status of rollback segment 18 set. [message #161552 is a reply to message #161534] |
Mon, 06 March 2006 00:41  |
girish.rohini
Messages: 744
Registered: April 2005
Location: Delhi (India)
|
Senior Member |
|
|
This may help:
[Refer Metalink Doc ""Failure to Extend RBS" in the Alert Log with Automatic Undo Management" Note:247184.1 For detail]
RBS is in FULL status and it is not able to extend.
While it is marked FULL, no new transactions will use the rollback segment.
When the last transaction in the rollback segment commits, the FULL status is
cleared. Altering the rollback segment ONLINE or OFFLINE will also clear the
FULL flag, even if not all transactions have committed yet.
And Yes as Tarun said, mentioning the Oracle Version always helps.
--Girish
|
|
|
|
| Re: FULL status of rollback segment 18 set. [message #161653 is a reply to message #161484] |
Mon, 06 March 2006 08:33 |
lanawee
Messages: 2
Registered: March 2006
|
Junior Member |
|
|
sorry, Oracle version is 9.2.0.2, HP-Unix.
Later on it was discovered that there was also a hard disk failure which affect this instance, so have to wipe it out. I am cloning the instance from another instance.
But still, I will be interested how to overcome this error.
regards
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
