SAP Knowledge Base Article - Preview

2448795 - tp call error happens when alwayson availability group fails over.

Symptom

The following error happens when importing a transport request into a system which is based on a SQL Server database in an alwayson availability group.

ERROR: Connect to <SID> failed (The target database, '<SID>', is participating in an availability currently not accessible for queries. Either data movement is suspended or the availability replica is not eaccess. To allow read-only access to this and other databases in the availability group, enable read access secondary availability replicas in the group.  For more information, see the ALTER AVAILABILITY GROUP statem Books Online.)

 

In ERRORLOG of this target database, the following error appears:

Error: 976<c/> Severity: 14<c/> State: 1.
The target database '<SID>'is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group enable read access to one or more secondary availability replicas in the group.  For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.


Read more...

Environment

SAP appilcation servers based on SAP Netweaver 7.0 or higher.

SQL Server 2012 or higher.

Product

SAP ERP Central Component 6.0

Keywords

tp call , KBA , sum , swpm , sapinst , 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.