on 05-19-2011 4:34 AM
Hi SDN Gurus,
I'm tuning our system to handle heavy loads. But encounter issues during our tuning.
our setup:
2 Apps instance in Win2008 R3(3 of such servers) to DB instance in Unix AIX.
Initial setup was fine and we have no problem setting the WP of each instance(around 40 WP for each instance). but when we try to increase the WP to 50 we encounter some issues.
After we started the SAP instance, Some of our WPs starts to fail and stop running. The logs have the following error message:
[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xx.xx.xx.xx<our db server>". Communication function detecting the error: "send". Protocol specific error code(s): "10054", "*", "0". SQLSTATE=08001
R3Trans -d show similar errors. If we turn off one of the instance the error will disappear.
Our user base is very large and SAP have confirmed that our server resources/hardware are able to handle the user load. So memory/CPU wise is not the issue. We need 50 WP to handle high loads. Our network is simple setup with no FW so don't think there's any issue (works with 40 WP anyway)
The funny thing if we turn on the Unix apps instances, only the Windows apps WP will fail while the Unixs WPs remains running so we suspect the bottleneck may not be in the DB server.
Is there a certain limit to the number of DBconnections or sockets connections for Windows? Or is there any limits to connect to windows from Unix AIX?
Any advise or hints will be greatly appreciated! Thank you!
Regards,
Jansen
Edited by: Jansen Low on May 19, 2011 5:35 AM
Hi,
Please check following link from ibm site.
https://www-304.ibm.com/support/docview.wss?uid=swg21164785
-Sanjay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
Resolved.
- After more troubleshooting, concluded that even the AIX Apps server also encounter the same issue. So not just a Windows issue
- After checking the settings, SAP, CLI and DB are Ok. Suspect AIX OS is the culprit
- Discovered a AIX OS level-firewall setting is enabled by default in the DB server. disabled it
- The error disappear.
Thanks all for attention.
Edited by: Jansen Low on May 30, 2011 8:56 AM
Edited by: Jansen Low on May 30, 2011 8:56 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.