Hi All
Apologies if this has been posted elsewhere; I’ve tried searching on this board and on Google but not found anything that quite matches the issue I’m getting; apologies also if this is the wrong place - I suspect that this is a universe issue, but the symptoms I’m getting manifest themselves in Deski, which is what I work with. I’m not a designer (I’m self-taught on Deski, too). We’re on BOXI Deski, R2.
The situation is this: we have a large database, provided by a 3rd party, and they provide a BO universe to query this database. In order to give us a bit more control over this universe, our implementation team (long gone) created ‘our’ universe, with our own custom objects to supplement ‘their’ universe. These two were linked, with ‘their’ universe becoming the core universe (I think that’s right; it’s the greyed out one in designer) and ‘our’ universe being the derived one (the white one in designer).
So far, so good - however our 3rd party suppliers make updates to the universe every 6 months - and if we want support from them, we need to keep using the latest verion of ‘their’ universe. And of course, we want to use new objects etc that they introduce. It’s at this point we get problems. We can link in the new version of ‘their’ universe to ‘our’ one, and all of the new objects appear in Deski. But when we come to use them, we get a synchronisation problem, with multiple mutually-exclusive SQL statements being created for the new objects… like so:
qryXXXX.cube1
qryXXXX.cube2
We’ve managed to work around the issue up until now, but in this release of ‘their’ universe, they’ve really changed some fundamental bits, and so the multiple mutually-exclusive SQL statements are causing us a problem. On the advice of the almighty Google (which, like the Oracle at Delphi, can be mighty obscure), I’ve noticed a couple of refrences to contexts…
So I went into designer, which I’m not familiar with at all, to see what I can find. The universe has 6 contexts, and on comparing ‘their’ vanilla universe to ‘our’ linked one (that includes theirs), I can’t find any evidence of the offending tables being part of a context in either universe (for reference, I’m using the ‘list view mode’ in Designer… correct me if wrong). So I’m not sure that’s an issue. I’ve then checked the joins, and parsed a few of the objects, all of which turned out fine…
Just to complicate matters, I decided to try and reference and join the tables directly through using freehand SQL in BO, and in TOAD. This actually worked. So the tables don’t seem to be the issue, but the way the universe uses them. So at this point… I’m stumped.
The questions mainly are: what is causing this split-query issue (and is it something to do with the linking?); how can one fix it? and if it is something to do with contexts, what is the best way to check? Or is it a BOXI issue?.. any and all help gratefully received…,
Many thanks,
Neil
** Edit 28/07
Further to this, I’ve come across the Universe parameters, and compared the parameter list, not that I know what it does, but searching for cvariation seems a good thing. There is one parameter in ‘their’ universe that is not present in ours: it’s ‘COMPARE_CONTEXTS_WITH_JOINS’ and is set to ‘Yes’ in theirs. the following link on this forum explains this, but doesn’t help decipher it:
https://bobj-board.org/t/145111/2
There are other parameters in ‘our’ universe that are not in ‘their’ universe - however these are all set to ‘No’, and I assume this is the same as a null… they are ‘DISABLE_ARRAY_FETCH_SIZE_OPTIMIZATION’; ‘JOIN_BY_SQL’; ‘OLAP_UNIVERSE’ and ‘TRUST_CARDINALITIES’… any clues here?
(apologies for caps; this is as they are shown in Designer)
SXDA1 
(BOB member since 2011-07-28)