Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ODBC Driver-specific TNSName issue

Jeff JohnsonDec 1 2009 — edited Dec 1 2009
I seem to be having a problem resolving TNSnames frm a local TNS file that is unique to the ODBC driver and would appreciate suggestions.

I have Oracle Client 10.2.0.3 and the like-versioned ODBC driver, on Windows Vista SP1. We are configured to use a central TNS Names file with an IFILE entry that includes a per-user names file. The IFILE entry looks like this:

IFILE=h:\oracle_tns\tnsnames.ora

(Everyone has an H drive in our environment).

The Oracle ODBC Driver, ONLY, seems to not be able to use names in the 'included' personal names file (you always get a name not resolved error). Interestingly, the dropdown list in the TNS Service Name part of the Oracle DNS configuration dialog has an entry for 'IFILE', and not any entries for the names in the included file. Even manually entered names don't work.

HOWEVER, these same names work fine with both SQL*Plus and the Microsoft ODBC Driver for Oracle.

Looks like a bug in the Oracle ODBC driver - though I can't understand why it's doing name lookup differently than SQL*Plus is. ANyway, did a look with Process Monitor and verified that doing a test connection in the ODBC DSN configuraiton dialog doesn't even try to open the 'included' file, just the central one, while doign the same thing with SQL*Plus DOES open the 'included' file.

Can anyone confirm this issue occurs and/or doesn't occur, and with other ODBC driver versions? Anyone know of any fiix or workaround to get my included file's names to work?
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 29 2009
Added on Dec 1 2009
4 comments
3,881 views