Months ago I worked with some SAP customers where they had some problems to startup their SAP Netweaver system after implementing AlwaysOn feature on SQL Server.
Basically the problem was strdbs.cmd script in yellow status and never starting the disp+work. This also affects the strdbsj2ee.cmd script during the startup of a JAVA stack.
After some troubleshooting it was discovered that the problem was related with the environment variable MSSQL_SERVER values. It contained the AlwaysOn Availability Group Listener and the parameter MultiSubnetFailover, like “MyAAGListener;MultiSubnetFailover=YES”. Later it was discovered that the same would happen to customers that use DBM with FailoverPartner, because like AlwaysOn, you need to add connection sgring options to MSSQL_SERVER (and to the default profile also).
More recently, SQL Server named instances or default instances running on non-default port and AlwaysOn Availability Group Listener running on TCP/IP port other than 1433 (default). This happens because you need to add the TCP/IP port number after the Database Server hostname/Instance or AlwaysOn Availability Group Listener. Here are some examples:
MSSQL_SERVER = SAPDBSRV,12205
MSSQL_SERVER = SAPDBSRV\ERP,12205
MSSQL_SERVER = SAPDB-ERP-LIST,1205
The more recent versions of strdbs.cmd and strdbsj2ee.cmd introduced a new code that in the above scenarios causes strdbs.cmd/strdbsj2ee.cmd to hang in yellow state during the startup of SAP NetWeaver ABAP/JAVA systems.
The SAP Knowledge Base Article 2137130 – SAP startup hangs with SQL Server address the above scenarios and provide the solution and possible workaround for them.
In order to view the contents of the SAP Notes and KBAs, you will need to be logged into Service Marketplace.
I hope you enjoy this blog and any comments or suggestions are welcome.