Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Disabling ARCHIVELOG problem

Re: Disabling ARCHIVELOG problem

From: Jens Loebling <Jens_Loebling_at_yahoo.de>
Date: 1 Sep 2004 04:30:53 -0700
Message-ID: <5bdfa25a.0409010330.44421cb5@posting.google.com>


Hallo Chloe,

if Burt's idea is not true and if the file is realy corrupt and nobody recognized it before try to set it in read only mode - but no guarantee that this works.

Best regards
Jens Loebling

"Burt Peltier" <burttemp1REMOVETHIS_at_bellsouth.net> wrote in message news:<VYcZc.72323$0o5.38404_at_bignews1.bellsouth.net>...
> This might sound silly, but is it possible your backup did not take the
> tablespace for the datafile out of backup mode since back in June ? I have
> seen the "needing media recovery" when a database crashed during a hot
> backup and all I really needed to do was end the backup mode.
> - The "alter tablespace blah_tablespace end backup;" command was maybe not
> issued ... since June?!
> - You could select from some catalog tables to see if this is the case (in
> backup mode).
>
> Anyway, if the above is the case, you could simply end the backup mode and
> do something that probably won't help much like ending archivelog mode.
>
> And if the above is not the case, do a full export or at least export the
> schemas with data in that tablespace. Who knows, you might get lucky and get
> a good export. Then, you could simply drop the tablespace and recreate it
> and import the data.
>
> Anyway, others have also posted better methods for improving a batch job.
>
> --
>
> "Chloe Crowder" <chloe.crowder_at_bl.uk> wrote in message
> news:f27559a3.0408310058.5365b1f9_at_posting.google.com...
> > Hi
> >
> > We're running 8.1.7 on Solaris. In order to run a large batch job I've
> > been asked to disable archive logging (I know - I don't agree either).
> > When I tried to do so I got an error message:-
> >
> > ORA-01143 cannot disable media recovery - file XXXX needs media
> > recovery
> >
> > The documentation suggests either recovering or dropping the
> > tablespace.
> >
> > Out of curiousity I went to recover datafile and was prompted for an
> > archive log from 6/11/04 (presumably 11th June, otherwise we have a
> > *real* problem). However our backup cycle only goes back 28 days, so
> > we probably can't get this far back.
> >
> > This is our production database and everything appears to be working
> > correctly. We would be very reluctant to drop the tablespace.
> >
> > We perform backups on a daily basis (mixed full and incremental) using
> > RMAN and Veritas NetBackup.
> >
> > Can anyone explain what causes the problem on an otherwise error-free
> > system, and/or suggest a work round.
> >
> > Chloe Crowder
> > The British Library
Received on Wed Sep 01 2004 - 06:30:53 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US