Symptom
A tenant database (HDB in this example) doesn't start up automatically after trying to start it manually while the system shutdown was in progress.
The following log entries are captured in the nameserver traces:
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.170988 i TraceContext TraceContext.cpp(01367) : UserName=SYSTEM, ApplicationUserName=APP_USERNAME, ApplicationName=HDBStudio, ApplicationSource=csns.sql.editor.SQLExecuteFormEditor$4$1.run(SQLExecuteFormEditor.java:938);, StatementHash=4525c4ec9560a64c197a94cec3c4486c, StatementExecutionID=281479271681170
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.170988 e NameServer MDCRequestHandler.cpp(01002) : start databaseServer for database=3 on : hana05:30043 failed (idxFailed=4, idxWaiting=3)
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.180709 i MultiDB MDCRequestHandler.cpp(01554) : Stop database HDB(3) : BY FAILED DATABASE START
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.182538 i MultiDB MDCRequestHandler.cpp(01554) : Stop database HDB(3) : BY FAILED DATABASE START
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.182839 e NameServer MDCRequestHandler.cpp(01204) : stopDatabase 3 is not in active state:stopping
[47603]\{100282\}[14/-1] 2023-09-27 15:00:22.236440 i TraceContext TraceContext.cpp(01367) : UserName=SYSTEM, ApplicationUserName=APP_USERNAME, ApplicationName=HDBStudio, ApplicationSource=csns.sql.editor.SQLExecuteFormEditor$4$1.run(SQLExecuteFormEditor.java:938);, StatementHash=4525c4ec9560a64c197a94cec3c4486c, StatementExecutionID=281479271681170
[47603]\{100282\}[14/-1] 2023-09-27 15:00:22.236440 i DaemonClient Client.cpp(00090) : Sending signal 10
[47603]\{100282\}[14/-1] 2023-09-27 15:00:22.236536 i DaemonClient Client.cpp(00078) : Sending signal 10 to 47513
[47603]\{100282\}[14/-1] 2023-09-27 15:00:22.236560 i DaemonClient Client.cpp(00080) : Sent signal 10 to 47513 rc 0
[47603]\{100282\}[14/-1] 2023-09-27 15:00:22.236563 i DaemonClient Client.cpp(00155) : Send signal 10
[47700]\{100282\}[14/-1] 2023-09-27 15:00:22.280196 e tns_ddl TNSClient.cpp(00951) : start database '3' failed:Database could not be started; start databaseServer for database=3 on : hana05:30043 failed(5709)
The following entries are logged in the daemon traces:
[47513]{-1}[-1/-1] 2023-09-27 15:00:22.236715 i Daemon SignalsUNIX.cpp(00601) : signo 10=SIGUSR1 from user. errno 0 code 0. Requested 'RECONFIGURE'. Sender pid 47538, real user 'hdbadm'=1000, executable 'hdbnameserver'
[47513]{-1}[-1/-1] 2023-09-27 15:00:22.236819 e Daemon DaemonHandle.cpp(00134) : Daemon is shutting down. Reconfigure call ignored
The active status of the tenant is displayed as "STOPPED BY FAILED DATABASE START":
hdbsql -j -U SYSTEMDB "select * from m_databases where database_name='HDB';"
DATABASE_NAME ,DESCRIPTION ,ACTIVE_STATUS ,ACTIVE_STATUS_DETAILS ,OS_USER ,OS_GROUP ,RESTART_MODE ,FALLBACK_SNAPSHOT_CREATE_TIME
"HDB" ,"HDB-00" ,"NO" ,"STOPPED BY FAILED DATABASE START" ,"" ,"" ,"DEFAULT" ,?
Read more...
Environment
SAP HANA, platform edition 2.0
Product
SAP HANA, platform edition all versions
Keywords
Tenant DB, start, STOPPED BY FAILED DATABASE START , KBA , HAN-DB , SAP HANA Database , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.