Can't create plan for join query

[patrickbachmann]

Hi superhero's,

I have a calculation view that is script based and combines a bunch of ce_olap_views and ce_projections, does some ce_aggregations and ce_union_all.  Nothing too extraordinary and it is validating successfully and activating succesfully however when trying data preview I get this error;

column store error: search table error: [23008] Can't create plan for join query

I haven't found much related to this error when searching Al Gore's world wide web so I was wondering if any of my super friends have seen this before or have any guesses what to look into next?

Thanks,

-Patrick

[lbreddemann · Accepted solution]

Maybe stupid sounding question but: can you re-activate all the views successfully?

Sounds as if there is something broken in the view-structures.

[patrickbachmann · Accepted solution]

Yes I can reactivate this view successfully.  I can copy it and then reactivate the copy successfully.  Then data preview on the copy does not work and get same error. 

[patrickbachmann · Accepted solution]

Wait or do you mean all of the olap views that I'm calling in my calc view?  ie: all the source views.

[former_member182302 · Accepted solution]

I have hit similar errors, and as lars suggested.. reactivation worked for me a lot of times

Regards,

Krishna Tangudu

[patrickbachmann]

Ok thanks for your suggestions guys.  It looks like reactivating one of the source views being called by the calc view worked.  Of course it was the very last view that I tried to reactivate that did the trick!

-Patrick

[justin_molenaur2]

Instead of data preview, can you see if the SQL select from this view works instead?

Regards,

Justin

[patrickbachmann]

Ok I tried select * from "_SYS_BIC"."MySchema/MyView" and it also failed with same error.

[justin_molenaur2]

Can you try commenting out all the calls except one or two, activating and then testing to see which view might be causing the problem? In this case I would make sure each component is executable, and slowly combine until you can discover the error.

Regards,

Justin