Errors in calculation views after upgrading to SAP HANA SP05

[former_member182302]

Hi Kulwinder/Lars,

I came across a similar error today:

executor: plan operation failed;ceUnionPop ($REQUEST$): Failed to append column COL13; current column type = ValueArrayColumn<seconddate> other column type =ValueArrayColumn<longdate>

Current HANA Version 1.0.84

Is it also calls for a support incident or can be related to a code bug?

Any inputs would be helpful

Regards,

Krishna Tangudu

[former_member182302]

Hello Folks,

Update:

We had a case condition for one of the column like below:

1. SELECT <columnlist> FROM ( 
2. SELECT <columnlist> FROM TABLE1 <filtercondtions> 
3. UNION ALL 
4. SELECT CASE WHEN <condition>  THEN <columnlist>
5. ELSE NULL END FROM TABLE1 <filterconditions>) 

The case condition was causing this issue. Even though the source datatype is SECONDDATE. So we pushed the case statement to the outer query and the issue got solved.

Regards,

Krishna Tangudu

[lbreddemann]

Hi Krishna,

please don't revive old/closed threads; especially when they are about a much older software version.

The error message alone doesn't really allow too much insight into the cause of the issue.

But it "reads" as if there is a type mismatch in the model.

Have you tried reactivating it?

Are there additional error information in the indexserver trace file?

- Lars

[former_member182302]

Hi Lars,

Thanks for your response.

Sincere apologies for picking an old thread for asking this question.

I have not reactivated but redeployed all the depending views. (Since it is in Production , I have not yet reactivated, Let me know if you want me to try this as well )

Based on that number COL13, I was checking for the 13th and 14th ( If the counting has started from COL0 ) and checked the data types and all the source columns, data types are SECONDDATE.

Have checked the indexserver traces but no additional information I found there as well.

The pseudocode of the CV: (77 columns)

SELECT <columnlist> FROM (
SELECT <columnlist> FROM TABLE1 <filtercondtions>
UNION ALL
SELECT <columnlist> FROM TABLE1 <filterconditions>)

The pseudo code for Procedure:

Insert into TARGET TABLE (select <columnlist> from CV)

The same procedure (full load)  was working fine in Quality system but failing inconsistently in Production system.
Upon failure, when we repeat the procedure job it is getting successful again.

Let me know if I need to share anyother additional information

Regards,

Krishna Tangudu