Summary of oracle psu upgrade, oraclepsu Summary

Summary of oracle psu upgrade, oraclepsu Summary
First, go to psu. first, let's take a look at readme.html. From this, we can know the detailed upgrade steps that have been rolled back. And avoids many pitfalls.
Before executing the PSU, you must first confirm the version you are about to upgrade and the version of your own system database. Just like this time, we upgraded from 11.2.0.4.0 to 11.2.0.4.2, find the corresponding PATCH from MOS
P18031668_112040_Linux-x86-64.zip

You can easily find the patch package in the mos, from readme.html of the patch package. We can see this requirement

2.1 OPatch Utility
You must use the OPatch utility version 11.2.0.3.6 or later to apply this patch. oracle recommends that you use the latest released OPatch version for 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.

Because the system disk we use is directly installed, the default version is this:

[oracle@storedb OPatch]$ ./opatch versionOPatch Version: 11.2.0.3.4

The version is 11.2.0.3.4, which is less than the minimum PATCH installation version. Therefore, we need another PATCH to update the opatch version.
Oracle provides such a patch
P6880880_112000_Linux-x86-64.zip
Used to upgrade OPATCH to the latest version.
To upgrade the oracle psu separately, follow these steps:

1. configure the Opatch environment variable to export PATH = $ ORACLE_HOME/bin: $ ORACLE_HOME/OPatch: $ PATH2. view the database version opatch [oracle @ <span style = "font-family: arial, Helvetica, sans-serif; "> storedb </span> OPatch] $ opatch versionOPatch Version: 11.2.0.3.4OPatch succeeded. opatch lsinventory [oracle @ kadora4 OPatch] $ opatch lsinventoryOracle Interim Patch Installer version 11.2.0.3.4Copyright (c) 2012, Oracle Corporation. all rights Reserved. oracle Home:/opt/app/oracle/product/11.2.0/db_1Central Inventory:/opt/oraInventory from:/opt/app/oracle/product/11.2.0/db_1/oraInst. locOPatch version: 11.2.0.3.4OUI version: 11.2.0.4.0Log file location:/opt/app/oracle/product/11.2.0/db_1/export toollogs/opatch/opatch2014-07-07_10-44-39AM_1.logLsinventory Output file location: /opt/app/oracle/product/11.2.0/db_1/export toollogs/opatch/l Sinv/lsinventory2014-07-07_10-44-39AM.txt export Installed Top-level Products (1): Oracle Database 11g 11.2.0.4.0There are 1 products installed in this Oracle Home. there are no Interim patches installed in this Oracle Home. -------------------------------------------------------------------------------- 3. update Patch Kit cd $ ORACLE_HOME/m V OPatch OPath_bakunzip p6880880_112000_LINUX.zipcd OPatch [oracle @ racdb1 db_1] $ cd OPatch [oracle @ racdb1 OPatch] $ lscrs docs emdpatch. pl jlib ocm opatch. bat opatchdiag. bat opatch. ini opatch. pl opatchprereqs oplan README.txt version.txt [oracle @ racdb1 OPatch] $ [oracle @ racdb1 OPatch] $ opatch versionOPatch Version: 11.2.0.3.6OPatch patch check whether the patch you need conflicts with the existing patch unzip release _Linux-x86-64.zip cd 18031668 [oracle @ racdb1 18031668] $ opatch prereq CheckConflictAgainstOHWithDetail-ph. /Oracle Interim Patch Installer version 11.2.0.3.6Copyright (c) 2013, Oracle Corporation. all rights reserved. PREREQ sessionOracle Home:/u01/app/oracle/product/11.2.0/db_1Central Inventory:/u01/app/oraInventory from: /u01/app/oracle/product/11.2.0/db_1/oraInst. locOPatch version: 11.2.0.3. 6OUI version: 11.2.0.4.0Log file location:/u01/app/oracle/product/11.2.0/db_1/export toollogs/opatch/opatch2014-07-09_01-59-50AM_1.logInvoking prereq "regular" Prereq "checkconflictagainstohwithdetail" passed. OPatch succeeded.5. shut down the database and update the latest Patch sqlplus/as sysdbashutdown immediatmcm 18031668 opatch applyopatch applyOracle Interim Patch Installer version 11.2.0.3.6Copyright (c) 2013, Oracle Corporation. all rights reserved. oracle Home:/u01/app/oracle/product/11.2/db_1Central Inventory:/u01/app/oraInventory from:/u01/app/oracle/product/11.2/db_1/oraInst. locOPatch version: 11.2.0.3.6OUI version: 11.2.0.4.0Log file location:/u01/app/oracle/product/11.2/db_1/export toollogs/opatch/17478514_Apr_02_2014_15_38_28/apply2014-04-02_15-38-28PM_1.log You have not provided 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/db_1') Is the local system ready for patching? [Y | n] yUser Responded with: YBacking up files... patching component oracle. nlsrtl. rsf, 11.2.0.4.0... patching component oracle. xdk. rsf, 11.2.0.4.0... patching component oracle. rdbms. rman, 11.2.0.4.0... OPatch found the word "warning" in the stderr of the make command. please look at this stderr. you can re-run this make command. stderr output: ins_emagent.mk: 113: warning: overriding commands for targe T 'nmosudo' ins _ emagent. mk: 52: warning: ignoring old commands for target 'nssudo'/u01/app/oracle/product/11.2/db_1/sysman/lib/ins_emagent.mk: 113: warning: overriding commands for target 'nmosudo'/u01/app/oracle/product/11.2/db_1/sysman/lib/ins_emagent.mk: 52: warning: ignoring old commands for target 'nmosudo 'Verifying the update... patch 17478514 successfully appliedOPatch Session completed with w Arnings. log file location:/u01/app/oracle/product/11.2/db_1/export toollogs/opatch/17478514_Apr_02_2014_15_38_28/apply2014-04-02_15-38-28PM_1.log OPatch completed with warnings.6. view the patch: opatch lsinventoryoracle @ racdb1 OPatch] $ opatch lsinventoryOracle Interim Patch Installer version 11.2.0.3.6Copyright (c) 2013, Oracle Corporation. all rights reserved. oracle Home:/u01/app/oracle/product/11.2.0/db_1Ce Ntral Inventory:/u01/app/oraInventory from:/u01/app/oracle/product/11.2.0/db_1/oraInst. locOPatch version: 11.2.0.3.6OUI version: 11.2.0.4.0Log file location:/u01/app/oracle/product/11.2.0/db_1/export toollogs/opatch/opatch2014-07-09_02-10-23AM_1.logLsinventory Output file location: /u01/app/oracle/product/11.2.0/db_1/export toollogs/opatch/lsinv/lsinventory2014-07-09_02-10-23AM.txt --------------- ----------------------------------------------------------------- Installed Top-level Products (1): Oracle Database 11g 11.2.0.4.0There are 1 product (s) installed in this Oracle Home. interim patches (1): Patch 18031668: applied on Wed Jul 09 00:16:43 EDT 2014 Unique Patch ID: 17255543 Patch description: "Database Patch Set Update: 11.2.0.4.2 (18031668) "Created on 20 Feb 2014, 05:15:58 hrs PST8PDTSu B-patch 17478514; "Database Patch Set Update: 11.2.0.4.1 (17478514)" Bugs fixed: 17288409,163 99083, 17205719,178 11429, 10136473,164 72716, 17614227 17050888,170 40764, 17865671,173 25413, 14010183,177 26838, 13364795 17389192,176 17080436,166, 17284817,174 13964, 17761775 41661, 17721717,167 17390431,182 21594, 17551709,173 03837, 16043574 44412, 17446237,168 18139690,170 63422, 71721, 17 501491,176 1000098, 17239687 17752121,174 68141, 17602269,182 03835, 17375354,173 13525, 17811456 16731148,141 33975, 18203838,169 56380, 17385178,172 35750, 13866822 17394950,174 78514, 17027426,129 05058, 14338435,164 50169, 13944971 18094246,169 29165, 16785708,172 65217, 17465741,162 20077, 16180763 16069901,175 46973, 16285691,173 23222, 18180390,170 88068, 16875449 17016369,174 43671, 16228604, 17811438,178 11447, 16837842,180 12768 16912439,173 32800, 17393683,176 22427, 17545847,171 86905, 16943711 16850630,170 82359, 17346671,148 52021, 17783588,174 37634, 16618694 17341326,172 96856, 17546761,177 Tib. run catbundle. SQL reflects the patch information to the database, so that the database knows what patches you applied last time or what patches have been rolled back: SQL> @? /Rdbms/admin/catbundle. SQL psu applySQL> RemSQL> SQL> set termout onSQL> set echo offPL/SQL procedure successfully completed. PL/SQL procedure successfully completed. PL/SQL procedure successfully completed.1 row selected.1 row selected. generating apply and rollback scripts... check the following file for errors:/u01/app/oracle/export toollogs/catbundle/catbundle_PSU_FTDB_GENERATE_2014Apr02_17_20_18.logApply script: /u01/app/oracle/product/11.2/db_1/rdbms/admin/catbundle_PSU_FTDB_APPLY.sqlRollback script: /u01/app/oracle/product/11.2/db_1/rdbms/admin/catbundle_PSU_FTDB_ROLLBACK. SQL PL/SQL procedure successfully completed. executing script file... 1 row selected. SQL> COLUMN spool_file NEW_VALUE spool_file NOPRINTSQL> SELECT '/u01/app/oracle/export toollogs/catbundle/' | 'catbundle _ PSU _ '| name |' _ APPLY _' | TO_CHAR (SYSDATE, 'yyyymondd _ hh24_mi_ss ', 'nls _ DATE_LANGUAGE = 'American ''') | '. log' AS spool_file FROM v $ database; 1 row selected. SQL> SPOOL & spool_fileSQL> exec dbms_registry.set_session_namespace ('server') PL/SQL procedure successfully completed. SQL> PROMPT Skipping Spatial because it is not installed or versions mismatch... skipping Spatial because it is not installed or versions mismatch... SQL> ALTER SESSION SET current_schema = SYS; Session altered. SQL> PROMPT Updating registry... updating registry... SQL> INSERT INTO registry $ history 2 (action_time, action, 3 namespace, version, id, 4 bundle_series, comments) 5 VALUES 6 (SYSTIMESTAMP, 'application ', 7 SYS_CONTEXT ('registry $ CTX ', 'namespace'), 8' 11. 2.0.4', 9 1, 10 'psu', 11 'psu 11.2.0.4.1 '); 1 row created. SQL> COMMIT; Commit complete. SQL> SPOOL offSQL> SET echo offCheck the following log file for errors:

This method is used to manually upgrade the database. For databases with a grid structure, we can use opatch auto to automatically upgrade the database.

1. Update gird and oracle user Opatch file unzip p6880880_112000_Linux-x86-64.zip-d/oracle/11.2.0/gridunzip p6880880_112000_Linux-x86-64.zip-d/oracle/app/oracle/product/11.2.0/db_12. generate the response file cd/oracle/11.2.0/grid/OPatch/ocm/bin. /emocmrsp3, automatic patching, when patching, the grid automatically restarts the database startup status su-root/oracle/11.2.0/grid/OPatch/opatch auto/oracle/media/psu-ocmrf/oracle/11.2.0/grid/OPatch. /ocm/bin/ocm. rsp in this step, we need to pay attention to several issues (1) the group of the patch set needs to be oracle: oinstall (2) We need to disconnect all databases, otherwise, the optach auto error will be reported during the upgrade. We will not see the installation log of the specific error content in the/u01/app/11.2.0/grid/export toollogs folder., if an error occurs, we can see the detailed error log to analyze the cause of the error (3) When we perform opatch auto, we need to close the database. The grid does not need to be closed, it is automatically disabled during the upgrade. 4. verify the installation

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.

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

All