Re: TNS...pls help.

Hello,

The SQLNET.ORA is not absolutely necessary, the parameters about "name." are something related to Oracle Names, which provides names-server-like service lookup for TNS services.

What Keith's response is sufficient for your problem. But the final thing you may like to check is :

1. The environment variable TNS_ADMIN defined? Because Oracle will lookup the listener.ora, tnsnames.ora and sqlnet.ora..etc there. Most likely it should be $ORACLE_HOME/network/admin. Make sure your process which runs Netview has the TNS_ADMIN defined properly.
2. Another possibility is the tnsnames.ora and listener.ora, etc though are text-files, are VERY SENSITIVE to tabs and spaces (and also escape characters), and Oracle may not parse correctly and that's why Oracle doesn't recommend us to manually edit the files. You may try to re-create the tnsnames.ora and retyping the entries carefully. Type in one service and test it, if it works, copy-and-paste that service and edit their service names for others.

Hope these help.

cheers,
geoffrey

cary_at_nams.net wrote:
>
> Hi, Ellen,
>
> Yes, the SQLNET.ORA file is absolutely necessary and should be located in
> the same directory as the TNSNAMES.ORA and other network files. It is a
> simple text file, and the contents of an example file are given here:
>
> AUTOMATIC_IPC = OFF
> TRACE_LEVEL_CLIENT = OFF
> names.directory_path = (TNSNAMES, HOSTNAME)
> names.default_domain = world
> name.default_zone = world
> names.default_domain=world
>
> The critical part is the names.directory_path variable. This example tells
> Oracle to use the TNSNAMES.ORA file to process SID requests and to use the
> local hosts file to match host names with IP addresses. Provided TNSNAMES.ORA
> is configured properly, the presence of the SQLNET.ORA file should eliminate
> your problems.
>
> Cary
>
Received on Wed Dec 30 1998 - 00:00:00 CST