It's due to Oracle using multiple archivers.
For every one that fails,  you will find an
another ARCX process that was already working
on it.
 
Using sequence number 87568 from below as an
example, grep for that number in the alert log and see
for yourself.
 
Matt
 

----
Matt Adams - GE Appliances - [EMAIL PROTECTED]
"Doing linear scans over an associative array is like
trying to club someone to death with a loaded Uzi."
    - Larry Wall (creator of Perl)

 
-----Original Message-----
From: AK [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 15, 2003 11:45 AM
To: Multiple recipients of list ORACLE-L
Subject: failed to archive

 
I see a lot of "failed to archive " messages in alert.log . But finally the log gets archived . Is it due overloaded archiver ?
 
this is from alert log.....
 
ARC0: Beginning to archive log# 3 seq# 87568
ARC0: Failed to archive log# 3 seq# 87568
ARC0: Beginning to archive log# 2 seq# 87569
Mon Jul 14 11:36:23 2003
ARC4: Completed archiving log# 3 seq# 87568
 
-ak
 
ocp dba 8i
 

Reply via email to