| Infodoc ID |
|
Synopsis |
|
Date |
| 18622 |
|
ypbind[pid]: service not installed, use /usr/sbin/ypinit -c and using Oracle |
|
24 Mar 1999 |
If you have a machine in an Oracle environment using the TNS listener and keep
getting the following error messages in /var/adm/messages and on the console
every 5 secs or so then it could be due to the way in which oracle has been
configured.
Jan 14 13:00:12 applsrv1 ypbind[9858]: service not installed, use
/usr/sbin/ypinit -c
NOTE: This problem does not seem to impact the performance of YP/NIS or
Oracle and appears to be annoying rather than a problem.
Oracle uses the following for configuration:
tnsnames.ora - Defines the client side connectivity, ie how to get
to the server.
listener.ora - Defines what connections the server side listens for.
sqlnet.ora - For both the client and server sides, it configures
the way the network transport operates.
If something (client or server side) formulates a query which that leads to
it attempting to contact a non existent database, the setup is likely to
send a query off to NIS/YP. It is at this stage, that the NIS/YP domainname
in ypbind gets corrupt.
Therfore sqlnet.ora needs to be configured such that it will never go near
NIS/YP. You need an entry in sqlnet.ora:
names.directory_path=(tnsnames,onames)
This needs to be done for all client and server side configurations. Is I
understand it oracle will look in the following order:
$TNS_ADMIN
$ORACLE_HOME/network/admin
/var/opr/oracle
to find the sqlnet.ora configuration.
Top
Sun Proprietary/Confidential: Internal Use Only