1

Topic: PL/SQL Developer and old applications do not see tnsnames under win7 x64

Help to adjust the client on Windows 764
Oracle Database server 11g
The client of Oracle Database 11g x32
OC Windows 7 x64 prof
Through Oracle Net Manager I test connection under the user:
Attempting to connect using userid: bad
The connection test was successful.
(Such here  bad)
Tnsping too it is fine  the server.
PLSQL Developer (ancient 5 versions, but another also it is not necessary to me) at start does not give the list of bases, i.e. does not see tnsnames.ora. Tried a basis name to write manually, but I receive an error:
SQL*Net not properly installed
OracleHomeKey:
OracleHomeDir:
There is an application written 100 years ago, with usage DOA, it too cannot incorporate to the server.
All Internet rummaged, at this forum already there was such question
http://www.sql.ru/forum/949759/sql-net- … -installed
But did not help.
I tried both the client 64 and the client 32 and under this link
http://www.foxbase.ru/administrirovanie … ows-64.htm
Tried to adjust through Instant Client - too most.
Tried also ways to throw in variable surroundings, and copied register branches, and created new branches. Helps nothing.
Where a rake, prompt.

2

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

Ancient Oracle Reports on Windows 10 at me did not rise.
Eventually all the same it is necessary to pass to new versions.
Or to dig, or the virtual machine under OS of the necessary version.

3

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

Add a system variable of a surrounding TNS_ADMIN=put-to-tnsnames.ora
SY.

4

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

SY;
Added, when tried instant client
Does not see the list from tnsnames.ora
When simultaneously tried the client and  the client, tnsping, at presence tns_admin, pulls the list from there.
But neither plsql nor , do not see this way generally sad

5

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

Once there was a same problem. The essence - old DOA tries to receive adjustments from key SOFTWARE\Oracle\HOME <N>, and modern SOFTWARE\ORACLE\KEY_Client <Version> for it anything. The decision idle time - to rename (for 64 bit it to do in Wow6432Node), and as to correct ORACLE_HOME_KEY (here already Wow6432Node it is not necessary to specify). I.e.
1. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_Client10205 to rename in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\HOME0,
2. ORACLE_HOME_KEY to set value SOFTWARE\ORACLE\HOME0
3. If first two points it is not enough - to correct ORACLE_HOME_NAME - instead of Client10205 to specify HOME0
PS: new applications to old HOME <N> concern normally.

6

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

MazoHist;
On idea, variable  systems   a priority, than registry

7

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

Vadim Lejnin, goodness knows that there old DOA think concerning a surrounding... Application Used by us in 2009/10 years has been written on Delphi 4 with DOA 3.4.x, I forced to work as its this method on 11 the client.

8

Re: PL/SQL Developer and old applications do not see tnsnames under win7 x64

MazoHist;
Thanks you enormous! Earned!
Truth is a little not so made, I completely copied section Key_... Also called it Home0
Since if simply to rename section in Home0 and accordingly to change key ORACLE_HOME_KEY ceases to work tnsping. On how many I could understand, new applications look in ORACLE_HOME_KEY, see OraClient11g_home1, and for remaining parameters to a name add KEY_ and search for section KEY_OraClient11g_home1