minimum downtime opatch link >>> http://abcdba.com/abcdbarachowtoapplymindowntimeopatch
OPATCH_JAVA_ERROR >>> http://oraclepitstop.wordpress.com/2008/11/04/opatch_java_error-an-exception-of-type-opatchexception-has-occurred/
$ cd $ORACLE_HOME/OPatch
$ opatch -help
To list component versions and patches applied to an Oracle Home
================================================
$ opatch lsinventory -detail
opatch lsinventory -details -invPtrLoc [New .loc file location]
For example :
opatch lsinventory -details -invPtrLoc /d01/oracle/DBA/apps/tech_st/10.1.3/oraInst.loc
Use OPatch to list all Oracle homes associated with an oraInventory
================================================
opatch lsinventory -all
to rollback or undo a patch installation
============================
opatch rollback
To rollback specific patch
-----------------------------------
% cd 11710576
% opatch rollback -id 11710576
displays the version of OPatch installed
=============================
opatch version
napply applies the patches in a directory
==============================
opatch napply
This is used while applying a patch that is a bundle of individual patches. napply eliminates the overhead of running opatch multiple times by the administrator. The napply option skips subsets or duplicates if they are already installed.
rolls back the patches using the IDs specified
==================================
opatch nrollback
TO APPLY THE PATCH
===================
Then Go to patch Directory and apply the Opatch.
$ cd 5965763/
$ opatch apply
opatch apply -minimize_downtime
This is specific to Real Application Clusters (RAC) enabled instances (DB tier patches). The -minimize_downtime option allows you to apply a patch by bringing down one database server instance at a time. OPatch applies the patch to the quiesced server instance, the instance is brought back up, and then OPatch moves on to the next database server in a Real Application Clusters pool.
opatch apply -force
-force overrides conflicts with an existing patch by removing the conflicting patch from the system.
Caution: This option should be only used when explicitly it is said safe to be used in the README of the patch.
opatch apply -invPtrLoc <...>
The option -invPtrLoc can be used to specify the oraInst.loc file in case it's not in the default location e.g., /etc/oraInst.loc in Linux. The argument to this option is the location of this file.
query command can be used to find out useful information about the patch
========================================================
opatch query
The query command can be used to find out useful information about the patch
Syntax to be used:
opatch query [-all] [-jre <LOC> ] [-oh <LOC> ] \ [-get_component] [-get_os] [-get_date] [-get_base_bug] \[-is_rolling_patch] [-is_online_patch] \ [-has_sql] [ <Patch Location> ]
all
Retrieves all information about a patch. This is equivalent to setting all available options.
get_base_bug
Retrieves bugs fixed by the patch.
get_component
Retrieves components the patch affects.
get_date
Retrieves the patch creation date and time.
is_online_patch
Indicates true if the patch is an online patch. Otherwise, the option is false.
is_rolling_patch
Indicates true if the patch is a rolling patch. Otherwise, the option is false.
oh
Specifies the Oracle home directory to use instead of the default directory. This takes precedence over the ORACLE_HOME environment variable.
Patch Location
Indicates the path to the patch location. If you do not specify the location, OPatch assumes the current directory is the patch location.