- Following a shutdown or abort of SAP IQ 16, the multiplex coordinator node's restart and recovery process is taking a long time and gives the appearance of being hung.
- Looking at the IQMSG file and SRV log file, the first sequence of "opendatabase" messages shows that the recovery process has successfully completed:
- But, the second sequence of "opendatabase" messages gives the appearance that the IQ Server is stuck or hung:
- However, when using an operating system tool to check CPU consumption, it shows that the IQ Server process continues to consume CPU cycles.
SAP IQ 16
mpx, cn, co-ordinator, IQ16, IQ 16, OS, linux, windows, aix, solaris, unix, crash, failure, hang, hung, abort, sybase, "taking a long time", "taking long", recovery, slow, suspended, "dead lock" , KBA , BC-SYB-IQ , Sybase IQ , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.