|
Problem IC63476
|
Status: Closed |
CHANGE EFFECTIVE ID TO MATCH INSTANCE OWNER FOR SSL PROGRAM DURING DB2START. SQL6048N IN DPF. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
PROBLEM:
After upgrading SSL from v1.0 to v2.0, db2start fails with
SQL6048N in a DPF system using SSL for intra node communication.
The following message is in the diag.log:
2008-12-08-08.20.56.641600-360 E40623A517 LEVEL: Error
PID : 528432 TID : 1 PROC :
db2start
INSTANCE: <instance name> NODE : 000
FUNCTION: DB2 UDB, oper system services,
sqloPdbInitializeRemoteCommand,
probe:
200
MESSAGE : ZRC=0x810F0012=-2129723374=SQLO_COMM_ERR
"Communication error"
DATA #1 : String, 31 bytes
<hostname>
DATA #2 : String, 31 bytes
<hostname>
DATA #3 : String, 45 bytes
ssh: real and effective user IDs must match. |
| Problem Summary: |
Programming Error Fixed |
| Local Fix: |
Workaround:
Use SSL 1.0 instead of 2.0 until this fix is applied. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Code Corrected |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.09.2009
18.01.2010
18.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
