You have a copyright on that one Christian, I didn't mention it to not have to owe you any money

Hi, Logs ... Look at the generated queries, check if there is some user based security which is applied to the users and not to your admin account, check if it's caching issue etc. EDIT: well ... Joel is quicker in posting

A little longer answer than Joel: it was supposed to be something coming with 12c, multiple instances support. In practice there isn't anything like that for now, therefor the short answer was "no" and the longer one is still "no". If really needed you would need to merge the 2 RPD into 1 or have 2 separate OBIEE instances…

Hi Farrukh, It all depends where the user comes from. You have a chance it is stored in the Weblogic internal LDAP, in that case log into the Weblogic Admin console, go in the security and search for the user. If you find it, you can then change the password there directly. If you can't find it (or can't change the…

And there we go! We "smelled" this tool was part of the deal and finally it's really there. I don't have that thing (and like Thomas I never wanted to use it), but it's a old thing. That's supposed to be an OBIEE account allowed to open the RPD online I would say, it's the only place where there is a username as a RPD…

Just what Christian said And if you were trying to do it in the RPD, you don't need the "by" syntax there as you have full access to all the properties of your model, so you set things by using content levels etc. That's why many on here had doubts about your model. As soon as you have a proper model with dimensions and…

As this thread is just like the other one about ColMax the same reply apply: The "by" syntax is perfectly valid and supported in OBIEE 12c. So give more info on what's your current situation and I'm sure the community will manage to give you some good hints on how to get over this point.

Trust me, I really prefer to be able to help people instead of proving them wrong ... This is OBIEE 12.2.1.3 (the exact same works on all the 12.2.1.x and also on 12.2.2.x) So, now that we all agree that OBIEE always supported (at least for the last 10 years) the "by" syntax in aggregations I guess it's time to make a step…

Because of MAX you need to do the sum yourself, so all you need is to use AGO twice to get the M-2 and M-1 value and add the current one. So your formula will be <measure> + AGO( measure M-1 ) + AGO( measure M-2 ) this isn't a valid syntax, it just gives you the idea on how to do

3744064 wrote:Thanks Angel but OBIEE 12c doesn´t aloud the syntax (by) OBIEE 12c perfectly accept and allow the "by" syntax. The question is more where and how you are using it. Did you build a proper model and is your analysis based on that? Because the "by" implies dimensions etc. to exists (or OBIEE will struggle in…

Or MAX(... by ....) as "quick-win"

Can you define the exact behaviour and logic of "ColMax" ? Because "return the largest value in a column of numbers" is just what MAX() gives you, but sounds too easy as an answer...

Can you define exactly what "CUME" is supposed to do? Or the full need you have which was covered by "CUME" ?

Before to go into the detail of your question (or what I understand of it) let's fix a detail of "wording" : What Christian was pointing out is that you call "report" a thing done in BI Publisher, while if you do that thing in OBI Answers (using a subject area etc.) the name is "analysis". So when you say it's an analysis…

Still a good reference to start the talk: https://speakerdeck.com/rmoff/source-control-code-deployment-and-concurrent-development-for-obiee-12c TL;DR https://speakerdeck.com/rmoff/source-control-code-deployment-and-concurrent-development-for-obiee-12c?slide=55

aPsikus wrote:We have decided to remove aggregation rule in RPD, but then in report there is error:State: HY000. Code: 14025. [nQSError: 14025] No fact table exists at the requested level of detail You are abusing a bit too much here OBIEE requires the business model to be a perfect star, a star schema has dimensions…

Look at your logs, check the generated query, open your RPD, fix the model and retry. As OBIEE is empty out of the box it's difficult to tell you anything more precise as you are the only one having your RPD and your analysis in front of you.

Multiplied by 360? Sounds like it's multiplied by every single day ... You are doing a join at a different level than the lowest granularity, so you have to model things right in the RPD telling the system how things are supposed to work. So the join and OBIEE are just doing exactly what you asked! And it's quite…

mmajdana1 wrote:I use this url to login to OBIEE http://bit.mprh.local/analyticsso it is the same url just without the port, and this is the format needed for Catalog Manager http://host/analytics doesn't mean you connect without the port, it just means you are using the default port 80 for HTTP. So in Catalog Manager you…

Details, details, details ... If you don't give more details of what you are doing, where, how and on which exact version it's like a lottery: we can post random things but it will not help you.