DB2 FOR LUW / DB2FORLUW / 970 - DB2

When remotely connecting to a database and specifying invalid 
CONNECT_NODE on the client, the server can return 
incorrectly formatted error message: 
 
SQL1469N  Instance "" (nodenum "") does not have node "" 
specified in its db2nodes.cfg file. SQLSTATE=08004 
 
There are missing instance name and node numbers.

USERS AFFECTED: 
All 
 
PROBLEM DESCRIPTION: 
When remotely connecting to a database and specifying invalid 
CONNECT_NODE on the client, the server can return 
incorrectly formatted error message: 
 
SQL1469N  Instance "" (nodenum "") does not have node "" 
specified in its db2nodes.cfg file. SQLSTATE=08004 
 
There are missing instance name and node numbers. 
 
PROBLEM SUMMARY: 
As above.

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
 

First fixed in DB2 UDB Version 9.7, FixPak 1 (s091114).

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC63264 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

28.08.2009
21.12.2009
21.12.2009

9.7.