Here's the configuration document: https://docs.oracle.com/cd/E28280_01/bi.1111/e10541/usage_track.htm#BIESG3758 It's hard to tell from what you've posted which steps you've followed or not ...

Does the error message in the OBIPS server log in EM give you more details? The details you might be looking for is a details of a shortcut to a folder than no longer exists on the Dev server ...

The thread I sent you to has the same error ... have you checked your classpath? Looks like the server can't find java to run the stuff it needs.

if you had: 1,2,3,4,5,5,5,6,7,8,9 --- mode would be 5 (it has the highest number of occurrences). Looks like you might need to have a separate (logical or physical) table that has the fact grain keys, the value you want the mode for and a 1 dummy column to sum, then you select the max(sum(1)) by the value-as-attribute ...…

How to ready error in Logfile?

"business users want data in local currency converted at report date" -- they want the rate at the run-time of the report or they want the rate at the time the original fact was recorded? The latter is typical - the former leads to a moving target for which each time the report is run a different answer is given.

Use a small section on your dashboard page which displays a narrative that is sourced from your ETL control table ...

Did you try something like this? http://hostilecoding.blogspot.com/2012/10/obiee-how-to-import-data-from-excel-on.html

Not a fault of the OBIEE tool ... https://support.microsoft.com/en-us/kb/2721825

If your users REALLY want real-time data - disable all cache ... You can run a script to purge the cache at any interval you want ... simple Google search reveals plethora of approaches.

Master-detail, navigate to BI content, drill, etc ... all are predicated on real data ... adding your own groupings at run-time is a disconnected (for lack of a better term) approach to the underlying data (whose relationships are maintained in the storage of data; your sales amount is stored with a date key and a customer…

You can model OLTP in the BMM layer ... you just need to be much more careful not to build circular joins and such ... most DWs have a little bit of snowflaking so it's a very common practice to have multiple LTS per logical table as well. I see red flags when I see an LTS of a fact joined to another fact -- in EVERY CASE…

You are creating that group at run-time (after the query data has been retrieved) and the BI server doesn't have keys (logical or physical) to perform the drill at that point ...essentially drilling is based on the concept of granularity of data not on the grouping of data ... so if you need this group to be drillable, you…

HOW did you create your group?

Quite frankly ... a properly formed warehouse has inner joins as any fact row that doesn't have an appropriate dimensional key has the -1 / 'Unassigned' key, so the star is made up of optimized indexed inner joins ... Furthermore, given the inner and join specs you've got in your LTS, it leads me to believe that your model…

Right off the bat ... don't join 2 fact tables directly ... star schema is such that dimensional attributes are used in a conformed way to related facts, in your case the facts of sales and costs are related through the commonality found in the channel and time dimensions.

" I created a BMM and Subject Area and deployed the repository." In the BMM you need to create the appropriate dimensional hierarchies and then set your logical dimensions' and facts' Logical Table Sources' content levels to the appropriate level. This set the grain for the tables, so that the BI server knows how to craft…

Yes ... I should have said the repository tables are required the actual utility (RCU) method is not.

Installing OBIEE 12c. Part 3: Creating the Repositories - Red Stack Tech It's a good step by step write up ... RCU is a required step ...

You might have a good connection, this error is often associated with the content levels set on logical table sources ... try setting the ones you need at their appropriate grain, then set the rest to their total levels.