I can't see how that will help, since he's clearly wishing to bypass
the tnsnames mechanism altogether, and all the TNS_ADMIN variable does
is point one to a new or different location for a tnsnames.ora file.
I find nothing in the documentation offering any connection method
outside of the SQL*Net model, however I don't write enough OCI code to
have come across any workarounds for database connections. Possibly
someone else has some further insight into this; for now I can only
say there is no other method, outside of using the tnsnames.ora file,
to connect to an instance.
Of course, I could be wrong. :-)
David Fitzjarrell
rs******@hotmail.com (Rauf Sarwar) wrote in message news:<92**************************@posting.google. com>...
"DP" <dp****@mw-inc.com> wrote in message news:<UB****************@news.uswest.net>... I am porting an existing application to OCI. I have 200+ client computers.
Since the existing app already has a way to retrieve settings off another
server I am looking to bypass tnsnames.ora.
Of course I could just rewrite tnsnames before calling OCILogon, but I was
hoping to be able to pass a key/value list or similar in the dbname
parameter. Alternately, can OCILogon use environment variables for this?
DP
Look at usage of TNS_ADMIN environment variable.
Regards
/Rauf Sarwar