Standby database managed Recovery

[alapps]

8i has a bug with managed standby databases such that the stand by must be in managed recovery mode (as jovery mentioned) prior to restarting the primary instance.

Should the standby lose contact with the primary under version 8i, it will not "reconnect" and transfer logs.

1. On standby, recover managed standby database
- This window must be left open and running at all times
(See script below)

2. "Bounce" (Shutdown & Startup) the primary
- This will start the two(2) databases talking



Below is a shell script that I wrote for one of my DB's

#!/bin/sh
sqlplus /nolog << EOF
connect / as sysdba
recover managed standby database;
exit;
EOF


put this script in a file (we'll call it smr.sh) on the standby box
execute it as follows:

nohup smr.sh &

This will start managed recovery as a background process and maintain the session after the invoking session disconnects (HangsUP).