|
Problem IC84147
|
Status: Geschlossen |
SQL1469N MAY REPORT BECAUSE DRDA WRAPPER INCORRECTLY FORWARD THE CONNECT NODE NUMBER TO DATA SOURCE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
On a DPF system, DRDA would incorrectly forward the connect node
number to data source, if the node number is not exist on the
data source, you would receive SQL1469N error when accessing
the nickname.
The problem can be reproduced with below steps:
1. Setup Federation Server with below db2nodes.cfg
1 FEDSERVER 0
2 FEDSERVER 1
3 FEDSERVER 2
2. Setup data source server with below db2nodes.cfg
1 DSSERVER 0
2 DSSERVER 1
3. Connect to the Federation Server on Node number 3, access a
nickname pointing to a table on the data source server.
4. You would receive SQL1469N error because DRDA wrapper
incorrectly forwards the connect node number 3 to data source,
but node 3 is not exist on the data source server. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* The user is running Federation Server with DPF environment. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Server V10.1 FP1. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Lösung |
Firstly fixed in DB2 Server V10.1 FP1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 12.06.2012
01.11.2012
01.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
