DATABASE PATCH UPGRADE

 

Prerequisites for Apply Patch on Database version 11.2.0.2

 On Windows Server

Sr.no.	Prerequisites	Responsibility
1	Download  patchset  DB  12.1.0.2.0 Patch: 27440294	INFRA
2	Download   OPatch utility release 12.1.0.1.2 or later	DBA
3	Prior to the patch installation, the following checks are performed Conflicts with other patches Conflicts with subset patches (existing patch is a subset of the patch being installed) If a conflict is found, then stop the installation and contact Oracle Support Services. If a subset is found, then continue the installation. All fixes for the subset patch are included in the patch being installed. The subset patches will be automatically rolled back prior to the installation of the new patch.	DBA
4	Back up the current database oracle home that is installed, the %ORACLE_HOME% directory and Oracle inventory under c:\Program files\oracle directory	DBA

Patch Apply Plan for database version 11.2.0.4 on Windows server

Sr. No.	Activity	Responsibility
1	Perform a clean shutdown of all Oracle services (databases, Oracle listeners, Oracle agents, and so on.) that run from the Oracle Home where we install this patch.	DBA
2	Stop all Oracle services, Recovery catalog, ODBC applications, and other applications that use Oracle Client.	DBA
3	Explicitly stop the Distributed Transaction Coordinator service (which is not an Oracle service) if it is running.	DBA
4	If Oracle OLEDB in use, unregister OraOLEDB11.dll. Navigate to the %ORACLE_HOME%\bin directory.	DBA
5	Set the ORACLE_HOME environment variable to the correct Oracle home that needs to be patched.	DBA
6	Go to the directory where we downloaded the patch:  27440294.	DBA
7	Ensure that the directory containing the OPatch script appears in PATH setting. And apply the Patch.	DBA
8	If Oracle OLEDB in use, register OraOLEDB11.dll. Navigate to the %ORACLE_HOME%\bin directory.	DBA
9	After installing the patch  Load modified .sql files into the database as follows: Start the OracleService<SID> and Oracle Listener Services if already not started. Ensure that all database instances running out of the ORACLE_HOME that you just patched are started. For each database instance running on the Oracle home being patched, run the datapatch utility as described in below Table:- Steps Single Tenant (non-CDB/PDB) 1 % sqlplus /nolog 2 SQL> Connect "/as sysdba" 3 SQL> startup 4 SQL> quit 5 % cd %ORACLE_HOME%/OPatch 6 % datapatch -verbose Check the following log files in  %ORACLE_HOME%\sqlpatch\27440294\ for errors:            27440294 _apply_<database SID>_<CDB name>_<timestamp>.log Where database SID is the database SID, CDB name is the name of the multitenant container database, and timestamp is of the form YYYYMMMDD_HH_MM_SS. In addition, you can check the log files for catbundle 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           Where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. Run dpload.sql % sqlplus /nolog SQL> Connect "/as sysdba" SQL> startup SQL>  @?/rdbms/admin/dpload.sql SQL> quit	DBA

ROLLBACK PLAN

Sr. No.	Activity	Responsibility
1	Cleanly shut down all processes running from the ORACLE_HOME (All instances and listeners associated with the Oracle home that you are updating).	DBA
2	Run the OPatch utility specifying the rollback argument as follows: Opatch rollback -id “patch id”	DBA
3	After rollback the patch : Start all database instances and listener running out of the ORACLE_HOME that you just patched.  For each database instance running out of the ORACLE_HOME being patched, connect to the database and run @%ORACLE_HOME%\rdbms\admin\ catbundle_WINBUNDLE_<database SID>_ROLLBACK.sql If catcpu_rollback.sql reports any Invalid Objects, compile the invalid objects by running utlrp.sql	DBA