Someone wanted to take away from all users ‘My Dashboard’. They want that the users only have the choice between the ‘common Dashboards’.
But the users (the report creators) need My Folders.
So Manage Privileges – Catalog – Personal Storage (My Folders and My Dashboard) does not fit exactly.
Someone has created default shared dashboards that they want the users to see/read by default, but they want to restrict user access to the Shared Dashboard folders.
They want users to be able to access their My Folders directory, but not have access to their My Dashboard link or My Dashboard folders. This is not possible with out of box functionality.
The following enhancement request has been created to benefit the users.
The only way to deny access to ‘My Dashboard’ is via the “Personal Storage (My Folders and My Dashboard)” Catalog privilege. Denying this privilege to a group or user will take away access to both ‘My Dashboard’ and ‘My Folders’ – currently, you can’t separate the two.
Jay Honnavalli suggested the following solution:
“Alternatively, here is a suggestion of using current functionality would be:
1. Create a web catalog group and dashboard via “Manage Presentation Catalog Groups and Users” to be used as the default user dashboard.
2. Grant the ‘Everyone’ web group the appropriate privilege to this catalog group via “Manage Presentation Catalog” – e.g. ‘Read’.
3. In the admin tool, create a session init block to set the ‘PORTALPATH’ session variable to the webcatalog path of the default dashboard page.
3.a. You can find the path by looking at the properties of the folder under ‘_portal’ in the catalog group folder the default dashboard was created in – e.g. “/shared/user_default/_portal/Home”.
3.b. The init string could either select the literal path (e.g. select ‘/shared/user_default/_portal/Home’ from dual) so all users would be routed to the same dashboard. Alternatively, the path could be stored externally, e.g. in a table, and selected from it per userid. That way, it would be manageable outside of the admin tool.
This would force all users to the default dashboard specified in the path used to populate PORTALPATH for all users.
One issue that may occur is with existing users that have set their ‘Default Dashboard’ to anything but ‘Default’ in the ‘My Account’ link – they may be required to set it to ‘Default’, then log-off/log-on for the default dashboard setting to take affect.
I know of no way to get around this potential issue for this scenario short of each user making the change OR deleting users from the webcat such that a subsequent logon will ‘re-initialize’ their account (which will then use the init block set PORTALPATH value). Both of these options seem severe, and the second may prove problematic as long as the ‘My Account’ link is still active. ”
It’s been very quiet lately. Maybe because the summer is leaving and everyone is trying to take advantage of its latest days. I’m still learning my ways around newly updated Oracle’s MySupport. So far I have mixed feelings – I like the speed compared to metalink3, however, I’m still not sure if I get the new interface as well as flash-based navigation.
Tom Siebel got into problem with an elephant – but everyone probably knows about it by now. I wish him a speedy recovery.
I’ve been busy preparing environment for new project. Learning about configuring SSO for WNA-enabled security under Linux using OAS. Luckily for me, there’s a good discussion in regards to this here: http://forums.oracle.com/forums/thread.jspa?threadID=847808
Also, I’ve started re-reading “The Data Warehouse Toolkit”. It’s an awesome book.
I can’t dedicate enough attention to OTN anymore, but cheers to everyone who’s doing a great job of helping people to learn. I’m still about 15 questions away from 10th spot, so don’t relax too much Goran
This is how top-10 looks like as of today:
Kishore Guggilla (2160)
Stijn Gabriels (1295)
John Minkjan (1175)
Madan Thota (1070)
Christian Berg (805)
Goran O (680)
Good luck all.
If you want to see correct calculations – then a BI Server Restart might be required after you change Aggregation Rule for a column from SUM to AVG (or in any way).
I noticed that problem on Grand-Total calculations – it just wouldn’t perform correct aggregation for the column after RPD change in online mode (with Aggregation Rule – Default).
After services restart, OBIEE would perform correct grand-total aggregation.
I think this is an interesting question especially for those who would like to know how BI “thinks”.
The goal is to understand what rule is followed when several fact are at the same content level
Normally the server uses the content level to pick the correct fact table.
The server is looking for the most aggregated source.
First choice is a query in which the grain of the query matches the grain of the content filter.
If there are no sources which match that criteria, it will look to other means to chose.
It looks at how many dimensions are associated with the fact table (size of the content filter), levels of the content filter, number of values from the level definitions multiplied.
There’s a bug in OBIEE 10.3.1.2 that renders time-series OBIEE function AGO useless if you’re using Filter on Logical Table Source (Content – WHERE). Apparently, the query generating AGO doesn’t pick it up and as a result – you will not see correct report. It might affect you in many ways if you’re using the LTS filters. The fix that Oracle suggested was to upgrade to 10.3.1.4, however, it’s not possible at the moment. We’ve created database views applying necessary filters there. Performance-wise we got a hit, but our business intelligence server is showing correct data.