SAP Knowledge Base Article - Preview

2011998 - SIGKILL or aborting of dbisql can leave an unused semaphore - SAP IQ


  • DBISQL always allocates a semaphore at the starting timing in AIX, HP-UX and Linux platforms.
  • The semaphore is used only for the same-computer SHMEM communications.
  • If dbisql exits by SIGKILL or aborting from some triggers, the allocated semaphore can be left.
  • As the result, when OS can run out of semaphore, the new dbisql connection will receive the following error message:

<Error message>
Could not connect to the database.
Connection error: Insufficient system resources - failed to allocate a SYSV semaphore
SQLCODE=-832, ODBC 3 State="08001"



  • SAP IQ 15.x
  • SAP IQ 16.0
  • SAP SQL Anywhere 12.0
  • SAP SQL Anywhere 16.0
  • SAP SQL Anywhere 17.0


SAP IQ 16.0 ; SAP SQL Anywhere 16.0 ; SAP SQL Anywhere 17.0 ; SAP Sybase IQ 15.2 ; SAP Sybase IQ 15.4 ; SAP Sybase SQL Anywhere 12.0


abort, ipcrm -s <smid> , KBA , BC-SYB-IQ , Sybase IQ , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To

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.