This content has been marked as final. Show 6 replies
Pl follow the steps in the README for 10.2.0.4. This MOS Doc may also be helpful.
Applying Patch Sets / Interim Patches with Physical Standby Database in Place in Oracle 9i [ID 187242.1]
How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
As you can see all you really do is install software on the Standby and let the redo apply handle the rest.
Disable log shipping from the Primary Shutdown Standby Install patch software on Standby Startup Standby in recovery mode (do NOT run any SQL at the standby) Shutdown Primary Install patch software on Primary Run SQL for patch on the Primary Re-enable log shipping Monitor the redo apply from Primary
Please close your question(s) when complete.
Please refer the MOS document *How To Upgrade A Primary Database And A Physical Standby To Oracle10gR2 (10.2) [ID 407040.1]*
Please update us about your other thread standby redologs on Physical Standby
If you feel that your doubt has been clarified, then provide appropriate points and close the thread rather than keeping it open.
I have followed the steps outlined in the following metalink note
How To Upgrade A Primary Database And A Physical Standby To Oracle10gR2 (10.2) [ID 407040.1]
1. Stop the standby database from applying redo logs
2. Stop the redo logs from being shipped
3. Upgrade the executables for the primary database server
4. Upgrade the executables for the standby database server
5. Upgrade the primary database using DBUA or using the upgrade scripts (see Note:316889.1)
6. Mount the standby database
7. re-enable the shipping of redo from primary to standby
8. restart the managed recovery process on the standby database to progress redo apply
Upgrade was successful but i still have a confusion
In Step 5 primary db has been upgraded (not the standby)
why standby db not required to be upgraded?
it takes time (e.g. 2 Hours) to upgrade primary db which is not acceptable in production
i think we should upgrade standby db first ,switchover to standby(just upgraded) and then upgrade the old primary
1. At Standby Stop the standby database from applying redo logs
2. At Primary Stop the redo logs from being shipped
3- Stop all services (db,em,lsnrctl) at Standby
4- Upgrade the executables for the standby database server
5-Upgrade DB for the standby database server
6-Switchover to Upgraded Standby
7-Upgrade old primary
I have successfully upgraded my DB by implementing the steps you provided but it requires some downtime based on db size (1-2hours)
I think we can do
1- upgrade physical standby first (using transient logical standby)
3- then upgrade the old primary
Muhammad Shakeel Azeem
You install the software on the Primary and Standby and run either DBUA or the upgrade scripts on the Primary only.
Restart ( Start Mount ) the Standby on the new Oracle home ( upgraded )
Startup the Primary and let the redo apply upgrade the Standby.
h1. The last one I did was
from Oracle 220.127.116.11 to 18.104.22.168.
Pre-Upgrade - I ran the Pre-Upgrade Information Tool
h2. Step by notes
On the Primary database :
alter system set log_archive_dest_state_2=defer;
Shutdown the Standby database.
SQL> alter database recover managed standby database cancel;
ORA-01109: database not open
Install 22.214.171.124 on Standby (if not already done)
Should be shutdown using old profile.
Install 126.96.36.199 on Primary (if not already done)
Step 6 and 7 ( were additional patches needed for 11 )
Run dbua for the Primary database.
Set profile to 188.8.131.52 and start dbua.
Shutdown Primary and double check listener on both servers :
( Since I was using a new home I made copies for the new home and changed as needed )
Startup Standby in recovery mode
Monitor the redo apply from Primary to Standby --- this will also upgrade the Standby data dictionary
If using a new home made sure you have a copy of the password file there.
On Oracle 11 watch out for problem noted in 977512.1
Edited by: mseberg on Apr 11, 2012 8:20 AM