PASSWORD MISSING - error

[db2_d_b_a]

Hello All,

I have a rather strange issue here connecting to the database on an ESE
environment. A little background on the issue. The cluster is an 8
server, 64 partition system. So when I try to do a rah or db2_all "db2
connect DBNAME", it works just fine. However, when i explicitly try to
connect from server1 to node9 (which is on server2) it gives me an
error.

server1->export DB2NODE=10
server1->db2 terminate
DB20000I The TERMINATE command completed successfully.
server1->db2 connect to EDWDB
SQL30082N Attempt to establish connection failed with security reason
"3"
("PASSWORD MISSING"). SQLSTATE=08001
server1->

Also, found the following entry in diag log, which i am not sure
whether its related.

2007-01-04-10.53.15.641964-360 I2959089A319 LEVEL: Warning
PID : 1823088 TID : 1 PROC : db2bp
INSTANCE: db2edwp2 NODE : 000
FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
RETCODE : ZRC=0x805C013E=-2141454018=SQLEX_PASSWORD_MISSING "Missing
password"

The servers are using ssh for connections and the KEYs have been
generated properly. As I said earlier RAH and Db2_all works just fine.

Any help figuring this out will be greatly appreciated.

Cheers !!

[Knut Stolze]

db2_d_b_a wrote:

Hello All,

I have a rather strange issue here connecting to the database on an ESE
environment. A little background on the issue. The cluster is an 8
server, 64 partition system. So when I try to do a rah or db2_all "db2
connect DBNAME", it works just fine. However, when i explicitly try to
connect from server1 to node9 (which is on server2) it gives me an
error.

server1->export DB2NODE=10
server1->db2 terminate
DB20000I The TERMINATE command completed successfully.
server1->db2 connect to EDWDB
SQL30082N Attempt to establish connection failed with security reason
"3"
("PASSWORD MISSING"). SQLSTATE=08001
server1->

I guess you have AUTHORIZATION set to SERVER? Connecting to nodes residing
on the same machine works because you are already logged in at the server.
With nodes on other machines, you come from a remote client and DB2 doesn't
know who you are and what your password is. Therefore, you will have to
provide both (or set the authorization to CLIENT).

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[db2_d_b_a]

I am not sure whether thats the problem here, for that situation shud
be taken care of by:

Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT

And more over i verified on another server with a similar setup. It
does not have this problem. It lets me connect to any node without
giving this error.
Knut Stolze wrote:

db2_d_b_a wrote:

Hello All,

I have a rather strange issue here connecting to the database on an ESE
environment. A little background on the issue. The cluster is an 8
server, 64 partition system. So when I try to do a rah or db2_all "db2
connect DBNAME", it works just fine. However, when i explicitly try to
connect from server1 to node9 (which is on server2) it gives me an
error.

server1->export DB2NODE=10
server1->db2 terminate
DB20000I The TERMINATE command completed successfully.
server1->db2 connect to EDWDB
SQL30082N Attempt to establish connection failed with security reason
"3"
("PASSWORD MISSING"). SQLSTATE=08001
server1->

I guess you have AUTHORIZATION set to SERVER? Connecting to nodes residing
on the same machine works because you are already logged in at the server.
With nodes on other machines, you come from a remote client and DB2 doesn't
know who you are and what your password is. Therefore, you will have to
provide both (or set the authorization to CLIENT).

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[Knut Stolze]

db2_d_b_a wrote:

I am not sure whether thats the problem here, for that situation shud
be taken care of by:

Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT

Those two settings are only relevant if AUTHORIZATION = CLIENT. Do you have
that?

And more over i verified on another server with a similar setup. It
does not have this problem. It lets me connect to any node without
giving this error.

Have you verified that the error message vanishes once you provide
username/password?

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[db2_d_b_a]

I agree to certain extent your point is valid. However, what astonishes
me is that the same setting for the other server works. And the db2_all
and the rah command works just fine for both the servers.
Knut Stolze wrote:

db2_d_b_a wrote:

I am not sure whether thats the problem here, for that situation shud
be taken care of by:

Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT

Those two settings are only relevant if AUTHORIZATION = CLIENT. Do you have
that?

And more over i verified on another server with a similar setup. It
does not have this problem. It lets me connect to any node without
giving this error.

Have you verified that the error message vanishes once you provide
username/password?

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[Knut Stolze]

db2_d_b_a wrote:

I agree to certain extent your point is valid. However, what astonishes
me is that the same setting for the other server works. And the db2_all
and the rah command works just fine for both the servers.

Then you have some sort of difference in the configuration of both servers
and it would be interesting to know what that is.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

[db2_d_b_a]

Thanks for all your assistance .. really appreciate that. And will
surely, update here if i find something worth regarding this.

Cheers !

Knut Stolze wrote:

db2_d_b_a wrote:

I agree to certain extent your point is valid. However, what astonishes
me is that the same setting for the other server works. And the db2_all
and the rah command works just fine for both the servers.

Then you have some sort of difference in the configuration of both servers
and it would be interesting to know what that is.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany