thanks Roelof - that did the trick
"R.S." <info_at_bytelife.com> wrote in message
news:a9kh4p$r00$1_at_newswriterENV1.svr.pol.co.uk...
> Hello Glen,
> Yes, the _corrupted_rollback_segments should work.
> Make an entry in init.ora:
>
> _corrupted_rollback_segments = (rbs1,... )
>
> Do an export right after you get the db to open !
> Good luck,
>
> Roelof Schierbeek
>
> R. Schierbeek, Bytelife BV
> email : info_at_bytelife.com
> www : www.bytelife.com
> Tel. : 070-3834350
> Mobiel: 06-27525453
> www : www.bytelife.com/sql4dba.htm
>
> Glen A Stromquist <gstromquist_at_nospamyahoo.com> schreef:
> > I have a test DB that would not start up due to a corrupted rollback
> > tablespace. From the mount stage I was able to do an offline drop of the
> > offending datafile and open the database.
> > From there I created another rollback tablespace, but I can't create any
> > rollback segments in it because I get an error saying it is still trying
> to
> > access the file I took offline. Being a test DB it is not in archivelog
> > mode, I can't put the file back online because it needs recovery, and if
I
> > try to recover it its looking for an archived log that doesn't exist.
> >
> > What are my options at this point?
> >
> > Would the _corrupted_rollback_segments paramater get me going? (I'm
going
> to
> > truncate the entire db and re-import anyway once its up)
> >
> > Any suggestions much appreciated
>
>
Received on Wed Apr 17 2002 - 16:57:48 CDT
