SAP Knowledge Base Article - Preview

2501261 - SAP IQ coordinator goes into a hang state on restart after crash

Symptom

  • SAP IQ coordinator goes into a hang state on restart after crash.
  • All secondary nodes are up and running and were not impacted by the coordinator crash.
  • Pstacks collected on coordinator node restart show no movement between the pstacks and two threads that are of interest in this case show the following functions:

Threads (1): 1228
#0  0x0000003d368eaf67 in semop
#1  0x00007f2fec6a5c5c in sysv_waiton_semaphore
#2  0x00007f2fec639d48 in c_cmdseq_conn_notifier::block(unsigned int)
#3  0x00007f2fec647070 in do_recv(c_strm_sconn*, unsigned char*, unsigned char*, void**)
#4  0x00007f2fec648679 in SQLPresReceive
#5  0x00007f2fec62fd86 in i_cs_ReceiveSuccessOrError
#6  0x00007f2fec61cbcc in i_cs_DoStreamsDisconnect
#7  0x00007f2fec61f24e in CmdSeqDisconnect
#8  0x00007f2fec6147ee in i_db_disconnect_explicit_name(a_global_data_structure*, char const*)
#9  0x00007f2fec617219 in idblib_db_string_disconnect
#10 0x00007f2fee641269 in inc_MpxConnection::~inc_MpxConnection()
#11 0x00007f2fee6398fd in inc_CommandHandler::CallRemoteRPC(unsigned int, unsigned int, inc_MpxRPCMsg&, inc_MpxRPCMsg&)
#12 0x00007f2fee639dcd in inc_CommandHandler::CallRemoteRPCForGTxnRec(unsigned int, unsigned int, inc_MpxRPCMsg&, inc_MpxRPCMsg&, s_bufman_errorInfo*)
#13 0x00007f2fee647ba5 in inc_gTxnRecEndpoint::CallProc(unsigned int, unsigned int, inc_MpxRPCMsg&, inc_MpxRPCMsg&, unsigned int, inc_rpcStats*, inc_connPool*, s_bufman_errorInfo*)
#14 0x00007f2fee64d462 in inc_gTxnRecEndpoint::GetGlobalTxnCxtData(unsigned int, unsigned char const*&, unsigned long long&)
#15 0x00007f2fee349f0e in st_database::DoRestoreGlobalTxnCxtData(gtrWorkUnitRow*, unsigned int, st_gTxnCxtRestoreWorkIter*)
#16 0x00007f2fee351301 in st_gTxnCxtRestoreWorkIter::ExecWork(int&, unsigned int)
#17 0x00007f2fed81e18a in workAllocator::DoWork(unsigned int)


Threads (1): 3057
#0  0x0000003d3700b63c in pthread_cond_wait@@GLIBC_2.3.2
#1  0x00007f2fed5dc08f in hos_condvar::Wait() const
#2  0x00007f2fee34f3a9 in st_gTxnCxtRestoreWorkIter::RestoreGlobalTxnCxtData()
#3  0x00007f2fee3503d5 in st_database::RestoreGlobalTxnCxtData()
#4  0x00007f2fee351165 in st_database::CompleteMpxRecovery()
#5  0x00007f2fed0d4e88 in UIQCtl_CompleteMpxRecovery
#6  0x00007f2fee3716c6 in st_SAIQInterfaceInfo::callFunction()


Read more...

Environment

  • SAP IQ 16.0
  • SAP IQ 16.1

Product

SAP IQ 16.0 ; SAP IQ 16.1

Keywords

 Sybase, CN , multiplex, deadlock, hung , CR809444, CR#809444, 809444, stacktrace, stktrc , stack trace , KBA , BC-SYB-IQ , Sybase IQ , Bug Filed

About this page

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

Search for additional results

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