Problem with a initialization block for a repository variable

Question

This is a very strange problem, some queryies which are issued on behalf of a Repository Variable give a succesfull completion but with 0 rows selected where it should select 1 row.
I have a query like this
select var1, var2, var3, var4 from table1
where var1 = (select max(var1) from table2);
When i test the query it gives nicely a result 1 row and the repository variables are filled correctly. The initialization block has a schedule so it will run once an hour.
In the logfile I can see that the query is fired on behalf of my repository variable with a result of 0 rows.
I thougt i could work around the problem by puttting the query in a view, import this view in my physical layer and do a simpel select var1, var2, var3, var4 from view in the initialization block.
This still had the same result, testing it works fine I get nicely one record, when it is fired as a result of a schedule it gets a result of 0 rows selected.
I've tried the query in different formats, the query that i started with was this (see below). When that didn't work i started testing with simplere query's like above
select var1, var2, var3 , var4 from (
     select var1
     from table2
     where type='x'
and datum = (select max(var1) from table2 where type='x')
) join table2 using (var1)
Other init blocks work fine. Those init block differ from the one with the problem, they have no join between two tables. The only join I have in one of the working blocks is a join with something from dual.
The other point is, this init block did work on a previous version of obiee, but after an upgrade it doesn't work anymore.
The OBIEE version is 10.1.3.4.1.090414.1900
The database is version 10.2.0.1.0
I was able to test it myself on a 10.2 database with a 10.1.3.4.0 obiee there it worked fine. Also with 10.1.3.4.1 with a 11g database and that worked ok to.
Has anybody else stumbeled on this problem and how can i solve it. Also workarounds are welcome. Preferably not changing to a session variable cause in that case i have to change all the reports that use this variable.
Kind regards,
Yvon

Answer 1

Have your DBA put a trace on your OBIEE sessions to see what SQL is OBIEE firing and to confirm the rows do exist. Are you sure this data is always there?