1. Yes, you have to define columns manually. 2. "View data" will show you the data after you define columns.

If your point 6 query is the exact one you are trying to use in BI, then remove ; from the query.

What is your OS? I've seen something similar on Windows Server 2008. It was Windows's bug (not 2008 specific).

Single value syntax: '@{variable}{default value}' Multiple values syntax: {@{variable}['@']{'default value'} select ... from ... wherecolumn in {@{variable}['@']{''} /*Some values selected*/or '@{variable}' is null /*All column values*/ or '@{variable}{na}'='na' /*Nothing selected*/

Here is the list of a few Oracle's VMs: http://www.siebelhub.com/main/2014/11/oracle-bi-sampleapp-public-instances.html 12c VM: http://slc02okq.oracle.com:7780/analytics

Yes, you will see all the users after publishing this rpd and opening it in on-line mode.

OK. A Typical cause of this error is the difference in data types of columns. On your screenshot (3) I can see that both facts are mapped "AS IS". You are supposed to make them of the same data type. Either cast double to varchar or vice versa. Like it was on this screenshot

That's not how things supposed to be done. At all. 1. Get the repository which was deployed to the server as version 8. 2. Edit this file. 3. Deploy it to the server as a new current repository (it will become _BI0009) using enterprise manager. If you don't have the file from point 1, then: 1. Connect to the server in…

Eeeh? Are you editing repository currently deployed on a server?

According to your screenshot, you've managed to create a hierarchy. What error and where do you get in this case?

That is usual when a logical table has more than one LTS. Simply create an empty dimension manually, define levels, and drag&drop SEQ_NUM field to the detail level.

This works only in offline mode. Make sure you aren't trying it in online. In case it is some UI glitch, you may try to right-click on the right field of the Identity manager and select "New Application role".

You are welcome. And it's very unlikely that google can crawl and index MOS.

That is a documentation bug. Use Locate function instead. LOCATE(expr1, expr2, integer) LocateN Function Is Failing With Error "Formula syntax is invalid" in OBIEE 11g (Doc ID 1391254.1)

It looks like this code can solve the problem (not mine, found on the Internet): Edit fiddle - JSFiddle I tried to redefine styles that way and my table sections became horizontal. Unfortunately, that brakes OBIEE UI completely so you need to find out which styles should be changed.

I can't imagine why would you need this. But I checked it, and it works. For 11g syntax is: select "Field name" from "Table name" eg: select "Calendar Date" from "Time" For 12c syntax is: select "Field name" from "Subject Area"."Table name" eg: select "Calendar Date" from "Sample Sales Lite"."Time"

The very basic idea is the following. 1. You create a report col1, col2, col3 and so on. 2. Add a narrative view. 3. Write HTML of your choice. You can reference columns by @1, @2 and so on (@1 - the first report column, @2 - the second...). 4. Set "Contains HTML Markup" flag. So your report with minimal markup could be…

This is only a sample data limit. Your reports will show full data. It's described in this note: The Rows count in the Data Tab of the Data Model is now limited to a maximum of 200 Records. (Doc ID 1679689.1)

Actually, quick and dirty narrative view took me about 15 minutes. I don't think it will take significantly more to make it good-looking. But yes, that is not the best report from a support point of view.

Look at this note: OBIEE 11g - New Application Roles not Synchronized to RPD (Doc ID 2068669.1) "This is an expected behavior due to the new changes introduced in 9.x to get rid of App role synchronization. " Doc: About Managing Application Roles in the Metadata Repository