Opatch log file location

This option can be used to specify the list of database instances and remote nodes. Example: oracle:dba:dba:mymachine,oracleNOTE: 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.

Needed when the installation used the -invPtrLoc flag. This option can be used to specify to OPatch the local node name to be used for RAC mode application of the patch.

This option can be used to specify the path to the base directory where all the patches to be applied are kept. Note: The directory should contain only non-duplicate patches in zipped or unzipped format.

This option can be used to specify complete path to the file containing the location of the patches to be applied. The user defined property file for OPatch to use. This property file takes precedence over the one that is supplied with OPatch. This option can be used to specify the SIDs of the database instances. This option can be used only for local system operations. Table A util Commands. Check if the given patch is suitable for the product e. Save configuration snapshot of current GI home to specified file.

Table A-2 apply Command Options Option Description delay Specifies how many seconds to wait before attempting to lock the inventory in the case of a previous failure. Options Table A-3 describes the options available for the lsinventory command. Table A-4 lspatches Command Options Option Description bugs Prints out bugs in addition to the summary id This option specifies the patch number.

Table A-5 napply Command Options Option Description delay Specifies how many seconds to wait before attempting to lock the inventory again for a previous failure. Table A-6 nrollback Command Options Option Description delay If you use the retry option with the rollback command, specifies how many seconds OPatch should wait before attempting to lock the inventory again if a previous failure occurs. Table A-7 rollback Command Options Option Description delay If you use the retry option with the rollback command, specifies how many seconds OPatch should wait before attempting to lock the inventory again if a previous failure occurs.

You can use this option for Oracle Real Application Clusters environments. This is equivalent to setting all available options. This option does not support System Patch. Otherwise, the option is false. Please provide them separated by commas help Display valid options can be attached to this operation. Table A prereq Commands Command Description CheckActiveFilesAndExecutables Check if there are any file s that are active, which are touched by the patch to be applied or rolled back.

CheckActiveServices Check for the services that are active. Note: Applicable for Windows platforms only. CheckConflictAmongPatches Check if there are any conflicts among the patch es to be applied. CheckOneOffSuperset Check if the given input Fusion Applications patch list are all candidates for one-off or singleton supersets.

CheckPatchShipHome Check if the given patch to be applied has the proper structure and has the correct permissions for all the files. CheckRemoteCommandInvocable Check if commands can be invoked on the remote machines. CheckSystemCommandAvailable Check if all the commands required for applying or rolling back the given patch are present in the system. CheckSystemSpace Check if enough system space is available for the patch es to be applied.

CheckUserAdminPrivilege Check is the user is 'root'. Note: OPatch should not be invoked by 'root', if so then this check fails. Table A prereq Options Option Description connectString This option can be used to specify the list of database instances and remote nodes.

CheckComponents Check if the given patch is suitable for the product e. Cleanup Remove the backup for restore area of the given patch or for all the patches. DisableOnlinePatch Disable and remove the specified online patch es on the given database instances. EnableOnlinePatch Install and enable the specified online patch es on the given database instances.

Compare two files generated by the opatch lsinventory -xml command. Lists what is currently installed on the system. Prints a summary of all installed patches. Installs n number of patches. Rolls back patches from several product e. Queries a given patch for specific details. Prints the current version of the patch tool. Specifies the order of nodes that OPatch should patch. Prints the action to the screen without executing it. Tells OPatch how many times it should retry when there is an inventory lock failure.

Suppresses user interaction, and defaults any answers to "yes. Prints additional OPatch output to the screen as well as to the log file. Instructs OPatch to display inventory information of the local node only. Specifies how many times OPatch should retry when there is an inventory lock failure. Prints out bugs in addition to the summary. Used to specify a directory containing patch directories or zip files.

Prints the actions to the screen without executing them. Instructs OPatch how many times it should retry when there is an inventory lock failure. Specifies to OPatch that this is the local node for the cluster to be used for rollback.

