Toad: 26.1.193.8012
The 2 paths are essentially the same, only difference is uppercase ‘N’ for Network in one and lowercase ‘n’ in the other. This is on Windows where files/directories are not case sensitive. To make things even more confusing, the TNS_ADMIN environment variable has lowercase ‘n’ and the actual directory name is lowercase as well, so not sure where the uppercase ‘N’ is being picked up.
Regards,
Doug
Hi Doug,
I think the uppercase one is coming from the registry, under HKLM\Software\Oracle\Key_OraClientXXHomeY, the ORACLE_HOME entry in that hive.
Even so, Toad should ignore case differences here and I'll fix that.
Thanks for reporting it.
John
Update:
On looking at the code, I see that Toad is complaining not because it thinks these files are different, but because they are defined in more than one place.
The Oracle client's Network\Admin folder will be found automatically. It doesn't need a TNS_ADMIN location specified for Toad to find it....but TNS_ADMIN is specified anyway.
Admittedly, I added this check after a working on a support case where the had TNSNames.ora files all over the place "for good measure". It took a while to figure that out.
I guess as long as the TNS_ADMIN folder is pointing to a client's network\admin folder, Toad should not complain. A valid complaint would be if you had TNS_ADMIN pointing somewhere else, AND you had a tnsnames.ora in the network\admin folder.
Just FYI. I'll fix it so it won't complain in your case.
Hi John,
This is running on Windows Server 2016 Datacenter edition. Although I am an admin on the server, I was not the person that installed that 21c Oracle Client and I often reconfigure Toad to use a 19c instant client and different tnsnames.ora file to avoid any issues with the other Toad user on this platform. Searched the registry for the key that you mentioned, but could not find it.
Thanks for looking into this. I rarely use the tnsnames.ora editor, so not a huge issue for me.
Regards,
Doug
You're welcome. It's more of a caution and not really a problem.
So, if we have a TNS_ADMIN that points to some path that is different from the client’s network/admin location, AND there is a tnsnames.ora in both places, this error will throw?
I will be running 26.1 on 2022 DataCenter, but I have not installed it yet. I just need to know what to expect.
Cheers,
Russ
It's not an error. The icon next to the TNSNames Editor's button turns to a caution sign, and if you click it, you get that message. Other than that, Toad will behave as it always has. No message/error will pop up on its own
OK I never use Toad’s editor because I have a special structure for my file. As long as it works, that’s all that matters.
Cheers,
Russ
Yeah, I tend to avoid the TNSNames editor for the same reason. I prefer my own goofy format.
By the way...a little hidden feature....you can right-click on the Database dropdown (without dropping it down first) and choose "Show TNSNames entry" to get the tnsnames.ora in a regular text editor (and it will locate whichever entry was selected in the dropdown when you right-clicked)
Is that a Toad text editor screen or something out of Windows?
it's just a built-in popup text editor...the same thing you'd get by double-clicking a varchar2 cell in a grid.
I noticed that it only has a save-as and not a straight save so that I have to save-as the same file and OK the warning.
But, does that editor (I have not tried it yet) change the format of the file in any way? I assume it just saves what it shows along with any changes without reformatting.
Cheers,
Russ
The TNSNames Editor does have a "Format" feature (with a few levels of compactness) but as long as you don't format it then it will keep whatever format you already have.
