>> I had once a problem with system transactions
>> (in SYSTEM RBS) that got stuck.
Good questions, but I don't know for sure.
I guess I have been *lucky* with my UNDO-RBS corruption/loss...it has always been not non-SYSTEM segments.
I would think my procedures would work, but I guess you would need an additional SYSTEM UNDO/RBS segment before trying to kill/drop the old one? With non-SYSTEM UNDO/RBS segments I was just whipping them all out, but allways had a SYSTEM UNDO/RBS segments available.
If you try it let us know.
From: Alex Gorbachev [mailto:firstname.lastname@example.org]
Sent: Thu 10/27/2005 2:09 AM
To: Marquez, Chris
Subject: Re: Trying to drop old undo tablespace that needs recovery
I had once a problem with system transactions (in SYSTEM RBS) that got
stuck. SMON was core dumping all the time and complaining. The
database was working like that for few months (test system but
important one) excluding certain functionality (this is where
dictionary was affected I guess).
Do you think that can be rocovered as well? In fact, I still have it -
just finished migration to a new database and about to give away this
old "broken" DB. Would be interesting to try to recover it now.
2005/10/27, Marquez, Chris <email@example.com>:
> Your problem is likely the oracle (transactions) are still holing on to and
> UNDO segment and oracle want to right itself.
> >>They [offline undo segments] don't show a status of needing recovery.
> I have not been in the exact position, but in a very similar one...sadly
> several times.
> I would like to see more of the ORA-00600 or other ORA- error details.
> I have my own notes titled;
> Drop Rollback or UNDO Tablspace With Active / Corrupt / "NEEDS RECOVERY"
> I will send them to you directly.
> But in a basically it goes like this;