Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
In graph properties:
-
I think the best choice is to use a dashboard and Save/Apply customizations. This allows you to have a set of named combinations of filters.
-
I think you are trying to solve a non-existent problem. Instead of trying to build a strange system with explicit restriction of everything, you simply need to remove all privileges from authenticated-role. PS. @Christian Berg is faster.
-
"I'm using a rpd developed by a separate group of people. When I say previous version I mean the version they gave me previously. I don't believe they changed anything major." I think the best you can do is compare current rpd with the "good" one and find out what exactly was changed (Admin tool: File->Compare). So we may…
-
That is still a database issue. I can see only two possibilities: 1. You find an error in the query so we can try to figure out why OBIEE generates the wrong SQL. 2. You trying to understand why this query brings no data.
-
So, I think we came to the conclusion that this problem is not OBIEE related. OBIEE generates correct SQL, which returns no data, right? To solve this issue you need to analyse this SQL and data and find out why it returns no rows. You have the data and the query. It's a pretty easy task. I can guess that "Start…
-
OK. And what happens when you execute these queries?
-
Have you looked at the SQL this report generates for both cases? Typically it allows to understand what is going on instead of guessing.
-
As far as I know, there is no option to show correct/incorrect values for June in OBIEE. Your model definitely contains some errors. I'd say the most probable one is incorrect dimension keys. But it's impossible to say that looking at these samples.
-
Just because it's Friday. EVALUATE_PREDICATE('REGEXP_LIKE(%1,%2)', "Approver"."Approver Name", '.*'||replace('@{reviewerAssignedTo}{}',',','.*|')||'.*') But it uses EVALUATE - bad practice, REGEXP - slow. In real life, I'd use "is LIKE (pattern match)" operator.
-
Are you sure that "Datawh1 Usage Tracking"."Usage Tracking Connection Pool"."S_NQ_ACCT" is a correct table name? Not something like "Datawh1 Usage Tracking"."Usage tracking schema"."S_NQ_ACCT"?
-
Managing Presentation Services Privileges Deliver Agents to Specific or Dynamically Determined Users Allows users to deliver agents to other users.
-
It's hard to answer your question without a crystal ball, but I'll try. It seems that your prompt initializes some presentation variable which is later used in a report. In the report this variable is used in a form like this: @{variable_name}{'filterValues'}. If nothing is selected the variable remains undefined and a…
-
I don't think anyone will answer you anything other than "because Oracle wants so". All 11g version are 11.1.1.x. There is no 11.2. 12c started with 12.2 number. It's marketing.
-
There is no OBIEE 12.1.x. The first OBIEE 12c release was 12.2.1.0.0 and the current one is 12.2.1.1.0. None of them is certified with DB 11.2.0.3.
-
@Anirban1, maybe you should alter requirements a little? I mean instead of changing the filter every month you can create a filter with a session (repository?) variable and change the variable value rather than use dirty hacking?
-
A proof for what @rmoff said: OBIEE 11g Information About the Use of Variables in the Connection Pool (Doc ID 1925713.1) PS. I know that this note is for 11g, but the cause won't change for 12c
-
Just to be sure: you are not trying to open rpd as a file while the server is running, right?
-
Your code: AND st.name in (@{Site_DBR}['@']{'SSP10'}) /*something selected*/or (@{Site_DBR}['@']{'SSP10'}) is null /*always false*/ should be: AND st.name in (@{Site_DBR}['@']{'SSP10'}) /*something selected*/or '@{Site_DBR}' is null /*All column values*/or '@{Site_DBR}{SSP10}'='SSP10' /*nothing selected, optional*/
-
Chris, actually, the core issue was the error in the query (that semicolon in the end). Columns definition is necessary but a query syntax supposed to be correct in the first place.