‘sapstartsrv’ service not started error after SAP HANA installation:
Check if the service is started on the server:
With netstat you know which port the process is using:
Try to telnet to the port (50213 in this case) from outside of server. If you are able to reach you will have to reach out to your Infrastructure team to get the port open on firewall.
Or if you you are on cloud, you need to add this to the inbound rule of your secuirty group.
I have come across situations where it was necessary to check the ports before even installing an application to see if firewall is open or if no other application is already using the port.
On Linux environments this can be done using command ln:
Use yum or zypper or apt-get to install the tool:
Now simulate your port and test:
On windows I did not find a ready-made way to do the same. So designed my own, with some help from internet.
No installation required and it is version independent. Just download and run it from below link:
Simulate Port on Windows
Unzip the file to your desktop.
Double click to execute the file:
If prompted allow firewall access.
And you are ready to test.
Once you are connected, you get a message in your simulator:
Note: After the test is done end the test process from your task manager. Otherwise the port will be kept occupied.
Sometimes you might find issues starting up your SAP services, with a error that the service is not able to bind to a particular port.
In the example below, I was not able to start the SMTP service from SMICM.
This mean, there could be another service that is already using this port.
Lets find out:
netstat -nepal | grep 25
Now we have the process ID. Lets see what is this process all about:
ps -ef | grep 6760
Postfix was using my service, which was not required.
Kill/Stop the service that is not required before starting your service again.
In my example:
# postfix stop
Make sure that you disable the unwanted service from starting up next time when you reboot the server using chkconfig:
# chkconfig postfix off
#HDB info showed that not all index servers are started.
Since this is multitenant database, looked in following directory for the error logs:
/usr/sap/<SYSTEM SID>/HDB<Instance Number>/<Host Name>/trace/DB_<TENANT SID>/.
For SAP HANA single database, trace files can be found at:
/usr/sap/<SYSTEM SID>/HDB<Instance Number>/<Host Name>/trace/
Found the issue, resolved and restarted to get all my index servers running again.
Telnet can be used to deploy a SCA file on to the JAVA stack. This is the most easiest and quickest way to deploy individual packages.
You can refer to SAP Note SAP Note 1715441 for detailed instructions.
Key points to remember:
- Telnet port to connect to is 5<Instance Number>08.
- Use command lsc to list the available server nodes.
- Use command jump <server node> to connect to a particular node.
- Server node will get restarted during the deployment and you will get disconnected from the telnet session.
- Use get_result to get the result of the deployment. You may receive error, command not found when you run the command. This may be because the node is still coming up. Give it some time until the node is available again.
1715441 – Deploy/Undeploy/Force Redeploy WAR/EAR/RAR/SDA/SCA files on SAP AS JAVA
2640229 – How to find dependencies of a deployed SDA/SCA on SAP AS Java