Are you sharing the same schema in this database?

Is your servicename really "ORCL123"?

@Christian Berg is right - search and replace within catalog manager is the way to go. My unsupported bit was assuming some kind of commandline approach with e.g. sed.

First off -- it is really bad netiquette to post a question and then delete it, as you did yesterday. I spent time writing a reply, only to hit save and find that you'd deleted your question in the meantime. So, assuming that you don't delete this one : The proper way: use aliases in your presentation table - although I'm…

Just download the client tools from Oracle Business Intelligence Downloads That includes the Admin Tool - not sure about Catalog Manager.

The OBIS log is nqsserver.log -- can you post that.

[SQL Server]Setting QuotedIdentifier to 'OFF' is not supported That looks like the issue. I'm not so familiar with SQL Server but this makes it look like PDW won't accept it being OFF. https://msdn.microsoft.com/en-GB/library/ms174393.aspx?f=255&MSPPError=-2147217396

Did you check the log file? And just because one ODBC connection is right, it doesn't necessarily follow that the other would be.

Have you set up the ODBC correctly on the Linux server? Once you deploy the RPD / if you're working online, it'll work for import metadata using your local Windows DSN, but when you query the data it does it from the BI Server - which if it's running on Linux needs to have the necessary ODBC config. Check the the…

OK, so checking DBFeatures.default on 12.2.1, the differences are simply to do with when OBIEE creates a table (with Aggregate Persistence) and whether it's going to do so in memory, compressed, and/or with hybrid columnar compression. For querying the data, the exact same query will be generated regardless of which…

That doc link is useful, but I'm presuming all the talk of creating tables is for Aggregate Persistence. In general (and without checking the DBFeatures.ini), I'd presume that the generated SQL for querying the data is going to remain the same.

Have a look at the different settings enabled/disabled in DBFeatures.ini for each one. Be interesting to see how OBIEE treats each one differently - assuming that it does.

I always recommend automated deployments to clients that I work with. Whether it's to avoid getting up at 0400 in the morning for out-of-hours, or simply to make life easier -and reduce the human error from manual deploys- it's a Good Thing to do. As @Gianni Ceresa says, WLST in 11g (example script), or the native 12c…

yeah - so what @Gianni Ceresa said - you've got the actual extension as .zip which is breaking things. Rename the files so that the actual extension is 001, 002, 003, 004 and try again. Configure Explorer not to hide known extensions, or use the command line.

Can you paste the command and the output that you get if you run 7zip from the commandline?

+1 to @handat. WLST would be completely the wrong tool for this. Use curl, or a simple python program using the requests library. Here's a sample that uses the requests library - it's commented so you can see which bits you'd need to include just to test login time.

Have a look at SampleApp, and the utilities that come with it. One of them scans through your Presentation Catalog and inserts details of every single analysis (including columns used) into a DB table, which is then exposed through the RPD for querying. Works for 11g and 12c. Online example:…

Personally - I'd leave the cluster controller alone, and raise an SR for your *actual* problem.

No. OBIEE 12c is a single-node cluster. Don't disable the cluster controller. Why do you even want to?

Glad it worked.