PSU PATCH APPLY 11.2.0.4
Sr no. | Prerequisites | Responsibility |
1 | Download Database patchset | Infra |
2 | Take full Rman or Expdp backup of database | DBA |
3 | Take backup of RDBMS_HOME | DBA |
4 | OPatch utility version should 11.2.0.3.6 | DBA |
Sr. No. | Activity | Responsibility |
1 | Ensure latest OPatch version is installed within RDBMS Home. OPatch utility version should 11.2.0.3.6 or later. cd $ORACLE_HOME/OPatch opatch lsinventory | DBA |
2 | Take Backup of following thing using tar:(tar –cvpf <destination> <source>) on NODE For Oracle : Oracle Home and Oracle opatch | DBA |
3 | Ensure that the “opatch prereq CheckConflictAgainstOHWithDetail” output with ./ relative path. Use the following steps to manually discover conflicts and resolutions: Determine whether any currently installed one-off patches conflict with the PSU patch as follows: A) unzip /oracle/patch/p24006111_112040_<platform>.zip3. cd 24006111 B) opatch prereq CheckConflictAgainstOHWithDetail -ph ./ C) The report will indicate the patches that conflict with PSU 24006111 and the patches for which PSU 24006111 is a superset. Note that Oracle proactively provides PSU 11.2.0.4.161018 one-off patches for common conflicts. Note: When performing the conflict analysis on the Database Oracle Home inventory, use the Database PSU patch instead of the Grid Infrastructure PSU patch. | DBA |
4 | Validation of Oracle Inventory Before beginning patch application, check the consistency of inventory information for GI home and each database home to be patched. Run the following command as respective Oracle home owner to check the consistency. su - oracle $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME <Put oracle home path as ORACLE_HOME in above command > Note: If this command succeeds, it lists the Oracle components that are installed in the home. Save the output so you have the status prior to the patch applies. | DBA |
5 | Download and Unzip the Patch for Database and unzip it to one location Unzip patch to a location, this is called the <UNZIPPED_PATCH_LOCATION>. This directory must be empty and not be/tmp. Additionally, the directory should have read permission for the ORA_INSTALL group. Unzip process done in step 3. | DBA |
6 | Stop EM Agent Processes Prior to Patching and Prior to Rolling Back the Patch You must stop the EM agent processes running from the database home. Execute the following command on the node to be patched or the node where the patch is to be rolled back. As the Oracle database home owner execute: $ su - oracle $ORACLE_HOME/bin/emctl status dbconsole $ $ORACLE_HOME/bin/emctl stop dbconsole | DBA |
7 | Shut down instance and listeners associated with the Oracle home that you are updating. | DBA |
8 | GI Home and the Database Homes that are not shared and ACFS [Oracle ASM Cluster File System] [file system is not configured. As root user, execute the following command on database home: For RDBMS: Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands unzip p24006111_112040_<platform>.zip [Done in step 3] cd 24006111 opatch apply | DBA |
9 | Start instance and listener associated with the Oracle home that you are updating. | DBA |
10 | Patch Post-Installation Instructions Loading Modified SQL Files into the Database a) For database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows and also Check database already started or not if not then start it as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> spool /oracle/catbundle_date.log SQL> @catbundle.sql psu apply SQL> QUIT b) If the OJVM PSU was applied for a previous GI PSU patch, you may see invalid Java classes after execution of the catbundle.sql script in the previous step. If this is the case, run utlrp.sql to re-validate these Java classes.
cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / as sysdba SQL> spool /oracle/utlrp_date.log SQL> @utlrp.sql
| DBA |
11 | Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for any errors: catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log Where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. | DBA |
12 | Check the details after patch apply: FOR ORACLE: $ cd $ORACLE_HOME/Opatch $ opatch lsinventory | DBA |
13 | Checking database status and connectivity. | DBA |
Note: Time will vary on depends of the system response, so depends on resources