Message-ID: <E0CEF5CFE1A2D21184160090271E025604F75620@DALEXCH01> From: "Hollis, Les" <Les.Hollis@ps.net> Date: Wed, 31 Oct 2001 14:35:55 -0600 Subject: RE: [suse-oracle] Corrupted/Missing Rollback Tablespace
Only thing to add is the complete parameter is
_corrupted_rollback_segments = TRUE
I have had to use this before and it IS highly unrecommended, but it did
allow me to startup my database without the corrupted rollback segment. If
you use it, be sure and back up your database IMMEDIATELY in its current
state once you get it open.
-----Original Message-----
From: Casey Dyke [mailto:cdyke@froggy.com.au]
Sent: Wednesday, October 31, 2001 1:26 PM
To: Matthew Iskra
Cc: suse-oracle@suse.com
Subject: Re: [suse-oracle] Corrupted/Missing Rollback Tablespace
Matthew,
You're not in a good position at all. The missing rollback segment is
likely to contain updates to the data dictionary. Using undocumented
parameters such as _corrupted_rollback_segments may allow you to get the
database open after which you could export all your data - but they're
not recommended and I would suggest using them only alongside Oracle
support. Risky business.
Had this situation myself w/colleagues who tried a migration to 8i from
8.0 using the migration assistant and not command line stuff. It failed
and managed to overwrite the rollback segment tablespace datafile. How
I do not know - but the outcome was a rollback to a previous backup and
rollforward to a point in time before the error. They were not happy.
Again though, the issue w/opening the database w/out that rollback
segment is that important data dictionary transactions could be in
missing rbs and not applying them could corrupt the db. You may not
notice it for a week, perhaps a month. But when you do, you'll be
screwed. Bummer huh?
Others may have nifty ways out of this, but my view is rather
unfortunately a bleak one.
Best of luck.
Casey ...
> Matthew Iskra wrote:
>
> A tricky situation.
>
> I have an Oracle 8i database on a SuSE 7.0 box. The original DBA added
> a new file and tablespace, called RBS, to hold additional rollback
> segments. A programmer tried to export from Access using ODBC and but
> the data directly into the oracle database. Something went wrong and
> the load failed. In the process of 'fixing' the database and undoing
> the load, the RBS tablespace got corrupted. Eventually I get called
> in. Recognizing that we do not need the data in the segment, I
> attempted an offline drop. That worked, although in hindsight it was
> probably not the correct thing to do. I then tried dropping the user
> with cascade options to eliminate all the bad data. It won't work -
> the database still wants the missing rollback segment to be online
> which is now impossible.
>
> There is data in other tables that we need, so I do not want to
> reinstall oracle is I don't have to.
>
> Any ideas?
>
> --Matthew Iskra
>
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-oracle-unsubscribe@suse.com
For additional commands, e-mail: suse-oracle-help@suse.com
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-oracle-unsubscribe@suse.com
For additional commands, e-mail: suse-oracle-help@suse.com
This archive was generated by hypermail 2.1.0 : Wed Oct 31 2001 - 12:39:50 PST