|
Problem IC62661
|
Status: Closed |
Error SQL30090 occurs on the iSeries V5R4 client when connecting to federated DB2 LUW server. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Error SQL30090 occurs on the iSeries V5R4 client when
connecting to a federated DB2 LUW server.
The explanation for this error is the following:
The DB2 for LUW server provides federated access to remote
DB2 and non-DB2 data sources. Prior to V9, the DB2 for LUW
server supported only 1PC (one-phase commit) access outbound to
federated data sources, even though some data sources,
such as DB2, already support 2PC (two-phase commit) access
inbound, while others do not. Because of that, the 2PC
connection to a DB2 LUW federated server was downgraded to 1PC
for certain non-LUW clients, so that they can still do 1PC
update to federated data sources.
As of V9, DB2 LUW federated server can indicate
to the client when a 1PC update has been performed. It will
then be up to theclient whether the update should be allowed.
So, if the client has the DRDA level that allows this
negotiation, the LUW federated server will no longer downgrade
its 2PC connection to 1PC.
One of the clients that now have this
capability is iSeries (or System i) V5R4M0 and
higher. This defect has been opened becauseof the wrong check
that is done by DB2 LUW federated server whenan iSeries
client tries to connect to it as2PC to see whether that
connection needs to be downgraded to 1PC. Instead of
downgrading the connection for iSeries clients that are
lower than V5R4M0, the LUW federated server does that only
for clientsthat are lower than V5R4M1. This results in 2PC
connections fromV5R4M0 clients being unnecessarily
downgraded. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Error SQL30090 occurs on the iSeries V5R4 client when *
* *
* connecting to a federated DB2 LUW server. *
****************************************************************
* RECOMMENDATION: *
* Upgraded the server to V9.7 FP1 *
**************************************************************** |
| Local Fix: |
|
| 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 |
Fixed in V9.7 FP1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.08.2009
21.01.2010
21.01.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
|
 |
