|
Problem IT36628
|
Status: Closed |
ZRC=0xFFFFFFFF=-1 error in db2diag.log when using purescale withSSL
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
3257115 data DB2 UDB base sys utilities sqlePopulateSrvlstEntry
fnc (3.3.5.1830.0.20)
pid 21971 tid 139802959668992 cpid 22099 node 1 probe 20
bytes 360
Data1 (PD_TYPE_DIAG_LOG_REC,352) Diagnostic log record:
2021-04-05-18.50.49.941245-240 I73468E351 LEVEL:
Error
PID : 21971 TID : 139802959668992 PROC :
db2sysc 1
INSTANCE: NODE : 001
HOSTNAME:
EDUID : 22 EDUNAME: db2pdbc 1
FUNCTION: DB2 UDB, base sys utilities, sqlePopulateSrvlstEntry,
probe:20
RETCODE : ZRC=0xFFFFFFFF=-1
This error is caused because sqlccGenerateSynclog is the
function to see the error. The condition for the error in this
function is that "SVCENAME is not set". Customer is using SSL,
so they did not set SVCENAME. A temporary work-around is to set
SVCENAME same as SSL_SVCENAME. There is no need to add TCPIP to
DB2COMM. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.7 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.7 or higher *
**************************************************************** |
| Comment |
Upgrade to 11.5.7 or higher |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.04.2021
30.11.2021
30.11.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
