DB2 - Problembeschreibung
Problem IT25633 | Status: Geschlossen |
PMR37651,999,000 BOOL DATATYPE MISMATCH B/W MICROSOFT AND DB2 LUW ( DB2 ON CLOUD) | |
Produkt: | |
DB2 CONNECT / DB2CONNCT / B10 - DB2 | |
Problembeschreibung: | |
Business Impact Level: This is POC and we are migrating .NET application from Netezza to IIAS Business Impact Description: Application migration is failing for BOOL datatypE Environment: IIAS version 1.0.8 Mismatch of Boolean data type : MS data type is BOOL where as DB2 LUW type is has SQL_Boolean which is causing the problem. They are trying to connect via ODBC and when accessing boolean datatype, they are getting error unknown SQL type -16 ============ Bool types in DB2 are known as SQL_BOOLEAN(2 bytes length) and in microsoft ODBC specification, matching data type for BOOL is SQL_BIT(1 byte length). Since application is fetching describe information for bool type and DB2 server is returning SQL_BOOLEAN(2 bytes length), this does not map to SQL_BIT. as per ODBC standard, SQL_BOOLEAN is 16 and SQL_BIT is -7. But we are DB2 compliant as DB2 expects SQL_BOOLEAN for Boolean type. https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com .ibm.db2.luw.apdv.cli.doc/doc/r0000526.html Either way, we need a mapping. We cannot go back and change server interpretation, however, we can provide patch in client to have correct mapping according to ODBC standard. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 ODBC users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 11.1.4.4 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 10.07.2018 02.12.2018 19.02.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |