The official documentation is quite good in general: B.9 Migrating 11g WebLogic Users to 12c And never forget that Google is your friend ... The idea of the OTN community forum isn't to have somebody doing your work, but more to give you directions to explore...

Hi, First you clearly need to identify where the users/groups you want to migrate come from. Are you talking about users/groups of the embedded LDAP inside Weblogic? (so the users you create in Weblogic Console?) These ones must be migrated by hand, there are scripts (wlst) able to export and import if you look for it. If…

Keeping it short ... what @Pedro F said Yours is a common case and the "reduction" of the snowflake to a start is done inside the same logical table in the way Pedro said. OBIEE will be smart enough to not make the joins to D and C if only columns of B will be requested by the analysis, so you don't have to worry about it…

The question is ... why? Why do you want 2 instances of OBIEE? You probably (for sure) can have a single one answering the needs of all your users. The resources which will be highly impacted is more RAM: CPU not much as it's used when something need to be done, but lot of RAM will be used. Depending on the number of users…

Thanks for confirming what I was saying with visual examples As said: once selected it is selected and it will not be unselected without manual action (unselect them or reset). In 11g it's the same business, that's how OBIEE worked, works and will probably continue to work (and it makes sense ....).

In extension of what Sherry George said: currently running agents (so doing something at the time you look) and agents are .... fast, so they don't run for hours.

That's what I said: a measure column will be replicated for all the attributes ... And in addition you have the grant total as well. OBIEE isn't supposed to manage that requirement, your user being too lazy to make a "right click > insert row" isn't enough to justify to build a weird pivot. A pivot has some basic rules and…

I guess you forgot/missed to upload screenshot or something (or they disappeared). Arjun_Mehta wrote:Users dont want to take the trouble of adding one row on his part every time.... Please tell that user that he is lazy, and a lazy user using the wrong tool for the wrong need is "dangerous" (yes, I say it and mean it )

You maybe got it wrongly ... "archive" isn't based on any date/time parameter. "archive" works on a path, it archive what is in that path at the time of running the command. You have runcat.cmd installed on your workstation/laptop to see the attributes the runcat.cmd -cmd archive accept. (Catalog Manager being installed…

The requirement sounds a bit "dumb" as in Excel your user just need to go down or right and he has a empty row/column. You can add a column and give it a NULL value and you have a empty thing. Of course it depends totally on how your pivot looks like (because a "measure column" will be repeated for all your attributes and…

Correcting my previous answer ... Sure SampleApp has 2 domains configured against a single install ... But when you start it, 2 weblogic Admin server, 2 weblogic managed servers etc. So double resources used (ram, cpu) even if sharing the same binaries on disk.

By the way, joining the party later ... You apparently can have multiple domains on the same OBIEE install (so same "oracle_home" and multiple configs). Sample App has that with 2 BI instances.

Multiple installs? Sure, all independent and not sharing anything, no problem for that.

As the idea of the attribute is to be unique (based on the logical keys you defined), if you add the logical key to your analysis you will get the correct level of granularity. The distinct will still be there as that's how things are supposed to work (when using measures there is a group by, when only attributes it use…

Did you read what I wrote above? Because I actually gave you inputs on your original post (in the middle of the reply to your second one...). Aren't you in the described case? All the cache things ("checkbox" , prefix box etc.) are in the analysis using the value of your 2 prompts. But the prompt itself doesn't have these…

Hi, Your first case has an issue where OBIEE will not really help you a lot: you have a "dynamic" list of people. Having prompts allowing you to enter values, store these values in variables and use them in formulas in the analysis is fine. But your first example is typically somewhere where you would want a Qtr and FY…

Different reports, different columns ... Master-detail to not care as long as the column "driving" the logic (customer) is the same one, and it's your case ! Master-detail is often used inside the same analysis to drive different views, but can always perfectly works between different analysis in the same dashboard page.…

Good it works for you, as it has been suggested as solution ... Can you please close the thread? This question is Not Answered.

Hi, What do you mean by: Selva Pandiyan wrote:OBIEE reports by default generates the physical query with DiSTINCT CLAUSE. You mean when you make a query on attributes only? What's your use case? Because you can definitely avoid the effects of a "DISTINCT", depends on what you try to do exactly ...

Hi, Not sure to get exactly how your thing work. Report 2 and 3 always display data of a single customer, the one you click on report 1? If that's the case you better use master-detail instead of navigation. Master-detail will only change report 2 & 3 (both details) by selecting the customer you click on report 1 (master).