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 IT04010 Status: Geschlossen

SQL101N MAY BE RETURNED WHEN SPECIAL REGISTER IS REFERENCED MANY TIMES IN
THE SAME EXPRESSION IN THE SELECT LIST OR IN THE WHEN

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
SQL101N may be returned when the special register CURRENT DATE, 
CURRENT TIMESTAMP, CURRENT TEMPORAL SYSTEM_TIME or CURRENT 
TEMPORAL BUSINESS_TIME is referenced multiple times in a complex 
expression 
 
The multiple references could also be a result of a single 
reference of the special register in the search condition of a 
CASE expression that has many WHEN clauses.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FixPack 5                               * 
****************************************************************
Local-Fix:
Set registry variable DB2_EXTENDED_OPTIMIZATION=OLD_SPREG_FF. 
 
For example: 
db2set -im DB2_EXTENDED_OPTIMIZATION=OLD_SPREG_FF
Lösung
Upgrade to DB2 V10.1 FixPack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.08.2014
16.07.2015
16.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList