[Oracle] The oraclepsu upgrade process

[Oracle] The oraclepsu upgrade process
The following is the content in the PSU's readme file: 3.2 Patch Installation Instructions

Follow these steps:

1. If you are using a Data Guard Physical Standby database, you must install this patch on both the primary database and the physical standby database, as described by My Oracle Support Note 278641.1.

2. Do one of the following, depending on whether this is a RAC environment:

   • If this is a RAC environment, choose one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime ), and shutdown instances and listeners as appropriate for the installation method selected.

     This PSU patch is rolling RAC installable. Refer to My Oracle Support Note 244241.1 Rolling Patch-OPatch Support for RAC.

   • If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating. For more information, see Oracle Database Administrator's Guide.

3. Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:

   unzip p12419378_11201_<platform>.zipcd 12419378opatch apply

4. If there are errors, refer to Section 5, "Known Issues ".

3.3 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

1. Apply conflict resolution patches as explained in Section 3.3.1.

2. Load modified SQL files into the database, as explained in Section 3.3.2.

3.3.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed when you have med the steps in Section 3.1.4, "One-off Patch Conflict Detection and Resolution ".

3.3.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.

1. For each database instance running on the Oracle home being patched, connect to the database using SQL * Plus. Connect as SYSDBA and runcatbundle.sqlScript as follows:

   cd $ORACLE_HOME/rdbms/adminsqlplus /nologSQL> CONNECT / AS SYSDBASQL> STARTUPSQL> @catbundle.sql psu applySQL> QUIT

   Thecatbundle.sqlExecution is reflected in the dba_registry_history view by a row associated with bundle seriesPSU.

   For information aboutcatbundle.sqlScript, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle. SQL.

2. Check the following log files in$ORACLE_HOME/cfgtoollogs/catbundleFor any errors:

   catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.logcatbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log

   Where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, refer to Section 5, "Known Issues ".

The procedure is as follows:

Decompress the upgrade package:

[Oracle @ ITAA soft] $ unzip p12419378_112010_LINUX \. zip

Check:

[Oracle @ ITAA soft] $ opatch prereq CheckConflictAgainstOHWithDetail-phBaseDir./12419378

Oracle Interim Patch Installer version 11.2.0.3.6

Copyright (c) 2013, Oracle Corporation. All rights reserved.

 

PREREQ session

 

Oracle Home:/u01/app/oracle/product/11.2.0/dbhome_1

Central Inventory:/u01/app/oraInventory

From:/u01/app/oracle/product/11.2.0/dbhome_1/oraInst. loc

OPatch version: 11.2.0.3.6

OUI version: 11.2.0.1.0

Log file location:/u01/app/oracle/product/11.2.0/dbhome_1/export toollogs/opatch/opatch2014-09-24_13-04-16PM_1.log

 

Invoking prereq "checkconflictagainstohwithdetail"

 

Prereq "checkConflictAgainstOHWithDetail" passed.

 

OPatch succeeded.

Close the database:

[Oracle @ ITAA ~] $ Sqlplus/as sysdba

 

SQL * Plus: Release 11.2.0.1.0 Production on Wed Sep 24 12:34:18 2014

 

Copyright (c) 1982,200 9, Oracle. All rights reserved.

 

 

Connected:

Oracle Database 11g Enterprise Edition Release 11.2.0.1.0-Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

 

SYS @ ORCL> shutdown immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

Upgrade PSU:

[Oracle @ ITAA 12419378] $ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.6

Copyright (c) 2013, Oracle Corporation. All rights reserved.

 

 

Oracle Home:/u01/app/oracle/product/11.2.0/dbhome_1

Central Inventory:/u01/app/oraInventory

From:/u01/app/oracle/product/11.2.0/dbhome_1/oraInst. loc

OPatch version: 11.2.0.3.6

OUI version: 11.2.0.1.0

Log file location:/u01/app/oracle/product/11.2.0/dbhome_1/export toollogs/opatch/124191__sep_24_2014_12_35_57/apply2014-09-24_12-35-57PM_1.log

 

Applying interim patch '000000' to oh'/u01/app/oracle/product/11.2.0/dbhome_1'

