Comments below...
--
--------------------------------------------------------------------------
Opinions expressed are my own, and not those of Oracle Corporation
Oracle DBA Resources: http://www.geocities.com/howardjr2000
--------------------------------------------------------------------------
"nomenclature" <nom_at_tonal.net> wrote in message
news:39CB87FD.3B89CE8C_at_tonal.net...
> "Howard J. Rogers" wrote:
> >
> > If he's in nomount stage, he won't be able to drop the tablespace. You
can
> > only talk tablespace language when you're fully open (Hence, if he
follows
> > your advice, he'll get an ORA-01109 error). And how on earth is he
supposed
> > to create a new tablespace in the nomount stage?? If he tries it, he'll
get
> > another ORA-01109. And it won't work in mount stage, either.
>
> Fine - I asked to be corrected, like I said I've
> done this before - if I'd been going slower I'd
> have said mounted but not open. Who crapped in
> your lunch today?
>
You don't get it, do you? Your proposed solution will not work in either
the nomount or mount stages. To claim that you have 'done this before' is
therefore an example of being economical with the truth, because you can't
possibly have done it the way you suggested. You can *only* drop or
recreate tablespaces in the fully open stage -and since his problem is that
he can't *get* to the open stage, your advice was somewhat less than
useless.
> >
> > If you're going to offer advice, I think you need to do a minimum amount
of
> > checking that it is not total nonsense. Yours, in this case,
unfortunately
> > is. Particularly as it seems you have no idea of the difference between
> > mount and nomount stages.
>
>
> Arrogant tosser - try to help someone and a total
> stranger tosses insults. The key point I made was
> correct - he has to drop the tablespace. Thus you
> are simply wrong - it is not 'total nonsense'
>
Yes, he may have to drop his tablespace. Full marks for pointing out the
obvious. Now, about that 'trying to help someone' -care to offer him advice
as to *how* he can drop his tablespace?? Apparently not. Not advice that
is actually follow-able, anyway.
> You rightly mention backups and archivelogs which
> I didn't so hats off to you, but get an attitude
> lesson. Kids these days...
>
I'm probably old enough to be your elder brother, so it's not a question of
attitude or arrogance. This forum is for offering help and advice. The
least you can do is to make sure that that which you proffer is not full of
contradictions, basic errors and mis-directions.
HJR
>
> >
> > The correct approach is:
> >
> > 1. Make sure your init.ora is not trying to bring the affected rollback
> > segment(s) online automatically (remove them from the rollback_segments
> > parameter setting if so)
> >
> > 2. Get the database to the MOUNT stage (startup mount)
> >
> > 3. Alter database datafile 19 offline drop
> >
> > 4. Alter database open
> >
> > 5. Drop tablespace X including contents
> >
> > 6. Create a new rollback tablespace and new rollback segments within
that
> > tablespace.
> >
> > 7. Shutdown immediate
> >
> > 8. Edit init.ora to ensure the new rollback segments are brought online
> > automatically
> >
> > 9. Startup normally
> >
> > ...and that's not even contemplating things like restoring the datafile
from
> > backup and applying redo logs.
> > HJR
> > --
>
> --------------------------------------------------------------------------
> > Opinions expressed are my own, and not those of Oracle Corporation
> > Oracle DBA Resources:
http://www.geocities.com/howardjr2000
>
> --------------------------------------------------------------------------
> >
> > "nomenclature" <nom_at_tonal.net> wrote in message
> > news:39CB626B.F315ACF4_at_tonal.net...
> > > Chuck Carson wrote:
> > > >
> > > > I created a rollback segment and then later deleted the datafile by
> > > > accident. Here is what I get when trying to Start the DB:
> > > >
> > > > ORA-01157: cannot identify/lock data file 19 - see DBWR trace file
> > > > ORA-01110: data file 19: '/u08/oradata/OPS/bigrbs201.dbf'
> > > >
> > > > This is a development DB and there was no activity during this time
> > > > (probably 12 hours idle)
> > > >
> > > > How can I fix this?
> > > >
> > > > (This is Oracle 8.1.6R2 on Solaris 2.7)
> > >
> > > Try to startup nomount and drop the rollback tablespace,
> > > create a new one and off you go.
> > >
> > > If you've deleted the datafile you are screwed
> > > and have to drop the tablespace.
> > >
> > > If I'm wrong - please correct me!
> > > Happened to me before but never again.
Received on Fri Sep 22 2000 - 18:22:59 CDT
