Re: Standby database issue

You could use the 'fuser' utility to see if any processes are accessing the file.

"ff" <cfs3526_at_ureach.com> wrote in message news:WhKH6.7841$Aj1.3878670_at_typhoon2.ba-dsg.net...
> We have a standby databse, and we use a in house developed perl script to
> copy the redologs from the remote production database.
> The way we do is we use 'ls -l' to detect the redolog file, as soon as we
> see it, wait for 30 seconds, and then we copy it over. Most of time it
> worked, but sometimes, the copy begins before the production finish
 writing
> to the redo, and we got corrupted file.
> Is there any way we can monitor the finish of the redologs and begin to
 copy
> only after the writing of redologs have finished?
>
> Thanks for your help.
>
> PS: Could some body show me your script for manually copy your redo
 logfile
> to remote standby database?
>
> Thanks.
>
>
>
>
>
Received on Wed May 02 2001 - 15:31:54 CDT