Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)

Oracle 12.1.0.2.0 - Applying Patch 21948354: DATABASE PATCH SET UPDATE 12.1.0.2.160119 (INCLUDES CPUJAN2016)

- Download Patch 21948354 (p21948354_121020_Linux-x86-64.zip)

- Before applying this patch, ensure Oracle home has 12.1.0.2.0 Database installed

- Ensure OPatch utility version is 12.1.0.1.7 or later to apply this patch

- If applying the PSU to environment with Grid Infrastructure home, ensure Grid Infrastructure PSU 12.1.0.2.160119 Patch 22191349 is applied to the Grid Infrastructure home and Database home.

- Set the environment variables

Please note below steps for Standalone DB only (For RAC, Single / Multitenant (CDB/PDB), patching steps vary slightly. Refer to patch readme for more details)

Applying Patch 21948354

- Unzip the patch

$ unzip p21948354_121020_Linux-x86-64.zip

$ cd 21948354

- Run conflict checks

$ opatch prereq CheckConflictAgainstOHWithDetail -ph ./

- Shutdown the services

- Run opatch apply

$ opatch apply

- Start the services

Post-Patching Steps

- Load Modified SQL Files into Database

$ cd $ORACLE_HOME/OPatch

$ ./datapatch -verbose

- Upgrade RMAN Catalog (if using Oracle Recovery Manager)

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;


Patch Rollback Steps

If any issues after applying patch and rollback is required,

- Shutdown all services

- Run opatch rollback

$ opatch rollback -id 21948354

- Start all Services

- Run datapatch utility

$ cd $ORACLE_HOME/OPatch

$ ./datapatch -verbose

- Upgrade RMAN Catalog (if using Oracle Recovery Manager)

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;



Related Posts

Oracle 12.1.0.2.0 - Applying Patch 18201352: ORA-7445 [QERTBSTART()+3105] CRASHES QUERY WITH DISTINCT AND PJE TRANSFORMATION

Oracle 12.1.0.2.0 - Applying Patch 20228093: MATERIALIZED VIEW DEFERRED MODE ORA-00918: COLUMN AMBIGUOUSLY DEFINED

Oracle 12.1.0.2.0 - Applying Patch 22139226: OJVM PATCH SET UPDATE 12.1.0.2.160119

Oracle Database 12.1.0.2.5 - Applying Patch 19509982: DISABLE FIX FOR RAISING ORA-1792 BY DEFAULT.

Oracle Database 12.1.0.2.5 - Applying Patch 19509982: DISABLE FIX FOR RAISING ORA-1792 BY DEFAULT.

- Download Patch 19509982 (p19509982_121025_Linux-x86-64.zip)

- Patch 19509982 is RAC Rolling Installable, Data Guard Standby-First Installable

Pre-requisites

- Ensure 12c Release 12.1.0.2.5 Patch Set Update (PSU) 21359755 is already applied

- Verify OPatch 12c Release 12.1.0.1.7 or higher

Applying Patch 19509982

- Set environment variables like ORACLE_HOME, PATH, etc

- Unzip the patch

$ unzip -d PATCH_TOP p19509982_121025_Linux-x86-64.zip

- Shutdown services

- $ cd PATCH_TOP/19509982

$ opatch apply

- Verify the patch

$ opatch lsinventory |grep 19509982

- Start services


Patch De-installation

If any issues after applying the patch and rollback is required, follow below steps:

- Shutdown services

- $ cd PATCH_TOP/19509982

$ opatch rollback -id 19509982
  
- Start services

- Verify patch was removed 

$ opatch lsinventory


Related Posts:

Oracle 12.1.0.2.0 - Applying Patch 21260431: GETTING ORA-4031 AFTER 12C UPGRADE


Oracle Database 12.1.0.2.0 - Applying Patch 21359755: DATABASE PATCH SET UPDATE 12.1.0.2.5

Rollback Patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Rollback Patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

If after Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015), there are any post patching issues for which a patch rollback is needed, please follow below steps. 

Please note these steps are for NON RAC. (For RAC, steps vary slightly, refer to patch README.TXT for details)

Patch rollback

- Start DB services including listener
- Run the roll back scripts

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle_PSU_<database SID>_ROLLBACK.sql
SQL> QUIT

- If the OJVM PSU was applied for a previous 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> @utlrp.sql

- Start all remaining services after patch roll back and do the health checks

Related Posts:

Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

libserver11.a:/qksbg.o Patch 12942119 conflicts when applying Oracle 11.2.0.3.0 Patch 20760997: DATABASE PATCH SET UPDATE 11.2.0.3.15 (INCLUDES CPUJUL2015)

Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

- Download patch 21352635 (p21352635_112040_Linux-x86-64.zip) (chose zip file for relevant platform) 

- Copy and unzip the patch onto the server at a location with appropriate permissions say PATCH_TOP

- Ensure all patch pre-requisites are met as documented in the patch README.TXT file

- Shutdown Mid-Tier and DB services and take a cold backup before applying the patch (recommended)

Check for patch conflicts:

Refer to Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015) for details.


Apply latest OPatch

- Backup existing OPatch directory

cd $ORACLE_HOME
mv OPatch OPatch_<ddmmyy>

- $ unzip /sid/PATCH_TOP/p6880880_112000_Linux-x86-64.zip
- $ copy /sid/PATCH_TOP/OPatch $ORACLE_HOME/
- $ export PATH=$ORACLE_HOME/OPatch:$PATH
- $ opatch version

Apply DB PSU Patch 21352635

- $ cd /sid/PATCH_TOP/21352635
- $ opatch apply

Any existing previous PSU patches will be rolledback by OPatch

- Start DB services including listener

Post patching steps

- $cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply

- Run utlrp.sql

SQL> @utlrp.sql
SQL> QUIT

- Check the following log files in $ORACLE_HOME/cfgtoollogs/catbundle or $ORACLE_BASE/cfgtoollogs/catbundle for any errors:

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

- Start all services and verify no post patching issues by doing quick post patching health checks

Related Posts:

Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Rollback Patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

libserver11.a:/qksbg.o Patch 12942119 conflicts when applying Oracle 11.2.0.3.0 Patch 20760997: DATABASE PATCH SET UPDATE 11.2.0.3.15 (INCLUDES CPUJUL2015)

Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Checking for Patch conflicts - 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

Before applying patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015), check for patch conflicts with any existing patches on the Database where patch 21352635 is to be applied.


- cd /sid/PATCH_TOP/21352635 

where PATCH_TOP is the directory where patch is copied

Check for conflicts with existing patches as below

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph .

- Rollback any conflicting patches highlighted during one-off patch conflict detection.

- Follow patch conflict resolution steps as necessary in the conflict report. Also refer to Section 3.1.4 for more details.

Related Posts:

Rollback Patch 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)


Applying 21352635: DATABASE PATCH SET UPDATE 11.2.0.4.8 (INCLUDES CPUOCT2015)

libserver11.a:/qksbg.o Patch 12942119 conflicts when applying Oracle 11.2.0.3.0 Patch 20760997: DATABASE PATCH SET UPDATE 11.2.0.3.15 (INCLUDES CPUJUL2015)