Re: Failed to archive log ...

You are running with 2 ARCH processes (ARC0 and ARC1). Both of the ARCH processes attempted to archive seq#361 at the same time. Of course, only 1 of the ARCH processes actually succeeds in the archival attempt - the other ARCH gets a failure message (because it could not acquire the lock on the logfile).

For more information, you can dynamically set the "log_archive_trace" init.ora parameter to the value "127" (refer to the manual for an explanation of this value) and then examine the ARCH trace files. Quite educational...

Hope this helps.

Rick

Sybrand Bakker wrote:

> "Epicentre team A" <oracle_at_epicentre.fr> wrote in message
> news:aj33dt$skl$1_at_wanadoo.fr...
> > Hi
> >
> > In alert files i've this error but it's really a problem ?
> >
> > ARC0: Beginning to archive log# 1 seq# 361
> > Sat Aug 10 14:49:20 2002
> > Thread 1 advanced to log sequence 363
> > Current log# 3 seq# 363 mem# 0: D:\EPIC0\REDO\REDO03.LOG
> > Sat Aug 10 14:49:20 2002
> > ARC1: Beginning to archive log# 1 seq# 361
> > ARC1: Failed to archive log# 1 seq# 361 (!!!!!!!!!)
> > ARC1: Beginning to archive log# 2 seq# 362
> > Sat Aug 10 14:49:24 2002
> > ARC0: Completed archiving log# 1 seq# 361 (!!!!!!!)
> >
> >
> > Thanks
> > Epicentre Team A
> >
> >
>
> No version of course!
> Oracle 8.1.5 shows the same behavior
>
> Hth
>
> --
> Sybrand Bakker
> Senior Oracle DBA
>
> to reply remove '-verwijderdit' from my e-mail address
Received on Mon Aug 12 2002 - 14:01:16 CDT