Friday, November 17, 2017

OAC - PBCS Connectivity

I am not one to re-post Oracle Documentation or Oracle Readme's and pretend to make it my own.  My intent for any of my blog posts is to extend the information provided or provide clarity.

The OAC 17.3.5 (August 2017) release extended connectivity to PBCS / EPBCS.

The configuration / setup instructions can be found here.  OAC PaaS Docs

If you need to see pictures of this process you can do internet search for other blog posts that another person produced.

I followed each of these and when I attempted to connect and import metadata I received the following:


the NQSAdminTool.log file was not too helpful


However, I got to thinking; for the connectivity to Essbase Cloud I needed to open up ports on my Cloud Compute.  I checked with my contact within my contact within Product Development and this was confirmed.

So after logging into myCloudService and switching to the Compute Console / Network





I created a new Security Application with connectivity on port 9506


 

Next, I created a Security Rule with the Destination ANALYTICS/instance/ora_bi_infraadmin


Then back to my OAC Client Admin tool.  I provided all the necessary connection information and Voila!  I am able to import my EPBCS cubes into my RPD.


 Until next time!




Monday, November 13, 2017

UPDATE: OAC - Import Essbase Cloud to OAC-BI Admin Tool


In my post OAC - Import Essbase Cloud to OAC-BI Admin Tool

I shared that the Essbase 11.1.2.3.500 Database Type does not work for importing Essbase metadata and that you needed to use the Essbase 9 type the switch back to Essbase 11.1.2.3.500 in order to pass the consistency check.

Well I opened an SR and was told that this fixed in the OAC 17.4.1 patch and related BI Admin Tool.  

So I have updated my Database Type in my Essbase Connection


And when I attempted to import metadata I still get the error.
 

Since i am in the test mode I figured I would see if the Essbase 11 database type worked.
 

 And... low and behold it does.


Now I no longer need to switch the Database Type to 9 then to 11.1.2.3.500 each time I need to import metadata.  And I can leave the Database Type set to Essbase 11 and it will pass consistency check.

Until next time.

Friday, November 3, 2017

OAC - Service Console

I recently ran into an issue where in our OAC instance we move our DBaaS to a different cloud instance and thereby it was assigned a new IP address.  Unfortunately the RPD Connection Pool was not updated.  Our RPD has a number of Session Variables that when we attempted to sign on to our OAC instance all we saw was the following:



It took a while to figure out what was going on and it was only after I looked at the diagnostic logs for the BI Server that I found that my connection was blacklisted.


/bi/domain/fmw/user_projects/domains/bi/servers/obis1/logs


Now came the hard part.  How do I sign into OAC and access the Console interface where I can Replace the Data Model with a new RPD?

Fortunately there is an administration interface that can be accessed that does not link to BIServer.  This interface is the Business Intelligence Cloud Service - Service Console


This Service Console allowed me access to the Snapshots
 


Access to this Service Console is via the following URL:

https://server:port/biserviceadministration


With access to this screen I was able to replace the RPD with a corrected connection string and was able to successfully log in to my OAC instance.

Hopefully this URL will save many hours of frustration.