cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Column store errors during runtime

Former Member
0 Likes
2,074

Hi,

I created a HANA instance in the trial landscape and directed my application to use the HANA instance schema. Over time, I get errors:

SAP DBTech JDBC: [2048]: column store error: search table error: [29] attribute not defined for physical index;internal error: attribute 'NEO_29J91OPIP2IAEWXFUZRHT093R:CA_EV_VENUEen/PK_EVENT_VENUE_ID' not found in indexInfoMap

I'm using the HANA instance instead of the default schema created from the application because I need to run spatial queries, which is currently only available in the HANA instance.

Does anyone know what's wrong?

View Entire Topic
Former Member
0 Likes

Have you found any solution? I'm getting the same Error:

attribute not defined for physical index … not found in indexInfoMap …

And also this exception, which might be the Soruce:

(90358): exception  1: no.10000008  (ims_search_api/Delta/impl/DeserializerContext.cpp:2112

Attribute engine failed(6900); $function$=writeDataIntoDelta

TableLoad.cpp(00580) : TableLoad::load(): replay log failed

And I can confirm, it happens to tables with a spatial column. Also a few days ago, hana started to loose data after restarting the system, Shutdown at 25.08.2014, the data could not be loaded the next day after starting HANA again :

Now the whole table seems to fail :- (

Former Member
0 Likes

Unfortunately not. I had to ditch the spatial columns and created lat/lon columns and convert them on the fly to st_point during queries.

Former Member
0 Likes

Ok thanks, I'll open a ticket and post a solution here as soon as there is a patch available.