Manually Patching Oracle Enterprise Data Quality

B Manually Patching Oracle Enterprise Data Quality

This appendix describes how to prepare and install the Bundle Patch files for Oracle Enterprise Data Quality.

Note:

This feature is applicable only for EDQ 12.2.1.4.1 release.

You can manually install a patch for Oracle Enterprise Data Quality through OPatch NextGen 13.9.2.0.0 utility.

Note:

Oracle recommends that you always install the latest Bundle Patch.

Patching process uses both unzip and Opatch executables. After sourcing the ORACLE_HOME environment, Oracle recommends that you confirm that both of these exist before patching. Opatch is accessible at: $ORACLE_HOME/OPatch/opatch

You can check your version using the following command:

ORACLE_HOME/OPatch/opatch version

Set the ORACLE_HOME environment variable to the directory where you have installed Oracle Enterprise Data Quality.

Follow the below procedure to manually install the bundle patch for Oracle Enterprise Data Quality.

It includes the following sections:

B.1 Installing a Patch on Weblogic

Follow the below procedure to install a patch for Oracle Enterprise Data Quality on Weblogic:

Unzip the patch zip file to a desired location (for example, PATCH_TOP).
```
$ unzip -d PATCH_TOP p28526695_122120_Generic.zip 
```
Note:
On WINDOWS, the preferred location is the drive root directory. For example, C:\PATCH_TOP and avoid choosing locations like, C:\Documents and Settings\username\PATCH_TOP. This is necessary due to the 256 characters limitation on windows platform.

On WINDOWS, the unzip command has a limitation of 256 characters in the path name. If you encounter this, use an alternate ZIP utility like 7-Zip to unzip the patch. For example: To unzip using 7-zip, run the command:
```
"c:\Program Files\7-Zip\7z.exe" x  p28526695_122120_Generic.zip
```
Set your current directory to the directory where the patch is located.
```
$ cd PATCH_TOP/28526695
```

Run OPatch to apply the patch.

$ opatch apply

Note:

When OPatch starts, it validates the patch and makes sure that there are no conflicts with the software already installed in ORACLE_HOME.

In case of opatch conflict, you will see a warning message similar to the one mentioned below:

Interim Patch XXXX has Conflict with patch(es) [ YYYY ] in OH ...
Conflict patches: YYYY
Patch(es) YYYY conflict with the patch currently being installed (XXXX).
If you continue, patch(es) YYYY will be rolled back and the new patch (XXXX) will be installed.
If a merge of the new patch (XXXX) and the conflicting patch(es) ( YYYY) is required,contact Oracle Support Services and request a Merged patch.
Do you want to proceed? [y|n]
n

You must stop the patch installation and contact oracle support to know how to proceed further.

Restart all servers (AdminServer and all Managed server(s)) and ensure that edq.war is successfully deployed. This is necessary to redeploy the original applications and bring the environment back to it's original state.

B.2 Installing a Patch on Tomcat

Follow the below procedure to install a patch for Oracle Enterprise Data Quality on Tomcat:

Unzip the patch zip file to a desired location (for example, PATCH_TOP).
```
$ unzip -d PATCH_TOP p28526695_122120_Generic.zip 
```
Note:
On WINDOWS, the preferred location is the drive root directory. For example, C:\PATCH_TOP and avoid choosing locations like, C:\Documents and Settings\username\PATCH_TOP. This is necessary due to the 256 characters limitation on windows platform.

On WINDOWS, the unzip command has a limitation of 256 characters in the path name. If you encounter this, use an alternate ZIP utility like 7-Zip to unzip the patch. For example: To unzip using 7-zip, run the command:
```
"c:\Program Files\7-Zip\7z.exe" x  p28526695_122120_Generic.zip
```
Set your current directory to the directory where the patch is located.
```
$ cd PATCH_TOP/28526695
```

Run OPatch to apply the patch.

$ opatch apply

Note:

When OPatch starts, it validates the patch and makes sure that there are no conflicts with the software already installed in ORACLE_HOME.

In case of opatch conflict, you will see a warning message similar to the one mentioned below:

Interim Patch XXXX has Conflict with patch(es) [ YYYY ] in OH ...
Conflict patches: YYYY
Patch(es) YYYY conflict with the patch currently being installed (XXXX).
If you continue, patch(es) YYYY will be rolled back and the new patch (XXXX) will be installed.
If a merge of the new patch (XXXX) and the conflicting patch(es) ( YYYY) is required,contact Oracle Support Services and request a Merged patch.
Do you want to proceed? [y|n]
n

You must stop the patch installation and contact oracle support to know how to proceed further.

Edit catalina.properties file, to remove the reference to Oracle Application Development Framework (ADF). Optionally, you can remove lib.adf directory from their respective shared library path.
Note:
This step is a one time activity and is specific to 12.2.1.4.1 bundle patch installation.

Remove the entry ${catalina.home}/lib.adf/*.jar in the file.
For example,
```
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,
```
Stop the Application Server.
Deploy the edq.war file on your application server.
For more details, refer to the Tomcat Web Application Deployment documentation.
Restart your application server and ensure that edq.war is successfully deployed. This is necessary to redeploy the original applications and bring the environment back to it's original state.