home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC88649 Status: Geschlossen

SELECT STATEMENT WITH TO_DATE MAY TRAP IN FEDERATED ENVIRONMENT.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
select statement with to_date may trap in federated environment. 
 
A column which is specified date or timestamp. 
 
For example) 
date case 
db2 "describe table ndate" 
 
                                Data type 
Column 
Column name                     schema    Data type name 
Length     Scale Nulls 
------------------------------- --------- ------------------- 
---------- ----- ------ 
D1                              SYSIBM    DATE 
4     0 Yes 
 
timestamp case 
=> db2 "describe table nts" 
                                Data type 
Column 
Column name                     schema    Data type name 
Length     Scale Nulls 
------------------------------- --------- ------------------- 
---------- ----- ------ 
D2                              SYSIBM    TIMESTAMP 
10     6 Yes 
 
Both of the following SQL may trap. 
select * from ndate 
  where to_date(d1,'yyyy-mm-dd') ='2011-11-11' 
select * from nts 
  where to_date(d2,'yyyy-mm-dd') ='2011-11-11' 
 
Here is a snippet of stack trace. 
 
<sqlnq_qclqncparent::op> 
<sqlnt_translate::sqlnt_add_function> 
<sqlnt_translate::sqlnt_add_expression> 
<sqlnt_translate::sqlnt_add_function> 
<sqlnt_translate::sqlnt_add_expression> 
<sqlnt_translate::sqlnt_add_predicates> 
<sqlnt_translate::sqlnt_translate_scan> 
<sqlnt_translate::dispatch_pop> 
<sqlnt_translate::sqlnt_translate_sort> 
<sqlnt_translate::dispatch_pop> 
<sqlnt_translate::sqlnt_translate_scan> 
<sqlnt_translate::dispatch_pop> 
<sqlnt_translate::sqlnt_translate_mate> 
<sqlnt_translate::dispatch_pop> 
<sqlnt_translate::sqlnt_translate_pipe> 
<sqlnt_translate::dispatch_pop> 
<sqlnt_translate::sqlnt_translate_ship>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* FEDERATED ENVIRONMENT                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 2.                   * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.11.2012
31.12.2012
31.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList