Oracle Analytics Forum

Home› Oracle Analytics and AI› Oracle Analytics and AI Forums› Oracle Analytics Forums› Oracle Analytics Forum

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Connection for the repository

Received Response
37
Views
2
Comments
Support Kitry
Support Kitry Rank 2 - Community Beginner
in Oracle Analytics Forum

Hi,

We have done a migration from OBIEE 12.2.1.4 to OAS with a BAR file.

The connection pool used in that RPD use Session Variables to connect to the database regarding the "User" connected to "Analytics".

So the connection pool in the RPD is using the session variable to connect to the right database with

"Data source name" = "VALUEOF(NQ_SESSION.PROJECT_DSN)"

E.G. : Connection as user "TEST1" ⇒ session variable "PROJECT_DSN" = "DB_TEST1" and the data source name (the schema) used is "DB_TEST1"

With OAS in "Analytics" we are not able to create a analysis on the repository, the connection is not working.

Since in OAS the connections are defined in DV, do we need to create any connection in DV for using the repository ?

Or do we need to configure a tnsnames.ora file in OAS ?

Jean-Pierre

Tagged:

Answers

  • Brendan T
    Brendan T Rank 7 - Analytics & AI Coach

    Have a look at where the tnsnames file is located. It is in a different location in OAS, look for DOMAIN_NAME as it as its own Oracle Client

  • Gianni Ceresa
    Gianni Ceresa Mod

    What Brendan said: OAS still requires to be provided with the right tnsnames.ora for your connections to work (if not using a full connection string).

    And in OAS, you can still have the normal connections details in the connection pool, just like you had in OBIEE. OAS didn't remove them.

    The Semantic Modeler is the one expecting you to create your connections as system connections in DV, but the Model Administration Tool has both options. And there are even command line tools to update the connection pool details, for when you deploy the RPD to a different server and need to update the connections (for example when moving from dev to prod, and having to update the connection pools to point to the prod data sources).