See the following documentation for information:. While OPatch is integrated with many Oracle product installations, you may still find that you need to use the OPatch directly.
The core OPatch tool is used directly by admins as part of manual patching. OPatch is also useful for conflict detection and resolution as well as troubleshooting. Detect conflicts among incoming patches and between it and previous patches that have been applied. OPatch suggests the best options to resolve a conflict.
With these patching tools, you can design and implement a patch plan based on the configuration of your Oracle products. In addition to Enterprise Manager, many Oracle software products have integrated the OPatch utilities to provide for a seamless and efficient patching task.
Depending on the application, the call to the OPatch utility may be transparent, and all patching activity is maintained within the respective application. These applications listed below have integrated OPatch into their respective environments. Always check the user documentation for any patching instructions before applying a patch. Other Oracle products, such as Fusion Middleware and Fusion Applications, integrate OPatch and may require different interaction to apply a particular patch.
Refer to the following documentation:. Section 2. With OPatch integrated in many Oracle products, the utility is automatically installed when you install the respective product for example, Enterprise Manager.
The patching tools are installed in the following directories:. This command applies an interim patch to an Oracle home from the current directory. Specifies the list of database instances on which the patch needs to be applied.
Specify the value for this option using the following syntax:. The SID is required, but you can disregard the other parameters if desired, because OPatch provides default values for them. Note: If the system is not part of an Oracle RAC setup and you want to patch just the local node, provide the node name as an empty string. Specifies how many seconds to wait before attempting to lock the inventory again for a previous failure.
You can use this option only if you specify the retry option. Removes conflicting patches from the system. If a conflict exists that prevents the patch from being applied, you can use this option to apply the patch.
OPatch removes all the conflicting patches before applying the current patch. Passes parameters to the init script, which executes before prerequisite checks are run. The values for this option must be enclosed in double-quotes.
Specifies the location of the oraInst. The invPtrLoc option is needed when this option is used during installation. Oracle recommends the use of the default Central Inventory for a platform. Specifies that OPatch should patch the local node and update the inventory of the local node. It does not propagate the patch or inventory update to other nodes. You can use this option on Oracle Real Application Clusters environments and non-clustered environments.
If an entire cluster is shut down before patching, you can use this option for non-rolling patches. Tells OPatch the local node for this cluster. You can use this option on Oracle Real Application Clusters environments.
This option only applies to Oracle Real Application Clusters environments. You cannot use it with the -local option with a rolling patch. Specifies to error out if the current patch's bugs-to-fix is a superset or same set of an installed patch's bugs-fixed in the Oracle home directory. Bypasses the inventory for reading and updates. You cannot use this option with the local option.
This option places the installation into an unsupported state. This option does not perform any make operations. You can use it during multiple patch applications and to perform the linking step only once. OPatch does not keep track of the make operations it did not perform. You need to make sure to execute OPatch without this option at the end for compilation. Specifies that OPatch does not need to update the files in the system. It only updates the inventory. It also does not execute the pre and post scripts.
Specifies the Oracle home directory to use instead of the default. Marks the end of the init options. You use this option with the init option. If you do not use this option, everything after init until the end of the command is passed into init. Marks the end of the post option. You use this option with the post option.
If you do not use this option, everything after post until the end of the command is passed into post. Marks the end of the pre options.
You use this option with the pre option. If you do not use this option, everything after pre until the end of the command is passed into pre.
Indicates the path to the patch location. If you do not specify the location, OPatch assumes the current directory is the patch location. Specifies the parameters to be passed to the post script.
This script is executed after the patch is applied. You need to enclose the values for this option in double-quotes. Specifies the parameters to be passed to the pre script. This script is executed before the patch is applied. Specifies 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 OPatch supplies.
Tells OPatch the list of remote nodes. The node names must be separated with commas, but without spaces. Instructs OPatch to use JDK jar from the specified location instead of the default location under the Oracle home directory. If you do not specify the jre option, JVM is executed from the jdk location. You cannot specify the jdk and jre options together.
Each line in the file points to a location of a patch. 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. Skips patches to be applied that are subsets 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. For example, if you used napply yesterday for patch A that fixed bugs 1 and 2, then you use napply today with this option for patch B that fixes bug 1 and patch C that fixes bugs 1, 2, and 3, then subset patch A is skipped, and patch C then becomes a superset of patch A.
Ordinarily, an Oracle Clusterware patch requires several manual steps before and after you apply the patch, such as:. The opatch auto command automates all of these tasks for patching the grid infrastructure home and all other applicable RDBMS homes.
If you do not specify the patch location, the current directory is considered the patch location. Comma-separated Oracle homes to patch. The default is all applicable Oracle homes. Path of the Oracle Clusterware home. Use this option to patch only Oracle Clusterware homes where Oracle Clusterware has been stopped already.
The following example applies a patch with an unzipped patch location to all applicable Oracle homes on the system:. This command lists the inventory for a particular Oracle home, or displays all installations that can be found. This command does not have any required options. See Table 7—5 for descriptions of the command options. The following example shows the output of opatch lsinventory -detail for products and one interim patch:. It also prints the Oracle binary's size and checksum on all nodes.
You cannot use this option with the all , detai l, or patch options. 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 option to obtain sort orders with installed patches. If you specify retry, this option tells OPatch how many seconds it should wait before attempting to lock the inventory again in case of a previous failure.
Reports the installed products and other details. You cannot use this option with the -all option. Specifies that OPatch should group all installed patches by the date they were installed in the Oracle home.
Lists all the inactive patches that have been superseded by other superset patch es installed in the Oracle home. You need this option if you used the invPtrLoc option during the installation. Oracle recommends using the default Central Inventory for a platform. Specifies the location of a particular JRE Java to use instead of the default location under the Oracle home directory.
Specifies the Oracle home directory to use instead of the default directory. Lists the patch IDs installed in the Oracle home in ascending asc or descending desc order, which is the default, based on installed time. Indicates the user-defined property file that OPatch should use.
The path to the property should be absolute. This property file takes precedence over the property file that OPatch supplies. Displays the translation patch, language code, installed time of the translation patch, and base patch for any single row in the table. This command queries a specific patch for specific details.
It provides information about the patch and the system being patched. Indicates true if the patch has SQL-related actions. Otherwise, the option is false. This command removes an existing one-off patch from the appropriate Oracle home directory indicated by the reference ID.
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. Indicates the patch to be rolled back.
Use the lsinventory option to display all patch identifiers. Each one-off patch is indicated by its ID. To successfully roll back a patch, you must provide the patch identifier.
You need to use this option if you used the invPtrLoc option during installation. Specifies that OPatch roll back the local node, then update the inventory of the local node. Specifies that OPatch need not update the files in the system, only the inventory.
This option does not perform any make operation in the patch. You can use this option during multiple patch removals and to perform the compilation step only once. Use this option with the init option.
Marks the end of the post options. Use this option with the post option. Use this option with the pre option. Specifies the valid patch directory area. Rollback uses the command types found in the patch directory to identify which commands are used for the current operating system.
Specifies the parameters to be passed inside the post script. This script executes after the patch is removed.
You must enclose the value of this option in double-quotes. Specifies the parameters to be passed inside the pre script. This script executes before the patch is removed.
Specifies to OPatch the list of remote nodes to be used for rollback of the patch. Don't take your car here for brakes. You get some unpleasant surprises. The cost jumped on the brake job because they had not included some items…. Whether you need extensive repair work or just a quick checkup, come in today or schedule an….
From Business: Specializing in Advertise with Us. Find a location. View all 2 Locations. Website Services. Click for Coupon. BM I've been going to Firestone in edgewater park for 10 years with 4 cars in our family. Click to Schedule Your Appointment Now! Schedule Appointment.
The following table describes the options available for the apply command. Table B-1 apply Command Options. If this option is selected, the environment will be analyzed for suitability of the patch on each home without affecting the home. The patch will not be applied or rolled back and targets will not be shut down. Enables sharded database sdb rolling mode where database s are patched one after the other.
Enables remote node patching. This is supported only for Grid setup and it should be up and running. If opatchauto apply is run and encounters an individual patch within a patch set that cannot be installed, that patch will be skipped and OPatchAuto will continue with the installation of the next patch in the sequence.
0コメント