What do you call an "Analytics report names"? What kind of "export" did you do in catalog manager? Catalog Manager is perfectly able to read the OBIEE/OAS/OAC object names, therefore the names are accessible.

It isn't the same "product", it doesn't have the same features. So the "GO URL" no, but if you look at URLs of DV you can find what sort of URL you need to call for what you are after.

as per my requirement, I have to join snowflake dim to oracle dim in physical But do you actually have the physical join between the 2 tables? Because you jump straight into describing your logical model and the LTS, without saying if you actually have a physical join or not... (This is for point 3) above posted by…

https://community.oracle.com/tech/apps-infra/discussion/comment/16832366#Comment_16832366 Going into more details, you must have that script if you are in the right place. The script is on the server, not on the client installation. You should go on the server and run it from there.

A catalog archive isn't the same thing as a BAR. You can for sure do catalog archives, as long as you don't expect to get a BAR as result but a real catalog archive.

A detail first: "reply asap" in a community forum where users are investing their own personal time and aren't paid to post any reply is considered unpolite, try to avoid it in the future (or hire a consultant and he will be paid to reply "asap"). Did you try with a CASE WHEN ? It's the IF-ELSE in an OBIEE analysis.

BIP is a different product, it's totally different as it works with data models and it's a totally different thing. I suspect you will need to do manual parsing of things to get some info out BIP reports.

The security logic is the same, but at the moment you should focus on tracking things in your OAS without caring much about 12c. A user to be able to login should first have a valid username and password that will be authenticated, after it should have the required authorizations and those come from roles. Start debugging…

Did you configure the security? Just defining a LDAP is only part of the configuration, you cover authentication, but you still need to deal with authorization. Do your users have roles? Are the roles correct? Do they inherit privileges from the default roles? Did you create fully new roles?

At report level or server-wide in the Administration page > Runtime configuration > Properties.

You can't? You can use whatever variable you want in the LSQL of a prompt, what make you say that you can't use the variables? Are you saying that because you don't see it working? Did your page reload after setting the first 2 prompts? Because if you don't submit prompts, the variables still don't exist and therefore your…

The header isn't a formula field, it's a text field. Variables are matched and replaced. Your 'variable' || ' ' || etc. should be written as text with the variables inside, don't try to concatenate things or anything like that. Because it's only a variable replacement, it will match the variable value, the default value…

There are ways, there aren't simple ways. The catalog (the analysis) isn't aware of that info because that's covered by the RPD. You can export lineage information from your RPD, you can get the info of what subject areas or columns are used by the analysis, you can connect all the dots and get the whole info. It isn't…

Assign a sort order column and/or a descriptor ID column to your logical column. But it's just a warning, because it all depends how and where you are going to use your logical column, and based on that you will maybe never ever use the sort order column or the descriptor ID column. If you really want to get rid of that…

I'm downloading the files right now, no issues at all. While not knowing exactly how the Oracle website is built, the SampleApp 607 files are behind license agreement + login. From time to time the Oracle account struggle a bit and fail to login. Maybe try with a different browser or by deleting all temp files etc.

I just tested, it does work fine. Where are you entering it? (what is exactly that you call header) How are you writing the reference to the variable? A screenshot is worth more than hundreds of words...

Did you try just the normal syntax @{variable_name} ?

It's not relate to the generated queries or the source models (RPD). Sorry but if how can you say it isn't related to the RPD if you have the same behavior when creating an analysis? If you aren't using a DDR it definitely has something to do with the RPD and how queries are generated.

Hi, Maybe you want to start by providing a bit more context? What product and version? Did you look at the generated queries? How are they different when the column is alone vs when you have it with the additional column? Most of the time, you can see this kind of problems because of the source models (in your RPD) and how…

Don't you have in your RPD an object (user/role) defined that doesn't exist anymore in your OAS? The error seems to fail retrieving settings (grants etc.) of a user or role.