Saturday 6 February 2016

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



No comments:

Post a Comment