Symptom
SAP system cannot connect to SQL Server after Alwayson or mirroring fails over to the secondary replication.
The error on ABAP developer trace is such as below:
Invalid object name 'DBPROPERTIES'.
Connection 0 opened (DBSL handle 0)
Invalid object name 'SVERS'.
ERROR: -1 in function StartSelect (execute) [line 13394]
Statement(s) could not be prepared.
LOG BZA=> table SVERS does not exist on database
LOG R19=> ThInit, db_connect
ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1)
The error on JAVA stack could look like the followings:
Exception of type com.microsoft.sqlserver.jdbc.SQLServerException caught:
Cannot open user default database. Login failed.
Read more...
Environment
SAP application server based on SQL Server Alwayson functionality or SQL Server Database Mirroring.
Keywords
High Availability, Disaster Recovery, secondary, node, fail over, clustering, Return Code 004096, DB-Connect Failed, , 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.