If you installed OEE on a 64-bit version of Microsoft Windows, you must also install a 32-bit version of the Oracle database client and then copy your
tnsnames.ora file to a subdirectory under the database client installation directory.
Note:64- vs. 32-bit Oracle database drivers. Because JD Edwards EnterpriseOne is a 32-bit program, it needs to load 32-bit Oracle database driver DLLs; however, you must install a 64-bit Oracle database in the section of this guide entitled: Chapter 5, "Installing the Oracle Local Database". Therefore, you also need to install 32-bit Oracle database driver DLLs. These 32-bit DLLs are provided by a 32-bit Oracle database client.
This chapter discusses these topics:
To obtain a 32-bit Oracle database client:
Download the 32-bit Oracle 12c database client from the Oracle Software Delivery Cloud located at this link:
Click through the license agreement if you accept the terms of the Oracle site usage.
On Oracle Software Delivery Cloud, in the Filter Products By list of checkboxes, be sure Programs is checked.
In the Product field, enter this string:
Oracle Database Enterprise Edition
On Oracle Software Delivery Cloud, in the Select Products pulldown, select this checkbox:
Microsoft Windows x64 (64-bit)
Click the Continue button.
On the results screen, expand the entry Oracle Database Enterprise Edition by clicking the arrow to the left of the release name.
Under the expanded entry for Oracle Database Enterprise Edition, uncheck all checkboxes except this:
Oracle Database Client
Click the Continue button.
On Oracle Standard Terms and Restrictions, read the license agreement, click the checkbox if you accept, and click the Continue button.
On File Download, click the link for the Oracle Database Client for Microsoft Windows (32-bit).
Save the downloaded file to your computer.
Extract the contents of the downloaded file.
To install a 32-bit Oracle database client:
In the directory where you expanded the download in the previous step in this chapter, run this setup file to start the Oracle database client installer:
On Step 1 of 6, select the Administrator radio button and click the Next button.
On Step 2 of 6, select the English language from the list of Available languages and click the Next button.
On Step 3 of 8, you can accept the default value which is:
Use Windows Built-in Account
Note:Unlike the installation of the database where Oracle recommends not using the built-in account, this option for the database client is acceptable.
Click the Next button.
On Step 4 of 8, enter path values for the Oracle base and Software location.
Click the Next button.
On Step 6 of 8, verify the Global Settings and click the Install button.
On Step 7 of 8, the installer displays the Progress.
On Step 8 of 8, the installer indicates the installation was successful. Click the Close button to exit the installer.
Note:This section provides important instructions on working with the PATH environment variable as it relates to the Oracle database and the Oracle database client.
If you installed the 64-bit Oracle database, the installer placed the path to the database (for example,
c:\Oracle\E1local\bin) at the start of the Windows PATH environment variable. Then when you installed the 32-bit Oracle database client, the installer placed the path to the database client (for example,
c:\Oracle\product\12.1.0\client_1\bin) at the start of the Windows PATH environment variable.
When EnterpriseOne runs, it looks for database drivers in each directory from start to finish in the PATH. The first occurrence of a driver DLL that EnterpriseOne finds will be loaded. This means that the path to the 32-bit Oracle database client must come BEFORE the path to the 64-bit Oracle database.
If you installed the 64-bit database and 32-bit database client in that order, the order in the PATH should be correct. However, if you installed them in the opposite order, you need to correct the order in the PATH.
To reverse the order of the 64-bit database and 32-bit database client paths in the Windows PATH, follow these steps:
From the Start button, select Control Panel and then System.
On the left side of the window that comes up, click Advanced system settings.
Click the Advanced tab.
Click the Environment Variables… button.
In the System variables box, highlight the variable path and click the Edit… button.
In the Variable value field, cut the 32-bit database client's path including the trailing semicolon. For example:
Paste the client's path and semicolon at the start of the Path value.
Click the OK button.
Click the OK button to exit from the Environment Variables window.
Click the OK button to exit from the System Properties window.
Close the Control Panel system window.
There is a known issue with the Oracle 12c 32-bit database client programs that import (
impdp.exe) and export (
expdp.exe) JD Edwards EnterpriseOne data and spec databases during installation of the Development Client. To work around the problem, you can force the system to use the
expdp.exe in the Oracle 12c 64-bit database
\bin folder for importing and exporting data. This resolves the issue because the 64-bit version of these files do not exhibit the known issue that is observed with the 32-bit version.
After you install the 32-bit database client, you must either delete or rename these files (so they are not executable) within the
\bin folder of the 32-bit client:
For example, you could change the extension on these files (so they are not executable) using these commands:
rename impdp.exe impdp.exe.bak
rename expdp.exe expdp.exe.bak
In order for your Oracle database client to function properly, you must copy the
\\<deployment server name>\<release>\client
<32-bit Oracle Client Install Dir>\network\admin