Archive log transport after Physical Standby bounce

Hi all.

Oracle 10.2.0.3, AIX 5.3 TL05. I have a dataguard setup, primary db(DB1) on server A, standby db on Server B. TNS info is DB1 for the primary and DB1_LOC2 for the standby site. Log_archive_dest_2 is 'SERVICE=DB1_LOC2 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=DB1_LOC2 LGWR ASYNC REOPEN=60000 MAX_FAILURE=2000)' Example of the standby bounce:

shutdown immediate;
startup nomount;
alter database mount standby database;
alter database recover managed standby database disconnect;

After bouncing the standby, querying the primary v$archive_dest, the standby dest stays in error, in fact ora-3113. Note that I'm able to connect to the standby db as sysdba, and am able to connect to the primary. Now, back in 9.2 with Dataguard, in order to get the rfs processes to send the missing archive logs and resync, you connected to the primary and performed the following:

alter database archive log stop;
alter database archive log start;
alter system switch logfile;

After the log switch, Oracle would attempt to re-open the standby archive destination, dest_2. But now, in 10.2, log_archive_start is an obsolete parameter so this no longer works. I've read thru 10.2 dataguard docs and seem to be missing it. Anyone have any ideas(short of bouncing the primary), to get the archive logs transporting again?

TIA,
Pete's Received on Thu May 03 2007 - 09:40:08 CDT