When I had a problem with an invalid join that I could not see, I
exported the universe and then re-imported it. That seemed to fix the
problem. You might try that.
Michael
“AMY B. MARTEL” wrote:
I have a universe defined against an Oracle 7.3 database (BO 4.1.3). When I print the definition of the universe from Designer, it prints out 2 joins that are completely blank. when I run an integrity check on the universe, it tells me that there are two errors on the joins. I think the problem is with the 2 blank joins. But I can’t see the joins anywhere in Designer. I’ve looked in the structure window and in the actual join list. The only place I see this problem is when I print the defintion.
Has anyone ever seen this happen, and if so, do you have any idea how I can delete these joins from my universe. (The universe is not even exported yet…it is still new and under development.)
This is a known bug. You need to export the universe and then import it
back from the repository. The blank spaces between the joins will
disappear.
Good Luck
How about trying to locate the join in List Mode. Sometime this has worked
for me in the past in locating errant joins.
I have a universe defined against an Oracle 7.3 database (BO 4.1.3). When
I print the definition of the universe from Designer, it prints out 2 joins
that are completely blank. when I run an integrity check on the universe,
it tells me that there are two errors on the joins. I think the problem is
with the 2 blank joins. But I can’t see the joins anywhere in Designer.
I’ve looked in the structure window and in the actual join list. The only
place I see this problem is when I print the defintion.
Has anyone ever seen this happen, and if so, do you have any idea how I can
delete these joins from my universe. (The universe is not even exported
yet…it is still new and under development.)
The problem doesn't solve with importing and exporting the universe.
It will only temporarely re-number the joins.
The problem is the oracle user. You must devine it the BO version3
way. This is as follows:
The oracle user needs private synonyms on the tables it gets its data
from. Do not grant this user the select right through a rule on the
synonyms. You have to grant the oracle user direct select rights.
In this way you will never ever have empty joins again. I had this
problem onces and after changing the oracle user the problems where
gone.
Marc
marc.schunselaar@mail.ing.nl