DB2 - Problembeschreibung
Problem IT02091 | Status: Geschlossen |
DB2 hang when using load utility with dumpfile option | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
1. Problem description DB2 hang while loading large data files using db2 load utility with dumpfile option during the analysis phase. However, By removing the DUMPFILE option from the LOAD command, the db2 hang problem can be avoided and the LOAD command can complete successfully. There is also another case. If cleaning up the data, such as the numerical data coming from Oracle data source NUMBER data type that is too big for DB2's datatype to handle, the db2 hang problem would not happen and the LOAD command can complete successfully. 2. Operating system and level: AIX 64BIT 7.1 3. Client, server, and gateway information c. Server information, if applicable Project: DB2 v10.5.0.3 Build Level: s140203 Environment (including Platform and bitness): AIX 64BIT 7.1 4. System setup Server is running DB2 partitioned database environment. Number of nodes in db2nodes.cfg is: 1 Current node number is: 0 Node information from the db2nodes.cfg file: 0 db210lpar2.svl.ibm.com 0 5. Diagnostic information callstack in debugger pthread_kill () from /lib64/libpthread.so.0 ossPthreadKill (threadId=46913235708224, eduSignal=12) at /view/ypchen_db2_v105fp3_linuxamd64_n140427_0427/vbs/common/osse /core/inc/ossthread.h:117 sqloDumpEDU () from /nfshome/ypchen/sqllib/lib64/libdb2e.so.1 sqle_panic (flags=0) at sqle_bsu.C:555 sqle_trap () at sqle_bsu.C:867 sqlzAssertFailedValist () from /nfshome/ypchen/sqllib/lib64/libdb2e.so.1 sqlzAssertFailed () from /nfshome/ypchen/sqllib/lib64/libdb2e.so.1 sqluiGetNextLoadBuf (pUicwa=0x2aaba94e1040, ppEndOfBuffer=0x2aaad6bfb8b8, pStatus=0x2aaad6bfb84c, pbMoreDataThisSeq=0x2aaad6bfb854) at /view/ypchen_db2_v105fp3_linuxamd64_n140427_0427/vbs/engn/squ/.. /sqi/sqluicgf.C:1375 sqlulcgf ( pStartOfField=0x2aaba94e20b8 "2014-01-13 00:00:00\rcom depreciaᅦ￵ᅦワo equipamentos/aplicativos de informᅦᆳ\" 226\" \" o\" ", pEndOfField=0x2aaba94ea075 "", pUicwa=0x2aaba94e1040, bKeepBlanksHere=false, uiSqlType=263) at /view/ypchen_db2_v105fp3_linuxamd64_n140427_0427/vbs/engn/squ/.. /sqi/sqluicgf.C:1201 sqlulcrr (pTcb=0x2aab989f2b80, pValues=0x2aab9824ea20, pUicwa=0x2aaba94e1040, pPrivateACB=0x2aab9822f080, AppnCp=1208) at /view/ypchen_db2_v105fp3_linuxamd64_n140427_0427/vbs/engn/squ/.. /sqi/sqluicrr.C:741 sqluGetAndFormatRecords (pComACB=0x2aab9811f080, pFrmCB=0x2aacdd793218, iNumVals=21, columnInUse=0x2aaad6bfcdb8, columnInUseSize=21, data=0x2aab9820e0a0, pWorkArea=0x2aaba94e1040 "", ppOrderedValues=0x2aab9824ea20, Values=0x2aab9824e4a0, pFailButBuild=0x2aaad6bfc9a0) at sqluldat.C:3185 sqluRunCDEAnalyzePhase (pComACB=0x2aab9811f080, pFrmCB=0x2aacdd793218, iNumVals=21, columnInUse=0x2aaad6bfcdb8, columnInUseSize=21, data=0x2aab9820e0a0, ppWorkArea=0x2aaad6bfcdb0, ppOrderedValues=0x2aab9824ea20, Values=0x2aab9824e4a0, bPrimaryFormatter=0, mtMsgType=SqluMessage::SqluSignalRoundRobinMsg) at sqlu_tfmt.C:553 sqluCFormatter::iRun (this=0x2aacdd793080) at sqluldat.C:1570 sqluLoadEDUDriver (pArgs=0x2aaad6bfdf88 "\200\360\021\230\253*", argsSize=168) at sqluedus.C:2817 sqloEDUEntry () from /nfshome/ypchen/sqllib/lib64/libdb2e.so.1 start_thread () from /lib64/libpthread.so.0 clone () from /lib64/libc.so.6 ?? () 6. How to reproduce the problem n/a 7. Did anything in particular seem to cause this problem? No. this problem happens on the latest version v10.5 fp3 8. Is this problem a regression? If so, please provide details on the last successful build level similar to (3) above. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2LUW * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 FP4 * **************************************************************** | |
Local-Fix: | |
By removing the DUMPFILE option from the LOAD command, the db2 hang problem can be avoided and the LOAD command can complete successfully. If cleaning up the data, such as the numerical data coming from Oracle data source NUMBER data type that is too big for DB2's datatype to handle, the db2 hang problem can be avoided and the LOAD command can complete successfully. | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 28.05.2014 29.09.2014 29.09.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |