Configuring Oracle Analytics Cloud (OAC)

Oracle Analytics Cloud (OAC) provides a complete analytics solution with capabilities from Oracle’s traditional business intelligence (BI) offerings such as OBIEE 12c, Essbase, and Data Visualization.  Key features of the OAC Platform-as-a-Service (PAAS) solution include:

  1. Extensive service management capabilities to create instances; scale out services to meet demand; start and stop services; use APIs and client tools; and manage all aspects of development lifecycle operations.

  2. SSH connectivity to the server to access log files and configuration files, or to monitor any aspect of the environment.

  3. Easily scalable to boost the system capacity (CPU or memory) to support adding users when the workload demands it.

Services in Oracle Analytics Cloud

In order to run all of the OAC services in the cloud, it is necessary to also purchase additional cloud services for the database, storage and backup service, and a compute engine. OAC’s main services include:

Oracle Business Intelligence Cloud Service (BICS). One of Oracle’s proven solutions in the cloud which can be used to build dashboards and analyses based on a common metadata model.  The metadata model can be configured using either the traditional on premise OBIEE admin tool with “lift-and-shift” to the cloud or can be modified using a web-based simplified modeling tool.

Oracle Data Visualization Cloud Service (DVCS)Helps in self-service visualizations that empowers the business users to convert raw data to meaningful business insights. It eliminates the need for IT to blend data and to build visualizations. You can also combine data from a variety of sources such as Oracle and other SaaS applications, on-premises systems, external sources and personal files.

With PAC, the above two services are combined with the Essbase Cloud Service (EssCS). EssCS lets you build OLAP cubes quickly and efficiently and offers improved performance and advanced modeling capabilities.  EssCS retains most of the on-premise features of Essbase.

Configuration Steps for OAC

The configuration steps outlined below are based on OAC Version 17.2.3.

  1. Create Cloud Storage. Before creating an OAC service, an “Oracle Cloud Storage” container needs to be created. This container is used for storing backups, provisioning log files, etc. Creating a container is as simple as providing a name for it; for example, “OAC” in the examples that follow. This storage container will later be referenced in the OAC service creation steps.

  1. Create Cloud Database Service. The database configuration step is similar to configuring an on-premise database. Remember, with OAC you don’t need to download and install any software, you just configure a database instance.

To configure the database service, specify the below mandatory parameters:

  1. Service Name. The name of the database service.

  2. Service Level. Two service levels are available:

  3. Oracle Database Cloud Service (DBaaS). With this option, you configure the database and follow additional steps for backup, recovery and patching.

  4. Oracle Database Cloud Service (DBCS). With this option, you configure the database and no additional steps are required for backup, recovery and patching.

Metering Frequency – This defines how the service will be charged. Two options are available: Monthly or Hourly.

Software Release – Oracle DB software release available are 11.2, 12.1 and 12.2.

Software Edition – This includes below options, choose as needed.

  1. Standard Edition

  2. Enterprise Edition

  3. Enterprise Edition – High Performance

  4. Enterprise Edition – Extreme Performance

Database Type – This option is primarily used in case of Production environments for high availability and disaster recovery options. Below are the options available:

  1. Single Instance

  2. Database Clustering with RAC

  3. Single Instance with Data Guard Standby

  4. Database Clustering with RAC and Data Gard Standby

After clicking next, in the second section specify all the service details.

In the database configuration section highlighted above, specify the name of the database, the container database if the chosen software release was 12c and the password.

Usable Database Storage – This is the amount of space required for the OS, DB software, temp files etc. In an actual scenario an instance can utilize more space than what is mentioned here.

Compute Shape – This specifies the capacity of the VM. Multiple combinations of OCPUs and RAM are available. Choose based on your own requirements. Note: This can be altered in future.   A higher combination of OCPUs and Memory will result in a more powerful environment – but it is important to remember that OAC service costs will be based on the number of OCPUs and memory, so be careful to not over configure the environment.