Symptom
- Execution of the command "drop connection" to standby database fails with Error 60036:
drop connection to STANDBY_ASE.DB_NAME
go
Msg 60036, Level 12, State 0:
Server 'REP_SERVER_NAME':
Failed to acquire lock on sync element 'UNKNOWN'. Info 21.
- Same problem can also happen when trying to purge the queue manually with command "sysadmin sqm_purge_queue".
- This usually happens when there is large stable device(s), and it contains much data.
- The following stacktrace is also printed in the errorlog:
The DSI thread for database 'ACTIVE_ASE.DB_NAME' is shutdown.
(44): CatchUpQ is dropped right away
The DSI thread for database 'STANDBY_ASE.DB_NAME' is shutdown.
(44): CatchUpQ is dropped right away
DIST for 'STANDBY_ASE.DB_NAME' is waiting for SQM(s) to flush to outbound queue(s).
SQM stopping: 106:0 LDS_DB_NAME.LDB_DB_NAME
SQM stopping: 106:1 LDS_DB_NAME.LDB_DB_NAME
Purging Queue 106:1
Thread USER(sa) infected with signal 11.
../..
Dumping memory trace.
***************STACK TRACE***************
*****thread USER(sa)*******
.exc__appDumpStack ()
.exc_terminate_my_thread ()
.exc_terminate_thread ()
.bsd_catch_signal ()
.aix_get_lock ()
._sync_lockheld ()
._sqm_check_warnings ()
.sqm_delete_queue_segments ()
.sqm_purge_queue ()
._ddl_drop_db ()
._ddl_db ()
.ddl_exec_cmd ()
.ddl_exec_cmd_wrapper ()
._ex_process_cmds ()
._ex_process_lang ()
.ex_lang_handler ()
.srv__exechandler ()
.srv__runclient ()
.srv__connhandle ()
.srv__start_function ()
*****End of stack trace.****
Read more...
Environment
SAP Replication Server (SRS) 16.0
Product
Keywords
RepServer, 60031, CR#823950, 823950, CR823950 , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed
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.
SAP Knowledge Base Article - Preview