Dear Team,
We have installed one SAP HA system using Windows 2012 R2 + SQL 2012AlwaysOn + ECC 6.0 SR3. Now we are facing a problem with databaseconnectivity The problem is once primary database node goes down theavailability group (AG01) moves on to the secondary database node andmysap application does not gets connected to the secondary database.
Basically we have tested 4 scenarios in our HA SAP landscape but twoscenarios has been successfully tested and two scenarios failed. Wehaveexplained these scenarios in below.
1. Once database group (AG01) is on cluster node 1 and SAP Applicationgroup (SAP ECP) is on cluster node 2, this case is successful and SAPApplication has been connected and working fine.
2. But the database group (AG01) is on cluster node 1 and SAPApplicationgroup (SAP ECP) is on cluster node 1, this also successful and SAPApplication started and connected properly.
3. Once the database group (AG01) is on cluster node 2 and SAPApplicationgroup (SAP ECP) is on cluster node 1, In this case SAP Application havebeen failed and not connected database system.
4. And the same case also here, the database group (AG01) is on clusternode 2 and SAP Application group (SAP ECP) is on cluster node 2, TheSAPApplication have been failed and not connected database system.
But as per SAP Note 1772688 andhttp://blogs.msdn.com/b/saponsqlserver/archive/2012/03/29/sql-server- 2012-alwayson-part-6-buildingan-alwayson-availability-group.aspxsuggest,we have changed the SAP profile and enter the SQL always onhigh availability group listener name to SAP application side and SAPalso started and working fine with group listener name.
For your reference we have attached the trans.logs and SQL error logs screen below . Please find the attached logs and suggestASAP.
If any query, please call me in this no: 9899591315
Best Regards.
Saumya Mohanty