cancel
Showing results for 
Search instead for 
Did you mean: 

erro: Internal deployment of column view failed While validating/Activating DECISION TABLE.

vijay_kn
Explorer
0 Kudos

Hello Experts,

i'm getting following error message while activating DECISION TABLE, Please advise on this.

Error Report:

Server-side validation: Activation ID: 6429

Repository: Activation failed for at least one object;At least one runtime reported an error during activation. Please see CheckResults for details

Internal deployment of column view failed;Repository: Encountered an error in repository runtime extension;Internal Error:Central table does not exist in column store: $varSchema$:$varTableName$.

Repository: Encountered an error in repository runtime extension; Column View Deployment Failed

Snap shots of Decision table joins and actions:

pfefferf
Active Contributor
0 Kudos

Hi Vijay,

have you checked what the error message is saying to you. Is your central table in the column store or in the row store (which would lead to the error)?

Regards,
Florian

vijay_kn
Explorer
0 Kudos

Hi Florian,

I have given the error message/complete report in my initial question, i don't see any other information other than that.

all my join tables are column store table(in the attached first snap shot you can see the column table icon too), and Data preview is working fine on each table.

Thanks,

Vijay

0 Kudos

Hi,

I am receiving the same error..how was this resolved?

Reg
Deb

Problem resolved !..Finally after hours of arduous efforts...
So, basically this is kind of bug I would say...
Here's the solution: WHen you add a table, HANA stuido is adding an alias with the naming convention - 'XYZ_1' and this creates a confusion for the activation for creating the central table.

I can see in your screenshot also, the same problem lies - alias with '*_1' nomenclature. Just click the table and in the properties, remove the alias and voila!..You won't have any activation issue:

vijay_kn
Explorer
0 Kudos

Sorry for late response, i took different route to implement same logic. so i ignored this problem.

Thanks for the reply. Appreciated.

Regards,

Vijay

Accepted Solutions (0)

Answers (0)