![]() ![]() IPv6 addresses can be distinguished by alphanumeric digits separated by colons, rather than periods as in IPv4 addresses. If your Deployment Server is not working as expected, use this procedure to determine if the problem is due to your Windows machine using IPv6 and if so, to remedy:Īfter installing the local Oracle database, use a text editor to open the log.xml file which is typically located in this directoryĬ:\Oracle\diag\tnslsnr\\listener\alert\.Įxamine the contents of the log.xml file for indicators that the machine is using IPv6 addresses. ![]() The JD Edwards EnterpriseOne Deployment Server requires Microsoft Windows Internet Protocol Version 4 (IPv4) for connectivity. Paste the client's path and semicolon at the start of the Path value.Ĭlick OK to exit from the Environment Variables window.Ĭlick OK to exit from the System Properties window.Īfter you install the Deployment Server, you can copy this tnsnames.ora file that the installation delivered:ģ.3.4 Microsoft Windows Internet Protocol Version 4 (IPv4) In the "Variable value" field, cut the 32-bit database client's path and the following semicolon (for example, c:\Oracle\product\11.2.0\client_1\bin ). ![]() In the "System variables" box, highlight the variable Path and click Edit…. On the left side of the window that comes up, click Advanced system settings. To reverse the order of the 64-bit database and 32-bit database client paths in the Windows PATH, follow these steps:įrom the Start button, select Control Panel and then System. However, if you installed them in the opposite order, you need to correct the order in the PATH. If you installed the 64-bit database and 32-bit database client in that order, the order in the PATH should be correct. This means that the path to the 32-bit Oracle database client must come BEFORE the path to the 64-bit Oracle database. The first occurrence of a driver DLL that EnterpriseOne finds will be loaded. When EnterpriseOne runs, it looks for database drivers in each directory from start to finish in the PATH. Then when you installed the 32-bit Oracle database client, the installer placed the path to the database client (for example, c:\Oracle\product\11.2.0\client_1\bin) at the start of the Windows PATH environment variable. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |