Which is exactly the way Oracle Data Guard 3.x for 8.1.7 EE works, almost completely ksh-script based. There even is an alert-file parser active. It can add datafiles to the standby database automatically.... If you are on 9i or higher, you can use tha archive_lag_target parameter to perform the logswitch automatically. Saves a dbms_job or cron script, thus reducing the chance of a failure there. Best regards, Carel-Jan Engel === If you think education is expensive, try ignorance. (Derek Bok) === On Thu, 2005-05-19 at 21:16, Khemmanivanh, Somckit wrote: > Speaking of which.... > > We actually backup our archivelogs "on demand" to our DR site. On demand > means as soon are the log is fully archived to the archive directory. We > do this by reading the alert log, this tells us when the logfile has > been archived. We then identify the file and back it up to tape at the > DR site (the script also verifies the backup to tape was successful).=20 > > This give us instant up to date logs at the DR site without the need for > any remote mirroring technology. > > If we so chose to, we also schedule routine archivelog switches to > minimize the exposure window... > > Thanks!=20 > -- //www.freelists.org/webpage/oracle-l