DB2 - Problembeschreibung
Problem IC63627 | Status: Geschlossen |
CHANGE EFFECTIVE ID TO MATCH INSTANCE OWNER FOR SSL PROGRAM DURING DB2START. SQL6048N IN DPF. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
Programming Error Corrected | |
Local-Fix: | |
Workaround: Use SSL 1.0 instead of 2.0 until this fix is applied. | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Code Fixed | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.10.2009 18.01.2010 18.01.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
9.5.0.5 |