DB2 - Problembeschreibung
| Problem IC92705 | Status: Geschlossen |
THE REMOTE CONNECTION'S ISOLATION LEVEL IS SERIALIZABLE WHEN USING SQL SERVER WRAPPER 2PC FEATURE | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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: | |
| Local-Fix: | |
| verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
| Lösung | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Kommentar | |
New requirement for F2PC | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC96413 IC96418 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 31.05.2013 16.12.2013 16.12.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.9 |
|
| 9.7.0.9 |
|