Re: trigger script after archive log switch

Why can't you just create a process in the OS that scans for new files (every minute, 5 minutes or so whatever you need) and send the file to the remote location at that point. To keep track of what is there and is what is not, create a table that logs each archive log in it after successful completion of the archive log being copied and then also at the beginning of each script run, you can compare the new table with v$archived_log to only send what is needed.

Sorry if I am missing something but that seems like a viable choice to me.

Brandon

"Philip Brown" <phil+s3_at_bolthole.no-bots.com> wrote in message news:slrnahi3bf.2hg3.phil+s3_at_bolthole.com...
> On Wed, 26 Jun 2002 01:25:50 +0200, postbus_at_sybrandb.demon.nl wrote:
> >>[Philip Brown wrote]
> >>Actually, more disaster recovers reasons. But security is also an issue.
> >
> >Implement a *proper* standby database. NOT your own. I have seen that
> >in operation. It just DOESN'T WORK!
>
> We do not want to implement a standby database at this time.
> We are looking to have a remote machine store reasonably up-to-date
> archive logs, for disaster recovery purposes. We already have a
> clustered database. So this other site is mainly for storing data, for
> by-hand recovery at a later time.
> We may have multiple databases dumping their archive logs to this one
> machine. We dont want to be running 10 standby instances of oracle for
this
> purpose.
>
> Immediate startup of another database is not neccessarily a priority.
> However, having the most current set of data, *is*.
>
> Yes, we have looked at the reopen option. That does not address the
problem
> of "the connection to the remote machine has been down through multiple
> archive log writes". Or at least it didnt in our tests so far.
> It merely wrote the latest log, leaving a gap in the log sequence.
>
> The script to be triggered, will intelligently evaluate whether it needs
to
> copy over just the latest archive log, or multiple ones that did not make
> it previously.
>
>
> --
> [Trim the no-bots from my address to reply to me by email!]
> [ Do NOT email-CC me on posts. Pick one or the other.]
> S.1618 http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
> http://www.spamlaws.com/state/ca1.html

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.371 / Virus Database: 206 - Release Date: 6/13/02