Re: tnsping OK, but database does not exist what next

Wayne,
What I do is copy SQLNET.ORA and TNSNAMES.ORA from the server to the client. And don't use tabs in them.
TNSPING from client to server is only making a connection to the listener and not to the database. So you can TNSPING while the db is not up and have as result OK.
You could start tracing on ADMIN-level. In the output (cryptic) you can read where things go wrong.

Succes,
Eric van der Spoel

"> Hi List,
> I have added a new 8.1.6 database to a server taht already has 3
> working dbs.
> But when I try to connect with a Clarify Client it says "database does
> not exist".
> Which I was not expecting, cos from the W2000 client tnsping ORT
> succeds.
>
> The server tnsnames.ora, and listener.ora files look a bit strange,
> but they worked for UAT so why not ORT?
> And the client tnanmes.ora is much the same.
>
> Is there an obvious next move to diagnose this problem?
> Is a successfull tnsping good enough to prove that the sqlnet stuff is
> OK?
>
> Just in case it isn't, I append some of the config files...
>
> tia
>
> Wayne
>
>
Received on Fri Aug 03 2001 - 16:41:23 CDT