|
Problem IC65517
|
Status: Closed |
ERROR MESSAGE FROM ACCEPTSECURITYCONTEXT MAY BE WRITTEN IN DB2DIAG.LOG, EVEN THOUGH THERE IS NO ERROR IN THE CONNECT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
Error message from AcceptSecurityContext() may be written in
db2diag.log, even for the case that the connection is
established successfully.
The message is logged by DB2's Kerberos Plug-in. The problem
exists on the Windows platform only.
2010-01-06-12.32.47.414000+540 I2120F424 LEVEL: Error
PID : 3504 TID : 4516 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPLE
APPHDL : 0-534
EDUID : 4516 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 38 bytes
AccpetSecurityContext returned 0x90312
This error can be safely ignored. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error description field for more information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.5 FixPack 6. *
**************************************************************** |
| Local Fix: |
Not Available. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.5 FixPack 6. |
| Workaround |
see LOCAL FIX. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65572 IC67903
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.01.2010
22.06.2010
22.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
