SQL6048N when using stopsap on DB2 dpf

[former_member196032]

when running stopsap/startsap as sidadm, the database does not come up. This is a dpf with 4 nodes.

I have to manually issue a db2start/db2stop force as db2sid, then su over to sidadm to bring up SAP.

What setting am I missing for the sidadm user?

[Former Member]

We have a similar situation. Did you ever get db2start/db2stop to work with sidadm and SSH?

[Former Member]

Goerge,

perhaps with this dokument you can see the light at the end of the tunnel:

http://www.ibm.com/developerworks/db2/library/techarticle/dm-0506finnie/index.html

best regards,

Joachim

[former_member196032]

Here is the answer: comes right from teh horses mouth, (SAP, that is) I had to open an OSS message:

DB2 Service has created V9 APAR IZ17763, and V8 APAR IZ17778 to fix thisSSH issue. Development is currently determining which V8 and V8 fixpaks

the APARs will be available in. Once that has been determined we will

let you know. If you need an immediate fix please let me know and we canrequest a special build ontop of your current DB2 level. If you need a

special build please issue 'db2level' and paste the output into this

message.

Here is the APAR description:

APAR IZ17763: WITH SSH SETUP DB2START FAILS BY A NON-INSTANCE USER WHO'SSECONDARY GROUP IS PART OF SYSADM, SYSCTRL OR SYSMAINT

ERROR DESCRIPTION:

When SSH is setup a db2start issued by a non-instance user

fails. The users's secondary group is part of sysadm or sysctrl

or sysmaint. But, the primary group is not.

The problem found out to be an improper value used for the real

group id of the non-instance user which is not equal to the

effective group id of the same user. The effective group id of

the user is equal to the primary group id of the instance

user.

The fix is to make the real group id same as the effecive group

id in the part of the code which was failing.

[Former Member]

Hi,

db2start on DPF uses rsh for communications between the nodes.

First check, if db2_all (which internally uses rsh) works as <sapsid>adm.

db2_all ls

If this also does not work, check the .rhosts file to verify if rsh is configured correct.

Best regards, Jens

[former_member196032]

db2_all ls checks out fine using sidadm user.

rsh is not active - per SOX - we use ssh

I don't use .rhosts file

Per IBM I set the DB2 registry var DB2RSHCMD=/usr/bin/ssh

thus I can submit ssh calls, just not the db2start or db2stop command.

All other db2_all commands work great with user sidadm

[Former Member]

Hi,

ok. SQL6048N indicates a communication error, otherwise my next question would be, if the users and groups setup is correct.

Have you checked the db2diag.log for additional information ?

Best regards, Jens