Help: sometimes #SYNTAX where refreshing

Hi all…

I’m a little lost cause I’ve encoutered a lot of problem with my reports (problem with analysing) on DB2 and it’s going on.

Sometimes, when I refresh my report… all the variables are modified like that:
If i have a variable called

<CreditSum> =<credit(Query 1)>+<credit(Query 2)>

After the refresh, the fields containing in my table are displaying #SYNTAX cause the variable has became :

<CreditSum> =<credit>+<credit>

And it affects all my variables containing 2 or more identical dimensions from multiple queries.
Why did the variables change?


Toby :fr: (BOB member since 2005-10-28)

Try,

Var1=<credit(Query 1)>
Var2=<credit(Query 2)>

=+


KhoushikTTT :us: (BOB member since 2005-02-24)

Hi,

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.

Hope this helps.

Regards,
Suresh


chvsuresh (BOB member since 2005-03-25)

I suffer a similar problem…it drives me crazy!!! what the hell is wrong??? :confused:


MichM3 (BOB member since 2005-06-07)

Did you check whether the links between DP1 and DP2 dimensions after the change/refresh still exists…or LOST…??

If you go as Newyorkbasha said, your problem should be solved…


BO_Chief :us: (BOB member since 2004-06-06)

links are still there

solution of Newyorkbasha doens’t work either…still #SYNTAX error


MichM3 (BOB member since 2005-06-07)

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??? :confused: :confused: :confused:


Toby :fr: (BOB member since 2005-10-28)

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.


larryc (BOB member since 2004-04-15)

What do you mean by “changing owner names in the universe”? :expressionless: …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…


MichM3 (BOB member since 2005-06-07)

Try changing the names of the data providers, it usually re-establishes the correct names for the objects/variables, e.g from Query 1 to Qy1

no luck :cry:


MichM3 (BOB member since 2005-06-07)

Damn, that worked for me, at least in Toby’s original scenario it did.

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 :reallymad: ).

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…

larry


larryc (BOB member since 2004-04-15)

Any chance one of your dataproviders is dependent on the results of another?? I believe the functionality is called Query Results?


JTAMBLYN :canada: (BOB member since 2003-05-28)

yep. All my data-providers are dependent on the ‘first’ query against the my calendar table with a prompt.


larryc (BOB member since 2004-04-15)

yes…same here…all DP’s are dependent from the first and are linked using the “Query result” technique…

By the way, I’m now busy redesigning my report again from scratch :reallymad:


MichM3 (BOB member since 2005-06-07)

What version are you running? Did you go into the ‘cube’ and refresh each data-provider manually?


larryc (BOB member since 2004-04-15)

I got stuck with this problem as well a while ago. I stay clear of the Query Results technique. Here is one thread that I would take a look at.

Hope this helps.


JTAMBLYN :canada: (BOB member since 2003-05-28)

Hi,

I’m using 6.5.1…seems that the query-result technique isn’t bug-free yet…

Yes I did refresh all DP manually and renamed them and saved it and re-opened the report…no luck

Anyway, just did a make-over of the report from scratch…everything works fine now…I’ll keep an eye on it :wink:

Thanks for the input…it’ll defenitely have to do with the Query Result - thing


MichM3 (BOB member since 2005-06-07)

Iam Facing the same problem…Have any one solved the Issue?


AvadiZone :india: (BOB member since 2008-04-19)