|
Problem IC62724
|
Status: Closed |
ON AIX THE TCP_NODELAYACK IS NOT BEING CORRECTLY SET IN THE SOCK ET LAYER BY DB2 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Starting in V95 of DB2, we decided to enable the TCP_NODELAYACK
option at the socket layer instead of globally at the OS level
for better performance of network operations between partitions
when traffic is low. This APAR is open to address the fact that
this is not being set correctly. |
| Problem Summary: |
Users Affected: Any using DPF feature across multiple machines
Problem Description: TCP_NODELAYACK is not being set correctly
at the socket layer which can results in inter-partition
communication delays
Problem summary: see above |
| Local Fix: |
As a workaround you can enable TCP_NODELAYACK in the kernel by
setting it to 1. |
| 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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
Problem was first fixed in Version 9.7 FixPak 1 |
| Workaround |
As a workaround you can enable TCP_NODELAYACK in the kernel by
setting it to 1. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.08.2009
28.12.2009
28.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
