Re: Oracle 8i RMAN archiver error

From: Don Khan <dkhan_at_mediaone.net>
Date: 1999/10/29
Message-ID: <jtqS3.3994$IT5.242495_at_ndnws01.ne.mediaone.net>#1/1


Thanks for your response. Yup you are correct. The catalog database ground to a halt because it's archive og directory was filled. I'm registering a 3.2TB database and the damm catalog resync is generating lots of logsfiles. Thanks again.

Sybrand Bakker <postmaster_at_sybrandb.demon.nl> wrote in message news:941236731.26676.0.pluto.d4ee154e_at_news.demon.nl...
> Your archive log medium for the catdb database is full, and because of
 this
> the archiver has stopped. This will stop the database also. Try either to
> make some space on that device or redirect the archiver to a different
> device
> In case of freeing up space
> svrmgr30
> connect internal
> archive log next
> exit
> will resolve the problem
> in case of redirection replace next in the archive log command by start
> '<any directory name>'
>
> Hth,
>
> --
> Sybrand Bakker, Oracle DBA
> Don Khan <dkhan_at_mediaone.net> wrote in message
> news:TEnS3.3970$IT5.237867_at_ndnws01.ne.mediaone.net...
> > Does anyone know how to fix the following problem. I had to abort the
> > initial database registration of this database in the catalog server.
 Any
> > help appreciated.
> >
> >
> > RMAN> connect rcvcat rman/rman_at_CATDB
> >
> > RMAN-00571: ===========================================================
> > RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> > RMAN-00571: ===========================================================
> > RMAN-04004: error from recovery catalog database: ORA-00257: archiver
> > error. Connect internal only, until freed.
> >
> >
>
>
Received on Fri Oct 29 1999 - 00:00:00 CEST

Original text of this message