1. Applications Installation Guide for UNIX with IBM DB2 for Linux, UNIX, and Windows
  2. Installing a 32-Bit Oracle Database Client

Installing a 32-Bit Oracle Database Client

You must install a 32-bit version of the Oracle database client and then copy the resulting 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: Installing the Local Oracle Database on the Deployment Server. 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.

To install a 32-bit Oracle database client:

  1. Download the 32-bit Oracle 12c database client from the Oracle Software Delivery Cloud located at this link:

    http://edelivery.oracle.com

  2. Install the database client.

    Caution: Important Installation Note: When installing Oracle the database client, be sure to select Administrative on the Select Installation Type screen.
    Caution: Working with the PATH Environment Variable. Refer to the following step for important instructions on working with the PATH environment variable as it relates to the Oracle database and the Oracle database client.

  3. After you installed the 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.3\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 followed the recommended installer order and installed the 64-bit database and then the 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:

    1. From the Start button, select Control Panel and then System.

    2. On the left side of the window that comes up, click Advanced system settings.

    3. Click the Advanced tab.

    4. Click the Environment Variables… button.

    5. In the System variables box, highlight the variable path. and click the Edit… button.

    6. In the Variable value field, cut the 32-bit database client's path including the trailing semicolon. For example:

      c:\Oracle\product\12.1.3\client_1\bin;

    7. Paste the client's path and semicolon at the start of the Path value.

    8. Click the OK button.

    9. Click the OK button to exit from the Environment Variables window.

    10. Click the OK button to exit from the System Properties window.

    11. Close the Control Panel system window.

  4. 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 Deployment Server. To work around the problem, you can force the system to use the impdp.exe and 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:

    • impdp.exe

    • expdp.exe

    For example, you could change the extension on these files (so they are not executable) using these commands:

    cd <32-bit_db_client_install_dir>\bin

    rename impdp.exe impdp.exe.bak

    rename expdp.exe expdp.exe.bak

  5. After you install the Deployment Server, you can copy this tnsnames.ora file that the installation delivered:

    From:

    \\<deployment server name>\<release>\client

    To:

    <32-bit Oracle Client Install Dir>\network\admin