Retrieves all information about a patch. This option says 'true' if the patch is a System Patch, 'false' otherwise. Retrieves components the patch affects. Retrieves the patch creation date and time. OPatch also maintains an index of the commands executed with OPatch and the log files associated with it in the history. OPatch supports the following log levels:. Note that LLE has been deprecated. You should upgrade to SSL to secure network links. Apurva is a PeopleSoft consultant and a big advocate of everything PeopleSoft.

He is also a technology enthusiast and loves learning and implementing newer and open source technologies. He spends his spare time updating this blog and likes to read books on self help and productivity.

The opatch. Newer versions of the Oracle EPM System may not require any switches in order to run the OPatch lsinventory command, but in older versions they are likely needed. How to run the opatch. Location: Where to run this command from is very important. The OPatch utility provides several commands that you can use to apply and roll back patches to Oracle software in your Oracle Fusion Middleware environment.

Note: Oracle has recently implemented a new patch nomenclature for Oracle products. Formerly known as CPU. Information for Oracle WebLogic Server Smart Update Users Smart Update is a standalone Java application through which you upgrade the software installations quickly and easily with maintenance patches and maintenance packs. Preparing to Use OPatch To ensure successful patching, complete these prerequisites to prepare your environment to run OPatch, such as obtaining the latest version of OPatch, obtaining required patches from My Oracle Support, and backing up the Oracle home.

For more information on preparing your environment, see the following topics:. To run OPatch, run the opatch command in this directory.

In general, there is a version of OPatch available for each version of the Oracle Universal Installer software. Note: The Oracle Fusion Middleware customers must use the OPatch version in Oracle Home, and must move to a different version only when stated by the support team.

Backup and Recovery Considerations for Patching It is highly recommended that you back up the Oracle home before any patch operation. Log in, search for, and download the patches required for your specific installation. Verifying the Prerequisites for a Patch Apply the patch. Verifying the Installation after Applying a Patch Troubleshoot the application of a patch. Applying Multiple Patches Using the OPatch napply Command opatch lsinventory This command lists the inventory for a particular Oracle home, or displays all installations that can be found.

Using the OPatch lsinventory Command to Verify the Patches Applied to an Oracle Home opatch rollback This command removes an existing one-off patch from the appropriate Oracle home directory indicated by the reference ID. Rolling Back a Patch You Have Applied opatch nrollback This command rolls back multiple interim patches at the same time.

Examples of Applying and Rolling Back Patches Using OPatch After you obtain the patches required for your installation, use the appropriate OPatch commands to verify any patch prerequisites, apply a patch to an Oracle home, and if necessary, roll back the application of a patch. Verifying the Prerequisites for a Patch You can use the checkApplicable command as a prerequisite check before applying a patch. The following are examples of patches not applicable: Patches requiring components that are not installed in the Oracle home or installed but not of the same version.

Files mentioned by patch metadata that could not be patched. Table Options for the OPatch checkApplicable Command: Options Description -allhomes This option will overide all other options involved in the logic of getting the homes for the test of 'checkApplicable'. Using the -report option To verify that a patch can be applied to a specific Oracle home, you can also use the -report option with the opatch apply command.

This example assumes that: The patch you have downloaded has been saved to a directory that is named for the patch number in My Oracle Support. All rights reserved. OPatch continues with these patches: Do you want to proceed? Patching component oracle. Patches , successfully applied. This example assumes that the patches you applied were patch numbers and RollbackSession removing interim patch '' from inventory Rolling back patch Troubleshooting a Patch by Viewing the OPatch Log File To understand how a patch is applied and to troubleshoot any problems with the application of a patch, review the log file for the OPatch session.

The file name for each log file identifies the date and time it was executed. Using the OPatch lsinventory Command to Verify the Patches Applied to an Oracle Home To verify what patches have been applied to an Oracle home, or to find out additional information about the Oracle home, use the opatch lsinventory command.

Interim patch. Bundle patch. An iterative, cumulative patch that consists of security fixes.