| Oracle OPatch Version 19c |
|---|
| General Information | ||
| Library Note |
|
|
| Purpose | OPatch is Oracle's patching utility for database, ASM, and Clusterware. | |
| APPLY | ||
| Applies an interim patch to an ORACLE_HOME from the current directory. The patch location can specified using the parameter patch_location. This command does not support System Patch. |
SYNTAXopatch apply [-connectString <List of connect strings>]OPTIONS -all_nodesApply the patch using all-node mode. -connectStringThis option can be used to specify the list of database instances on which the patch needs to be applied. The value for this option is specified as per the following syntax "SID:User:Passwd:Node". The SID is a must, others can be ignored, OPatch takes default values for it. Ex: oracle:dba:dba:mymachine,oracle1::: NOTE: If the system is not part of RAC setup, then to patch just the local node, provide the node name as empty string. -delayIf -retry is specified, this options tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -forceThis option is meaningful with 'silent' option and is used to override the behavior of silent under specific circumstances. -force_conflictIf a conflict exist which prevents the patch from being applied, the -force_conflict flag can be used to apply the patch. OPatch will remove all the conflicting patches before applying the current patch. This will override the 'silent' behavior for conflicts and hence is meaningful only when used with 'silent' option. -initThis option is used to pass parameters to the init script. This script is executed before prerequisite checks are run. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_init_end'. -invPtrLocUsed to locate the oraInst.loc file. Needed when the installation used the -invPtrLoc flag. This should be the path to the oraInst.loc file. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -localPatch the local node, then update inventory of the local node. Do not propagate the patch or inventory update to other nodes. -local_nodeThis option can be used to specify to OPatch the local node name to be used for RAC mode application of the patch. -minimize_downtimeOnly applied to RAC instances. User supplies the order of nodes to be patched. This option cannot be used in conjunction with -local option with a rolling patch. -no_bug_supersetThis option tells OPatch to error out if the current patch's bugs-to-fix is a super-set (or same set) of an installed patch's bugs-fixed in the Oracle Home. -no_inventoryThis option specifies not to update the inventory, it just updates the files in the system. If inventory is readable, then OPatch tries to read the inventory. -no_relinkThe nolink option does not perform any make operations. This option can be used during multiple patch applications and perform the linking step only once. OPatch does not keep track of the make operations it did not perform. It is the job of the OPatch users to make sure the execute OPatch without this option at the end, so that compilation happens once. -no_sysmodThis option specifies not to update the files in the system. It just updates the inventory. It also will not execute the pre and post scripts. -ocmrfGive OPatch the absolute path to the OCM response file to be used for OCM configuration. -silent must be used in conjunction with -ocmrf if Oracle Home doesn't have OCM installed and configured. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -opatch_init_endThis option is used to mark the end of init options. Without this option everything after init till end of the command is passed into init. This option is meaningless without -init option. -opatch_post_endThis option is used to mark the end of post options. Without this option everything after post till end of the command is passed into post. This option is meaningless without -post option. -opatch_pre_endThis option is used to mark the end of pre options. Without this option everything after pre till end of the command is passed into pre. This option is meaningless without -pre option. -postThis option is used to pass parameters to the post script. This script is executed after application of the patch. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_post_end'. -preThis option is used to pass parameters to the pre script. This script is executed before application of the patch. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_pre_end'. -profile_maskIf the patch to be applied specifies WLS patch/patchset as prerequisites, OPatch will read the WLS default patch profile. To have OPatch read non-default patch profile, specify the patch profile name with this option. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -ptlConnectThis option can be used to specify the connect string of the portal schema. -ptlPasswordThis option can be used to specify the password of the portal schema. -ptlSchemaThis option can be used to specify the schema of the portal repository patch. -remote_nodesThis option can be used to specify to OPatch the list of remote nodes to be used for RAC mode application of the patch. The node names are comma separated and without spaces. -reportJust prints out the actions without executing. -retryThis option tells OPatch how many times it should retry in case of an inventory lock failure. -runSqlThis option can be used to specify OPatch to run the sql scripts and sql procedures if they are present in the given patch. -silentThis suppresses any user-interaction. -sqlScriptThis option can be used to specify the custom sql script to be run by OPatch after patching is completed. -verboseThis option prints more OPatch output to the screen as well as to the log file PARAMETERS Patch Location Path to the location for the patch. If the patch location is not specified, then the current directory is taken as the patch location. |
|
| TBD | ||
| CHECKAPPLICABLE | ||
| This operation checks if a given patch is applicable to one or more Oracle Homes. For a Fusion Middleware installation, OPatch will look for Oracle Homes present under the Middleware home and registered with a single defined central inventory. If environment variable MW_HOME (or) 'mw_home' option is not defined and the ORACLE_HOME environment variable or 'oh' option is also not defined then OPatch will run the command on the applicable Middleware Home. If ORACLE_HOME environment variable is defined or the 'oh' option is given, OPatch will run the command on the referenced Oracle Home with precedence given to the 'oh' option. Examples of patches not applicable are: - Patches requiring components that are not installed in the Oracle Home (or) installed but not of the same version. - Files mentioned by patch metadata could not be patched. |
SYNTAXopatch checkApplicable -ph <Patch location>OPTIONS -allhomesThis option will overide all other options involved in the logic of getting the homes for test of 'checkApplicable'. This option ensures that the check is only applied to all registered homes in central inventory. -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -mw_homePath of the Middleware Home. This takes precedence over MW_HOME environment variable. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. This also ensures that the command runs only on this Oracle Home. -phThe location of the patch to be checked if it is applicable. PARAMETERS The location of the patch to be queried |
|
| TBD | ||
| CHECKINSTALLEDONEOFFS | ||
| This operation checks if the given patch(es) are installed on a number of Fusion Middleware Oracle Homes. For a Fusion Middleware installation, OPatch will look for Oracle Homes present under the Middleware home and registered with a single defined central inventory. If environment variable MW_HOME (or) 'mw_home' option is not defined and the ORACLE_HOME environment variable or 'oh' option is also not defined then OPatch will run the command on the applicable Middleware Home. If ORACLE_HOME environment variable is defined or the 'oh' option is given, OPatch will run the command on the referenced Oracle Home with precedence given to the 'oh' option. If 'domain' option is given, the command will be invoked on Fusion Middleware Oracle homes associated with a domain. |
SYNTAXopatch checkInstalledOneOffs -id <List of Patch IDs separated by commas> ]OPTIONS -idA single Patch ID (or) comma separated list of Patch IDs. -domainName of the domain. -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -mw_homePath of the Middleware Home. This takes precedence over MW_HOME environment variable. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. This also ensures that the command runs only on this Oracle Home. PARAMETERS Patch IDs separated by commas |
|
| TBD | ||
| COMPARE | ||
| Allows for comparison between two files generated by the 'opatch lsinv -xml' command. Currently, the command only takes in two such files as input. | SYNTAXopatch compare [<file1> <file2>]OPTIONS -helpThis will bring up this help text. PARAMETERS <file1> <file2> These are the two files that will be compared. Currently, only two file names will be accepted, and these files must have been generated by the 'opatch lsinv -xml' command. |
|
| TBD | ||
| DEPLOY | ||
| This operation deploys the following modified artifacts. 1. Life cycle operations for JEE. 2. SOA composite artifacts. This operation assumes that the patch is already installed in the Oracle Home. So, 'id' option needs to be used to specify the patch for deployment. Please refer the following instructions for life cycle & SOA composite deployment. The -domain <DOMAIN_NAME> option has to be specified along with the -auto option for automated rollout to the Fusion Middleware domain. If only a single domain has been created out of the Oracle Home you can omit specifying the domain name. Only certain patches which have been certified by Oracle Product Support can be rolled out using this command. OPatch will pose questions to query for information necessary for accessing the Fusion Middleware domain. They are Admin Server URL, Admin Server User, Admin Server Password, Node Manager User and Node Manager password. Node Manager User and Node Manager password are not needed for SOA composite deployment. |
SYNTAXopatch deploy -id <ID of the patch installed in Oracle Home>OPTIONS -domainThe name of the Fusion Middleware domain to which the artifacts affected by the patch will be redeployed. -autoThis option is deprecated and is no-op for 'deploy'. -idA single Patch ID that is installed in the Oracle Home. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. For SOA deployment, the following keys are required with the necessary values. 'AdminConfigFile' - Encrypted file for Admin Server user. 'AdminKeyFile' - Encrypted file for Admin Server password. 'AdminServerURL' - Admin Server URL. For encryption files, Please check 'storeUserConfig' WLST command for details. For life cycle deployment, the following keys are required with the necessary values. 'AdminConfigFile' - Encrypted file for Admin Server user. 'AdminKeyFile' - Encrypted file for Admin Server password. 'AdminServerURL - Admin Server URL. 'NodeManagerConfigFile' - Encrypted file for Node Manager user. 'NodeManagerKeyFile' - Encrypted file for Node Manager password. For encryption files, Please check 'storeUserConfig' WLST command for details. The Key, value pair is of the format 'x=y' where 'x' is OPatch understood key and each pair is separated by newline in the property file. This option is typically used for silent operations. -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -mw_homeThe Middleware Home for the Fusion Middleware install. This takes precedence over the environment variable MW_HOME. -ohThe Oracle Home of the Fusion Middleware product which is to be used for the deploy operations. This takes precedence over the environment variable ORACLE_HOME. -reportJust prints out the actions without execution. -silentInvoke the operation in silent mode. Path to custom property file may be provided which will have required inputs as name-value pairs. If required inputs are not found, OPatch willl error out with missing key values. Please check 'property_file' option for more details. PARAMETERS The 'id' option should be used and it mandates that patch be installed in the Oracle Home. |
|
| HELP | ||
| Display OPatch help | opatch -help |
|
C:\Users\oracle>opatch -h |
||
| LISTCOMPOSITES | ||
| This command lists down all the SOA Composites that are deployed to a SOA Server. The option '-name' can be used to shortlist the composites of a specified name. It operates through the Admin Server of the domain which needs to be accessible. In addition, the Node Manager is required to be configured and running on the machines which have the WebLogic Server instances installed and affected by this command. OPatch will query for information necessary for accessing the Fusion Middleware domain such as Admin Server URL, Admin Server User and Admin Server Password. |
SYNTAXopatch listCompositesOPTIONS -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -ohThe Oracle Home to work on. This takes precedence over the environment variable ORACLE_HOME. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch For FMW components, 'AdminConfigFile', 'AdminKeyFile', location can be specified as keys with corresponding files as values. They refer to encrypted, decrypted files for Admin user and Admin password respectively. For encryption files, Please check 'storeUserConfig' WLST command for details. Similarly, Admin Server URL (key as 'AdminServerURL'), can be given as key with corresponding value. The Key, value pair is of the format 'x=y' where 'x' is OPatch understood key and each pair is separated by newline in the property file. -nameThe name of the composites to be shortlisted. -silentInvoke the operation in silent mode. Path to custom property file may be provided which will have required inputs as name-value pairs. If required inputs are not found, OPatch will exit with error message quoting the missing inputs. PARAMETERS There are no required parameters. |
|
C:\app18\OPatch>opatch listcomposites |
||
| LSDOMAINS | ||
| This command produces a list of WebLogic domains that have been created from the application and library artifacts installed in the given Fusion Middleware product Oracle Home. The Middleware Home can be specified by using the 'mw_home' command-line option or by specifying the MW_HOME environment variable (the command-line option has higher precedence). |
SYNTAXopatch lsdomains [-invptrloc <Path to oraInst.loc> ]OPTIONS -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -mw_homePath of the Middleware Home. This takes precedence over MW_HOME environment variable. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. PARAMETERS There are no mandatory parameters defined for this command. |
|
C:\Windows\system32>opatch lsdomains |
||
| LSHOMES | ||
| This command lists all the Oracle Homes pertaining to logical entities such as Host or Domain. For a Host, the list of Oracle Homes is obtained from the machine's central inventory. For a WebLogic domain, the list of homes is limited to product Oracle Homes that are installed within a top-level Middleware Home. If the 'domain' or 'domaindir' option is used the command lists the Oracle Homes that have been used to create or extend the WebLogic domain. If the 'domain' or 'domaindir' option is not given, all the homes registered with the machine's central inventory or the inventory location specified using the 'invPtrLoc' are listed. The Middleware Home can be specified by using the 'mw_home' command-line option or by using MW_HOME environment variable. When the Middleware Home is specified and the 'domain' or 'domaindir' option is not specified this command will list all the Oracle Homes within the Middleware Home that are registered with the machine's central inventory or the specified inventory location. | SYNTAXopatch lshomes [-domain <Name of the domain> | -domaindir <Path to the WebLogic domain> ]OPTIONS -domain The name of the domain. -domaindir The path to the location of the Weblogic domain. -invptrloc Used to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -mw_home Path of the Middleware Home. This takes precedence over MW_HOME environment variable. -oh The reference Oracle Home to work on. This takes precedence over the environment variable ORACLE_HOME. PARAMETERS There are no mandatory parameters for this command. |
|
C:\Windows\system32>opatch lshomes |
||
| LSINV | ||
| Crosscheck installed products and Oracle home directories. List the inventory for a particular $ORACLE_HOME or display all installations that can be found. | SYNTAXopatch lsinventory [-all ] [-all_nodes] [-bugs_fixed <asc | desc> ]OPTIONS -all Report the name and installation directory for each $ORACLE_HOME found. -all_nodes Reports the patches installed on the given Oracle Home in all nodes of the RAC system. It also prints the oracle binary's size and checksum on all nodes. This option cannot be used in conjunction with -all, -detail, -patch. -bugs_fixed Reports bugs fixed by installed patches in a tabular format. Besides the bugs fixed, the report also displays the installed patches, installed times, and bug descriptions. The fixed bugs are sorted per installed patch. Default display is patches in descending order based on installed time and ascending order of bugs within each patch. You can use 'asc' (or) 'desc' with this option to enforce sort order on bugs within each patch. You can use this option with the patch (or) patch_id option to obtain sort orders with installed patches. -delay If -retry is specified, this option tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -detail(s) Report installed products and other details. This option cannot be used in conjunction with all option. -group_by_date This option tells OPatch to group all installed patches by the date they were installed in the Oracle Home. -inactive This option lists all the inactive patches that have been superseded by other superset patch(es) installed in the Oracle Home. -invPtrLoc Used to locate the oraInst.loc file. When the installation used the invPtrLoc flag. This should be the path to the oraInst.loc file. -jre This option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -local This option tells OPatch to display inventory information of the local node only. -oh The oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -patch Lists the patch IDs installed in the Oracle home in ascending (asc) or descending (desc) order, which is the default, based on installed time. -patch_id Lists the patch IDs installed in the oracle home in ascending (asc) or descending (desc) order based on patch numbers. The value defaults to ascending (asc). -ptlConnect This option is used to specify the connect string credentials of the portal schema. -ptlPassword This option is used to specify the password of the portal schema. -ptlSchema This option is used to specify the schema of the portal repository. -property_file The user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -retry This option tells OPatch how many times it should retry in case of an inventory lock failure. -translation_patch Report installed translation patch(es) in a tabular format. The report displays translation patch, unique patch identifier, language code, installed time of the translation patch and base patch for any single row in the table. -xml This option must be followed with an xml filename, and it will generate xml output based on the current Oracle Home inventory into the filename. PARAMETERS This operation does not have any required parameters. |
|
C:\Windows\system32>opatch lsinv |
||
| LSINVENTORY | ||
| Crosscheck installed products, patches, and Oracle home directories and lists the inventory for a particular $ORACLE_HOME or display all installations that can be found. | SYNTAXopatch lsinventory [-all ] [-all_nodes]OPTIONS -all Report the name and installation directory for each $ORACLE_HOME found. -all_nodes Reports the patches installed on the given Oracle Home in all nodes of the RAC system. It also prints the oracle binary's size and checksum on all nodes. This option cannot be used in conjunction with -all, -detail, -patch. -bugs_fixed Reports bugs fixed by installed patches in a tabular format. Besides the bugs fixed, the report also displays the installed patches, installed times, and bug descriptions. The fixed bugs are sorted per installed patch. Default display is patches in descending order based on installed time and ascending order of bugs within each patch. You can use 'asc' (or) 'desc' with this option to enforce sort order on bugs within each patch. You can use this option with the patch (or) patch_id option to obtain sort orders with installed patches. -delay If -retry is specified, this option tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -detail(s) Report installed products and other details. This option cannot be used in conjunction with all option. -group_by_date This option tells OPatch to group all installed patches by the date they were installed in the Oracle Home. -inactive This option lists all the inactive patches that have been superseded by other superset patch(es) installed in the Oracle Home. -invPtrLoc Used to locate the oraInst.loc file. When the installation used the invPtrLoc flag. This should be the path to the oraInst.loc file. -jre This option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -local This option tells OPatch to display inventory information of the local node only. -oh The oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -patch Lists the patch IDs installed in the Oracle home in ascending (asc) or descending (desc) order, which is the default, based on installed time. -patch_id Lists the patch IDs installed in the oracle home in ascending (asc) or descending (desc) order based on patch numbers. The value defaults to ascending (asc). -ptlConnect This option is used to specify the connect string credentials of the portal schema. -ptlPassword This option is used to specify the password of the portal schema. -ptlSchema This option is used to specify the schema of the portal repository. -property_file The user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -retry This option tells OPatch how many times it should retry in case of an inventory lock failure. -translation_patch Report installed translation patch(es) in a tabular format. The report displays translation patch, unique patch identifier, language code, installed time of the translation patch and base patch for any single row in the table. -xml This option must be followed with an xml filename, and it will generate xml output based on the current Oracle Home inventory into the filename. PARAMETERS This operation does not have any required parameters. |
|
-- windows-- linux sudo su - oracle |
||
| LSPATCHES | ||
| List and verify patch metadata specified by patch ID (installed in ORACLE_HOME) or patch location. | SYNTAXopatch lspatches [-bugs] [-id <patch ID> ]OPTIONS -bugs Print bugs info for every patch. -id This option specifies the patch number. It must be registered in the Oracle Home inventory. It can be any numeric sequence or combined with language. Ex. 11111, 11111/zh_CN. It can't support multiple patch IDs. -invPtrLoc Used to locate the oraInst.loc file. When the installation uses the invPtrLoc flag, the value should indicate the path to oraInst.loc file. -jre This option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -oh The oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -qfile Specify the relative path to Oracle Home of the file to determine the latest patch that touches this file. Ex. On Linux: admin/rdbms/catcpu.sql On Windows: admin\rdbms\catcpu.sql OPatch can tell which latest patch touches the file catcpu.sql in Oracle Home. -required This option will print key metadata only. This includes the following metadata: required components, prereq patches, executables to shutdown and support platforms. This option should be accompanied by either option -id <PATCH_ID> or <PATCH_LOCATION>. -verify This option would verify if the specified patch ID or patch location is registered in Oracle Home inventory or not. Besides, it will verify if all patch files are ok in $ORACLE_HOME. This option should be accompanied by either option -id <PATCH_ID> or <PATCH_LOCATION>.This option doesn't support System Patch. Ex. opatch lspatches -id 111 -verify opatch lspatches /scratch/test/111 -verify |
|
C:\app18\OPatch>opatch lspatches |
||
| NAPPLY | ||
| Used to Apply a set of patches one at a time. Use -silent to apply the patches in silent mode. This command doesn't support System Patch. | SYNTAXopatch napply [patch_location] [-id comma-separated list of patch IDs]OPTIONS -all_nodes Apply the patch using all-node mode. -connectString This option can be used to specify the list of database instances on which the patch needs to be applied. The value for this option is specified as per the following syntax "SID:User:Passwd:Node". The SID is a must, others can be ignored, OPatch takes default values for it. Ex: oracle:dba:dba:mymachine,oracle1::: NOTE: If the system is not part of RAC setup, then to patch just the local node, provide the node name as empty string. -delay If -retry is specified, this options tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -force This option is meaningful with 'silent' option and is used to override the behavior of silent under specific circumstances. -force_conflict If a conflict exist which prevents the patch from being applied, the -force_conflict flag can be used to apply the patch. OPatch will remove all the conflicting patches before applying the current patch. This will override the 'silent' behavior for conflicts and hence is meaningful only when used with 'silent' option. -id Use 'lsinventory' option to display all patch ids. Each one-off patch is indicated by its id. A comma separated list of patches can be given to select the patches to be applied. For translation patches, the patch id should be of the format <Patch ID>/<Language code>. -idFile The input to be given is a file location that contains a list of apply patch ids separated by commas or white spaces. This option cannot to be in conjunction with 'id' option. For translation patches, the patch id should be of the format <Patch ID>/<Language code>. -init This option is used to pass parameters to the init script. This script is executed before prerequisite checks are run. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to init scripts of all patches being applied. This option should be ended by option 'opatch_init_end'. -invPtrLoc Used to locate the oraInst.loc file. Needed when the installation used the -invPtrLoc flag. This should be the path to the oraInst.loc file. -jre This option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -local Patch the local node, then update inventory of the local node. Do not propagate the patch or inventory update to other nodes. -local_node This option can be used to specify to OPatch the local node name to be used for RAC mode application of the patch. -minimize_downtime Only applied to RAC instances. User supplies the order of nodes to be patched. This option cannot be used in conjunction with -local option with a rolling patch. -no_bug_superset This option tells OPatch to error out if the current patch's bugs-to-fix is a super-set (or same set) of an installed patch's bugs-fixed in the Oracle Home. -no_inventory Bypass the inventory for reading and updates. -no_relink The nolink option does not perform any make operations. This option can be used during multiple patch. applications and perform the linking step only once. OPatch does not keep track of the make operations it did not perform. It is the job of the OPatch users to make sure the execute OPatch without this option at the end, so that compilation happens once. -no_sysmod This option specifies not to update the files in the system. It just updates the inventory. It also will not execute the pre and post scripts. -ocmrf Give OPatch the absolute path to the OCM response file to be used for OCM configuration. -silent must be used in conjunction with -ocmrf if Oracle Home doesn't have OCM installed and configured. -oh The oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -opatch_init_end This option is used to mark the end of init options. Without this option everything after init till end of the command is passed into init. This option is meaningless without -init option. -opatch_post_end This option is used to mark the end of post options. Without this option everything after post till end of the command is passed into post. This option is meaningless without -post option. -opatch_pre_end This option is used to mark the end of pre options. Without this option everything after pre till end of the command is passed into pre. This option is meaningless without -pre option. -phBaseDir Used to specify a directory containing patch directories (or) zip files. -phBaseFile If <patch_location> is not specified, use this option to point OPatch to a file containing a list of patches to be n-applied. Each line in the file points to a location of a patch. -ptlConnect This option can be used to specify the connect string of the portal schema. -ptlPassword This option can be used to specify the password of the portal schema. -ptlSchema This option can be used to specify the schema of the portal repository patch. -post This option is used to pass parameters to the post script. This script is executed after application of the patch. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to post scripts of all patches being applied. This option should be ended by option 'opatch_post_end'. -pre This option is used to pass parameters to the pre script. This script is executed before application of the patch. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to pre scripts of all patches being applied. This option should be ended by option 'opatch_pre_end'. -profile_mask If the patch to be applied specifies WLS patch/patchset as prerequisites, OPatch will read the WLS default patch profile. To have OPatch read non-default patch profile, specify the patch profile name with this option. -property_file The user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -remote_nodes This option can be used to specify to OPatch the list of remote nodes to be used for RAC mode application of the patch. The node names are comma separated and without spaces. -report Just prints out the actions without executing. -retry This option tells OPatch how many times it should retry in case of an inventory lock failure. -runSql This option can be used to specify OPatch to run the sql scripts and sql procedures if they are present in the given patch. -silent This suppresses any user-interaction. -skip_duplicate This skips patches to be applied that are duplicates of other patches installed in the Oracle Home. Two patches are duplicates if they fix the same set of bugs. -skip_subset This skips patches to be applied that are subset of other patches installed in the Oracle Home. One patch is a subset of another patch if the former fixes a subset of bugs fixed by the latter. -sqlScript This option can be used to specify the custom sql script to be run by OPatch after patching is completed. -verbose This option prints more OPatch output to the screen as well as to the log file. Example: 'opatch napply <patch_location>' to apply all patches under <patch_location> directory 'opatch napply <patch_location> -id 1,2,3' to apply patches 1, 2, and 3 which are present under <patch_location> directory. 'opatch napply <patch_location> -skip_subset -skip_duplicate' to apply all patches under <patch_location> directory. OPatch will skip duplicate patches and subset patches (patches under <patch_location> that are subsets of patches installed in the Oracle Home). 'opatch napply <patch_location> -id 1,2,3 -skip_subset -skip_duplicate' to apply patches 1, 2, and 3 which are under <patch_location> diretory. OPatch will skip duplicate patches and subset patches (patches under <patch_location> that are subsets of patches installed in the Oracle Home). 'opatch napply <patch_location> -idfile /tmp/list.txt' where list.txt contains a list of patch IDs to be applied. The list should be separated by a space or comma. For example: 1 2 3. 'opatch napply <patch_location> -id 1/fr,2/de' to apply patches 1 (french patch), 1 (german patch) which are present in the <patch_location> directory. |
|
| TBD | ||
| NROLLBACK | ||
| Used to Rollback a set of patches one at a time. Use -silent to Rollback the patches in silent mode. | SYNTAXopatch nrollback -id <comma-separated list of patch IDs>OPTIONS -all_nodesRollback the patch using all-nodes mode. -connectStringThis option can be used to specify the list of database instances on which the patch needs to be applied. The value for this option is specified as per the following syntax "SID:User:Passwd:Node". The SID is a must, others can be ignored, OPatch takes default values for it. Ex: oracle:dba:dba:mymachine,oracle1::: NOTE: If the system is not part of RAC setup, then to patch just the local node, provide the node name as empty string. -delayIf -retry is specified, this option tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -id Use 'lsinventory' option to display all patch ids. Each one-off patch is indicated by its id. To rollback a patch the id for that patch must be supplied. A comma separated list of patches to be rolled back must be given. For translation patches, the patch id should be of the format <Patch ID>/<Language code> (ex: 1234/fr) -idFileUse 'lsinventory' option to display all patch ids. Each one-off patch is indicated by its id. To rollback a patch, the id for that patch must be supplied. The input to be given is a file location that contains a list of rollback patch ids separated by commas or white spaces. For translation patches, the patch id should be of the format <Patch ID>/<Language code>. This option cannot to be in conjunction with 'id' option. -initThis option is used to pass parameters to the init script. This script is executed before prerequisite checks are run. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to init scripts of all patches being rolled back. This option should be ended by option 'opatch_init_end'. -invPtrLocUsed to locate the oraInst.loc file. Needed when the installation used the invPtrLoc flag. This should be the path to the oraInst.loc file. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -localRoll back then update inventory of the local node. Do not propagate the patch or inventory update to other nodes. -local_nodeThis option can be used to specify to OPatch the local node name to be used for RAC mode rollback of the patch. -no_inventoryThis option specifies not to update the inventory, it just updates the files in the system. If inventory is readable, then OPatch tries to read the inventory. NOTE: -phBaseDir or -phBaseFile has to be used to specify the patch location(s). -no_relinkDo not perform the make operations in the patch. This option can be used during multiple patch removals and perform the compilation step only once. -no_sysmodThis option specifies not to update the files in the system. It just updates the inventory. It also will not execute the pre and post scripts. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -opatch_init_endThis option is used to mark the end of init options. Without this option everything after init till end of the command is passed into init. This option is meaningless without -init option. -opatch_post_endThis option is used to mark the end of post options. Without this option everything after post till end of the command is passed into post. This option is meaningless without -post option. -opatch_pre_endThis option is used to mark the end of pre options. Without this option everything after pre till end of the command is passed into pre. This option is meaningless without -pre option. -postThis option is used to pass parameters to the post script. This script is executed after removal of the patch. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to post scripts of all patches being rolled back. This option should be ended by option 'opatch_post_end'. -preThis option is used to pass parameters to the pre script. This script is executed before removal of the patch. The value for this option have to be enclosed in double quotes. The parameters will be common parameters which will be passed to pre scripts of all patches being rolled back. This option should be ended by option 'opatch_pre_end'. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -ptlConnectThis option can be used to specify the connect string of the portal schema. -ptlPasswordThis option can be used to specify the password of the portal schema. -ptlSchemaThis option can be used to specify the schema of the portal repository patch. -remote_nodesThis option can be used to specify to OPatch the list of remote nodes to be used for RAC mode rollback of the patch. The node names are comma separated and without spaces. -reportJust prints out the actions, without executing. -retryThis option tells OPatch how many times should retry in case of an inventory lock failure. -runSqlThis option can be used to specify OPatch to run the sql scripts and sql procedures if they are present in the given patch. -silent This suppresses any user-interaction and defaults any Y|N question to Y. This option is not supported on RAC yet. -sqlScriptThis option can be used to specify the custom sql script to be run by OPatch after patching is completed. -verboseThis option prints more OPatch output to the screen as well as to the log file. Example: 'opatch nrollback -id 1,2,3' to roll back patches 1, 2, and 3 that have been installed in the Oracle Home.'opatch nrollback -id 1/fr,2/de to rollback patches 1 with language 'fr', 2 with language 'de' that have been installed in the Oracle Home. |
|
| TBD | ||
| PREREQ | ||
| This operation runs the prerequisite checks on an ORACLE_HOME. This command doesn't support System Patch. | SYNTAXopatch prereq <command> [-id <Comma separated list of patch IDs>]COMMANDS CheckActiveFilesAndExecutablesCheck if there are any file(s) that are active, which are touched by the patch to be applied or rolled back. CheckActiveServicesCheck for the services that are active. Note: Applicable for Windows platforms only. CheckApplicableCheck for the presence of the required components in the ORACLE_HOME and check if all the actions of the given patch(es) are applicable. CheckApplicableProductCheck if the patch is applicable for the given Oracle Home. If the patch is marked for stand-alone homes, then it can not be applied on normal oui-based home and vice versa. Also, a patch can be marked as a hybrid patch, where it is applicable for both homes. CheckCentralInventoryForOHCheck if the given ORACLE_HOME is registered in the central inventory specified by the oraInst.loc file. CheckCentralInventoryForRWSessionCheck if a RW (read-write) session can be created for the given central inventory. CheckCentralInventoryLocationValidate the Central Inventory location. Check if it has the correct directory structure and has the inventory.xml with read permissions. CheckComponentsCheck for the presence of the required components in the ORACLE_HOME. CheckConflictAgainstOHCheck if there are any conflicts between the patch(es) to be applied and the patch(es) in the OH. CheckConflictAgainstOHWithDetailCheck if there are any conflicts between the patch(es) to be applied and the patch(es) in the OH, by giving out the detailed information about the conflicts/supersets. CheckConflictAmongPatchesCheck if there are any conflicts among the patch(es) to be applied. CheckConflictAmongPatchesWithDetailCheck if there are any conflicts among the patch(es) to be applied, by giving out the detailed information about the conflicts/supersets. CheckFileVersionsCheck if the copy actions of Fusion Applications patch(es) have alleast one or more file version(s) greater than the version(s) installed in the Oracle Home. CheckFusionAppsCompatibleCheck if OUI for the Oracle Home supports patching of Fusion applications. CheckForCRSHomeIfRACCheck if the given Central Inventory has a CRS Home registered with it, if it is a RAC setup. CheckForIdenticalPatchInOracleHomeCheck if the given list of patch(es) are identical with respect to the patch(es) installed in the Oracle Home. CheckForInputValuesCheck if the input values provided to OPatch are enough for OPatch to proceed further. CheckForNoOpPatchesCheck if any of the patch(es) provided by the user are no-op. patches. A no-op patch. cannot be applied to the Oracle Home and can be skipped. This prereq will fail for no-op. patches. CheckIfOHLockedForPatchingCheck if the ORACLE_HOME is locked for patching by any previous unsuccessful OPatch Session. CheckInstalledOneOffsCheck if all the patches provided by the user to rollback are present in the given Oracle Home. CheckMinimumOPatchVersionCheck if all the patches provided by the user satisfy the requirement of minimum OPatch version for the OPatch currently being used. CheckOneOffSupersetCheck if the given input Fusion Applications patch list are all candidates for one-off (or) singleton supersets. This prereq does not do any checks among the input patch list. CheckOracleHomeCheck if the given ORACLE_HOME is valid. Check if it has the inventory files with proper permissions. CheckOraInstLocationCheck if the oraInst.loc file is proper and has the read permissions. CheckOUILocationCheck the ORACLE_HOME for the presence of OUI. CheckOUIVersionCompatibleCheck if the OUI in the ORACLE_HOME is compatible for the OPatch. CheckPatchApplicableOnCurrentPlatformCheck if the given patch(es) is applicable on the current platform. CheckPatchApplyDependentsCheck if all the patch(es) required by the patch(es) currently being installed is present in the Oracle Home or not. CheckPatchRollbackDependentsCheck if there are any patch(es) in the Oracle Home that are depending on the patch(es) being currently rolled back. CheckPatchShipHomeCheck if the given patch to be applied has the proper structure and has the correct permissions for all the files. CheckRACNodeListCheck if all the nodes in the RAC setup are valid, up and reachable. CheckRemoteCommandInvocableCheck if commands can be invoked on the remote machines. CheckRemoteCopyAndRemoveCheck if files can be copied to and removed from the remote machines. CheckRequiredLibsCheck if all the required OUI libraries are present in the given ORACLE_HOME. CheckRollbackableCheck if the given patch(es) can be rolled back from the ORACLE_HOME. CheckRollbackSidCheck if the given patch(es) can be rolled back from the ORACLE_HOME using the given SIDs. CheckStandAloneHomeCheck if the Oracle Home is a stand-alone home or a normal oui-based home. CheckSystemCommandAvailableCheck if all the commands required for applying or rolling back the given patch are present in the system. CheckSystemSpaceCheck if enough system space is available for the patch(es) to be applied. CheckUserAdminPrivilegeCheck is the user is 'root'. Note: OPatch should not be invoked by 'root', if so then this check fails. CheckPatchingModelCheck if the patching model of all incoming patch(es) is compatible with that of the Oracle Home. OPTIONS -connectString This option can be used to specify the list of database instances and remote nodes. The value for this option is specified as per the following syntax "SID:User:Passwd:Node". The SID is a must, others can be ignored, OPatch takes default values for it. Ex: oracle:dba:dba:mymachine,oracle1::: NOTE: If the system is not part of RAC setup, then to specify just the local node, provide the node name as empty string. This option cannot be used along with 'sid' option. -idThis option can be used to specify the patch IDs of all the patches that are to be rollbacked from the given OH. -invPtrLocUsed to locate the oraInst.loc file. Needed when the installation used the -invPtrLoc flag. This should be the path to the oraInst.loc file. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -local_nodeThis option can be used to specify to OPatch the local node name to be used for RAC mode application of the patch. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -phThis option can be used to specify the path to the patch location. Ex: /tmp/101010-phBaseDirThis option can be used to specify the path to base dir where all the patches to be applied are kept. Note: The directory should contain only non-duplicate patches in zipped or unzipped format. -phBaseFileThis option can be used to specify complete path to the file containing the location of the patches to be applied. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -remote_nodesThis option can be used to specify to OPatch the list of remote nodes to be used for RAC mode application of the patch. The node names are comma separated and without spaces. -sidThis option can be used to specify the SIDs of the database instances. This option can be used only for local system operations. |
|
| TBD | ||
| QUERY | ||
| This operation loads and prints out various information about a patch. Parameter patch_location points to where a patch is located. For example, if you specify "path", there should be sub-dir. "etc/config" under "path". | SYNTAXopatch query [-all] [-is_auto_patch] [-is_translatable_patch]OPTIONS -allGet everything available about a patch. This is equivalent to setting all available options.This command doesn't support System Patch. -is_auto_patchThis option says 'true' if the patch is auto-enabled, 'false' otherwise. This command doesn't support System Patch. -is_system_patchThis option says 'true' if the patch is a System Patch, 'false' otherwise. -is_translatable_patchThis option says 'true' if the patch is translatable, 'false' otherwise. This option doesn't support System Patch. -get_base_bugGet bugs fixed by the patch. This option doesn't support System Patch. -get_componentGet components touched by the patch. This option doesn't support System Patch. -get_dateGet patch creation date and time. This option doesn't support System Patch. -get_osGet platforms for which this patch could be applied. This option doesn't support System Patch. -get_patch_typeGet the patch type. This command doesn't support System Patch. -get_patching_modelGet the patching model. This option doesn't support System Patch. -get_patch_languageGet the language supported by the patch. This option doesn't support System Patch. -get_product_familyGet the product family to which the patch belongs. This option doesn't support System Patch. -has_sqlThis option says 'true' if the patch has sql related actions, 'false' otherwise. This option doesn't support System Patch. -is_sql_patchThis option says 'true' if the patch is a sql patch, 'false' otherwise. This command doesn't support System Patch. -is_online_patchThis option says 'true' if the patch is a online patch, 'false' otherwise. This option doesn't support System Patch. -is_rolling_patchThis option says 'true' if the patch is a rolling patch, 'false' otherwise. This option doesn't support System Patch. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. PARAMETERS The location of the patch to be queried. If the patch location is not specified, then the current directory is taken as the patch location. |
|
| TBD | ||
| ROLLBACK | ||
| Rollback an existing one-off patch indicated by the reference-id. This command doesn't support System Patch. | SYNTAXopatch rollback -id <ID> [-connectString <List of connect strings>]OPTIONS -all_nodesRoll back the patch using all-nodes mode. -connectStringThis option can be used to specify the list of database instances on which the patch needs to be applied. The value for this option is specified as per the following syntax "SID:User:Passwd:Node". The SID is a must, others can be ignored, OPatch takes default values for it. Ex: oracle:dba:dba:mymachine,oracle1:::NOTE: If the system is not part of RAC setup, then to patch just the local node, provide the node name as empty string. -delayIf -retry is specified, this option tells OPatch how many seconds it should wait before attempting to lock inventory again in case of a previous failure. -idUse 'lsinventory' option to display all patch id's. Each one-off patch is indicated by its id. To roll back a patch the id for that patch must be supplied. For translation patches, Please specify <id>/<language code> (ex: 1234/fr). -initThis option is used to pass parameters to the init script. This script is executed before prerequisite checks are run. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_init_end'. -invPtrLocUsed to locate the oraInst.loc file. Needed when the installation used the invPtrLoc flag. This should be the path to the oraInst.loc file. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -localRoll back then update inventory of the local node. Do not propagate the patch or inventory update to other nodes. -local_nodeThis option can be used to specify to OPatch the local node name to be used for RAC mode rollback of the patch. -no_inventoryThis option specifies not to update the inventory, it just updates the files in the system. If inventory is readable, then OPatch tries to read the inventory. NOTE: ph has to be used to specify the patch location. -no_relinkDo not perform the make operations in the patch. This option can be used during multiple patch removals and perform the compilation step only once. -no_sysmodThis option specifies not to update the files in the system. It just updates the inventory. It also will not execute the pre and post scripts. -ohThe oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -opatch_init_endThis option is used to mark the end of init options. Without this option everything after init till end of the command is passed into init. This option is meaningless without -init option. -opatch_post_endThis option is used to mark the end of post options.Without this option everything after post till end of the command is passed into post. This option is meaningless without -post option. -opatch_pre_endThis option is used to mark the end of pre options. Without this option everything after pre till end of the command is passed into pre. This option is meaningless without -pre option. -phSpecify the valid patch directory area. Rollback will use the command types found in the patch directory to identify what commands are to be used for the current operating system. -postThis option is used to pass parameters to the post script. This script is executed after removal of the patch. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_post_end'. -preThis option is used to pass parameters to the pre script. This script is executed before removal of the patch. The value for this option have to be enclosed in double quotes. This option should be ended by option 'opatch_pre_end'. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. -ptlConnectThis option can be used to specify the connect string of the portal schema. -ptlPasswordThis option can be used to specify the password of the portal schema. -ptlSchemaThis option can be used to specify the schema of the portal repository patch. -remote_nodesThis option can be used to specify to OPatch the list of remote nodes to be used for RAC mode rollback of the patch. The node names are comma separated and without spaces -reportJust prints out the actions, without executing. -retryThis option tells OPatch how many times should retry in case of an inventory lock failure. -runSqlThis option can be used to specify OPatch to run the sql scripts and sql procedures if they are present in the given patch. -silentThis suppresses any user-interaction and defaults any Y|N question to Y. This option is not supported on RAC yet. -sqlScriptThis option can be used to specify the custom sql script to be run by OPatch after patching is completed. -verboseThis option prints more OPatch output to the screen as well as to the log file -all_subpatchesThis option is valid ONLY for composite patches. It allows the user to rollback all subpatches of a composite series in one shot. PARAMETERS Patch ID of the patch to be rolled back unless the command is invoked within a patch area. For translation patches, it will be <Patch ID>/<Language code>. |
|
| TBD | ||
| START | ||
| This command allows Fusion Middleware runtime entities to be started. This command operates through the Admin Server of the domain which needs to be accessible.
In addition, the Node Manager is required to be configured and running on the machines which have the WebLogic Server instances installed and affected by this command. OPatch will pose questions to query for information necessary for accessing the Fusion Middleware domain such as Admin Server URL, Admin Server User, Admin Server Password, Node Manager User and Node Manager Password. |
SYNTAXopatch start [-domain <DOMAIN_NAME> ]OPTIONS -domainThe name of the Fusion Middleware domain for which the specified targets will be started. -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -ohThe Oracle Home to work on. This takes precedence over the environment variable ORACLE_HOME. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch For FMW components, 'AdminConfigFile', 'AdminKeyFile', 'NodeManagerConfigFile' and 'NodeManagerKeyFile' location can be specified as keys with corresponding files as values. They refer to encrypted, decrypted files for Admin user, Admin password, Node Manager user and Node Manager password. Similarly, Admin Server URL (key as AdminServerURL), Domain Home (key as DomainHome) and Applications Directory (key as ApplicationsDir) can be given as keys with corresponding values. The Key, value pair is of the format 'x=y' where 'x' is OPatch understood key and each pair is separated by newline in the property file. For encryption files, Please check 'storeUserConfig' WLST command for details. -reportJust prints out the actions without execution. -targetsThe list of targets to be started. -target_typeThe type of target to be started. Only supported target type is 'fmwServer'. This option is *deprecated*. -silentInvoke the operation in silent mode. Path to custom property file may be provided which will have required inputs as name-value pairs. If required inputs are not found, OPatch will exit with error message quoting the missing inputs. PARAMETERS The required parameter is targets |
|
C:\app18\OPatch>opatch start report |
||
| STOP | ||
| This command allows Fusion Middleware runtime entities to be stopped. This command operates through the Admin Server of the domain which needs to be accessible.
In addition, the Node Manager is required to be configured and running on the machines which have the WebLogic Server instances installed and affected by this command. OPatch will pose questions to query for information necessary for accessing the Fusion Middleware domain such as Admin Server URL, Admin Server User, Admin Server Password, Node Manager User and Node Manager Password. |
SYNTAXopatch stop [-domain <DOMAIN_NAME> ]OPTIONS -domainThe name of the Fusion Middleware domain for which the specified targets will be stopped. -invptrlocUsed to locate the oraInst.loc file. Needed when the installation uses the -invPtrLoc flag. This should be the path to the oraInst.loc file. -ohThe Oracle Home to work on. This takes precedence over the environment variable ORACLE_HOME. -property_fileThe user defined property file for OPatch to use. The path to the property file should be absolute. This property file takes precedence over the one that is supplied with OPatch. For FMW components, 'AdminConfigFile', 'AdminKeyFile', 'NodeManagerConfigFile' and 'NodeManagerKeyFile' location can be specified as keys with corresponding files as values. They refer to encrypted, decrypted files for Admin user, Admin password, Node Manager user and Node Manager password. Similarly, Admin Server URL (key as AdminServerURL), Domain Home (key as DomainHome) and Applications Directory (key as ApplicationsDir) can be given as keys with corresponding values. The Key, value pair is of the format 'x=y' where 'x' is OPatch understood key and each pair is separated by newline in the property file. For encryption files, Please check 'storeUserConfig' WLST command for details. -reportJust prints out the actions without execution. -targetsThe list of targets to be stopped. -target_typeThe type of target to be stopped. Only supported target type is 'fmwServer'. This option is *deprecated*. -silentInvoke the operation in silent mode. Path to custom property file may be provided which will have required inputs as name-value pairs. If required inputs are not found, OPatch will exit with error message quoting the missing inputs. PARAMETERS The required parameter is targets |
|
C:\app18\OPatch>opatch stop report |
||
| UTIL | ||
| This operation invokes the chosen utilities on an ORACLE_HOME. This command does not support System Patch. | SYNTAXopatch util [ -help ] [ COMMAND ]Use opatch util [ COMMAND ] -help to get help on a particular command. COMMANDS ApplySqlApply sql, sql procedure related actions for patches, which are already applied using Apply or NApply operation. CheckMinimumOpatchVersionCheck if patch is compatible with the given user input version. CheckComponentsCheck if the given patch is suitable for the Oracle Homes registered in the central inventory by components check. CleanupRemove the backup for restore area of the given patch or for all the patches. CopyListedDirsRecursively copy all directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_dirs.txt to remote nodes. CopyListedDirsTestRecursively copy a single directory to remote nodes. CopyListedFilesCopy all files listed in ORACLE_HOME/.patch_storage/<ID>/rac/copy_files.txt to remote nodes. CopyListedFilesTestCopy a single file to remote nodes. DisableOnlinePatchDisable and remove the specified online patch(es) on the given database instances. EnableOnlinePatchInstall and enable the specified online patch(es) on the given database instances. GetPatchLevelReturn the patching level on Local Grid Home. InstallOCMInstall and configure OCM. IsSharedReturns true if running on shared environment, else it returns false. LoadXMLPrompt for path/name of the XML file, then check if the XML is correct. RemoveListedDirsRecursively remote directories listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_dirs.txt on remote nodes. RemoveListedDirsTestRecursively remove a directory on remote nodes. RemoveListedFilesRemove files listed in ORACLE_HOME/.patch_storage/<ID>/rac/remove_files.txt on remote nodes. RemoveListedFilesTestRemove a single file on remote nodes. RestoreOHRestore the OracleHome to the previous state. RollbackSqlRollback sql, sql procedure related actions for patches, which are already rolled back using Rollback or NRollback operation. RunAnyCommandRun any command on remote nodes. RunLocalMakeInvoke re-link on the local node. Commands are stored in ORACLE_HOME/.patch_storage/<ID>/make.txt. RunRemoteMakeInvoke re-link on remote nodes. Commands are stored in ORACLE_HOME/.patch_storage/<ID>/rac/make_cmds.txt. SaveConfigurationSnapshotSave configuration snapshot of current GI home to specified file. ORACLE_HOME shall point to GI home. Default snapshot file is ORACLE_HOME/cfgtoollogs/opatch/sysconfig/configData.txt. UpdateRemoteNodesPropagate/Remove files/directories to/on remote nodes using files under ORACLE_HOME/.patch_storage/<ID>/rac/*. UpdateOPatchVersionUpdate the version of OPatch in the inventory of Oracle Home. VerifyUsing the defined ORACLE_HOME and given patch location via -ph, the program will check to make sure the patch was applied to the ORACLE_HOME. Example: 'opatch util verify -ph /tmp/patchLoc' |
|
c:\> set oracle_home=c:\app\oracle\product\12.1.0\dbhome_1 |
||
| VERSION | ||
| Print the version of OPatch for a particular $ORACLE_HOME or display all OPatch version in the Central Inventory. | SYNTAXopatch version [-all]OPTIONS -allThis option displays versions of OPatch(es) of all Oracle Homes registered in the Central Inventory. -invPtrLocUsed to locate the oraInst.loc file. When the installation used the invPtrLoc flag. This should be the path to the oraInst.loc file. -jreThis option tells OPatch to use JRE (java) from the specified location instead of the default location under Oracle Home. -ohThe Oracle home to work on. This takes precedence over the environment variable ORACLE_HOME. -v2cThe standard 5-digit version to compare. If this option is specified with an valid version which made by no more than 5 numbers separated by '.', those oracle homes with valid version will be break up to two parts, one is those oracle homes which have opatch version higher or equal to the value of this option, and the other is those with lower version. -phThe patch location from where the Minimum OPatch Version (if defined) will be picked. If a valid patch location is provided, will take the required minimum opatch version from the patch and set it as the standard opatch version to be compared to. -ohsList of Oracle Homes to be considered. Please provide them separated by commas. -help (or) -hDisplay valid options can be attached to this opereation. PARAMETERS This operation does not have any required parameters. |
|
c:\> set oracle_home=c:\u01\orahome19\WINDOWS.X64_193000_db_home |
||
| Patching the Opatch Utility | ||
| Patching OPATCH | From time-to-time it may be necessary to patch the OPatch utility in order to apply the most recent patches.
When you need to visit Oracle Support and look for patch 6880880. This patch page will let you select your version and operating system and download the most recent OPatch for your version. Copy the a staging directory, unzip it to read the readme file and then follow the readme file's directions which will likely be to copy the .zip file to $ORACLE_HOME and unzip it there after first making a backup copy of the files currently in the $ORACLE_HOME/OPatch directory. |
|
| Related Topics |
| Built-in Functions |
| Built-in Packages |
| DBMS_OPTIM_BUNDLE |
| DBMS_QOPATCH |
| What's New In 21c |
| What's New In 26ai |
| This site is maintained by Daniel Morgan. Last Updated: | This site is protected by copyright and trademark laws under U.S. and International law. © 1998-2026 Daniel A. Morgan All Rights Reserved | ||||||||
|
|
|||||||||