If you are using version e651, I believe that there is an issue of similar kind when you have multiple data providers.
Contact Tech Support as they might be helpful to let you know whether this is a known issue or not.
For the moment I’ve tried to group my DP in one with a partial success:
I’m now using variables to separate the data that I want (using In, ForEach …)
and I’ve often #ERRI error… I’ve tried many solutions… sometimes it works but that I don’t understand (and its making me ill) is that when the message #ERRI appears… I edit the variable… do nothing and click OK and then the display become correct… the #ERRI disappears. Why??
I ve got the feeling that replacing all DP dimensions by variables is a solution… is it really???
I am having a similar problem (in fact I just posted the problem before I saw yours). I actually only lost all my variables that were defined because they dropped the data-provider.
So, I am not sure creating variables will help you with your problem. I’ve never had this problem before (and I am on 6.5.1), but my problem popped-up after I change owner names in the Universe.
What do you mean by “changing owner names in the universe”? …could be helpful because at our company the problem also started after someone did some changes in the universe, but I don’t know exactly which…
BLOG of a BO/Teradata Junkie looking for a ‘fix’ (I have to try and laugh, otherwise I would cry):
On Friday, I upgraded my client to 6.5.2 (SP2) from 6.5.1 (205 client fixes). I noticed there were several fixes related specifically to Teradata, so I was hopeful. This did not fix the problem… I spent about 4 hours redefining most of my variables, only to refresh the entire report and lose the data-provider names from the variables again!!!
On Saturday, I gave up and started recreating the report ‘fresh’ against the Universe with the new ‘owner’ name (table names and data-provider names have not changed, only owner name changed from fcc_uat to fcc_prod.
After creating 9 of my data-providers (refreshing each one as I went along), I refreshed the entire report and had the same problem (all the data-provider names where gone from the variables and each variable had the dreaded #SYNTAX error!!!
On Sunday, I made a copy of my ISH_DEV universe to ISH_PROD and modified the table owner names to fcc_prod. At this point I started having some weird universe issues. My normally named sys_calender.calender.x table was now sys_calender.calender.calender.x when I looked at the sql in the report. I ended up removing all objects associated with sys_calender and re-adding. I gave up at this point and figured I’d get a fresh start on Monday morning.
Monday Morning:
Started over again with my original dev report. I changed the Universe of all 30 data-providers from ISH_DEV to ISH_PROD by going into the cube and selecting the new Universe. I checked each data-provider sql and it reflected the ISH_PROD (fcc_prod) owner names. HOWEVER, when I ran the data-provider, it kept coming back and telling me that fcc_dev.x did not exists? what the heck!!!??? I went into the cube and refresh each data-provider manually before trying to refresh the entire report. Things started getting better at this point and I am now using the report that I started with on Thursday of last week (I only lost 4 days ).
Summary:
I don’t know what really fixed my problem… Sorry… But all of our other data sources (we use Informix, Oracle and Ingres) do not change owner names between environments. I have been using BO for quite some time and have NEVER had to do some of the things I had to do to make this thing work. After talking with my DBA we suspect that most of the BO work is towards other data-sources (Oracle, DB2) and that most of the weirdness was due to the BO/Teradata combination.
The only thing I didn’t try was changing the data-provider name… Sounds like that would’t have worked either…