If you have an application that calls sqlugrpn() to load DATE
data into a partitioned table from a DB2 client 10.1 (or later),
the application may trap in sqlvdate().
For example, a DataStage job may generate a core dump with the
following stack :
Program terminated with signal 11, Segmentation fault.
#0 0x00007f5a2d3b7e69 in sqlvdate () from
/opt/IBM/db2/V10/lib64/libdb2.so.1
(gdb) where
#0 0x00007f5a2d3b7e69 in sqlvdate () from
/opt/IBM/db2/V10/lib64/libdb2.so.1
#1 0x00007f5a2d11c852 in sqlugrpn(unsigned short, unsigned
char**, unsigned short*, unsigned short, unsigned short,
sqlupi*, short*, short*, unsigned short, sqlca*, short, void*,
void*) () from /opt/IBM/db2/V10/lib64/libdb2.so.1
#2 0x00007f5a2d0bea0c in sqlugrpi_api () from
/opt/IBM/db2/V10/lib64/libdb2.so.1
#3 0x00007f5a2eb2ed62 in APT_DB2_GetRowPartitionInfo(sqlupi*,
char**, unsigned short*, APT_CharsetConverter&) ()
from
/opt/IBM/InformationServer/Server/DSComponents/bin/orchdb2op.so
#4 0x00007f5a2eb70d9d in APT_DB2HashRep::db2Node() const ()
from
/opt/IBM/InformationServer/Server/DSComponents/bin/orchdb2op.so
#5 0x00007f5a2eb712ad in
APT_DB2HashRep::db2NodeIndexInNodeGroup() const ()
from
/opt/IBM/InformationServer/Server/DSComponents/bin/orchdb2op.so
#6 0x00007f5a2eb7134c in APT_DB2Hash::db2NodeIndexInNodeGroup()
const ()
from
/opt/IBM/InformationServer/Server/DSComponents/bin/orchdb2op.so
#7 0x00007f5a374db1c8 in APT_DataSetRep::putRecord_part(bool&,
bool&) ()
from
/opt/IBM/InformationServer/Server/PXEngine/lib/liborchx86_64.so
#8 0x00007f5a374dbd0d in
APT_DataSetRep::putRecord_nonCombined(bool) ()
from
/opt/IBM/InformationServer/Server/PXEngine/lib/liborchx86_64.so
#9 0x00007f5a374c626b in APT_DataSetRep::putRecord(bool) ()
from
/opt/IBM/InformationServer/Server/PXEngine/lib/liborchx86_64.so
#10 0x00007f5a374c5001 in APT_OutputCursor::putRecord() ()
from
/opt/IBM/InformationServer/Server/PXEngine/lib/liborchx86_64.so |
