Re: Data Guard question

From: David Barbour <>
Date: Mon, 11 Feb 2008 22:15:25 -0500
Message-ID: <>

And I thought I was nuts. Okay, guess that depends on who you ask, but I've had something similar. I get an ORA-308 Error locating archivelog filename then, because I know it's there, when I try to register it I get an ORA-16089 Archive log already registered! I've done something similar, I delete the file, ftp it over but with the same name, then cancel and restart the managed recovery process. Haven't had the file header issue though.

This is Oracle on AIX 5.3

On 2/11/08, Goulet, Dick <> wrote:
> All,
> I'm seeing this strange intermittent happening with Data Guard
> that I can't explain & it seems that OTS can't either. About once a month,
> or less, I end up with a gap at the standby location, but the log file is
> there. I'll then try registering it and catch an "ORA-00317: file type 0
> in header is not log file" error. I'll then remove the file & let the fetch
> archive log process do its thing only to see the gap still there 30 minutes
> later, same file & once again it's on the standby. Again I'll try to
> register it & get the same error again. But if I binary ftp the file to the
> log_archive_dest_1 location but with a slightly modified file name, ..dbf0
> instead of .dbf, & register it with the modified file name it works as
> advertised. Can't understand the initial error. Anyone else ever see this
> behavior???
> ______________________________________________________________
> Dick Goulet / *Capgemini*
> North America P&C / East Business Unit
> Senior Oracle DBA / Hosting
> Office: 508.573.1978 / Mobile: 508.742.5795 /
> Fax: 508.229.2019 / Email: **
> 45 Bartlett St. / Marlborough, MA 01752
> *Together: the Collaborative Business Experience *
> ______________________________________________________________
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute, or
> use this message or any part thereof. If you receive this message in error,
> please notify the sender immediately and delete all copies of this message.

Received on Mon Feb 11 2008 - 21:15:25 CST

Original text of this message