cancel
Showing results for 
Search instead for 
Did you mean: 

Which ports are needed for SAP HANA Studio <-> HANA DB communication?

Former Member
0 Kudos

I want to connect SAP HANA Studio to a HANA instance. The HANA instance number is 40.

The SAP note 1592925 states that the ports 5$$13/5$$14 and 3$$15 should be open to allow communication between the HANA Studio and the HANA database. I even see the instance in the HANA Studio, but I cannot administrate it and the HANA studio gives this general "I don't want you to know what the error actually is" message:

!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-16 14:01:40.627
!MESSAGE [HDB hostname 40 (SYSTEM)] Error on refreshing system
!SUBENTRY 1 com.sap.ndb.studio.navigator 4 0 2012-01-16 14:01:40.627
!MESSAGE SAPControl request failed
!STACK 0
com.sap.ndb.studio.sapcontrol.SAPControlException: SAPControl request failed
	at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:118)
	at com.sap.ndb.studio.sapcontrol.SAPControl.getInstanceProperties(SAPControl.java:439)
	at com.sap.ndb.studio.sapcontrol.SAPControl.collectProperties(SAPControl.java:466)
	at com.sap.ndb.studio.sapcontrol.SAPControl.open(SAPControl.java:297)
	at com.sap.ndb.studio.sapcontrol.SAPControlManager.getSAPControl(SAPControlManager.java:108)
	at com.sap.ndb.studio.sapcontrol.SAPControlManager.getSAPControl(SAPControlManager.java:81)
	at com.sap.ndb.studio.sapcontrol.SAPControlManager.needCredentials(SAPControlManager.java:57)
	at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.executeTrySAPControl(SAPSystemObjectUpdate.java:102)
	at com.sap.ndb.studio.navigator.operations.SAPSystemObjectUpdate.execute(SAPSystemObjectUpdate.java:63)
	at com.sap.ndb.studio.navigator.operations.UpdateSAPSystemOperation.execute(UpdateSAPSystemOperation.java:75)
	at com.sap.ndb.studio.datamodel.controler.DataModelOperation.execute(DataModelOperation.java:67)
	at com.sap.ndb.studio.datamodel.controler.DataModelOperationQueue$DataModelOperationThread.run(DataModelOperationQueue.java:99)
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
	at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.call(Unknown Source)
	at com.sap.ndb.studio.sapcontrol.operations.SAPControlOperation.execute(SAPControlOperation.java:94)
	... 11 more
Caused by: com.sun.xml.internal.messaging.saaj.SOAPExceptionImpl: Message send failed
	at com.sun.xml.internal.messaging.saaj.client.p2p.HttpSOAPConnection.post(Unknown Source)
	... 13 more
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.PlainSocketImpl.doConnect(Unknown Source)
	at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
	at java.net.PlainSocketImpl.connect(Unknown Source)
	at java.net.SocksSocketImpl.connect(Unknown Source)
	at java.net.Socket.connect(Unknown Source)
	at java.net.Socket.connect(Unknown Source)
	at sun.net.NetworkClient.doConnect(Unknown Source)
	at sun.net.www.http.HttpClient.openServer(Unknown Source)
	at sun.net.www.http.HttpClient.openServer(Unknown Source)
	at sun.net.www.http.HttpClient.<init>(Unknown Source)
	at sun.net.www.http.HttpClient.New(Unknown Source)
	at sun.net.www.http.HttpClient.New(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)
	... 14 more

Do I need to open any other ports to make HANA Studio work with HANA DB?

Regards,

Mark

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hi Mark,

The HANA Studio connects to HANA DB Instance with JDBC on port 3<Instance number>15.

For your HDB with Instance Number 40, the port would be 34015.

HANA Studio will automatically assign the JDBC port number when you assign the instance number when you add new system.

Looking at the error message that you posted:

!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-16 14:01:40.627

!MESSAGE [HDB hostname 40 (SYSTEM)] Error on refreshing system

It looks like the hostname entry was not entered correctly (you might have entered "hostname" value when adding the system in HANA Studio).

Here is an example of correct log entry on DCA database instance on hanasvr-01 server with Instance number 00:

!ENTRY com.sap.ndb.studio.navigator 4 1 2012-01-10 13:55:23.598

!MESSAGE [DCA hanasvr-01 00 (SYSTEM)]

You may want to delete and re-add your HDB instance in your HANA Studio.

Regards,

Ferry

Answers (4)

Answers (4)

Former Member
0 Kudos
Mofizur
Contributor
0 Kudos

Hi,

Single DB system: port 3xx15 connects to the master index server SQL port, where 'xx' is the instance number

Example how port coverage may appear in an MDC system:

Thanks,

Mofizur

0 Kudos

Hi guys,

take care when installing a multitenant database. You need the port 3<instancenummber>13 also.

Regards,

Robert

Former Member
0 Kudos

Hello,

please check if the SAPStartSrv can be reached with the browser.

http://<server>:5<instance number>13/?wsdl

If yes, please check the Studio preferences:

Window->Preferences->Network Connections

and change value: "Native" to "Direct".

Also see SAP note 1639568

Best Regards

Wolfgang

Former Member
0 Kudos

I have redirected the ports 54013 and 34015 via SSH from Linux to my PC. The redirection works fine.

The SAPStartSrv URL can be reached without problems:

http://localhost:54013/?wsdl

Connection preferences have been changed from "Native" to "Direct".

The hostname isn't an issue, I use localhost due to the port redirection.

The yellow status from SAP note 1639568 won't vanish, but since the SQL editor and administration do work (with the only exception of starting and stopping the HANA instance via Studio), this isn't a real problem. Maybe some time in the future the SAP note 1639568 will be amended what else should be done to fix that yellow status.

Thanks for your tips!

Former Member
0 Kudos

Hey Wolfgang Auer,

       My aws server had been working fine but suddenly the database connectivity was lost. The status on amazon server was green with 2/2 checks passed and the elastic ip was associated to it; but the studio was throwing an error "database connection not available". Wasn't sure what was wrong so tried your suggestion and the database connection is now available. Although it is up and running I am still unaware of what went wrong and how did changing the network connection make it work.