Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC89715 Status: Geschlossen

Bad performace when using Sybase nickname with BIGINT column predicates

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The logical and mathematical expression with BIGINT can't be 
pushed down by Sybase wrapper. 
E.g. Here testnick is Sybase nickname,  c1 is BIGINT type: 
update  testnick set c2='aa' where c1=1003898714
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Bad performace when using Sybase nickname with BIGINT column * 
* predicates                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 fixpack 3.                           * 
****************************************************************
Local-Fix:
alter nickname <your_nickname> alter column <bigint_column> 
local type DECIMAL(19, 0)
verfügbare FixPacks:
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
This problem is fixed in version 10.1 fixpack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.01.2013
30.10.2013
30.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList