DB2 - Problembeschreibung
Problem IC96418 | Status: Geschlossen |
THE REMOTE CONNECTION'S ISOLATION LEVEL IS SERIALIZABLE WHEN USING SQL SERVER WRAPPER 2PC FEATURE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
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. | |
Problem-Zusammenfassung: | |
User affected: Users who use SQL Server wrapper of InfoSphere Federation Server with 2PC Problem description and summay: See error description | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem was fistly fixed in Version 10.5 FixPak 3. This fix should be applied on the federation Server. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.09.2013 10.03.2014 10.03.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.3 | |
10.5.0.3 |