DB2 UDB 7.2 WSE
Fixpak 9
Linux Red Hat 7.3
A very strange thing just happened w/ my DB2 server. I am on Linux and
using NIS - the instance owner is in the servers /etc/passwd file.
Suddenly, DB2 would not authenticate any NIS-based logins, but it
*would* authenticate the local non-NIS instance owner. This was
happening not only w/ local connections on the server, but also
connections across the network (I am using JDBC and db2jstrt daemon)
When I tried to login w/ a NIS login, I got:
SQL1403N The username and/or password supplied is incorrect.
SQLSTATE=08004
Even though I was using a good login and password.
NIS logins have been working just fine for months and months. No
configuration has been changed. Here are the relevant config
settings:
Database manager authentication (AUTHENTICATION) = SERVER
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
I stopped and started NIS on the server, but no help. "ypcat passwd"
output looked correct..
So in desperation I did a db2stop and a db2start and suddenly NIS
logins could be used again...
Bringing the database down around here is a very big deal, so now I
will need to debrief you-know-who on why it happened.
Any ideas? Why would DB2 suddenly become unable to NIS
authenticate?
TIA
allen