Re: Standby database problem

Chuck wrote:

> -----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-----
Chuck,

What patch set are you running?
If you are running 8.1.7.0.0 with no patches, its likely that the application of a patch set may fix a known bug.

Check the release notes for the patch sets - and the "Bugs" section of Metalink.

8.1.7.3.0 would be a good call ...
8.1.7.2.1 + 8.1.7.2.7 might work also.

Paul Received on Mon Mar 11 2002 - 00:03:28 CST