Toad World® Forums

New Toad Version on same machine not able to detect Oracle Home, why and how can this be solved?

I have two different toad version 9.6 and 12.7. both of them installed in same machine, however older version is able to detect some client and new is detecting some other.

For example

Older Toad Version 9.6 shows as per below:

old.png

And newer Toad Version 12.7 detects as per below

new.png

Not sure what else to be done, to get that “DevSuiteHome1” client to be shown in 12.7 as well.

Please your input on the same.

With Regards,

Pankaj

Morning Pankaj,

Toad 9.6 was 32 bit. The latest versions can be 32 or 64 bit.

32 bit Toad must have a 32 bit Oracle Client.

64 bit Toad must have a 64 bit Oracle Client.

I suspect that the old Toad is showing g only 32 bit clients while new Toad is actually 64 bit and is showing only 64 bit clients.

You need to install 32 bit new Toad, or, a 64 bit equivalent for your old DevSuiteHome client.

HTH.

Cheers,

Norm [ TeamT ]

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hi!

I’m having a similar problem with Toad 12.9.

In Toad 12.8 I can choose which client to use when I make the connection.

In Toad 12.9 the drop down list only has one entry or doesn’t show at all.

Seems like a bug to me…

If I press the box with three dots it shows correctly the installed clients but I don’t seem to be able to choose which one to use.

This is a problem for me since it’s important to be able to choose which client to use since we have both Oracle 11 and Oracle 12 databases and for example the Datapump jobs has to be running with the correct client.

Best regards

/Rickard

Rikard, are Toad 12.8 and 12.9 the same bit version (32/64)? You can check under Help -> Support Bundle. It will say right at the top.

I tried a few ways to reproduce the small “connect using” dropdown as shown in your last screen shot, but I wasn’t able to reproduce it. If you have any more information about when that happens, please let me know.

Thanks Team for the response, And yes you are right this could be due to different bit version of the installed toad, however my question is now then why the old version of 32 bit was able to detect tnsnames.ora file while the new version is not able to despite no pre-config setting was done for the older version i.e. TNS_ADMIN variable etc.

Also i tried to point my path under newly created env variable TNS_ADMIN as per below but no luck:

D:\app\admin\product\11.2.0\client_1\Network\Admin\tnsnames.ora

Please help me understand if new 64 bit version Toad has different way of detecting the tnsnames as compare to older version.

Thank you!

Tnsnames.ora is looked for as follows,

In the location defined by tns_admin.

In oracle_home/network/admin

So it is possible that your Tnsnames.ora was in the latter location?

Cheers,

Norm. [ TeamT ]

Sent from my Android device with K-9 Mail. Please excuse my brevity.

PS. I think there maybe a registry setting that affect windows. I may be wrong.

Cheers,

Norm. [ TeamT ]

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Dear Team,

Thanks for your response !

I also placed my tnsnames.ora under oracle_home as well but same result. I did look for regedit entry for oracle_home, below are the screen shot of the same:

Regedit ORACLE_HOME:

tnsnames.ora in above defined location:

tns_path.png

You need the Tnsnames.ora file in the network/admin folder within oracle home, not in oracle home itself.

Cheers,

Norm. [ TeamT ]

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hi Norm,

As my mentioned in previous post, first attempt was having the file in "D:\app\admin\product\11.2.0\client_1\Network\Admin\tnsnames.ora" and the file still there in the same directory. However when you mentioned about ORACLE_HOME, i copied it to that dir as well.

Issue is still the same.

With Regards,

Pankaj

You can specify the folder where tnsnames.ora lives like this:

Hi John,

Thanks for your response, however same is already in place and its not able to detects by this way either.

I have done following steps to get this issue sorted but no luck so far:

  1. Installed OraClient11g_home1 (11.2.0.1)

  2. Configured ORACLE_HOME path both in regedit and env variable

  3. Created new env variable as TNS_ADMIN with correct part of tnsnames.ora (i.e. ORACLE_HOME/NETWORK/ADMIN)

  4. Added oracle client path in PATH env variable.

Please let me know if any further step still needed to get this done. I am also not sure why the new Toad version(12.7) has so much steps to be done, while older version was able to detect the same automatically.

With Regards,

Pankaj

I am also not sure why the new Toad version(12.7) has so much steps to be done, while older version was able to detect the same automatically.

To be honest, there shouldn’t be anything additional that you have to do for 12.7. Did you ever verify that 12.7 is 32 bit, the same as your old 9.6 version?

Yes i verified. My new version is 64 bit , However older version does not mention the same in Support Bundle, but that too should be in 64 bit otherwise how will that be installed in 64 bit machine.(I assume). But more important is why the new version can not detect the same and why the Dell has not provided the option to manually be map to correct TNS if that is so much trouble.

32 bit Toad can be installed on a 64 bit machine, no problem. The Support bundle in Toad 9.6 did not mention 32 or 64 bit because there was no 64 bit version of Toad 9.6 - only 32 bit.

If you specify the TNS_ADMIN variable the way I showed before, and point it to a common location (For example, I use D:\Oracle\TNSADMIN), then you can put a tnsnames.ora file in that folder and it will be shared by all of your Oracle homes (and all copies of Toad). This is meant to override the \network\admin location under each Oracle Home.

Oh, and I forgot to mention - 32 bit Toad can only use 32 bit Oracle clients. 64 bit Toad can only use 64 bit Oracle clients.

www.toadworld.com/…/32-64-bits-toad-and-oracle-clients

Toad 9.7 did not have a 64 bit version. Remember that a 64 bit OS can run both 32 and 64 bit programs. It sounds like the client you used in 9.7 was indeed 32 bit and the client you’re using for 12.7 is indeed 64 bit so they are not compatible.

You either need to get a 64 bit version of the client you used for 9.7 or you need to use the 32 bit version of 12.7.

From: pankaj.marchand [mailto:bounce-pankajmarchand@toadworld.com]

Sent: Friday, June 24, 2016 12:23 PM

To: toadoracle@toadworld.com

Subject: RE: [Toad for Oracle - Discussion Forum] New Toad Version on same machine not able to detect Oracle Home, why and how can this be solved?

RE: New Toad Version on same machine not able to detect Oracle Home, why and how can this be solved?

Reply by pankaj.marchand

Yes i verified. My new version is 64 bit , However older version does not mention the same in Support Bundle, but that too should be in 64 bit otherwise how will that be installed in 64 bit machine.(I assume). But more important is why the new version can not detect the same and why the Dell has not provided the option to manually be map to correct TNS if that is so much trouble.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - General Forum
notifications altogether.

Toad for Oracle - Discussion Forum

Flag
this post as spam/abuse.

Hi John,

That attempt was also done and file is placed in the that folder, let me share you the screen shot of the same:

Please find in below:

You named your Variable TNS_NAMES. It should be TNS_ADMIN.

The file is tnsnames.ora. I get these mixed up sometimes too. :slight_smile:

Yes agree, but in my very first post as mentioned, Newer version is able to detect the client which is 64 bit but not able to detect the tnsname file of the same.