Actually there may be no problem at all. Your standby
database might be up to date, the last available archive log file has been
applied to your standby database and Oracle tried to apply the next archive log
file 'D:\ORACLE\ORA81\DATABASE\ARCHIVE\ARC00505.001 and did not find it, since
you did not copied it to the standby server or it does not even exist - yet - in
the primary site.
Check if the file missed by Oracle exists on the
standby site archive directory.
Actually if you use managed standby database, Oracle
can transfer the archived logs to the standby database through SQLNet and can
make the standby database applie them automatically. But you will need
Enterprise Edition Licences to do this :-((
If you move the archived log files from the primary
site to the standby manually, it can work very well too, without additional
licence fees. In this case create soma batch files for moving the files and
applying them to the standby site. The triggering of the batch files can be
achieved by OS specific scheduling commands. Actually we implemented it
this way and it's working fine for us.
HTH,
Tamas Szecsy
|
- Trouble.. Standby Database. Urgent!! Saurabh Sharma
- Re: Trouble.. Standby Database. Urgent!! Szecsy Tamas
- Re: Trouble.. Standby Database. Urgent!! Joseph S. Testa
- RE: Trouble.. Standby Database. Urgent!! Kevin Lange