Patch - Oracle Patch by Opatch Utility



In this Doc I am appliyimg a patch which is provided by Oracle Support through opatch utility.


$ unzip -d . p10319478_10205_HPUX-IA64*.zip -----this is a example of patch


Archive:  p10319478_10205_HPUX-IA64[1].zip ----Unzip the pacth

   creating: ./10319478/
   creating: ./10319478/files/
   creating: ./10319478/files/lib/
   creating: ./10319478/files/lib/libserver10.a/
  inflating: ./10319478/files/lib/libserver10.a/kzul.o
  inflating: ./10319478/files/lib/libserver10.a/kss.o
  inflating: ./10319478/files/lib/libserver10.a/kstt.o
   creating: ./10319478/etc/
   creating: ./10319478/etc/config/
  inflating: ./10319478/etc/config/inventory.xml
  inflating: ./10319478/etc/config/actions.xml
  inflating: ./10319478/etc/config/deploy.xml
   creating: ./10319478/etc/xml/
  inflating: ./10319478/etc/xml/GenericActions.xml
  inflating: ./10319478/etc/xml/ShiphomeDirectoryStructure.xml
  inflating: ./10319478/README.txt

$ pwd   --- To see the path of patch

/u01/home/oracle/product/10.2.0/OPatch/p10319478
$ cd ..

$ which opatch
./opatch
$
$ opatch apply p10319478/10319478  ------Applying patch through this command

Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/home/oracle/product/10.2.0
Central Inventory : /u01/home/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.5.0
OUI location      : /u01/home/oracle/product/10.2.0/oui
Log file location : /u01/home/oracle/product/10.2.0/cfgtoollogs/opatch/opatch2010-11-27_09-47-53AM.log

Patch history file: /u01/home/oracle/product/10.2.0/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch '10319478' to OH '/u01/home/oracle/product/10.2.0'

Running prerequisite checks...
Problem with accessing response file of "/u01/home/oracle/product/10.2.0/ccr/bin/setupCCR".

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.


Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/u01/home/oracle/product/10.2.0')


Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '10319478' for restore. This might take a while...
Backing up files affected by the patch '10319478' for rollback. This might take a while...

Patching component oracle.rdbms, 10.2.0.5.0...
Updating archive file "/u01/home/oracle/product/10.2.0/lib/libserver10.a"  with "lib/libserver10.a/kzul.o"
Updating archive file "/u01/home/oracle/product/10.2.0/lib/libserver10.a"  with "lib/libserver10.a/kss.o"
Updating archive file "/u01/home/oracle/product/10.2.0/lib/libserver10.a"  with "lib/libserver10.a/kstt.o"
Running make for target ioracle
ApplySession adding interim patch '10319478' to inventory

Verifying the update...
Inventory check OK: Patch ID 10319478 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 10319478 are present in Oracle Home.

The local system has been patched and can be restarted.


OPatch succeeded.
$
$
$ opatch lsinventory   ---- To check patch is applied successful or not this shows the patch
Exception in thread "main" java.lang.NoClassDefFoundError: OsInfo
Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/home/oracle/product/10.2.0
Central Inventory : /u01/home/oracle/oraInventory
   from           : /var/opt/oracle/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.5.0
OUI location      : /u01/home/oracle/product/10.2.0/oui
Log file location : /u01/home/oracle/product/10.2.0/cfgtoollogs/opatch/opatch2010-11-27_09-49-48AM.log

Patch history file: /u01/home/oracle/product/10.2.0/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : /u01/home/oracle/product/10.2.0/cfgtoollogs/opatch/lsinv/lsinventory2010-11-27_09-49-48AM.txt

--------------------------------------------------------------------------------
Installed Top-level Products (4):

Oracle Database 10g                                                                 10.2.0.1.0
Oracle Database 10g Products                                                  10.2.0.1.0
Oracle Database 10g Release 2 Patch Set 3                            10.2.0.4.0
Oracle Database 10g Release 2 Patch Set 4                            10.2.0.5.0
There are 4 products installed in this Oracle Home.


Interim patches (1) :

Patch  10319478     : applied on Sat Nov 27 09:49:23 GMT 2010
Unique Patch ID:  13176627
   Created on 24 Nov 2010, 18:53:54 hrs PST8PDT
   Bugs fixed:
     10319478



--------------------------------------------------------------------------------

OPatch succeeded.


Comments

  1. PrashantD5 July 2012 at 02:37

    Steps provided for opatch (The Unlearned)so easy. I've successfully tested this utility at my end.

    Thanks Alok Sir.


    - Prashant Dixit

    ReplyDelete

Post a Comment

Popular posts from this blog

Key points on Read-Only Instance and Read-Only Database

 In Oracle, both Read-Only Instance and Read-Only Database provide mechanisms to limit data modifications, but they are used in different contexts and for different purposes. Here's a comparison: 1. Read-Only Instance Definition : A read-only instance is a configuration in Oracle Real Application Clusters (RAC) where one or more instances of a multi-instance database are set up to operate in read-only mode. This is typically done in environments with high concurrency for both read and write operations. Key Features : Allows real-time query scaling by dedicating specific instances to read-only operations. Write operations are not allowed on the designated read-only instance, but other instances in the cluster can still handle write operations. Useful in RAC configurations for load balancing , where read workloads can be distributed across multiple read-only instances. Instance-specific: The database remains fully functional (read-write) when accessed through other instances. Us...
Read more

Steps to create database link between Oracle database and SQL Server

 Creating a database link between SQL Server and Oracle allows seamless data exchange between the two systems. Here’s a step-by-step guide: Step 1: Install the Required Drivers Install Oracle Database Gateway for SQL Server (ODG4MS). This acts as a bridge between Oracle and SQL Server. Ensure the Oracle Client is installed on the Oracle database server or the server acting as the gateway. Step 2: Configure the Oracle Database Gateway Locate Configuration Files: Navigate to the $ORACLE_HOME/network/admin directory on the Oracle Gateway server. Edit tnsnames.ora: Add an entry for the database link pointing to the SQL Server database: dg4msql =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = <SQL_SERVER_HOSTNAME>)(PORT = 1521))     (CONNECT_DATA = (SID = dg4msql))     (HS=OK)  -- Required for heterogeneous services   )   Edit listener.ora: Update the Oracle listener configuration to recognize the gateway: SID_LIST_LISTENE...
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo...
Read more