#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.
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.