Opatch Detects Your Platform As 23 While This Patch' title='Opatch Detects Your Platform As 23 While This Patch' />Patching Oracle Software with OPatch. Standalone patching is available for Oracle homes that have not been installed using the Oracle Universal Installer. Standalone patching does not have Central Inventory registration, but still generates inventory files for the one off inventory and future conflict checking. OPatch uses the presence of the OUI directory under ORACLEHOME to determine whether it should operate in OUI based or standalone mode. Unsupported Services for Standalone Patching. Standalone patching provides most of the services that OUI based patching provides. However, standalone patching does not provide the following services that OUI based patching provides. Looking up the component inventory. DuA2SnoZEoU/hqdefault.jpg' alt='Opatch Detects Your Platform As 23 While This Patch' title='Opatch Detects Your Platform As 23 While This Patch' />Standalone OPatch enables you to look up which patches have been applied to a standalone Oracle home, but it does not support looking up product components. For example, if you run opatch lsinventory on a JDeveloper Oracle Home, OPatch shows a list of patches applied on the home. It does not show which components the home has, however. Looking up the Central Inventory. You cannot run opatch lsinventory all to list all Oracle homes registered on the host through the Central Inventory repository. Migrating from standalone to OUI based patching and vice versa. The assumption is that after you have installed a product as standalone without OUI, it remains standalone. For example, after having installed JDeveloper, you cannot put OUI through copying or proper installation onto the Oracle home and expect OPatch to treat the home as an OUI based Oracle home. Conversely, the assumption is that after you have installed a product with OUI, it remains OUI based. For example, after you install Oracle RDBMS, you cannot remove OUI either by removing or proper deinstallation and expect OPatch to treat the home as a standalone Oracle home. OPatch will not work properly in this case and will corrupt the home. Interoperating between standalone and OUI based patches. Oracle Documentation. While this guide provides detailed instructions for successfully installing a complete Oracle Database 11g Release 2 system, it is by no means a. Your registration with Eweek will include the following free email newsletters News Views. Since you cannot migrate a home from standalone to OUI based and vice versa, OPatch does not support interoperability between standalone and OUI based Oracle homes. Seamlessly working on a cloned standalone Oracle home. If you clone a standalone Oracle home S1 to another Oracle home OH2, Opatch will not function properly on the new cloned OH2. Supporting RACOPatch relies on OUI to detect RAC and propagate files. Hence, standalone OPatch does not support RAC it does not attempt to detect RAC, and its utility will not work. That is, OPatch always runs as opatch apply local. OPatch does not support any patch propagation from one node to another node. Also, standalone OPatch does not support RAC related utilities such as opatch util run. Remote. Make invokes relink on remote node. Performing patch set operations. OPatch does not support patch set operations in either standalone or OUI modes. You need to use OUI for patch set operations. Standalone Patching Requirements. Standalone patching requires the following environment JRE version 1. Oracle home without OUIOPatch that supports standalone patching. All of the required files and directories must exist for OPatch to function correctly. If any of the files are missing, OPatch perceives that the patch has not been applied. You would then have to take corrective action, returning the standalone inventory to a stable state. OPatch Utility for Standalone Homes. As with OUI based patching, you can run the OPatch utility, located in the lt PathtoOracleHome OPatch directory, with various commands and options. The following string shows the syntax for the OPatch utility lt PathtoOPatch opatch help report command optionwhere help Displays the help message for the command. Prints the actions without executing. One of the OPatch commands. One of the OPatch command options. Table 7 9 lists the commands available for standalone patching. Table 7 9 OPatch Standalone Commands. The following sections provide the syntax and options for each of these commands. Apply Command for Standalone OPatch. The Apply command applies an interim patch to a standalone home from the current directory. Syntax. Use the following syntax for this command. LOC nobugsuperset noinventory oh lt ORACLEHOME silent verbose norelink pre lt parameters for the pre script in escaped double quotes opatchpreend post lt parameters for the post script in escaped quotes opatchpostend nosysmod propertyfile lt Path to property file init lt parameters for the init script in escaped double quotes opatchinitend report lt Patch Location. Options. Table 7 1. Apply command. Table 7 1. Apply Options for Standalone Patches. Option. Descriptionforce. Removes conflicting patches from the system by enabling you to change the product and version number of the standalone Oracle home. 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. Instructs OPatch to use JRE Java from the specified location instead of the default location under the Oracle home directory. Specifies to error out if the current patchs bugs to fix is a superset or same set of an installed patchs 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. This takes precedence over the environment variable ORACLEHOME. 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. 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. 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. You need to enclose the values for this option in double quotes. Specifies the user defined property file for OPatch to use. Sample Unveiling Program. The path to the property file should be absolute. This property file takes precedence over the one that OPatch supplies.