3433497 - Error during execution of command identifier 'ACTIVATE' : com.sap.dbtech.rte.comm.CommunicationException: Released

Installation fails, and error from swpm/sapinst_dev.log:

ERROR      2024-02-15 21:28:05.103 (root/sapinst) (startInstallation) [CSiStepExecute.cpp:1104] id=controller.stepExecuted errno=FCO-00011 CSiStepExecute::execute()
The step sdb_instance_activate with step key |SAP_CONTENT_SERVER|ind|ind|ind|ind|0|0|SAP_CONTENT_SERVER_UNIX|ind|ind|ind|ind|auto.id:1|0|CS_DB_INSTALL|ind|ind|ind|ind|csDb|0|SdbPreInstanceDialogs|ind|ind|ind|ind|dbinstance|0|SdbInstanceDialogs|ind|ind|ind|ind|instance_dialogs|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|instance_create|0|sdb_instance_activate was executed with status ERROR (Last error reported by the step: Error during execution of command identifier 'ACTIVATE' : com.sap.dbtech.rte.comm.CommunicationException: Released).

SdbCmdOut.log->
Thu Feb 15 21:28:03 NZDT 2024 | class com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession | Run command: db_activate *,*
Thu Feb 15 21:28:04 NZDT 2024 | class com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession | Close dbmcli Session.
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.utils.DbCommand | com.sap.dbtech.rte.comm.CommunicationException: Released
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession.executeCommands(DbmJdbcSession.java:401)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession.executeCommands(DbmJdbcSession.java:324)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.connection.session.DbmJdbcSession.executeWithDbm(DbmJdbcSession.java:283)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.DbCommand.executeJdbcDbm(DbCommand.java:784)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.DbCommand.runDbActivate(DbCommand.java:617)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.cmd.ident.classes.ACTIVATE.run(ACTIVATE.java:23)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.sllib.utils.DbCommand.runCommand(DbCommand.java:3473)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.core.main.cmd.SdbCmdMain.<init>(SdbCmdMain.java:67)
Thu Feb 15 21:28:05 NZDT 2024 | class com.sap.sdb.sllib.api.exceptions.DatabaseCommandException | com.sap.sdb.core.main.cmd.SdbCmdMain.main(SdbCmdMain.java:212)

But there is no detailed error error from dbm.prt, KnlMsg or KnlMsgArchive.

Solaris SPARC

ACTIVATE, com.sap.dbtech.rte.comm.CommunicationException, SPARC, sdb_instance_activate  , KBA , BC-DB-SDB , MaxDB , BC-DB-SDB-INS , Installation with MaxDB , Problem