3006644 - SAP DBTech JDBC: [2]: general error: another tenant create/delete is already active;startDatabase 3 is not in stopped state: stopping

• Attempts to start a HANA tenant DB fail with the error "Could not execute 'ALTER SYSTEM START DATABASE 'SID' in 202 ms 690 µs .SAP DBTech JDBC: [2]: general error: another tenant create/delete is already active;startDatabase 3 is not in stopped state: stopping"

• One or more of the following symptoms are observed in the HANA service traces :

• hdbsql SYSTEMDB=> SELECT * FROM M_DATABASES

DATABASE_NAME,DESCRIPTION,ACTIVE_STATUS,ACTIVE_STATUS_DETAILS,OS_USER,OS_GROUP
"SYSTEMDB","SystemDB-SID-00","YES","","",""
"SID","","STOPPING","","",""

• Daemon trace

i Daemon           SignalsUNIX.cpp(00699) : signo 10 SIGUSR1 from user errno 0 code 0
sender pid 6241 real user id 788 executable '/sapmnt/SID/exe/linuxx86_64/HDB_1.00.122.28.1571903286_6099911/hdbnameserver'
i Daemon           TrexDaemon.cpp(04205) : reconfiguring all services
i Daemon           Daemon.cpp(00779) : comment file contains: reconfig triggered by daemonStopDatabase
 

• The <service>_<hostname>.<port_number>.000.trc trace files for HANA services with persistence contain entries indicating exhausted log volume capacity and/or the databse reaches it's configured maximum threshold for the "logshipping_max_retention_size" on primary site

w Logger           LogSegment.cpp(02247) : Log full - maximum number of log segments in log partition /hdb/SID/log/mnt00001/hdb00002/ reached, awaiting log backup and/or savepoint. Alternatively, you can manually increase the maximum number of log segments currently set to 10240.
i EventHandler     EventManagerImpl.cpp(00880) : AutoEventHandlerCallback::initial(period= 60)
i EventHandler     EventManagerImpl.cpp(00562) : reportEvent: LogFullEvent[volumeid=2,eventid=1,part=/hdb/SID/log/mnt00001/hdb00002/]
 
e NameServer TREXNameServer.cpp(11263) : startDatabase 3 is not in stopped state:stopping
e tns_ddl TNSClient.cpp(01040) : start database '3' failed.
i Logger LogSegment.cpp(03691) : Try to free RETAINED_FREE segment as logshipping_max_retention_size reached
i Logger LogSegment.cpp(01104) : Free segment kept for replication,
 
i Logger LoggerImpl.cpp(01062) : Starting logger with 8 log buffers per partition, 1024KB each, segment size 8MB, log mode normal, currentWritePos=0x4ff38c0
w Logger LogSegment.cpp(02249) : Log full in log partition /hdb/SID/log/mnt00001/hdb00003.00003/, awaiting log backup and/or savepoint
i EventHandler EventManagerImpl.cpp(00880) : AutoEventHandlerCallback::initial(period= 60)
i EventHandler EventManagerImpl.cpp(00562) : reportEvent: LogFullEvent[volumeid=3,eventid=1,part=/hdb/SID/log/mnt00001/hdb00003.00003/]
i Logger LogSegment.cpp(02276) : Could not immediately reserve a new log segment in LogPartition[/hdb/SID/log/mnt00001/hdb00003.00003/:0], waiting for a log segment to become available
 
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental. 

• SAP HANA PLATFORM EDITION 1.0
• SAP HANA PLATFORM EDITION 2.0 

log volume full, disk full, tenant startup, , KBA , HAN-DB , SAP HANA Database , HAN-DB-MON , SAP HANA Monitoring , Problem