![]() ![]() RESOLUTION 1: Create a new folder that is not under the Program Files folder, such as C:\Quest Software\ and install Toad under this new folder. Toad will have to be installed into a different folder without the parenthesis as shown in the following example: C:\Quest Software\ ![]() The default install directory for 32-bit applications on a 64-bit OS includes parenthesis as shown in the following example:Īccording to Oracle Metalink, Doc ID 334528, there is a network error that results causing any path with a parenthesis to have an issue. However, changes will need to be made to the installation path during installation. The application supports a Windows 64-bit OS. Windows 64-bit Operating System - Oracle Client Issue This path doesn't contain any parenthesis so it doesn't cause the existing networking bug. ![]() I deinstalled Toad from the following locationĬ:\Program Files (x86)\Quest Software\Toad for Oracle\Īnd reinstalled it in the following location TNS for 32-bit Windows: Version 10.2.0.1.0 - Production (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521))(CONNECT_DATA=(SID=XE)(CID=(PROGRAM=C:\Program Files (x86)\Quest Software\Toad for Oracle\toad.exe)(HOST=OCTOPUS)(USER=Joost)))) In my sqlnet.log i find the folowing lines: If so, you must relocate the application to a directory without any parenthesis in the path. Check the path to this location and see if it contains any parenthesis. NOTE: Currently the following patches have been released on Windows:ĩ.2.0.7.0 Patch 6: Apply Patch 4928723 or laterġ0.2.0.1.0 Patch 4: Apply Patch 4923768 or laterġ0.2.0.2.0 Patch 5: Apply Patch 5383042 or laterġ0.2.0.1.0 Patch 4: Apply Patch 4923787 or laterġ0.2.0.2.0 Patch 5: Apply Patch 5388871 or laterįor all other versions on Windows please use SOLUTION 2 for now.įind the location of the application that is generating the error. Use a version of the Oracle software that contains the fix for Bug 3807408. SolutionTo resolve this problem try either of the following solutions: The ORA-6413 is typical of using older interfaces which make legacy API calls such as Oracle's OCI Version 7 API: The ORA-12154 is the typical error seen when connecting with up-to-date interfaces using the latest version of the Oracle Call Interface (OCI): an ORA-6413 is generally due to which programmatic interface you have chosen to use to connect to Oracle. The following bug has been filed to correct this behavior:īug 3807408 - CANNOT EXTERNALLY AUTHENTICATE USER WITH QUOTE IN USERNAME This causes an existing networking bug to occur where the networking layer is unable to parse program locations that contain parenthesis in the path to the executable which is attempting to connect to Oracle. Cause64-bit Microsoft OS's install 32-bit applications into the following location ORA-12154: TNS:could not resolve the connect identifier specified SymptomsYou are attempting to connect to the Oracle database from a Windows platform using one of the following programmatic interfacesĪfter installing 32-bit Oracle client software on a 64-bit Windows operating system (OS) you receive one of the following errors: Subject: ORA-12154 or ORA-6413 Running 32-bit Oracle Software on 64-bit Windows OS I found this document on Oracle Metalink: Just install TOAD in c:\Programs\TOAD instead of the default directory (avoid any parenthesis or spaces in the folder) and IT WILL WORK! Ask no questions, just work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |