I’ve been stuck on 12.1 GA due to an issue where 12.5 GA and now 12.6b would not connect to any of my databases using the ORACLE_HOME’s TNSNAMES.ORA file. This is basically from http://www.toadworld.com/products/toad-for-oracle/toad_for_oracle_beta_program/f/86/t/21781.aspx
I’ve been very heavily relying on Toad for a large-scale project of a merge of two companies. There’s a potential for more time savings with Toad bug fixes and new functionality, so I thought all of my overdue tasks can wait another 30 mins while I troubleshoot…
Here’s my setup and what I did to resolve Toad 12.5GA/12.6b not being able to use my TNSNAMES.ORA:
- Toad 184.108.40.206 64bit (no 128-bit version yet!)
- Two ORACLE_HOMEs, in the order installed.
- 220.127.116.11 client-only
- 18.104.22.168 database
- Win PATH: C:/database-path/bin;C:/client-path/bin;… <— NOTE the DB home is first, as it was last installed
- All Toad connections use client OH
- In Toad Connection screen, OH selector ellipsis shows the two OHs, both “correct”
- Desired TNSNAMES.ORA in client OH – database OH/network/admin has no connection in its TNSNAMES.ORA
- No TNS_ADMIN environment variable
- All connections using TNSNAMES.ORA were working in Toad 12.1GA
- No connections using TNSNAMES.ORA working in 12.5GA or 12.6b, failing with ORA-12154 (can’t resolve TNS entry).
To fix, I just modified my Win PATH variable to swap the client OH – and its TNSNAMES.ORA – with the database OH, putting the client OH first. Now all connections using client TNSNAMES.ORA work!
So, I wanted to verify this and I switched 1 connection’s OH to the database OH. The connection failed with ORA-12154, lending credence to my theory that the OH is ignored in the connection and the Win PATH is used instead. However, now the OH dropdown in the connection screen is greyed out and I can’t switch anything back to use the client’s OH. Hmm…restart Toad and I’m able to make the OH swap and all’s well.
From this mess I’ve made and tried to document here, it seems to me that Toad 12.5GA and 12.6b rely on the PATH variable to resolve TNS aliases, instead of the OH selected in the connection screen dropdown. I’m sure I’m missing something here, but this is what I’ve got so far.
p.s No, no, no…don’t…have…time…to…check out…new…ASH…interface…must…work…on…project…