Verifying environment and padding Ming prerequisite checks...

Patch 12419378: Optional component (s) missing: [oracle. client, 11.2.0.1.0]

All checks passed.

Provide your email address to be informed of security issues, install and

Initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

 

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y] es, [N] o) [N]: Y

 

 

 

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/app/oracle/product/11.2.0/dbhome_1 ')

 

 

Is the local system ready for patching? [Y | n]

Y

User Responded with: Y

Backing up files...

 

Patching component oracle. rdbms. rsf, 11.2.0.1.0...

 

Patching component oracle. rdbms. dbscripts, 11.2.0.1.0...

 

Patching component oracle. rdbms, 11.2.0.1.0...

 

Patching component oracle. oraolap, 11.2.0.1.0...

 

Patching component oracle. rdbms. deconfig, 11.2.0.1.0...

 

Patching component oracle. javavm. server, 11.2.0.1.0...

 

Patching component oracle. precomp. common, 11.2.0.1.0...

 

Patching component oracle. network. rsf, 11.2.0.1.0...

 

Patching component oracle. network. listener, 11.2.0.1.0...

 

Patching component oracle. rdbms. dv. Solaris, 11.2.0.1.0...

 

Patching component oracle. sdo. locator, 11.2.0.1.0...

 

Patching component oracle. sysman. console. db, 11.2.0.1.0...

 

Patching component oracle. sysman. oms. core, 10.2.0.4.2...

 

Patching component oracle. rdbms. dv, 11.2.0.1.0...

 

Patching component oracle. xdk. rsf, 11.2.0.1.0...

 

Patching component oracle. ldap. rsf. ic, 11.2.0.1.0...

 

Patching component oracle. ldap. rsf, 11.2.0.1.0...

 

Patching component oracle. sysman. plugin. db. main. repository, 11.2.0.1.0...

 

 

Verifying the update...

Patch 12419378 successfully applied

Log file location:/u01/app/oracle/product/11.2.0/dbhome_1/export toollogs/opatch/124191__sep_24_2014_12_35_57/apply2014-09-24_12-35-57PM_1.log

 

OPatch succeeded.

 

[Oracle @ ITAA ~] $ Cd $ ORACLE_HOME/rdbms/admin

[Oracle @ ITAA admin] $ sqlplus/as sysdba

 

SQL * Plus: Release 11.2.0.1.0 Production on Wed Sep 24 12:52:56 2014

 

Copyright (c) 1982,200 9, Oracle. All rights reserved.

 

Connected to an idle instance.

 

SYS @ ORCL> startup

ORACLE instance started.

 

Total System Global Area 849530880 bytes

Fixed Size 1339824 bytes

Variable Size 708841040 bytes

Database Buffers 134217728 bytes

Redo Buffers 5132288 bytes

Database mounted.

Database opened.

SYS @ ORCL> @ catbundle. SQL psu apply

 

PL/SQL procedure successfully completed.

 

 

PL/SQL procedure successfully completed.

 

 

 

 

 

Generating apply and rollback scripts...

Check the following file for errors:

/U01/app/oracle/product/11.2.0/dbhome_1/export toollogs/catbundle/catbundle_PSU_ORCL_GENERATE_2014Sep24_12_56_54.log

Apply script:/u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/catbundle_PSU_ORCL_APPLY. SQL

Rollback script:/u01/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/catbundle_PSU_ORCL_ROLLBACK. SQL

 

PL/SQL procedure successfully completed.

 

Executing script file...

......

Check the following log file for errors:

/U01/app/oracle/product/11.2.0/dbhome_1/export toollogs/catbundle/catbundle_PSU_ORCL_APPLY_2014Sep24_12_56_54.log

So far, the PSU has been upgraded.

Does oracle rac only need to apply the psu patch on one node? Or do I have to operate on all nodes?

All
 
Oracle uses opatch to view the PSU version and query dba_registry_history. Which of the following statements shall prevail?

Dba_registry_history
Depends on whether you have run the upgrade script of the corresponding PSU,

What opatch displays depends on whether you have installed the corresponding PSU patch. Generally, opatch prevails.