Skip to main content

Oracle DB Upgrade : Patch Apply

Patch Installation Steps:
-------------------------
1. Set your current directory to the directory where the patch is located.

cd /6196748

2. Apply the patch.

Use the following command to apply the patch to the ORACLE_HOME:

opatch apply


export PATH=$PATH:/usr/ccs/bin

1.Determine whether any currently installed one-off patches conflict with the PSU patch as follows:

unzip p12419397_10204_Linux-x86-64.zip
opatch prereq CheckConflictAgainstOHWithDetail -phBaseDir ./12419397

The report will indicate the patches that conflict with PSU 12419397 and the patches for which PSU 12419397 is a superset.

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

unzip p12419397_10204_Linux-x86-64.zip
cd 12419397
opatch apply


3.For each 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:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql opsu apply
SQL> @utlrp.sql
SQL> QUIT

4.Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle for any errors:

catbundle_OPSU__APPLY_.log
catbundle_OPSU__GENERATE_.log

The following steps recompile the views in the database. For a RAC environment, perform these steps on only one node.

1.Run the pre-check script (so named because it was initially released in CPUJan2008), which reports the maximum number of views and objects that may be recompiled:

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @recompile_precheck_jan2008cpu.sql
SQL> QUIT

The purpose of this step is to help you determine whether view recompilation should be done at the same time as the PSU install, or scheduled later.
2.If the database is not in a RAC environment, perform this step and skip the next step. (If the database is in a RAC environment, go to the next step.)

Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.

cd $ORACLE_HOME/cpu/view_recompile
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP UPGRADE
SQL> @view_recompile_jan2008cpu.sql
SQL> SHUTDOWN;
SQL> STARTUP;
SQL> QUIT

4.If any invalid objects were reported, run the utlrp.sql script as follows:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

Then, manually recompile any invalid objects. For example:

SQL> alter package schemaname.packagename compile;

================================================================

Rolling Back the Patch :

1.Verify that an $ORACLE_HOME/rdbms/admin/catbundle_OPSU__ROLLBACK.sql file exists for each database associated with this ORACLE_HOME.
2.Shut down all instances and listeners associated with the Oracle home that you are updating.
3.Run the OPatch utility specifying the rollback argument as follows.

opatch rollback -id 12419397

Post Deinstallation Instructions for a Non-RAC Environment
Follow these steps:

1.Start all database instances running from the Oracle home. (For more information, see Oracle Database Administrator's Guide.)

2.For each database instance running out of the ORACLE_HOME, connect to the database using SQL*Plus as SYSDBA and run the rollback script as follows:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_OPSU__ROLLBACK.sql
SQL> QUIT
In a RAC environment, the name of the rollback script will have the format catbundle_OPSU__ROLLBACK.sql.

3.Check the log file for any errors. The log file is found in $ORACLE_HOME/cfgtoollogs/catbundle and is named catbundle_OPSU__ROLLBACK_.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS.

======================================================

Patch Deinstallation Instructions:
----------------------------------

1. Make sure to follow the same pre-install steps when deinstalling
a patch. This includes verifying the inventory and shutting down
any services running from the ORACLE_HOME / machine before rolling
the patch back.

2. Change to the directory where the patch was unzipped.
cd /6196748

3. Run OPatch to deinstall the patch.
opatch rollback -id 6196748



Comments

Popular posts from this blog

CLSRSC-430: Failed to start rolling patch mode

############################################################ GRID PSU Failed on Node2: =========================== [root@server1 tmp]# /oracrs/oracle/product/12102/OPatch/opatchauto apply /path1/patches/23273629 -oh /oracrs/oracle/product/12102 -ocmrf /tmp/ocm.rsp OPatch Automation Tool Copyright (c)2014, Oracle Corporation. All rights reserved. OPatchauto Version : 12.1.0.1.10 OUI Version        : 12.1.0.2.0 Running from       : /oracrs/oracle/product/12102 opatchauto log file: /oracrs/oracle/product/12102/cfgtoollogs/opatchauto/23273629/opatch_gi_2016-11-25_06-13-44_deploy.log Parameter Validation: Successful Configuration Validation: Successful Patch Location: /path1/patches/23273629 Grid Infrastructure Patch(es): 21436941 23054246 23054327 23054341 DB Patch(es): 23054246 23054327 The following patch(es) are duplicate patches with patches installed in the Oracle Home.  [ 20299023] You hav...

SQL Plan Management [ SPM ]

============================================= SQL> SHOW parameter baselines NAME                                 TYPE        VALUE ------------------------------------ ----------- ------- optimizer_capture_sql_plan_baselines boolean     FALSE optimizer_use_sql_plan_baselines     boolean     TRUE SQL> ============================================= Connect as SPM user and create a table as follows. -------------------------------------------------- SQL> CREATE TABLE EMPLOYEE (code number,dept char(100),address char(1000)); Table created. SQL> ============================================= Populate some rows in the table =================================== declare c1 number; begin for c1 IN 1..10000 ...