DB2 - Problem description
Problem IC85574 | Status: Closed |
INFORMATIONAL MESSAGE ADM7016I LOGGED IN DB2DIAG.LOG EVEN IF DIAGLEVEL=3 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
If your DB2 server is configured to use SSL and NOTIFYLEVEL is set to 4, you may see for each connection the following informational message in your db2diag.log file even if DIAGLEVEL is set to 3. 2012-06-29-15.46.39.822000+120 E3184F386 LEVEL: Info PID : 14032 TID : 13560 PROC : db2bp.exe INSTANCE: DB2_03 NODE : 000 EDUID : 13560 FUNCTION: DB2 UDB, common communication, sqlccLoadSSLLibrary, probe:1120 MESSAGE : ADM7016I The allowed SSLv3 cipher specs are "NONE". The allowed TLSv1 cipher specs are "2F350A". or 2012-06-29-15.46.39.858000+120 E3572F419 LEVEL: Info PID : 12260 TID : 9460 PROC : db2syscs.exe INSTANCE: DB2_03 NODE : 000 APPHDL : 0-22 EDUID : 9460 EDUNAME: db2agent () FUNCTION: DB2 UDB, common communication, sqlccSSLSocketSetup, probe:200 MESSAGE : ADM7015I The connection is using SSL version "TLSV11" and cipher spec "2F". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * SSL users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.7 FP7 or later * **************************************************************** | |
Local Fix: | |
db2 update dbm cfg using NOTIFYLEVEL 3 | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 9.7 FP7 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC90063 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.07.2012 08.04.2013 08.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |