Re: Emergency Situation with Rollback Restore

From: Jeremiah Wilton <jeremiah_at_wolfenet.com>
Date: Tue, 10 Nov 1998 22:06:10 -0800
Message-ID: <Pine.OSF.3.95.981110214530.32539B-100000@gonzo.wolfenet.com>

On 6 Nov 1998, Jeroen van Sluisdam wrote:
>
> You should try the following:
>
> startup nomount
> drop rollback tablespace
> go to the os, delete rollback files
> startup nomount again
> create the new ones
>
> matthew_at_mattshouse.com wrote:
>
> > It was not backed up in Archive Log mode. What can I do?

The problem with just dropping the tablespace in this case is that it is a tablespace containing active rollback segments. When the database attempts to open, it tries to roll back any transactions that were uncommitted at the point in time that the database crashed or the point in time to which it was recovered. So, it probably isn't a good idea to drop the rollbacks tablespace.

There is a _CORRUPTED_ROLLBACK_SEGMENTS parameter that allows you to mark certain rollback segments as corrupt on startup. However, you have uncommitted blocks in your datafiles that need to be rolled back, and there is a high probability that even marking all rollback segments as corrupt will not result in an openable database.

--
Jeremiah Wilton http://www.wolfenet.com/~jeremiah Received on Wed Nov 11 1998 - 00:06:10 CST