getting NUll(Error:INF) error using Security override

I have 3 users who would like to view same report but data from 3 different sources. So for user1 (and everyone else ) through universe default connection will hit database I0DB6, but user2 has been set not to use default connection thru XI universe security restriction. So user 2 hits IODB4, so if user 2 runs the report he gets data from I0DB4 and for user 1 the data comes from default database I0DB6. But I am getting error when I am trying to add security restriction for the 3rd user. even if I delete the restrcition for the second user user2, I still get the error [null(error:INF). I have prompts in report and they are webi reports, I guess it has to do wit LOV stored in BO server somewhere.
untitled.GIF


shyamdev :japan: (BOB member since 2005-08-05)

The issue is solved. it has nothing to do with any overide limitation or anything like that.

The error in screenshot and some other DP API error that I was getting was due to the database client engine I configured in Universe connection. Even without the wrong engine the universe connection test works fine, but when run query thru infoview using the same universe it throws various API error depending upon what I do with the report.


shyamdev :japan: (BOB member since 2005-08-05)

Hi !

What’s your databases client and your Bo version ?

Sometimes we have this problem occuring, but we can’t reproduced it on demand…
Our environment : BOXISP2, Oracle 9.2 client and an Oracle 10g server.

Best regards


pod-soubenn :fr: (BOB member since 2007-03-09)

Ours is

BOXIR1, Oracle 9.2 and DB is Oracle 9.2 as well,

We have an upgrade project going on to BOXI r2 and Oracle 10g, so by mistake I used Oracle 10 engine while actually it’s still Oracle 9 database engine that I am sourcingf data for our reports.

when do you get this error?? check the database middleware client engine is set to correct version, the connection might workout well in universe, but reports dont handle well if it’s not perfact.


shyamdev :japan: (BOB member since 2005-08-05)

Thanks for your answer.

After having a look on the forum, the problem seems to be the specials caracters used in some prompts :

It occurs when users connect through a portal which contains the bo portal. In a direct access, there is no error.


pod-soubenn :fr: (BOB member since 2007-03-09)