DB2 - Problembeschreibung
Problem IC66378 | Status: Geschlossen |
DB2 INSTANCE ENDS ABNORMALLY COMPILING QUERY WITH A LARGE NUMBER OF UNIONS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Compiling a query with a large number of UNIONs may result in a stack overflow and termination of the DB2 instance. The call stack looks similar to this example from Linux: 0000002A97833854 _Z24sqlnq_process_connect_byP9sqlnq_qtbP3loc + 0x001c (/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6.glibc.2. 3/lib64/libdb2e.so.1) 0000002A97835D77 _Z24sqlnq_process_connect_byP9sqlnq_qtbP3loc + 0x253f (/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6.glibc.2. 3/lib64/libdb2e.so.1) 0000002A97835D77 _Z24sqlnq_process_connect_byP9sqlnq_qtbP3loc + 0x253f (/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6.glibc.2. 3/lib64/libdb2e.so.1) 0000002A97835D77 _Z24sqlnq_process_connect_byP9sqlnq_qtbP3loc + 0x253f (/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6.glibc.2. 3/lib64/libdb2e.so.1) ... For this problem to occur, the DB2_COMPATIBILITY_VECTOR registry variable must have the hierarchical query bit set (bit 4), e.g.: DB2_COMPATIBILITY_VECTOR=08 or DB2_COMPATIBILITY_VECTOR=ORA But the query does not necessarily have to use hierarchical queries (i.e. a CONNECT BY clause). | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * Compiling a query with a large number of UNIONs may resultin * * astack overflow and termination of the DB2 instance. * * Thecallstack looks similar to this example from * * Linux:0000002A97833854_Z24sqlnq_process_connect_byP9sqlnq_qtbP * 0x001c(/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6. * 0x253f(/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6. * 0x253f(/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6. * 0x253f(/ms/dist/ibmdb2/PROJ/ds/9.5.4.4/.exec/x86_64.linux.2.6. * this problem to occur, the * * DB2_COMPATIBILITY_VECTORregistryvariable must have the * * hierarchical query bit set (bit * * 4),e.g.:DB2_COMPATIBILITY_VECTOR=08orDB2_COMPATIBILITY_VECTOR= * the query does not necessarily have to use * * hierarchicalqueries (i.e. a CONNECT BY clause). * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 Fix Pack 2Otherwise, disable * * hierarchical queries if not needed byunsetting bit 4 * * inDB2_COMPATIBILITY_VECTOR. Alternatively, rewrite the * * querytoreduce the number of UNIONs. * **************************************************************** | |
Local-Fix: | |
Disable hierarchical queries if not needed by unsetting bit 4 in DB2_COMPATIBILITY_VECTOR. Alternatively, rewrite the query to reduce the number of UNIONs. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 v9.7 Fix Pack 2 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 16.02.2010 25.05.2010 25.05.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP2, 9.7.FP2Other | |
Problem behoben lt. FixList in der Version | |
9.7.0.2 |