/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
Alwayson is configured by following SAP note 1772688.
When performing SQL server failover from primary replica (node 1) to secondary replica (node 2) , SAP systems fails to start with the following errors in work process trace:
There is already an object named 'sap_set_spid_container' in the database.
Invalid object name 'SVERS'.
Statement(s) could not be prepared.
table SVERS does not exist on database
ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1
After run the "Configure additional Always On Node" on SWPM, the node 2 can connect to SQL Server. However, node 1 becomes unable to connect to SQL Server after failover.
Read more...
Environment
SAP NetWeaver Application Server system based on Microsoft SQL Server 2012 or higher
Product
Keywords
SVERS, sap_set_spid_container,alwayson , KBA , BC-DB-MSS , SQL Server in SAP NetWeaver Products , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)