Posts

Showing posts with the label CPU patching

Applying CPU Patch On Primary Database Server Environment

 Applying CPU Patch On Primary Database Server Environment.  Step 1: Incase if you have standby server. Now disable log shipping on the primary database by setting the log_archive_dest_state_2 to disable. As I said earlier, parameter log_archive_dest_2 on my primary database is set to point to the standby database. SQL> alter system set log_archive_dest_state_2=disable; System altered. Step 2: Shutdown the Primary database and stop the listener running on the primary database server.   [oracle@PRIM ~]$ sqlplus sys/"as sysdba" SQL*Plus: Release 11.2.0.2.0 Production Copyright (c) 1982, 2010, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production With the Partitioning, Automatic Storage Management, OLAP, DataMining and Real Application Testing options SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> exit Disconnected from Oracle Database 11g Enterprise Edit...

Applying CPU Patch in a dataguard (Physical Standby) environment

Here is a brief explanation on how to apply CPU(Critical Patch Update) in a dataguard environment In this demo, I am applying PSU 11.2.0.4.2 on the Primary and standby databases. Standby  Database Name :ORCL_STBY Primary  Database Name : ORCL Primary Server: [oracle@PRIM ~]$ sqlplus sys / oracle@srprim as sysdba SQL * Plus: Release 11.2 . 0.2 . 0 Production on Tue Sep 18 10 : 43 : 50 2012 Copyright (c) 1982 , 2010 , Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2 . 0.2 . 0 - 64bit Production With the Partitioning, Automatic Storage Management, OLAP, DataMining and Real Application Testing options SQL> select status,instance_name,database_role from v$database,v$instance; STATUS INSTANCE_NAME DATABASE_ROLE - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OPEN                ORCL         ...