‘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.
As continution to the previous blog Prepare SAP HANA for SSL, I am writing this blog to use SSL with SAP HANA Studio.
Even if do not want to use SSL with studio, this procedure can be used at leset to test SSL that has been configured on the SAP HANA server.
keytool -genkey -alias mykeystore -keyalg RSA -keystore .keystore -keysize 2048 -dName “CN=Firstname Lastname, OU=HANA, O=SAP, C=DE”
You are now ready to connect to SAP HANA server via HANA studio using SSL.
Test:
I am attaching additinal steps/screenshots from the errors so that it will be easy for others to troubleshoot similar issues:
Once added you will see a small lock on the system indicating that the connection is going via SSL.
Troubleshooting:
Errors can be check with log from studio as below:
You can open each error to get more details.
The COMMONCRYPTOLIB and OPENSSL (If you are using self signed certificate) are required on the HANA server. This is normally already installed along with your HANA installation.
CommonCryptoLib (libsapcrypto.so) is installed by default as part of SAP HANA server installation at $DIR_EXECUTABLE.
Check OPENSSL.
Certificates stored in the file system are contained in database-specific personal security environments or PSEs (default $SECUDIR/sapsrv.pse).
Navigate to $SECUDIR
This ensures all the prerequisites are met and all environment variables are properly set.
Important Note:
This creates two files:
Here you can use the pass phrase that you want.
With this step you have the certificate ready that can be used on Client machines.
Note that the pse file has a new timestamp with certificate added.
Import SAP Notes:
Note: These series of blogs related to error is only to give an idea about troubleshooting aspects of SAP HANA and not a definitive guide for error resolution.
When starting HANA database, I ran into below error:
I ran into this error right after I tried to configure SSL on the HANA machine.
Checked the log nameserverxx.trc under /usr/sap/<SID>/<SID<<InstanceNO>/<HOST./trace/ and found below error:
Clear that the issue is caused by wrong SSL settings.
Realized that one of the parameter settings for SSL has been missed (SAP Note 2561693).
Set the value of ssl to off in global.ini file and restated the HANA database to fix the issue.
SAP Note:
With so many memory areas of SAP HANA, What should I really Monitor with respect to Memory usage of HANA database?
Below picture is key in understanding the memory allocation sequence.
You can control the behaviour of total memory allocated to SAP HANA database by using allocation limit parameter (global.ini -> memorymanager -> global_allocation_limit)
Unless you have additional software running on the HANA server or the HANA licensed memory is less than you physical memory, global_allocation_limit need not be set.
Default value is 0 and most of the times this is not set assuming that the server will be only used by HANA database. This means HANA DB can use the complete memory of the server.
Memory allocation in HANA Database implements a pool concept. That is, memory is pre-allocated (reserved) from the operating system for performance reasons. By default, the HANA database will allocate up to approximately 90% of the available physical memory.
This will be used for queries that will need additional space at once. This will be RESERVED and not released back to Operating System.
Hence the reserved memory does not indicate any memory issues with the database.
Key figure to be monitored is the active memory usage of the HANA database:
Same has been clarified in below SAP Note:
You can monitor the current usage of memory by each tenant by using below query:
SELECT * FROM “SYS_DATABASES”.”M_SERVICE_MEMORY”
Total memory usage of the whole database can also be monitored with HANA_MEMORY_OVRVIEW (SAP Note 1969700 ).
You can also monitor the history of total memory usage using _SYS_STATISTICS, like example below:
To check if the SAP HANA Memory parameters are set optimally, you can use HANA_Configuration_Parameters_1.00.70+ (SAP Note 1969700).
Important SAP Notes:
There are scenarios where you do not connect to SAP HANA database instance directly via Host IP address or Physical hostname but via a Virtual IP or NAT address.
The main connection between NAT and the IP is established via DNS or a local entry in local host file.
But internally SAP HANA tries to make a connection to the Tenant DB using physical IP by default. Same has been depicted below with an example of SAP HANA Studio.
If you check the properties of a tenant database from studio you will see the following:
Even though you connect to DB using NAT IP (10.253.80.9) it is internally redirected to original IP (10.249.28.20) to make additional connections.
In this case when you try to make connection to a tenant database via webdispatcher or sql clients you will not be able to communicate to tenant DB.
You can also verify the same by querying M_HOST_INFORMATION.
This behaviour is controlled by parameter “public_hostname_resolution” under global.ini.
To change the behaviour you will have to change the parameter to “no” so that system is not forced anymore to use IP address of the Network interface. Instead you can map the hostname to required IP address as required.
Note: This change does not required a DB restart.
Now you can map the hostname with required IP address on client machine to connect to the database:
Changes can be observed again with studio again.
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:
Important SAP Notes:
#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.
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.
Example:
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
KEY DEFAULT
ENV : HANAHOST:30015
USER: SYSTEM
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.
Important Notes:
sapbasispro 