Ooops. Try selling management on the "rebuid" option when it's supposed to be a a DR site, it's 5.4 TB, it's in another city, and in addition to the time and cost of shipping the tapes to said city, it's a 12-hour restore. This doesn't make me too happy. Fortunately, although I may have been "bitten" by whatever is going on, it hasn't actually bitten anything off. On 2/12/08, Goulet, Dick <richard.goulet@xxxxxxxxxxxxx> wrote: > > Well, I got the following back form OTS this morning: > > > > There are several other customers who has encountered this error. Please > follow the steps I have given you earlier to fix this error. > > Here they are again: > > 1. Take a good copy of the archived log in question. > 2. FTP the file over to standby site in binary mode. > 3. Register the logfile on standby. > 4. Allow the recovery to continue again. > > If this does not help then the only other way is to rebuild your standby > using a good backup copy of primary. > > > > ______________________________________________________________ > Dick Goulet / *Capgemini* > North America P&C / East Business Unit > Senior Oracle DBA / Hosting > Office: 508.573.1978 / Mobile: 508.742.5795 / www.capgemini.com > Fax: 508.229.2019 / Email: *richard.goulet@xxxxxxxxxxxxx* > 45 Bartlett St. / Marlborough, MA 01752 > > *Together: the Collaborative Business Experience * > ______________________________________________________________ > ------------------------------ > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto: > oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *David Barbour > *Sent:* Monday, February 11, 2008 10:15 PM > *To:* Goulet, Dick > *Cc:* oracle-l@xxxxxxxxxxxxx > *Subject:* Re: Data Guard question > > > > 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 9.2.0.7 on AIX 5.3 > > On 2/11/08, *Goulet, Dick* <richard.goulet@xxxxxxxxxxxxx> 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 / www.capgemini.com > Fax: 508.229.2019 / Email: *richard.goulet@xxxxxxxxxxxxx* > 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. > > > 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. > >