Upload
sameers91s6070
View
225
Download
0
Embed Size (px)
Citation preview
7/25/2019 Connect Data Services 4 to HANA on AWS _ SCN
http://slidepdf.com/reader/full/connect-data-services-4-to-hana-on-aws-scn 1/3
16/12/2015 Connect Data Services 4 to HANA on AWS | SCN
https://scn.sap.com/thread/3188866
Getting Started Newsletters Store
Products Services & Support About SCN Downloads
Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join UsHi, Guest Search the Community
Activity Communications Actions
Browse
0 Tweet
5 Replies Latest reply: 17-Aug-2015 11:22 by Satheesh Kumar Manasani
Share 0Like
Connect Data Services 4 to HANA on AWS
This question has been Answered.
Hi everyone,
I'm facing a new issue : i'm trying to import my own data to the HANA on AWS : so i've installed data
services, patched to SP2 patch 4, and now trying to add HANA as a datastore in Data services.Unfortunatly i can't manage to give the right settings : i'm facing an error : ODBC-Error
My procedure : New Datastore => Database type : HANA => ODBC Administration => So here i'm
guessing i should add user or system data source , either way, the next steps are the same => Add =>
Select HDBODBC driver => then i'm asked about informations but i can't get it right :
Data Source Name : HDB ? imdbhdb ? some Amazon information ( AMI-id ? SAP HANA Developer
Edition ? instance name ?) ? some setting to do in Hana studio ?
Description : no problem
Server:Port : Should i enter the elasticip:30x15 ? ec2-2x-xx-xxx-xxx.compute-x.amazonaws.com ?
enter the private ip ?
Then i'm prompted for a username // password : which should i use : hdbadm ? root ? SYSTEM ?
( with the unselected option for ssh )
The error message is the following :
SAP HDB ODBC Connect ODBC-Error
SQLSTATE : 08S01
NATIVE ERROR : -10709
MESSAGE TEXT : [SAP AG][LIBODBCHDB DDL][HDB]
Communication link failure;-10709 Connection failed (RTE:[89006]
System call 'connect' failed, rc=10060 : a connection attempt
If you managed to connect dataservices on HANA AWS please tell me !
Thanks a lot if you can help !
Guillaume Blanchard 08-Jun-2012 00:15
Correct Answer
by Guillaume Blanchard on Jun 8, 2012 12:03 PM
HiI finally managed to connect my hana database to do so here is what i've done :
For the data source name i used the instance id available in amazon aws management console (
instance => instance name ).
I've entered a description
Then for server & port : the elastic ip : 3[instancenumber]15 so it's something like
2x.xx.xxx.xxx:30x15
Finally for user & password i used SYSTEM//password ( the default one is "manager" )
It worked perfectly, hope it will be usefull for others
Thanks
7/25/2019 Connect Data Services 4 to HANA on AWS _ SCN
http://slidepdf.com/reader/full/connect-data-services-4-to-hana-on-aws-scn 2/3
16/12/2015 Connect Data Services 4 to HANA on AWS | SCN
https://scn.sap.com/thread/3188866
4679 Views
Average User Rating
(0 ratings)
Re: Connect Data Services 4 to HANA on AWS
When using the ec2-2x-xx-xxx-xxx.compute-x.amazonaws.com with username SYSTEM and HDB
data source the error is diferrent :
SAP HDB ODBC Connect
ODBC-Error
SQLSTATE : 08S01
NATIVE ERROR : -10709
MESSAGE TEXT : [SAP AG][LIBODBCHDB DDL][HDB]
Communication link failure;-10709 Connection failed (no reachable host left )
Like (0)
Guillaume Blanchard 08-Jun-2012 00:48 (in response to Guillaume Blanchard)
Re: Connect Data Services 4 to HANA on AWS
Hi,
I was able to successfully load data to AWS HANA from Data Services 4.0 SP2 hosted on my
server.
When creating ODBC Data Source I used <HANA AWS Elastic IP>:30015 in Server:Port ODBC
field.
Make sure that you associated <Elastic IP> provided in the AWS HANA image with your running
HANA instance.
I guess ec2-2x-xx-xxx-xxx.compute-x.amazonaws.com would work instead of Elastic IP as well.
The only problem is that it will be always different after you stop-start your AWS HANA instance.
Note that <Elastic IP> should be associated again every time you stop-start your AWS HANA
instance.
Vlad
Like (0)
Vlad Mily 08-Jun-2012 05:28 (in response to Guillaume Blanchard)
Re: Connect Data Services 4 to HANA on AWS
Hi Vlad,
Hi have launch my aws hana instance, mapped the elastic ip and still can't manage to
connect.
What user name did you use : hdbadm ? root ? SYSTEM ?
Did you create the data source ( system ? user ? ) or just completed the informations in the
datastore creation file ?
Thanks a lot !
Like (0)
Guillaume Blanchard 08-Jun-2012 10:44 (in response to Vlad Mily)
Re: Connect Data Services 4 to HANA on AWS
Hi
I finally managed to connect my hana database to do so here is what i've done :
For the data source name i used the instance id available in amazon aws management
console ( instance => instance name ).
I've entered a description
Correct Answer
Guillaume Blanchard 08-Jun-2012 12:03 (in r esponse to Guillaume Blanchard)
7/25/2019 Connect Data Services 4 to HANA on AWS _ SCN
http://slidepdf.com/reader/full/connect-data-services-4-to-hana-on-aws-scn 3/3
16/12/2015 Connect Data Services 4 to HANA on AWS | SCN
https://scn.sap.com/thread/3188866
Follow SCNSite Index Contact Us SAP Help Portal
Privacy T erms of Use Legal Disclosur e Copyr ight
0 TweetShare 0Like
Re: Connect Data Services 4 to HANA on AWS
Hi,
I am facing same kind of problem.
I am able to configure Datastore to HANA and able to import table structure.
But when I execute a BODS job either to extract data from HANA (or) to load data into HANA table, I
am getting below error.
ODBC call <SQLDriverConnect> for data source <mx2> failed: <[SAP AG][LIBODBCHDB SO]
[HDBODBC] Communication link failure;-10709
Connect failed (no reachable host left)>. Notify Customer Support.
I got stuck here, no clue how to fix this.
Am able to ping and Tel net from BODS Server to HANA Server.
Appreciate your he lp. Thank You
Satheesh M
Like (0)
Satheesh Kumar Manasani 17-Aug-2015 11:22 (in response to Guillaume Blanchard)
Then for server & port : the elastic ip : 3[instancenumber]15 so it's something like
2x.xx.xxx.xxx:30x15
Finally for user & password i used SYSTEM//password ( the default one is "manager" )
It worked perfectly, hope it will be usefull for others
Thanks
Like (0)