|
Problem IC62186
|
Status: Closed |
AFTER ENABLING DB2_USE_IOCP, DB2 MAY ENCOUNTER EALREADY (56) "OPERATION ALREADY IN PROCESS" ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When DB2_USE_IOCP is enabled, the instance may crash with the
following error reported in the db2diag.log
2009-06-19-16.41.51.883506-240 E137264801A556 LEVEL: Error
(OS)
PID : 1204650 TID : 7290 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000
EDUID : 7290 EDUNAME: db2pclnr (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services,
sqloLioAssociateFHwithPort, probe:100
MESSAGE : ZRC=0x83000038=-2097151944
CALLED : OS, -, CreateIoCompletionPort
OSERR : EALREADY (56) "Operation already in progress"
DATA #1 : signed integer, 4 bytes
1874
DATA #2 : I/O Completion Port, PD_TYPE_IO_PORT, 4 bytes
0x0000011C
To avoid this problem set registry variable DB2_USE_IOCP=NO |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* AIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* When DB2_USE_IOCP is enabled, the instance may crash with *
* the *
* following error reported in the db2diag.log *
* *
* *
* *
* 2009-06-19-16.41.51.883506-240 E137264801A556 LEVEL: *
* Error *
* (OS) *
* *
* PID : 1204650 TID : 7290 PROC : *
* db2sysc *
* 0 *
* *
* INSTANCE: db2inst1 NODE : 000 *
* *
* EDUID : 7290 EDUNAME: db2pclnr (SAMPLE) 0 *
* *
* FUNCTION: DB2 UDB, oper system services, *
* *
* sqloLioAssociateFHwithPort, probe:100 *
* *
* MESSAGE : ZRC=0x83000038=-2097151944 *
* *
* CALLED : OS, -, CreateIoCompletionPort *
* *
* OSERR : EALREADY (56) "Operation already in progress" *
* *
* DATA #1 : signed integer, 4 bytes *
* *
* 1874 *
* *
* DATA #2 : I/O Completion Port, PD_TYPE_IO_PORT, 4 bytes *
* *
* 0x0000011C *
* *
* *
* *
* To avoid this problem set registry variable DB2_USE_IOCP=NO *
****************************************************************
* RECOMMENDATION: *
* Update to Db2 V9.7 FP1 *
**************************************************************** |
| Local Fix: |
To avoid this problem set registry variable DB2_USE_IOCP=NO |
| 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 |
DB2 V9.7 FP1 will contain the fix. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66396
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.07.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
