Skip to main content

What is CPU Patch and how to apply it in a RAC Environment

What is CPU Patch and how to apply it in a RAC Environment


What is CPU patch?
A Critical Patch Update is a collection of patches for multiple security vulnerabilities. Critical Patch Update patches are usually cumulative but each advisory describes only the security fixes added since the previous Critical Patch Update advisory. Thus, prior Critical Patch Update advisories should be reviewed for information regarding earlier published security fixes.

When is CPU Patches Released?
CPU patches is released 4 times a year.
January, April, July &October.
Information about the latest CPU Patch can be found in the below link

http://www.oracle.com/technetwork/topics/security/alerts-086861.html

Note: To download the latest CPU patch, one must have a valid oracle support login.

How to apply a Database CPU patch in a RAC Environment?

1} Shutdown the Database instance on Node 1
2} Ensure that the $PATH has the following executables: make, ar, ld, and nm.
export PATH=$PATH:/usr/bin & Also Make sure that your ORACLE_HOME etc is set.
2a) Set your current directory to the directory where the patch is located and then run the OPatch utility by entering the following commands:
2b) unzip p13466801_112030_<platform>.zip
2c) cd 13466801
2d) opatch napply -skip_subset -skip_duplicate
 3} Startup the instance using Srvctl commands
 Repeat the above 3 steps in all the Nodes.

Patch Post-Installation Instructions

After installing the patch, load modified SQL files into the database
Loading Modified SQL Files into the Database
The following steps load modified SQL files into the database. For a RAC environment, perform these steps on only one node.
  1. 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:
2.      cd $ORACLE_HOME/rdbms/admin
3.      sqlplus /nolog
4.      SQL> CONNECT / AS SYSDBA
5.      SQL> STARTUP
6.      SQL> @catbundle.sql cpu apply
7.      SQL> QUIT
The catbundle.sq

l execution is reflected in the dba_registry_history view by a row associated with bundle series CPU.


Note: CPU patches are meant to be applied only for the Database Home& Not the Grid Infrastructure Home

Comments

Post a Comment

Popular posts from this blog

Hard dependency with ip address Oracle RAC Cluster.

Command error out due to hard dependency with ip address [-Node1]/app/grid/oracle/product/11.2.0/grid/bin>./crsctl relocate resource RDBMS_DB -n Node2 CRS-2527: Unable to start 'RDBMS_DB' because it has a 'hard' dependency on 'sDB' CRS-2525: All instances of the resource 'sDB' are already running; relocate is not allowed because the force option was not specified CRS-4000: Command Relocate failed, or completed with errors. [-Node1]/app/grid/oracle/product/11.2.0/grid/bin>./crsctl relocate resource sDB  -n Node2 CRS-2529: Unable to act on 'DB' because that would require stopping or relocating 'LISTENER_DB', but the force option was not specified CRS-4000: Command Relocate failed, or completed with errors. [-Node1]/app/grid/oracle/product/11.2.0/grid/bin>./crsctl relocate resource LISTENER_DB  -n Node2 CRS-2527: Unable to start 'LISTENER_DB' because it has a 'hard' dependency on 'sD...
Post a Comment
Read more

19C NID ( Rename Database)

 [oracle@localhost ~]$ nid DBNEWID: Release 19.0.0.0.0 - Production on Thu Dec 23 00:05:36 2021 Copyright (c) 1982, 2019, Oracle and/or its affiliates.  All rights reserved. Keyword     Description                    (Default) ---------------------------------------------------- TARGET      Username/Password              (NONE) DBNAME      New database name              (NONE) LOGFILE     Output Log                     (NONE) REVERT      Revert failed change           NO SETNAME     Set a new database name only   NO APPEND      Append to output log           NO HELP        Displays these messages    ...
Post a Comment
Read more

ORA-01017/ORA-28000 with AUDIT_TRAIL

With default profile in Oracle 11g, accounts are automatically locked 1 day ( PASSWORD_LOCK_TIME ) after 10 failed login attempt ( FAILED_LOGIN_ATTEMPTS ): SQL > SET lines 200 SQL > SET pages 200 SQL > SELECT * FROM dba_profiles WHERE PROFILE = 'DEFAULT' ORDER BY resource_name; PROFILE                         RESOURCE_NAME                      RESOURCE LIMIT ------------------------------ -------------------------------- -------- ---------------------------------------- DEFAULT                         COMPOSITE_LIMIT                 ...
Post a Comment
Read more