1980826 - Due to Dynamic Collision, Emergency Shutdown of a Secondary server in IQ Multiplex - SAP IQ

• A secondary server in IQ Multiplex can be shutdown intentionally due to dynamic collision.
• Any changes of shared IQ object schema lead that the information is propagated to Secondary server by TLV replaying.
• When the same object is locked/used by sesison(s) on Secondary, Secondary server tries to disconnect the session(s) for TLV reply. 
• The session(s) may be not disconnected and it results in happening emergency shutdown, but in lower version of IQ16 SP08, there seems to be an issue why dropping session does work.
• For example, following .srvlog shows operations on Secondary server after detecting Dynamic Collision. It says "...connection(s) are still holding a lock..", but this message is not clear to know detail lock session and information.

I... User "dbo" dropped connection 911 ("DBA")
I... -- dropped 0 of 1 connection(s) for table: DBA.alt_sales_order -- but 1 connection(s) are still holding a lock
I... MPX dynamic collision on DBA.alt_sales_order -- connection 911
I... User "dbo" dropped connection 911 ("DBA")
...
I... -- dropped 0 of 1 connection(s) for table: DBA.alt_sales_order -- but 1 connection(s) are still holding a lock
I... Database server shutdown due to HUP signal
I... TCPIP listener on IP address 0.0.0.0:6639 is exiting
...

• SAP IQ 15.4
• SAP IQ 16.0 

MPX_SERVER_HANG_ON_EMERGENCY_SHUTDOWN , KBA , BC-SYB-IQ , Sybase IQ , Bug Filed