3 Create Services with Oracle Analytics Cloud
As Cloud Account Administrator, you can create and set up services in Oracle Analytics Cloud for your organization.
Typical Workflow to Create a Service
If you’re about to create an Oracle Analytics Cloud instance on Oracle Cloud Infrastructure in using Oracle Cloud Infrastructure Console for the first time, follow these tasks as a guide.
Task | Description | More Information |
---|---|---|
Before you start |
||
Activate your order and sign in to your Oracle Cloud account |
As the Cloud Account Administrator, you can complete all setup tasks for Oracle Analytics Cloud. |
|
Determine your service requirements |
Plan your Oracle Analytics Cloud deployment. Think about what you need before you start. |
|
(Optional) Enable other users to set up services |
If you don’t want to set up Oracle Analytics Cloud yourself, give other users permissions to create services. |
Give Another User Permission to Set Up Oracle Analytics Cloud |
(Recommended) Create a compartment for your service | Create a compartment for your Oracle Analytics Cloud deployment. | Create a Compartment |
Create the service | ||
Create a service |
Use Oracle Cloud Infrastructure Console to deploy a new service. |
|
Verify your service |
When your service is ready, check that you can sign in and your service is up and running. |
|
Complete the setup |
||
Set up users and groups |
Set up users and groups for Oracle Analytics Cloud and assign them to application roles. |
|
Set service-level options |
Configure service-level options for everyone using the service. |
|
Migrate content |
Leverage your existing content in Oracle Analytics Cloud. |
Before You Create a Service
Before you set up Oracle Analytics Cloud on Oracle Cloud Infrastructure using Oracle Cloud Infrastructure Console, Oracle recommends that you take some time to plan your service.
-
Give Another User Permission to Set Up Oracle Analytics Cloud (Optional)
-
Create a Compartment (Recommended)
Plan Your Service
Take some time to plan your Oracle Analytics Cloud service before you create it. Think about the questions outlined here and decide what you want to do, before you start.
Which Edition Do You Need?
When you set up a service you specify the edition you subscribe to and this determines which features are deployed.
Edition | Description |
---|---|
Professional Edition |
Enables you to deploy an instance with data visualization. |
Enterprise Edition |
Enables you to deploy an instance with enterprise modeling, reporting, and data visualization. |
For more information about the features available with each edition, see Editions: Enterprise and Professional .
Where Do You Want to Deploy Your Service?
Oracle Cloud Infrastructure (Gen 2) is hosted in several different geographic areas, called regions. When you sign up for Oracle Analytics Cloud, Oracle creates a tenancy for your company with access to one or more regions. If multiple regions are available to you, decide where you want to deploy your Oracle Analytics Cloud instance.
Note:
Do You Need a Public or Private Endpoint?
When you create an Oracle Analytics Cloud instance, you specify how you want to access your service: through a public internet accessible endpoint or a private endpoint.
After you've created Oracle Analytics Cloud, you can't switch from a public endpoint to a private endpoint (or the other way around). So it's important to decide what type of access your organization needs and complete the required prerequisites before you start. See Prerequisites for a Public Endpoint and Prerequisites for a Private Endpoint.
If you're not sure, see About Public Endpoints and Access Control Rules and About Private Endpoints.
What Sizing Options Are Available to You?
When you create an Oracle Analytics Cloud instance for your production or non-production environment, you either specify the number of Oracle Compute Units (OCPUs) you want to deploy or the number of people you expect to use the service.
- How Many OCPUs Do You Think You’ll Need?
- How Many People Do You Expect to Use the Service?
- What's the Difference Between Production and Non-Production Environments
How Many OCPUs Do You Think You’ll Need?
Oracle Analytics Cloud offers a range of compute sizes (OCPUs) to suit different scenarios and environments. The larger the compute size, the greater the processing power. If you're not sure which size to use, contact your sales team to discuss sizing guidelines.
The compute size you select also determines some configuration limits for the different types of content that users can create:
-
Data visualization projects
-
Classic analyses and dashboards
-
Classic pixel-perfect reports
For example, limits such as the maximum number of input rows you can return from a data source query or the maximum number of rows you can download from a report to a file (for example, when you export to a CSV file).
Limits Querying Data (Data Visualization Projects, Classic Analyses and Dashboards)
When you query a data source for data visualization projects or classic analyses and dashboards, the compute size determines the maximum number of rows that are returned from the data source.
Which compute size do you think you’ll need? | Limits when querying data for visualizations, analyses, and dashboards | |
---|---|---|
Max input rows returned from any data source query | Query timeout (seconds) | |
1 OCPU (non-production only) |
125,000 |
600 |
2 OCPU |
2,000,000 |
600 |
4 OCPU |
2,000,000 |
600 |
6 OCPU |
2,000,000 |
600 |
8 OCPU |
2,000,000 |
600 |
10 OCPU |
2,000,000 |
600 |
12 OCPU |
2,000,000 |
600 |
16 OCPU |
4,000,000 |
600 |
24 OCPU |
4,000,000 |
600 |
36 OCPU |
4,000,000 |
600 |
52 OCPU |
4,000,000 |
600 |
Limits Displaying Data (Data Visualization Projects, Classic Analyses and Dashboards)
When you display data in data visualization projects or classic analyses and dashboards, the compute size determines the maximum number of summarized rows returned from the data source that are displayed.
Which compute size do you think you’ll need? | Limits when displaying data in visualization projects, analyses, and dashboards |
---|---|
Max summarized rows returned from any data source query | |
1 OCPU (non-production only) |
125,000 |
2 OCPU |
500,000 |
4 OCPU |
500,000 |
6 OCPU |
500,000 |
8 OCPU |
500,000 |
10 OCPU |
500,000 |
12 OCPU |
500,000 |
16 OCPU |
1,000,000 |
24 OCPU |
1,000,000 |
36 OCPU |
1,000,000 |
52 OCPU |
1,000,000 |
Limits Exporting Data (Data Visualization Projects)
When you export data from a data visualization project, the compute size determines the maximum number of rows you can export to a CSV file.
Note:
Data exports are expensive operations and have a direct impact on the overall system performance. The impact on system performance increases with the number of rows and columns that you export. Oracle recommends that you export large amounts of data during non-peak hours to reduce any performance impact.Which compute size do you think you’ll need? | Limits when exporting data from data visualizations projects |
---|---|
Maximum number of rows to CSV | |
1 OCPU (non-production only) |
125,000 |
2 OCPU |
2,000,000 |
4 OCPU |
2,000,000 |
6 OCPU |
2,000,000 |
8 OCPU |
2,000,000 |
10 OCPU |
2,000,000 |
12 OCPU |
2,000,000 |
16 OCPU |
4,000,000 |
24 OCPU |
4,000,000 |
36 OCPU |
4,000,000 |
52 OCPU |
4,000,000 |
Limits Exporting Data (Classic Analyses and Dashboards)
When you export data from analyses and dashboards, the compute size determines the maximum number of rows you can export. There are different limits for formatted reports and unformatted reports.
-
Unformatted report limits: formats such as CSV, Excel, XML, and Tab Delimited.
-
Formatted report limits: formats such as PDF, Excel, Powerpoint, and Web Archive/HTML.
When two pivot views are laid out side by side in a union the formatted export limit will be 20,000 rows.
Note:
Data exports are expensive operations and have a direct impact on the overall system performance. The impact on system performance increases with the number of rows and columns that you export and the output format. Oracle recommends that you export large amounts of data during non-peak hours or export unformatted data to reduce any performance impact.Which compute size do you think you’ll need? | Limits when exporting data from analyses and dashboards | |
---|---|---|
Max rows exported to unformatted reports | Max rows exported to formatted reports | |
1 OCPU (non-production only) |
125,000 |
1,000 |
2 OCPU |
2,000,000 |
200,000 |
4 OCPU |
2,000,000 |
200,000 |
6 OCPU |
2,000,000 |
200,000 |
8 OCPU |
2,000,000 |
200,000 |
10 OCPU |
2,000,000 |
200,000 |
12 OCPU |
2,000,000 |
200,000 |
16 OCPU |
4,000,000 |
400,000 |
24 OCPU |
4,000,000 |
400,000 |
36 OCPU |
4,000,000 |
400,000 |
52 OCPU |
4,000,000 |
400,000 |
Limits Delivering by Email (Classic Analyses and Dashboards)
When you send analyses and dashboards by email, the compute size determines the maximum number of rows you can deliver in a single email. There are different limits for delivering formatted reports and unformatted reports.
-
Unformatted report limits: formats such as CSV, Excel, XML, and Tab Delimited.
-
Formatted report limits: formats such as PDF, Excel, Powerpoint, and Web Archive/HTML.
Note:
Content delivery by email is an expensive operation and has a direct impact on the overall system performance. The impact on system performance increases with the number of recipients, the number of rows and columns that you send, and the delivery format. Oracle recommends that you schedule deliveries during non-peak hours or change the delivery format to reduce any performance impact.Which compute size do you think you’ll need? | Limits when delivering analyses and dashboards by email | |
---|---|---|
Max rows in unformatted reports delivered by email | Max rows in formatted reports delivered by email | |
1 OCPU (non-production only) |
2,000 |
1,000 |
2 OCPU |
200,000 |
50,000 |
4 OCPU |
200,000 |
50,000 |
6 OCPU |
200,000 |
50,000 |
8 OCPU |
200,000 |
50,000 |
10 OCPU |
200,000 |
50,000 |
12 OCPU |
200,000 |
50,000 |
16 OCPU |
300,000 |
100,000 |
24 OCPU |
300,000 |
100,000 |
36 OCPU |
300,000 |
100,000 |
52 OCPU |
300,000 |
100,000 |
Data Size Limits (Classic Pixel-Perfect Reports)
The compute size determines several limits associated with generating reports.
Which compute size do you think you’ll need? | Report data size limits when generating pixel-perfect reports | |||
---|---|---|---|---|
Max data size for online reports | Max data size for offline (scheduled) reports | Max data size for bursting reports | Max data size for data generation | |
1 OCPU (non-production only) |
200MB |
500MB |
2GB |
500MB |
2 OCPU |
500MB |
2GB |
4GB |
2GB |
4 OCPU |
500MB |
2GB |
4GB |
2GB |
6 OCPU |
500MB |
2GB |
4GB |
2GB |
8 OCPU |
500MB |
2GB |
4GB |
2GB |
10 OCPU |
500MB |
2GB |
4GB |
2GB |
12 OCPU |
500MB |
2GB |
4GB |
2GB |
16 OCPU |
500MB |
4GB |
8GB |
4GB |
24 OCPU |
500MB |
4GB |
8GB |
4GB |
36 OCPU |
500MB |
4GB |
8GB |
4GB |
52 OCPU |
500MB |
4GB |
8GB |
4GB |
Processing Limits (Classic Pixel-Perfect Reports)
The compute size determines several limits associated with processing reports.
Which compute size do you think you’ll need? | Data model and report processing limits when generating pixel-perfect reports | ||||
---|---|---|---|---|---|
SQL Query timeout for scheduled reports (seconds) | Max rows for CSV output | Max number of in-memory rows in XPT layout | Max number of concurrent scheduled jobs | Max number of concurrent online reports | |
1 OCPU (non-production only) |
1,800 |
1,000,000 |
100,000 |
1 |
2 |
2 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
16 |
4 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
32 |
6 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
48 |
8 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
64 |
10 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
80 |
12 OCPU |
1,800 |
4,000,000 |
200,000 |
4 |
96 |
16 OCPU |
3,600 |
6,000,000 |
300,000 |
10 |
320 |
24 OCPU |
3,600 |
6,000,000 |
300,000 |
10 |
480 |
36 OCPU |
3,600 |
6,000,000 |
300,000 |
10 |
720 |
52 OCPU |
3,600 |
6,000,000 |
300,000 |
10 |
1040 |
How Many People Do You Expect to Use the Service?
With Oracle Analytics Cloud, you can opt to specify how many people you expect to use the service. Typically, services have between 10 and 3000 users.
Configuration limits are equivalent to those available with 4 OCPUs. For example, the maximum number of input rows you can return from any data source query is 2,000,000 rows, the maximum number of rows you can export to a formatted report (such as PDF) is 200, 000 rows, and so on.
What's the Difference Between Production and Non-Production Environments
-
Non-production environment: Oracle enables you to deploy a non-production environment with 1 OCPU. A non-production environment is specifically sized and designed for test, development and training purposes. Non-production services aren't intended for daily use, multiple concurrent users, or complex business scenarios.
You can't scale up a non-production environment (with 1 OCPU). If you want to keep the content that you create during testing, you can save it to a snapshot and copy it to a production service (minimum 2 OCPU or 10 users). See Migrate Oracle Analytics Cloud Using Snapshots.
-
Production environment: A production environment is designed for daily commercial use. You can scale some production environments up and down. For example, you can scale between 2 - 8 OCPUs and 10 - 12 OCPUs. You can also scale between various user ranges such as 10 - 400 users and 401 - 601 users. See About Scaling.
What Name Do You Want for Your Service?
Think about a suitable name for your service. The name that you specify is displayed in Oracle Cloud Infrastructure Console and the URL for your service.
Name restrictions:
-
Must contain between 1 and 25 characters.
-
Must start with an ASCII letter: a to z or A to Z.
-
Must contain only ASCII letters or numbers.
-
Mustn't contain any other special characters.
-
Must be unique within the identity domain.
Give Another User Permission to Set Up Oracle Analytics Cloud
When you activate your order for Oracle
Analytics Cloud, you get the Cloud Account Administrator role. This role gives you full
administration privileges in Oracle Cloud
Infrastructure so you can complete all aspects of Oracle
Analytics Cloud setup and much more. There’s no need to delegate this responsibility but, if you want to,
you can give someone else privileges to create and manage Oracle
Analytics Cloud instances through the manage analytics-instances
permission.
manage
analytics-instances
permission on a specific compartment or the tenancy
(any compartment in the tenancy). For example, you might create a policy statement that
looks like one of these:
-
allow group MyAdminGroup to manage analytics-instances in tenancy
-
allow group MyAdminGroup to manage analytics-instances in compartment MyOracleAnalytics
Create a Compartment
When you sign up for Oracle Cloud Infrastructure, Oracle creates your tenancy with a root compartment that holds all your cloud resources. You then create additional compartments within the tenancy (root compartment) and corresponding policies to control access to the resources in each compartment. Before you create an Oracle Analytics Cloud instance, Oracle recommends that you set up the compartment where you want the instance to belong.
You create compartments in Oracle Cloud Infrastructure Identity and Access Management (IAM). See Setting Up Your Tenancy and Managing Compartments.
Create a Service
You can create an Oracle Analytics Cloud instance using the Console, API, or command line.
Note:
Required IAM Policy
Verb: manage
Resource Type:
analytics-instance
,
analytics-instances
Custom Permission:
ANALYTICS_INSTANCE_CREATE
See About Permissions to Manage Oracle Analytics Cloud Instances.
Additional IAM Policy Required to Create a Public Endpoint
Verb: read
Resource Type:
virtual-network-family
,
compartment
,
compartments
See Prerequisites for a Public Endpoint.
Additional IAM Policy Required to Create a Private Endpoint
Verb: manage
Resource Type:
virtual-network-family
Verb: read
Resource Type: compartment
,
compartments
Required only for network security groups:
Verb: use
Resource Type:
network-security-groups
To learn about other, more detailed access policy options, see Prerequisites for a Private Endpoint.
Create a Service using the Console
You can use Oracle Cloud Infrastructure Console to set up a service instance with Oracle Analytics Cloud.
You must belong to an OCI group that is granted the required policies to create an Analytics instance. See Give Users Permissions to Manage Analytics Cloud Instances.
Create a Service using the REST API
You can use the CreateAnalyticsInstance
operation to
set up a service instance with Oracle
Analytics Cloud.
Refer to the Oracle Cloud Infrastructure REST API Reference for information about how to use this operation:
After You Create a Service
After creating and verifying a service with Oracle Analytics Cloud, you must set up your users and configure additional options for your service. If you’re migrating to Oracle Analytics Cloud from on-premises or another cloud service you might want to migrate your existing content now.
Verify Your Service and Sign In
Oracle sends an email to the designated email address when your Oracle Analytics Cloud service is ready. Navigate to your service in Oracle Cloud Infrastructure Console, click the Analytics Home Page button, and then sign in to verify your Oracle Analytics Cloud service is up and running.
Note:
Required IAM Policy
Verb: read
Resource Types: analytics-instance
,
analytics-instances
Permission: ANALYTICS_INSTANCE_READ
See About Permissions to Manage Oracle Analytics Cloud Instances.
Configure Options for Your Service
Administrators perform many critical duties; they control user permissions and amend accounts, set up database connections for data modelers, manage data storage to avoid exceeding storage limits, take regular snapshots so users don't risk losing their work, authorize access to external content by registering safe domains, troubleshoot user queries, and much more. After setting up a service with Oracle Analytics Cloud, you can review typical administrator tasks for your service.
See Administrator Task List in Configuring Oracle Analytics Cloud.
Migrate to Oracle Analytics Cloud from Other Environments
Do you have content in an existing on-premise system or another cloud service that you want to leverage in Oracle Analytics Cloud? After setting up your service, you can migrate the content to the new environment.
Migrate From... | More Information |
---|---|
Other Oracle Analytics Cloud deployments on Oracle Cloud Infrastructure |
|
Oracle Analytics Cloud - Classic deployed on Oracle Cloud Infrastructure Classic |
Migrating Oracle Analytics Cloud - Classic Instances to Oracle Cloud Infrastructure |
Oracle BI Cloud Service |
Migrating Oracle Business Intelligence Cloud Service Instances to Oracle Cloud Infrastructure |
Oracle Data Visualization Cloud Service |
Migrating Oracle Data Visualization Cloud Service Instances to Oracle Cloud Infrastructure |
Oracle Analytics Server |
In Oracle Analytics Server: Take a Snapshot and Export the Snapshot In Oracle Analytics Cloud: Import the Snapshot and Restore from the Snapshot |
Oracle BI Enterprise Edition |
Migrating Oracle Business Intelligence Enterprise Edition to Oracle Analytics Cloud |