common communication 错误？

• The problem was introduced in DB2 LUW Version 9.7 Fix Pack 9. It
  doesn't exist in Version 9.7 levels prior to Fix Pack 9.

  The problem exists in Database Partitioned Feature (DPF)
  environment only. It doesn't exist in single-node environment.

Local fix

• The problem can be avoided by setting DB2 registry variable
  DB2CHECKCLIENTINTERVAL=0 on DB2 server side.
  Please note the DB2 server instance must be recycled to pick up
  the change on the registry variable.

Problem summary

* USERS AFFECTED:                                              *
* All users of version 9.7 DPF environment on Linux, Unix and  *
* Windows platforms.                                           *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to DB2 LUW Version 9.7 Fix Pack 10 or higher levels.  *
****************************************************************

Problem conclusion

• First fixed in DB2 LUW Version 9.7 Fix Pack 10.

Temporary fix

• The problem can be avoided by setting DB2 registry variable
  DB2CHECKCLIENTINTERVAL=0 on DB2 server side.
  Please note the DB2 server instance must be recycled to pick up
  the change on the registry variable.

Comments

APAR Information

• APAR number

IT01529

• Reported component name

DB2 FOR LUW

• Reported component ID

DB2FORLUW

• Reported release

970

• Status

CLOSED PER

• PE

NoPE

• HIPER

NoHIPER

• Special Attention

NoSpecatt

• Submitted date

2014-05-05

• Closed date

2014-11-10

• Last modified date

2014-11-10

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

DB2 FOR LUW

• Fixed component ID

DB2FORLUW

Applicable component levels

• R970 PSN