Re: sqlnet v2 - non-unique name error on reboot

Tony Damon wrote:
>
> Gary Walker (gjwalker_at_cix.compulink.co.uk) wrote:
> :
> : On a Sol2 Ora7.2 setup, every time the LISTENER is run after reboot, it
> : complains that the (db?) names are non-unique on the network.
> :
> : Editing the connect aliases in tnsnames.ora and listener.ora fixes this.
> : But next reboot ... and the same complaint. Eg sqlplus scott/tiger_at_mydb1
> : could become sqlplus scott/tiger_at_mydb2. The listener is usually not
> : stopped for a reboot (...it will be in future!).
> :
> : BUT, the set of network/admin files - listener.ora, tnsnames.ora and
> : sqlnet.ora were copied from a SunOS setup (7.1.6 rdbms) - which doesn't
> : show this problem. Listener starts up fine every time. These files were
> : edited on the new Sol2 box to change host names , oracle home directories
> : and, of course, the aliases. But not the key string in sqlnet.ora (could
> : this be conflicting with the SunOS box on the same network?).
> :
>
> Ok, a couple of guesses -
>
> where is the listener.ora file you're editing ? /var/opt/oracle ?
> or in product/<release>/network/admin ? Are you editing the right
> file? When the listener starts up, what parameter and log files
> does it say it's using? Are they what you expect?
>
> What is in /var/opt/oracle/oratab ? any duplicate names ?
>
> After reboot, what environment is the startup process running
> in ? Oracle's? Roots? Should be oracle's.
>
> HTH,
> Tony DamonYou might want to check and make sure that during the reboot that you
have issued before bringing up the listener:

su - oracle ( this should give you the same environment as oracle)

You also want to check and make sure that the TNS_ADMIN variable is pointing to the correct network/admin directory where the .ora files for sqlnet reside. Received on Tue Mar 19 1996 - 00:00:00 CET