cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Data Hub 2.4 - Connection to Vora via SDA - How to get right Port?

0 Kudos

Dear Community,

we are already running Data Hub 2.4 successfully on AWS. Currently we are struggling with SDA connection from HANA to Vora. We also know the Node where the tx.coordinator is running.

But we stil get the following error:

SAP DBTech JDBC: [403]: internal error: Cannot get remote source objects: [SAP AG][LIBODBCHDB SO][HDBODBC] Communication link failure;-10709 Connection failed (RTE:[89008] Socket closed by peer

Where do i find the right Node and Port for Vora?

Thanks and regards,

Tobias

Accepted Solutions (1)

Accepted Solutions (1)

pascaldp
Explorer

Did you expose the tx-coordinator outside the kubernetes cluser? See this link.

Answers (7)

Answers (7)

pascaldp
Explorer
0 Kudos

Did you put default between quotes?

0 Kudos

Connection works without \ - thanks for the hint.

But we are using Vora Avro Ingestor and there all of our tables are written to schema default\admin because connection was created with user admin.

I tried option databaseSchema, but then we get an error message like this:

Any suggestions here?

pascaldp
Explorer
0 Kudos

If you create tables directly under the default schema, you should be able to see the table. I have the same issue with tables created in the user schema.

create table "default".test (col1 int, col2 int) TYPE STREAMING;
schneidertho
Advisor
Advisor
0 Kudos

Can you try a schema without \ and see if this works.

And if that does not help, paste a screenshot of the remote source.

Cheers, Thorsten

0 Kudos

Connection works now - there was an issue regarding connection from our local datacenter to AWS VPC.

Now we get another error:

Any suggestions? Seems to be an authorization error ...

Thanks for your help!

former_member307841
Discoverer
0 Kudos

How you solved the issue? I got the same failure if I tried to create a remote source for vora.

Even though the tx-coordinator-lb is accessible over a public IP and the port 30115.

pascaldp
Explorer
0 Kudos

Via the load balancer you should be able to use the hanawire port, being the third port mentioned in the "LoadBalancer" line. It should be something like 3xx15 (xx = hanawire instance that is defaulted to 01).

Be sure to check also this note:

https://launchpad.support.sap.com/#/notes/2711582

0 Kudos

Yes, we exposed it already.

I am getting the following entry when i run command kubectl -n $NAMESPACE get services:

Am I right here?

Which IP/Port do i have to use in my Remote Source and firewall configuration?

Thanks!