DB2 FOR LUW / DB2FORLUW / A10 - DB2

SQL Server wrapper uses the default isolation serializable when 
using federated two phase commit. 
 
Here is the reproducing scripts: 
db2 => set passthru <your_server>; 
 
db2 => select transaction_isolation_level from 
sys.dm_exec_sessions where host_name = '<your_federation_host>'; 
 
transaction_isolation_level 
--------------------------- 
                          2 
 
  1 record(s) selected. 
 
db2 => set passthru reset; 
DB20000I  The SQL command completed successfully. 
 
db2 => alter server SQLSERVER options(set DB2_TWO_PHASE_COMMIT 
'N'); 
DB20000I  The SQL command completed successfully. 
db2 => 
db2 => set passthru <your_server>; 
DB20000I  The SQL command completed successfully. 
db2 => select transaction_isolation_level from 
sys.dm_exec_sessions where host_name = '<your_federation_host>'; 
 
transaction_isolation_level 
--------------------------- 
                          2 
 
  1 record(s) selected. 
 
db2 => set passthru reset; 
DB20000I  The SQL command completed successfully. 
 
This APAR will support new behavior: set the remote 
corresponding  isolation according to DB2's isolation.

User affected: 
  Users who use  InfoSphere Federation Server 
Problem description and summay: 
  See error description

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
 

Problem was fistly fixed in Version 10.1, FixPak 3. This 
fix should be applied on the federation Server.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.09.2013
28.10.2013
28.10.2013