Re: trigger script after archive log switch

Sybrand Bakker wrote:
>
> >It was my understanding that in no way does oracle guarantee the remote copy.
> >It TRIES to make the copy, and if it doesnt make the copy, it marks the
> >archive destination as failed, and no longer tries to write to it for
> >future archive logs. (until you manually go in and bump it)
> >Unless you mark it as mandatory, in which case, oracle wont run if the
> >remote location is unavailable at that point.
>
> Of course the remote location should be a sqlnet service destination,
> not NFS. NFS is one of the most unreliable network mechanisms ever
> invented. If you're going to rely on NFS, you will get hurt, even when
> using your own 'smart' 'solution'

To use a tns service name in the log_archive_dest_n parameter, he'd have to have a standby database. He hasn't told us what he has, so it's hard to know if a tns service would help him. NFS may or may not help him. It can be stable enough to run a database on (think NAS), but can also be flaky enough to cause sleepless nights (just depends on how it's implemented). But without more information from Philip, it's difficult to provide a decent answer.

Regards,
Sean Received on Tue Jun 25 2002 - 18:48:14 CDT