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.
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
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 : Secondary server cannot maintain catalog sync.
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
Emergency Shutdown, Secondary server cannot maintain catalog sync, CR 760534, HUP signal in srvlog. , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this pageThis 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.