Standby upgrade issue

Question

Hi
I have a 11gR1 database with dataguard setup.I have successfully upgraded the primary database to 11gR2 using dbua.
Although 11gR2 software is installed on standby server,I realized archivelogs were not shipped to standby server during the database upgrade.
When I switch logfile in primary, I see below errors in standby alertlog:
RFS: 'Attach' request version mismatchI think it is because the database versions become different after the upgrade( primary became 11.2, standby is still 11.1)
Because of this issue, archivelogs are not being transferred.
Do I manually need to edit oratab, create new spfile and start standby instance from new oracle home (11.2) ? These things were done automatically on primary database by dbua.

Answer 1

Hello;
The short story on this is :
See Oracle support article : How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
My overview is :
Disable log shipping from the Primary.
Shutdown Standby .
Install 11.2.0.2 software only on the Standby.
Start the Standby in recovery mode ( using the new home and env. settings ) ( do not run DBUA on standby )
Re-enable log shipping
Monitor the redo apply from Primary to Standby -- this will upgrade the Standby
Your questions
Do I manually need to edit oratab, create new spfile and start standby instance from new oracle home (11.2) ?
You can edit the oratab afterwards on the standby.
You can move (copy) the spfile and password file to the new Oracle home on the standby. (This is what I do before restarting)
Yes, you need to change the env to the new Oracle home before starting up mount and starting recovery.
Just did four of these this week and I'm doing four more today. Will keep my eyes open for you.
Best Regards
mseberg
Later
Another thing I do is copy my tnsnames.ora and listener.ora to the new home on both the Standby and Primary and edit this in the listener.ora as needed :
(SID_DESC =
       (global_dbname = PRIMARY_DGMGRL.thanks.buddy.com)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0)
       (sid_name = PRIMARY)
    )Then if you restart the listeners on both and bounce the databases you will probably avoid a "heartbeat" error.
mseberg
Edited by: mseberg on Dec 10, 2011 6:12 AM