Hi all,
My ora600 error is finally solved.
There was a temporary segment in the rbs tablespace.
I created a rbs in the sys tablespace then dropped all
rbs and the rbs tablespace . I recreated the rbs
tablespace and the rbs. I shutdown the db , removed
the 10061 event in the init file and started the db et
voila.
Now, how come a temp segment got in the rbs tablespace
?
90 minutes before the crash on friday night, I dropped
and recreated the rbs.
I forgot to create a rbs in the system tablespace, so
after I dropped the last rbs I lost my connection. I
reconnect and created a rbs in the system tablespace
then created the other rbs.
Probably the temp segment was not cleaned out at the
time I lost my connection.
Thanks to everybody.
- paquette stephane <stephane_paquette_at_yahoo.com> a
écrit : > Hi,
>
> The compatible parameter is set to 8.1.0, not 8.1.6
> All tbs are read-write.
> If it's a bug, it means a lot of other people should
> have it . Oracle 816 on Solaris 5.7 is a popular
> mix.
>
> I can migrate to 817 , I just received the cd last
> week. I can also switch from locally to dictionnary
> managed tbs :-(
>
> Can the event 10061 be mid-long term solution ?
>
>
>
> --- sheisey_at_att.net a écrit : > Stephane, You are
> running into a bug. There seems to
> > be a
> > couple of solutions to this problem. One solution
> is
> > to
> > use dictionary managed tablespaces. Another
> solution
> > is
> > DO NOT set compatible=8.1.6. The event 10061 level
> > 10 is
> > another work around. This also seems to be a
> problem
> > with
> > read only locally managed tablespaces and was
> fixed
> > by
> > making the tablespace read-write.
> >
> > Scott
> > > I just started/stop the db with event 10061
> > several
> > > times, thanks to Barry Botuck.
> > >
> > > Now let's see if I removed the event....
> > >
> > >
> > > --- "Trassens, Christian" <CTrassens_at_uni2.es> a
> > > écrit : > Well, I suppose if it crashes when
> > acceses
> > > to uet$,
> > > > you can consider
> > > > enabling the event 10269. However and
> answering
> > your
> > > > question, there isn't a
> > > > way to prevent SMON starting. Remember that
> it's
> > one
> > > > of the backgrounds
> > > > processes.
> > > >
> > > > Analyzing your assumption, did you ever clone
> > those
> > > > databases ?. And did you
> > > > create each one with different names ?. Did
> > anything
> > > > weird happen when you
> > > > do it or did you do something non-conventional
> > to
> > > > clone if you'd cloned, of
> > > > course ??.
> > > >
> > > > Regards.
> > > >
> > > > > -----Mensaje original-----
> > > > > De: paquette stephane
> > > > [SMTP:stephane_paquette_at_yahoo.com]
> > > > > Enviado el: lunes 15 de enero de 2001 15:20
> > > > > Para: Multiple recipients of list ORACLE-L
> > > > > Asunto: RE: ORA-600 with smon crashing the
> db
> > as
> > > > soon it is started
> > > > >
> > > > > Well, that's what Oracle support told me.
> > > > > Those databases where created from the start
> > with
> > > > > locally managed tablespaces.
> > > > > I've run dbv on the datafiles but it
> reported
> > > > nothing.
> > > > >
> > > > > What amaze me, is that 2 databases out of 3
> > > > crashed at
> > > > > amost the same time (22:30 and 22:35).
> > > > > Pretty weird.
> > > > >
> > > > > Is there a way (with an hidden parameter) to
> > > > prevent
> > > > > smon to start or to start and do nothing
> when
> > > > starting
> > > > > the database ?
> > > > >
> > > > >
> > > > > --- "Trassens, Christian"
> <CTrassens_at_uni2.es>
> > a
> > > > > écrit : > Sorry, I've read it again and I
> have
> > a
> > > > > doubt. How
> > > > > > could it be the uet$
> > > > > > corrupted ?. Or did you transform an
> > dictionary
> > > > to
> > > > > > local with
> > > > > > dbms_space_admin ?.
> > > > > >
> > > > > > Regards.
> > > > > >
> > > > > > > -----Mensaje original-----
> > > > > > > De: Trassens, Christian
> > > > [SMTP:CTrassens_at_uni2.es]
> > > > > > > Enviado el: lunes 15 de enero de 2001
> > 13:15
> > > > > > > Para: Multiple recipients of list
> ORACLE-L
> > > > > > > Asunto: RE: ORA-600 with smon crashing
> the
> > db
> > > > as
> > > > > > soon it is started
> > > > > > >
> > > > > > > So, let us know the workaround.....if it
> > had
> > > > one.
> > > > > > >
> > > > > > > > -----Mensaje original-----
> > > > > > > > De: paquette stephane
> > > > > > [SMTP:stephane_paquette_at_yahoo.com]
> > > > > > > > Enviado el: lunes 15 de enero de 2001
> > 12:56
> > > > > > > > Para: Multiple recipients of list
> > ORACLE-L
> > > > > > > > Asunto: RE: ORA-600 with smon crashing
> > the
> > > > db as
> > > > > > soon it is started
> > > > > > > >
> > > > > > > > Unfortunately, the stack trace from my
> > > > problem
> > > > > > is
> > > > > > > > different from the stack trace of bug
> > > > 1397075
> > > > > > (and I
> > > > > > > > did not drop any locally managed tbs).
> > > > > > > >
> > > > > > > > According to Oracle, it seems to be a
> > > > corruption
> > > > > > in
> > > > > > > > uet$ (all my tbs are locally managed
> > except
> > > > > > system)
> > > > > > > >
> > > > > > > > Oracle will open a new bug. (Do I have
> a
> > > > t-shirt
> > > > > > ?)
> > > > > > > >
> > > > > > > > What bothers me is that it can happen
> > again
> > > > > > since no
> > > > > > > > correction have been applied.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --- "Trassens, Christian"
> > > > <CTrassens_at_uni2.es> a
> > > > > > > > écrit : > Hi,
> > > > > > > > >
> > > > > > > > > You've received the symptons of the
> > bug
> > > > > > 1397075.
> > > > > > > > > Have you dropped a read
> > > > > > > > > only tablespace locally managed ??.
> > > > > > > > >
> > > > > > > > > Startup mount the database and issue
> > and
> > > > alter
> > > > > > > > > database datafile '......'
> > > > > > > > > offline drop; for each datafile of
> the
> > > > tblsp
> > > > > > that
> > > > > > > > > you intended to drop. And
> > > > > > > > > then you can open the database and
> > drop
> > > > the
> > > > > > > > > tablespace with option including
> > > > > > > > > contents;
> > > > > > > > >
> > > > > > > > > Regards.
> > > > > > > > >
>
=== message truncated ===
Received on Tue Jan 16 2001 - 11:28:25 CST
