|
Problem IC96280
|
Status: Closed |
DIFFERENT BEHAVIOUR IN DB2 WHEN USING ORACLE SYNTAX "CONNECT BY NOCYCLE LEVEL" |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
An example SQL:
----------------------------------------------------------------
SELECT LEVEL FROM DUAL CONNECT BY NOCYCLE LEVEL <= 10
----------------------------------------------------------------
Since the virtual table DUAL has 1 row, the intermediate result
table Hn+1 would return the same row as the one that is already
in the hierarchical path. According to the documentation, the
NOCYCLE keyword will not include the repeated row. This is an
intended behaviour in DB2, which is different from Oracle
behaviour. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
Rewrite the query using DB2 syntax. The following technotes may
be of help:
http://www.ibm.com/developerworks/data/library/techarticle/dm-05
10rielau/
http://www.ibm.com/developerworks/ibmi/library/i-db2connectby/in
dex.html |
| available fix packs: |
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
|
| Solution |
Upgrade to DB2 version 10.1 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
02.10.2013
02.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
