SAP HANA Cockpit is a Web-Based tool for administration, monitoring and maintenance of SAP HANA systems.
Below we discuss installation steps and some key points with respect to cockpit:
- Download the required SAP file from SAP Market Place.
- Extract the SAR file and trigger installation using hdblcm.
Note that installer installs a HANA instance (Express edition) of its own.
More details here
- Verify the details, enter the password and continue. Like any HANA installation user SYSTEM is created on the DB which will be used to login to Cockpit also.
Along with SYSTEM, the other key user created is COCKPIT_ADMIN.
Note that 51021 and 51023 are the default ports for Cockpit and Cockpit manager respectively.
- First it is required to login to Cockpit manager to assign yourself required roles using user COCKPIT_ADMIN.
- Now you are ready to login to the HANA Cockpit.
- If you want to add additional users or resources (HANA systems) to cockpit, you can do so via SAP HANA Cockpit manager.
Important SAP Notes:
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.
When you change the password of connecting user of SAP HANA database, same should be updated in the key file of the HDBUSERSTORE on the Application Server.
You should be logged in with <SIDADM> for this procedure. Take care of this specially if you application server and database are running on same server.
#> hdbuserstore SET DEFAULT <hostname>:3<instance Number>15 <user> <password>
Note: User option -i along with the command if you want to enter the options (mainly password) interactively.
hdbuserstore SET DEFAULT hanahost:30015 SYSTEM Hana@123
Once updated check the list using the below command.
#> hdbuserstore list
DATA FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.DAT
KEY FILE : /home/appadm/.hdb/hanahost/SSFS_HDB.KEY
ENV : HANAHOST:30015
You can now check the connectivity with the DATABASE using R3trans -d.
If R3trans -d reports error, check the connectivity with hdbsql using the key created above.
#> hdbsql -U <KEY> #Key is “DEFAULT” in our example.
This should connect to the database without any issues.
You might receive error sql code rcSQL = -10709 in case of connectivity issues. Please check the host name and port again in case of issues.
In case of any issues/questions please leave a comment below. Happy learning.