DB2 - Problem description
Problem IC89081 | Status: Closed |
DIFFERENT BEHAVIOUR IN DB2 WHEN USING ORACLE SYNTAX "CONNECT BY NOCYCLE LEVEL" | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 9. * **************************************************************** | |
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 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Upgrade to DB2 Version 9.7 Fix Pack 9. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC95385 IC96280 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.12.2012 18.12.2013 18.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |