Symptom
Customer got an emergency shutdown of secondary node during recreating a user account which could not log on the secondary node. It's reproducible issue.
Followings are scenarios what customer faced and executed.
[ iqmsg of secondary node at the moment of emergency shutdown ]
...
I. 01/07 16:51:36. 0006082192 Txn 453226632 0 443956756
I. 01/07 16:51:36. 0006082192 Shared IQ Store update DDL statement:
CREATE user "user001" identified by encrypted 0x01430EE2F37718E27E20....
I. 01/07 16:51:36. 0006082192 Disposition: SQLSTATE:WW101 [ No recovery!! ]
I. 01/07 16:51:36. 0006082192 ***Emergency Shutdown***
I. 01/07 16:51:36. 0006082192 Exception Thrown from db_iqutility.cxx:4038, Err# 46, tid 70 origtid 70
I. 01/07 16:51:36. 0006082192 O/S Err#: 0, ErrID: 1025 (db_catalogException); SQLCode: -1009413, SQLState: 'QCB11', Severity: 23
I. 01/07 16:51:36. 0006082192 [21051]: Secondary server cannot maintain catalog sync.
-- (db_iqutility.cxx 4038)
I. 01/07 16:51:36. 0006082192 sp_mpxprocesstlvlog exception, SQLSTATE=QCB11 [Secondary server cannot maintain catalog sync.
-- (db_iqutility.cxx 4038)
...
Customer reported that this symptom has tooken place from time to time and wanted to know the root cause.
Read more...
Environment
SAP IQ 15.4
SAP IQ 16
Product
Keywords
"SQLSTATE:WW101", "sp_mpxprocesstlvlog exception", "cannot maintain catalog sync" , 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.