Symptom
- You are following the manual way to remove HADR Manually Removing HADR Replication
- On step1 while dropping the HADR related objects, they could fail due to table currently in use:
drop table hadrGetTicketHistory
go
Msg 3702, Level 16, State 1:
Server 'SID', Line 1:
Cannot drop or replace the table 'hadrGetTicketHistory' because it is currently in use.
Read more...
Environment
SAP Adaptive Server Enterprise (ASE) 16.0 with High Availability Disaster Recovery (HADR)
Product
SAP Replication Server 16.0
Keywords
sap_teardown, tear down, removehadr, hadrGetTicketHistory, hadrGetLog, hadrStatusResource , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , 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.