the catalog folder only appears on the one node, and it is there where it disappeared from. OK I'm confused again Is this a single BI domain, clustered across two nodes? If so, how do you mean it disappeared from *one* of the nodes, and that it only appears on *one* node? Normally you'd have the shared network folder…

Well if it wasn't a human then .. it was a computer And OBIEE wouldn't have got to where it is today if it made a habit of soiling its pants like this, so I would imagine it's something else running that's doing it (if it's not a human - malicious/accidental/ignorant). Can you speak to your Solaris admins and see what…

@user11394838 aside from the other questions - what OS are you on? Single or multi-node cluster?

Hi Jerry, I'm a bit confused. In your first post you talk about copying objects between RPDs manually. Your last post though talks about doing a merge. Are you using the AdminTool to do the merge? Why do you need to change the physical database name in the HR RPD? Is the same physical database object used by the main RPD?

*shudder* Why not just use the supported route through RPD merge in the Admin Tool? Hacking around with the RPD like this is only going to end in tears.

Either: 1) Your RPD is not modelling sufficiently robustly, and the change in version has caused OBIEE to pick a different execution path for your queries that results in different data 2) Your RPD is perfect, but you have hit a bug in the newer version of OBIEE. In which case, raise an SR to Oracle. In the clear majority…

You mention EAS but that is all. What software are you using? What version? What platform? What data? http://catb.org/~esr/faqs/smart-questions.html#beprecise

select T48352.ACC_CODE as c3, T48352.ACC_DESC as c4, T48352.CODE_COMBINATION_ID as c5, concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(concat(T48352.COM_CODE, '.'), T48352.DEPT_CODE), '.'), T48352.ACC_CODE), '.'), T48352.SUBACC_CODE), '.'),…

Hi Everyone,I meet the performance problem from obiee 11g. I was using a complex view in RPD from EBS, this is a gl account balance,about 40 thousands rows. I seperately query the view in client tool is very fast(1s),but run the report in web cost almost (47s) and I using the sql that biee generated in client is also…

There are three different BAR files that you can use as the basis for your OBIEE 12c deployment (or, and 11g migration jar). The SampleAppLite and Starter BAR files both contain BI ServiceAdministrator, BIConsumer, and BIContentAuthor application roles and permissions.…

As @Michael Verzijl says, the OBIEE SampleApp is a superb place to go for inspiration for (i.e. to rip-off ) what's possible with OBIEE visualisations. In terms of "good", it depends. There's "fancy that looks good in a presentation for the Board/Client" good, and there's "communicates the data in a clear and…

Have a look at the Administration tool's Query functionality: https://docs.oracle.com/middleware/1221/biee/BIEMG/mngreposfiles.htm#BIEMG643 You can use the Columns... option to add/remove columns from the view, including the table names and join condition.

Why are you even in the position to be migrating hundreds of reports *back* a version?

Let's look at this another way - what is it you're trying to do here? What's the requirement driving trying to populate a session variable like this?

Sorry yes you're right - version number is held in the .atr. XML hacking just to remove unsupported content, of which as you say there wasn't much difference in the two releases.

+1 to @Gianni Ceresa Use the nqquery.log (11g) / obis1-query (12c) to see detail of cache hit/miss, as well as Usage Tracking. As well as agents to seed the cache, you can directly populate it with SASeedQuery passing in a specific logical query (for example, at a detail level like Gianni suggests)

Nope. XML hacking only; completely unsupported and at your own risk.

They are independent. Size each connection pool based on (a) the estimated workload it will deal with and then (b) the actual workload based on DMS statistics to determine the high watermark of connections busy at one time per connection pool.

@Gianni Ceresa has pretty much said it all. I'd only add that if you are federating queries across both database A and B (for example, one stores sales, the other stores customer lookup data, and your end user runs a query asking for sales by customer) then OBIEE will indeed generate a query against each database, pull the…