SAP Knowledge Base Article - Preview

1939539 - SAP Sybase IQ secondary node's emergency shutdown due to dynamic collision

Symptom

On rare occasions IQ secondary nodes can be emergency shutdowned due to dynamic collision.
If such a scenario occurs, then you will see similar message to the following in the .srvlog & .iqmsg file.

 *.srvlog
 ==========
  I. 05/23 18:13:58. -- Too many retries on dropping user connections. Server is shutting down.
  I. 05/23 18:13:58. Database server shutdown due to HUP signal

 
 *.iqmsg
 ==========
  I. 05/23 18:13:58. 0001833684 -- dropped 16 of 17 connection(s) for table: TEST_TABLE
                              -- but 1 connection(s) are still holding a lock
  I. 05/23 18:13:58. 0001833684 -- Too many retries on dropping user connections. Server is shutting down.
  I. 05/23 18:13:58. 0001833684 ***Emergency Shutdown***
  I. 05/23 18:13:58. 0001833684 Exception Thrown from db_iqutility.cxx:3948, Err# 46, tid 220 origtid 220
  I. 05/23 18:13:58. 0001833684    O/S Err#: 0, ErrID: 1025 (db_catalogException); SQLCode: -1009413, SQLState: 'QCB11', Severity: 23
  I. 05/23 18:13:58. 0001833684 [21051]: Secondary server cannot maintain catalog sync.

 


Read more...

Environment

This error only occurs on SAP Sybase IQ Multiplex's secondary nodes.

  • SAP SYBASE IQ12.7
  • SAP SYBASE IQ15.1
  • SAP SYBASE IQ15.2
  • SAP SYBASE IQ15.4
  • SAP IQ16.0

Product

SAP IQ 16.0 ; SAP Sybase IQ 15.2 ; SAP Sybase IQ 15.4 ; Sybase IQ 12.7

Keywords

Emergency Shutdown, Secondary server cannot maintain catalog sync, CR 760534, HUP signal in srvlog. , KBA , BC-SYB-IQ , Sybase IQ , Problem

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.