Error "(dberror) [403]: internal error: Remote execution error Camel execution failed" on hana db?

[jeff_k]

I have used SDI DP Agent in order to establish connection between my snowflake db and hana db but after I create a virtual object and try to preview data I get the error: (dberror) [403]: internal error: Remote execution error Camel execution failed

I'll add more in depth detail of what it is I exactly did.

1) Using the DP Agent I have registered CamelJdbcAdapter to my hana instance.

2) Created a remote source in order to establish connection between snowflake db and hana. I know that the connection was successful because I can see all the snowflake schemas and tables as remote objects in remote source. It also allows me to create a virtual object of the snowflake tables.

3) After I create virtual table of the remote objects and try to "Open Data" of said virtual table it gives me error. If I use the sql console to query it gives me an empty table of the virtual object.

Here is a the full error message if I try to open data:

Could not open 'DBADMIN'.'virtual_customer'.

Error: (dberror) [403]: internal error: Remote execution error Camel execution failed. for query "SELECT "virtual_customer"."C_CUSTOMER_SK", "virtual_customer"."C_CUSTOMER_ID", "virtual_customer"."C_CURRENT_CDEMO_SK", "virtual_customer"."C_CURRENT_HDEMO_SK", "virtual_customer"."C_CURRENT_ADDR_SK", "virtual_customer"."C_FIRST_SHIPTO_DATE_SK", "virtual_customer"."C_FIRST_SALES_DATE_SK", "virtual_customer"."C_SALUTATION", "virtual_customer"."C_FIRST_NAME", "virtual_customer"."C_LAST_NAME", "virtual_customer"."C_PREFERRED_CUST_FLAG", "virtual_customer"."C_BIRTH_DAY", "virtual_customer"."C_BIRTH_MONTH", "virtual_customer"."C_BIRTH_YEAR", "virtual_customer"."C_BIRTH_COUNTRY", "virtual_customer"."C_LOGIN", "virtual_customer"."C_EMAIL_ADDRESS", "virtual_customer"."C_LAST_REVIEW_DATE" FROM """TPCDS_SF100TCL"".""CUSTOMER""" "virtual_customer" "

The data preview uses the following statement to fetch data:

SELECT TOP 1000

"C_CUSTOMER_SK",

"C_CUSTOMER_ID",

"C_CURRENT_CDEMO_SK",

"C_CURRENT_HDEMO_SK",

"C_CURRENT_ADDR_SK",

"C_FIRST_SHIPTO_DATE_SK",

"C_FIRST_SALES_DATE_SK",

"C_SALUTATION",

"C_FIRST_NAME",

"C_LAST_NAME",

"C_PREFERRED_CUST_FLAG",

"C_BIRTH_DAY",

"C_BIRTH_MONTH",

"C_BIRTH_YEAR",

"C_BIRTH_COUNTRY",

"C_LOGIN",

"C_EMAIL_ADDRESS",

"C_LAST_REVIEW_DATE"

FROM "DBADMIN"."virtual_customer"

Have I missed a step or doing something wrong?

[jeff_k]

Can you reproduce the issue after increasing the dpagent logging level to ALL? "Camel execution failed" suggests to me that the agent should have some more information than HANA.

[former_member794470]

Hi Jeff,

Still getting same error after changing logging level to ALL.

[jeff_k]

The point is just to make your agent print more information about the problem, you can check in the framework.trc files in the dpagent's log folder for any clear issues.

If you don't find any immediately actionable messages (login failed, database name not found or something simple like that), I suggest to submit a support ticket to HAN-DP-SDI.

[HakanHaslaman]

In such a situation, the issue needs to be deeper analyzed.

1) Please check the correct HANA version and the SDI you are using

2) If it is an existing remote source and failed now, please check, what exactly has been changed in the environment.

3) Please increase the loglevel of dpagent to ALL restart it and then reproduce the problem. Once that is done, please check the dpagent FullSystemDump and check the target HANA dpaserver.trc and indexserver.trc files that go with this.

if you are not familiar with getting these traces, please see the below KBA's for details.

2496051 - How to change "Logging Level" (Trace level) of a Data Provisioning Agent - SAP HANA Smart Data Integration
2807852 - How to create DP agent FullSystemDump - SDI

4) Please check once more the remote source configuration from HANA

[HakanHaslaman]

Please check this note, may it helps you further:
https://launchpad.support.sap.com/#/notes/3076509

[former_member794470]

I checked the note and the solution is to have a dp agent version of 2.5.5 or later. My dp agent version is 2.5.5.2

Here is the full versions.txt:

#Data Provisioning component versions

dpagent.version=2.5.5.2

lcmsdk.version=2.5.52

dpagentservice.version=2.5.3

dpadapters.version=2.5.3

repagent.syb.version=15.7.1SP210

repagent.sybfilter.version=15.7.1SP214

sqlanywhere.version=16.0.0.1691

ms.vcredist.2010.version=10.0.40219

ms.vcredist.2015.version=14.0.24212

ocs.version=16.0.03.10

ci.version=1.9.0-rc-2

dataservices.engine.version=14.2.14.2936

dataservices.lib.version=14.2.8.1504

dpagent.build.version=2.5.5.2

build.time=09.11.2021 @ 17:25:20 PST

git.hash=515a98fdac72f32560dd7d30b0bdfefac8388a6f