Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Standby database problem
Even though Oracle refuses to call this a bug, they did provide a workaround
for it. The problem seems to be that the archiver on the primary instance
loses contact with it's counterpart on the standby instance some time after
the standby gets shut down so it can be remounted for recovery. The solution
is to stop the archiver on the primary instance immediately prior to
shutting down the standby. Then restart the primary's archiver as soon as
the standby is mounted.
"Chuck" <chuck_hamilton_at_yahoo.com> wrote in message
news:a6ajf0$d4i98$1_at_ID-85580.news.dfncis.de...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have an 8.1.7 managed standby database that occasionally gets
> placed into read-only mode and then brought back into managed standby
> mode. Some time after being put back into standby mode, the
> production database fails to send a log over to it. It's usually the
> 2nd or 3rd archived log generated after putting the database back
> into standby mode that fails to ship over. The error in the
> production database's v$archive_dest view is always the same:
> "ORA-03113 end of file on communication channel". What is causing
> this and is there a way to prevent it? Is there an easy solution to
> have Oracle automatically retry to ship the log? Upgrading to 9i is
> not an option. The platform is SGI which is desupported after 8i.
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
>
> iQA/AwUBPIjRHGm5A4kkb4ZsEQI+dgCfVzJo2E8TTniL7dKV7A9ENLd47MYAnig5
> wtOHkAcG6B63QWbfFw4/jT1I
> =P9dO
> -----END PGP SIGNATURE-----
>
>
>
Received on Thu Mar 21 2002 - 14:31:32 CST