TNS cannot resolve service name

[dlstites]

Delpha 5, DOA 3.3, NT4.0 service pack 6

Interesting Problem
Server: 1 Instance of Oracle 8.05
3 Instance of Oracle 8.17
(therefore 2 Tnsnames.ora)
one oracle instance = LGLASS.world service name

tnsping lglass works great.
connect using sqlplus from any machine including server works great

application connect from another machine works great
application when running on server gives Unable to resolve tns service

Is there something I have to do for DOA to connect?

 

[dlstites]

Further research:
As previously noted, there are two instances of oracle on this server, and also 2 different tnsnames.ora.
Oracle 8.05 \orant\net80\admin\tnsnames.ora
oracle 8.17 \oracle\ora81\network\admin\tnsnames.ora.

Using the OracleAliasList function ... only those aliases in the 8.05 directory show. This is true ONLY when on that server (local). from all other machines ... they all show????

 

[Marco Kalter]

If you want to connect to all database instances from both Oracle Home's (8.0.5 and 8.1.7), then both tnsnames.ora files must contain aliases for all database instances.

I assume that the Primary Oracle Home is the 8.0.5 version, because this is what Direct Oracle Access will use by default. You can use the Oracle Home Selector (a standard Oracle Utility) to make 8.1.7 your Primary Oracle Home.

In any case, the tnsnames.ora file of the Primary Oracle Home must contain aliases for all database instances.

------------------
Marco Kalter
Allround Automations

 

[morten]

I suppose you got this working by now. Anyway, I got this problem earlier when we had a firwall-1 between the webserver (using doa) and the Oracle server. There was/is a bug in Firewall-1 concerning communication with Oracle. This caused a TNS: cannot resolve service name error. Firewall-1 got a patch. I'm sure this is not the problem in your case, but it's worth noticing