Document 806106.

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jsp...

How To Apply Interim Patch On Database With Physical Standby (Doc ID 806106.1)
Modified 14-SEP-2010 Type HOWTO Status UNDER_EDIT(EXTERNAL) Priority 3
To Bottom

In this Document Goal Solution References

Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.5 - Release: 10.2 to 10.2 Information in this document applies to any platform.

Goal
Goal of this article to provide steps to apply any interim patch or patch bundle on standalone database setup with physical standby.

Solution
1. Log in to the oracle account on both the primary and standby hosts and make sure the environment is set to the correct ORACLE_HOME and ORACLE_SID. 2. Shut down the existing Oracle Server instance on the primary host with normal or immediate priority. Stop all listeners, agents and other processes running against the ORACLE_HOME. SQL> shutdown immediate % agentctl stop % lsnrctl stop

3. Cancel managed recovery on the standby database. SQL> recover managed standby database cancel; 4. Shutdown the standby instance on the standby host. Stop all listeners, agents and other processes running against the ORACLE_HOME. SQL> shutdown immediate % agentctl stop % lsnrctl stop

5. Apply the Interim patch on both Primary and Standby using Opatch as per readme. 6. Startup mount the standby database. % sqlplus "/ as sysdba" SQL> startup mount

7. Place the standby database in managed recovery mode. SQL> recover managed standby database nodelay disconnect; 8. Startup the Primany Instance. % sqlplus "/ as sysdba" SQL> STARTUP 9. Ensure that remote archiving to the standby database is functioning correctly by switching logfiles on the

1 of 2

08.06.2011 10:08

Document 806106.1

https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jsp...

primary and verifying that v$archive_dest.status is valid. If not performing remote archiving make note of the current archive log sequence. SQL> alter system archive log current; SQL> select dest_id, status from v$archive_dest; 10. Run any post-installation scripts as per patch readme example:catcpu or catbundle.sql

11. Once the SQL script completes make note of the current log sequence and issue the following command: SQL> alter system archive log current; 12. Restart the primary database: SQL> SHUTDOWN SQL> STARTUP 13. Verify the standby database has been recovered to the log sequence. SQL> select max(sequence#) from v$log_history;

References
NOTE:278641.1 - How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration
Related
Products

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition > Oracle Data Guard > Physical Configuration
Knowledge Categories

ST > Server > HighAvailability > DataGuard > 10gRx Physical Standby (Primary)
Keywords

PHYSICAL STANDBY STANDBY DATABASE

Document Attributes Author ABSRIVAS.IN Owner Alias Visibility EXTERNAL Created By ABSRIVAS.IN Modified By javier.giral@oracle.com Reviewer james.erickson@oracle.com Source AWIZ Comments
Edit Comment Wouldnt this also apply for 9-11.2? Type Status Priority From NEW 2 To Modified By Created Date Modified Date 24-Jul-2010 24-Jul-2010 Return To Top

Status UNDER_EDIT(EXTERNAL) Publisher IMPORT.US Content Type TEXT/X-HTML Priority 3 Created Date 14-APR-2009 Modified 14-SEP-2010 Review Date 20-JAN-2011 Exception No

mark.richwine@oracle.com OWNER

2 of 2

08.06.2011 10:08