SAP Knowledge Base Article - Preview

2627946 - Streaming Service not getting started - SAP HANA Streaming

Symptom

  • The Streaming server was installed successfully as a dedicated host installation.
  • After shutting the HANA database down to do maintenance, restart of streaming server fails and the Streaming server trace file reports volumeID errors:

Apr 04 2018 12:00:17.744 INFO - SAP HANA smart data streaming Cluster Node 1.00.122.06/20170109.1/SP12 Rev122 PL06/linux/x86_64/64-bit/OPT/Mon Jan 9 13:30:07 PST 2017
Apr 04 2018 12:00:20.184 ERROR - CODE_700304 | Testing JDBC connection failed with following error: SAP DBTech JDBC: Cannot connect to jdbc:sap://64.101.0.151:30815 [Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.].
Apr 04 2018 12:00:25.184 INFO - CODE_700303 | Retesting JDBC connection
Apr 04 2018 12:00:25.186 ERROR - CODE_700304 | Testing JDBC connection failed with following error: SAP DBTech JDBC: Cannot connect to jdbc:sap://64.101.0.151:30815 [Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.].
Apr 04 2018 12:00:30.186 INFO - CODE_700303 | Retesting JDBC connection
Apr 04 2018 12:00:30.187 ERROR - CODE_700304 | Testing JDBC connection failed with following error: SAP DBTech JDBC: Cannot connect to jdbc:sap://64.101.0.151:30815 [Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.].
Apr 04 2018 12:00:35.187 INFO - CODE_700303 | Retesting JDBC connection
Apr 04 2018 12:00:35.189 ERROR - CODE_700304 | Testing JDBC connection failed with following error: SAP DBTech JDBC: Cannot connect to jdbc:sap://64.101.0.151:30815 [Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.].
Apr 04 2018 12:00:40.189 INFO - CODE_700303 | Retesting JDBC connection
Apr 04 2018 12:00:40.269 INFO - CODE_700308 | Testing JDBC connection successful
Apr 04 2018 12:00:42.952 FATAL - CODE_700418 | Could not load config from database
com.sybase.esp.cluster.config.ConfigException: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to VolumeID=14 [Cannot connect to host 64.101.0.152:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.152 (hana-np-20.mycompany.com))], -813.].
at com.sybase.esp.cluster.impl.ConfigDatabaseAccessor.load(ConfigDatabaseAccessor.java:907)
...
Caused by: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Cannot connect to VolumeID=14 [Cannot connect to host 64.101.0.152:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.152 (hana-np-20.mycompany.com))], -813.].
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:240)
...
... 5 more
Apr 04 2018 12:00:42.956 FATAL - CODE_700412 | Factory of new node failed

  • During the time of installing hana-np-18 as streaming node host, the streaming host was added into HANA configuration (hana-np-19 and hana-np-20) and the streaming server was added to a tenant. During the time of installation master index server and master name server are on the same node (hana-np-20). Now after restart master index server is on hana-np-19 and master name server is on hana-np-20. The streaming server trace file reports errors: 

Apr 04 2018 14:34:06.831 INFO - SAP HANA smart data streaming Cluster Node 1.00.122.06/20170109.1/SP12 Rev122 PL06/linux/x86_64/64-bit/OPT/Mon Jan 9 13:30:07 PST 2017
Apr 04 2018 14:34:09.334 ERROR - CODE_700305 | Testing JDBC connection failed with following error: SAP DBTech JDBC: Cannot connect to jdbc:sap://64.101.0.151:30815;64.101.0.152:30815 [None of the hosts could be reached: [Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.; host = 64.101.0.152:30815 error = Cannot connect to host 64.101.0.152:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.152 (hana-np-20.mycompany.com))], -813.]].
Apr 04 2018 14:34:09.336 FATAL - CODE_700418 | Could not load config from database
com.sybase.esp.cluster.config.ConfigException: com.sybase.esp.cluster.impl.DatabaseException: com.sybase.esp.cluster.config.ConfigException: com.sybase.esp.cluster.impl.DatabaseException: Could not create database connection
at com.sybase.esp.cluster.impl.ConfigDatabaseManager.load(ConfigDatabaseManager.java:100)
...
Caused by: com.sap.db.rte.comm.RTEException: Cannot connect to host 64.101.0.151:30815 [Connection refused (port 30815 to address ::ffff:64.101.0.151 (hana-np-19.mycompany.com))], -813.
at com.sap.db.rte.comm.SocketComm.openSocket(SocketComm.java:128)
...
Apr 04 2018 14:34:09.341 FATAL - CODE_700412 | Factory of new node failed


Read more...

Environment

  • SAP HANA Smart Data Streaming 1.0 SP12 (all revisions)
  • SAP HANA Streaming Analytics 2.0

Product

SAP HANA 1.0 smart data streaming ; SAP HANA 1.0, platform edition ; SAP HANA streaming analytics 2.0

Keywords

stream, processing, processor, sds, indexserver, nameserver , KBA , HAN-SDS , SAP HANA Smart Data Streaming , 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.