SAP Knowledge Base Article - Preview

1895331 - ESP crashes when sending data via the HANA Output Adapter

Symptom

  • An ESP project using the HANA Output Adapter crashes while trying to load data to HANA.
  • The "esp_server.log" file contains the following error:

2013-08-01 13:34:10.751 | 11894 | container | [SP-3-114113] (28.214) sp(11782) Platform()::processSignal(): fatal error (signal=11) in thread id 11894, thread name 'unknown thread'; aborting.

  • An examination of the core file shows the crash occurred in the following section of code:

% gdb $ESP_HOME/bin/esp_server core

(gdb) where

Program terminated with signal 6, Aborted.
#0  0x00007fc6bb352945 in raise () from /lib64/libc.so.6
(gdb) where
#0  0x00007fc6bb352945 in raise () from /lib64/libc.so.6
#1  0x00007fc6bb353f21 in abort () from /lib64/libc.so.6
#2  0x00007fc6be7d9a63 in SpServer::handleSignal(int) () from /usr/sap/sybase/sybase/ESP-5_1/bin/../lib/libesp_server_lib.so
#3  0x00007fc6ba940e09 in os::Linux::chained_handler(int, siginfo*, void*) () from /usr/sap/sybase/sybase/ESP-5_1/lib/jre/lib/amd64/server/libjvm.so
#4  0x00007fc6ba945537 in JVM_handle_linux_signal () from /usr/sap/sybase/sybase/ESP-5_1/lib/jre/lib/amd64/server/libjvm.so
#5  <signal handler called>
#6  0x00007fc6aad625db in SQLDBC_Retcode SQLDBC::Conversion::Translator::addCharacterData<3>(Communication::Protocol::ParametersPart&, SQLDBC::ConnectionItem&, Communication::Protocol::DataTypeCodeEnum, support::UC::char_iterator<3>, support::UC::char_iterator<3>, bool) ()
   from /usr/sap/hdbclient/libodbcHDB.so
#7  0x00007fc6aadae342 in SQLDBC::Conversion::StringTranslator::translateUCS2LEInput (this=0x51d66c0, datapart=..., citem=...,
    data=0x7fc60546b014 <Address 0x7fc60546b014 out of bounds>, lengthindicator=0x558a008, datalength=140488380252180, terminate=true)
    at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/SQLDBC/impl/StringTranslator.cpp:155
#8  0x00007fc6aad5ece1 in SQLDBC::Conversion::Translator::translateInput (this=0x51d66c0, datapart=..., parameter=..., citem=..., arrayoffset=1, 
    rowsize=0) at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/SQLDBC/impl/Translator.cpp:1885
#9  0x00007fc6aad0069a in SQLDBC::PreparedStatement::executeBatchFillData (this=0x5482500, requestpacket=<value optimized out>, 
    requestsegment=<value optimized out>, datapart=..., inputcursor=@0x7fc6a99b6ea8, firstrecord=@0x7fc6a99b6e98, startindex=0, nextindex=0, 
    maxNumberOfRecordsInBatch=32767, lobtruncated=@0x7fc6a99b6eee, errorindex=@0x7fc6a99b6ebc, used_error=...)
    at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/SQLDBC/impl/PreparedStatement.cpp:3020
#10 0x00007fc6aad14ec1 in SQLDBC::PreparedStatement::executeBatch (this=0x5482500)
    at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/SQLDBC/impl/PreparedStatement.cpp:868
#11 0x00007fc6aaca1c77 in ODBC_Statement::SQLExecute (this=0x51fed80)
    at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/ODBC/impl/ODBC_Statement.cpp:496
#12 0x00007fc6aaca5c38 in SQLExecute (statementHandle=0x51fe8d0) at /HDB/IMP/NewDB100_REL/src///sys/src/Interfaces/ODBC/impl/ODBC_Statement.cpp:2176
#13 0x00007fc6b1054b27 in SQLExecute () from /usr/lib64/libodbc.so.1
#14 0x00007fc6b12f28d1 in ChildLoader::bulkFlush(bool) () from /usr/sap/sybase/sybase/ESP-5_1/lib/adapters/libesp_adapter_db_hana_out_lib.so
#15 0x00007fc6b12f6474 in ChildLoader::execute() () from /usr/sap/sybase/sybase/ESP-5_1/lib/adapters/libesp_adapter_db_hana_out_lib.so
#16 0x00007fc6bf171471 in pt::_threadproc(void*) () from /usr/sap/sybase/sybase/ESP-5_1/bin/../lib/libesp_system_lib.so

NOTE: When examining the core file, take special notice of where "libodbc.so.1" was loaded from.


Read more...

Environment

  • ESP 5.1
  • unixODBC 2.3.1

 

Product

SAP Event Stream Processor 5.1 ; SAP Sybase Event Stream Processor 5.0

Keywords

core crash abort sigbus , KBA , BC-SYB-ESP , Sybase ESP (Event Stream Processor) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.