2 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 a service with Oracle Analytics Cloud 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 Cloud Account Administrator, you can complete all setup tasks for Oracle Analytics Cloud. |
|
(Optional) Enable other users to create Oracle Analytics Cloud 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 |
Decide on your service requirements |
Plan your Oracle Analytics Cloud service. Think about what you want before you start. |
|
Create the service | ||
Create a service |
Deploy a new service with one or more Oracle Analytics Cloud components. |
Create a Trial Service with a Single Click |
Complete the setup |
Verify that your service is up and running and that you can sign in. |
|
After creating your service |
|
|
Manage users |
Set up users for Oracle Analytics Cloud in Oracle Identity Cloud Service and assign roles to them. |
|
Configure more options for your service |
Configure service-level options for everyone using your service. The options available depend on the features that you chose to deploy.
|
|
Migrate content |
Leverage your existing content in Oracle Analytics Cloud. |
Before You Create a Service
Before you set up Oracle Analytics Cloud, Oracle recommends that you take some time to plan your service.
Give Another User Permission to Set Up Oracle Analytics Cloud
When you activate your Oracle Analytics Cloud order you get the Cloud Account Administrator role. This role gives you full administration privileges on the cloud account so you can complete all aspects of Oracle Analytics Cloud setup. There’s no need to delegate this responsibility but, if you want someone else to set up Oracle Analytics Cloud or Oracle Analytics Cloud Subscription, you can add more users and assign them to the required roles.
Required Service | Administrator Role | Required to... |
---|---|---|
Oracle Analytics Cloud | AUTONOMOUS_ANALYTICS_ServiceAdminstrator | Create and manage services with Oracle Analytics Cloud. |
Oracle Analytics Cloud Subscription | ANALYTICSSUB_ServiceAdministrator | Create and manage services with Oracle Analytics Cloud Subscription. |
Oracle Identity Cloud Service | Identity Domain Administrator | Add new users and manage roles. |
The user you just added receives an email inviting them to activate their account and provide a password. When they sign in to their Oracle Cloud account they have all the required permissions to set up Oracle Analytics Cloud.
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.
-
Edition: Which edition do you want to use?
-
Region: Where do you want to deploy your service?
- Deployment Size: What sizing options are available to you?
-
Size by Number of OCPUs: How many OCPUs do you think you’ll need?
-
Size by Number of Users: How many people do you expect to use the service?
-
-
Service Name: What name do you want for your service?
Which edition do you want to use?
The editions available to you depend on how you subscribe to Oracle Analytics Cloud or Oracle Analytics Cloud Subscription. You need Enterprise Edition if you want to offer Business Intelligence (enterprise modeling and reporting features).
Edition | Oracle Analytics Cloud | Oracle Analytics Cloud Subscription |
---|---|---|
Professional |
Data Visualization |
Data Visualization |
EssbaseFoot 1. |
Essbase |
Essbase |
Enterprise |
EssbaseFoot 2 Business Intelligence |
Business Intelligence (with Data Visualization) |
Footnote 1 Essbase Edition isn't available in Oracle Cloud accounts created after 12th December 2019
Footnote 2 Essbase deployments aren't available Oracle Cloud accounts created after 12th December 2019.
If you need more help to decide, see Professional and Enterprise Editions in Getting Started with Oracle Analytics Cloud
Note:
Oracle Analytics Cloud – Essbase Edition isn't available in Oracle Cloud accounts created after 12th December 2019. Instead, Oracle Essbase is available on Oracle Cloud Marketplace. See: https://docs.oracle.com/en/database/other-databases/essbase/index.html
Any Oracle Cloud account created before 12th December 2019 that includes Oracle Analytics Cloud – Essbase Edition, remains unchanged.
Where do you want to deploy your service?
Oracle Cloud Infrastructure is hosted in several different geographic areas, called regions. If multiple regions are available to you, decide where you want to deploy Oracle Analytics Cloud. This Guide describes how to deploy and manage Oracle Analytics Cloud on Oracle Cloud Infrastructure data regions in:
- North America, such as Ashburn, Phoenix, and Toronto (only Oracle Cloud accounts created before 14th February 2020).
- EMEA, such as London and Frankfurt (only Oracle Cloud accounts created before 2nd March 2020).
Note:
The way you deploy and manage Oracle Analytics Cloud depends on the region, type, and start date of your subscription. If your subscription gives you access to a region in Asia-Pacific (APAC) or Latin America (LAD), or you have access to a region in North America through an Oracle Cloud account created after 14th February 2020, or you have access to a region in EMEA through an Oracle Cloud account created after 2nd March 2020, the deployment process is different. See Administering Oracle Analytics Cloud on Oracle Cloud Infrastructure (Gen 2).
What sizing options are available to you?
Oracle offers two deployment options on Oracle Cloud Infrastructure: Oracle Analytics Cloud and Oracle Analytics Cloud Subscription. The main difference between these two options is the way you subscribe (how you're billed) and how you determine the size of your service.
If you subscribe to Oracle Analytics Cloud, you specify the number of Oracle Compute Units (OCPUs) you want to deploy. If you subscribe to Oracle Analytics Cloud Subscription, you either specify how many people you expect to use the service or the number of OCPUs.
Size Options | Oracle Analytics Cloud | Oracle Analytics Cloud Subscription |
---|---|---|
Number of OCPUs |
Yes |
Yes |
Number of Users |
- |
Yes |
How Many OCPUs Do You Think You’ll Need for Business Intelligence and Data Visualization?
Oracle Analytics Cloud offers a range of compute sizes (OCPUs) to suit different scenarios. 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 visualizations
-
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 Visualizations, Classic Analyses and Dashboards)
When you query a data source for data visualizations 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 | |
1 OCPU (trials 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 Displaying Data (Data Visualization, Classic Analyses and Dashboards)
When you display data in data visualizations 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 visualizations, analyses, and dashboards |
---|---|
Max summarized rows returned from any data source query | |
1 OCPU (trials 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 Visualizations)
When you export data from a data visualizations, the compute size determines the maximum number of rows you can export to a CSV file.
Which compute size do you think you’ll need? | Limits when exporting data from data visualizations to CSV file |
---|---|
1 OCPU (trials 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 data and unformatted data.
-
Unformatted data limits: formats such as CSV, Excel, XML, and Tab Delimited.
-
Formatted data limits: formats such as PDF, Excel, Powerpoint, and Web Archive/HTML.
Note: When two pivot views are laid out side by side in a union the formatted export limit will be 20,000 rows.
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 (trials 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)
If you plan to 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 data and unformatted data.
-
Unformatted data limits: formats such as CSV, Excel, XML, and Tab Delimited.
-
Formatted data limits: formats such as PDF, Excel, Powerpoint, and Web Archive/HTML.
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 (trials 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)
If you plan to generate pixel-perfect reports, the compute size determines several limits associated with report generation.
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 (trials 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)
If you plan to generate pixel-perfect reports, the compute size determines several limits associated with report processing.
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 (trials 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 |
46 |
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 OCPUs do you think you’ll need for Essbase?
Note:
Oracle Analytics Cloud – Essbase Edition isn't available in Oracle Cloud accounts created after 12th December 2019. Instead, Oracle Essbase is available on Oracle Cloud Marketplace. See: https://docs.oracle.com/en/database/other-databases/essbase/index.html
Any Oracle Cloud account created before 12th December 2019 that includes Oracle Analytics Cloud – Essbase Edition, remains unchanged.
Oracle Analytics Cloud offers a range of compute sizes (OCPUs) to suit different scenarios. 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.
Essbase can be Oracle Compute Unit (OCPU) intensive depending on your application. If you're planning a deployment with Essbase, the minimum number of OCPUs recommended for production deployments is 4 OCPUs, and the maximum is 52 OCPUs. To help you decide which compute size best suits your deployment, consider how many active users you expect to perform concurrent activities such as:
- Hybrid Block Storage (BSO) application type users running queries
- BSO users running calculations
- Aggregation Storage (ASO) users running reports or queries
Essbase provides you with standard storage for all compute sizes. Work with your sales team to verify that your storage requirements are met, based on the number of applications that you plan to deploy.
Which compute size do you think you’ll need? | Considerations |
---|---|
|
Not supported. |
|
Suitable only for trials or development services for outline design.
Not recommended for production deployments because this compute size isn't enough to support concurrent operations. |
|
4 - 52 OCPUs suitable for production deployments. 32 - 52 OCPUs available only in the Phoenix region. These larger sizes are dependent upon available capacity. Consult with Oracle Support if you have deployment issues. |
How many people do you expect to use the service?
With Oracle Analytics Cloud Subscription, you can opt to specify how many people you expect to use the service. Typically, services have between 10 and 3000 users.
-
Business Intelligence or Data Visualization
Configuration limits are equivalent to those available with 4 OCPUs. For example, the maximum number of 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.
-
Essbase
If you're planning a deployment with Essbase, consider:
- Number of users concurrently accessing the service
- Number of applications running on the service
- Hybrid Block Storage (BSO) users running queries
- BSO users running calculations
- Aggregation Storage (ASO) users running reports or queries
Work with your sales team to verify that your requirements are met, based on the number of users that you plan to deploy.
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.
Create Services
When you create a service with Oracle Analytics Cloud you can choose which compute shape and features you want to deploy. When you create a service with Oracle Analytics Cloud Subscription, you can either specify how many people you expect to use the service or the compute shape size you want to deploy. The options available to you depend on which product and edition you're subscribed to. If you're new to Oracle Analytics Cloud, you can set up a trial service using the QuickStart option.
Note:
The topics in this section apply if your Oracle Cloud account started before Oracle Analytics Cloud became available on Oracle Cloud Infrastructure Gen 2 in North America (14th February 2020) and EMEA (2nd March 2020).
If your Oracle Cloud account gives you access to regions in Asia-Pacific, Latin America, North America (after 14th February 2020), or EMEA (after 2nd March 2020) you deploy and manage Oracle Analytics Cloud on Oracle Cloud Infrastructure Gen 2. The deployment process is different on Oracle Cloud Infrastructure Gen 2. See Administering Oracle Analytics Cloud on Oracle Cloud Infrastructure (Gen 2).
Create a Trial Service with a Single Click
QuickStart instances offer a quick and easy way to trial Oracle Cloud services. You can create a QuickStart instance of Oracle Analytics Cloud with a single click.
It takes about 20 minutes to create the service. Oracle sends you an email when your service is ready. Go to the Activity page if you want to check the current status.
Create a Service with Oracle Analytics Cloud
Only follow the steps in this topic if you subscribe to Oracle Analytics Cloud through Universal Credits and your subscription started before Oracle Analytics Cloud became available on Oracle Cloud Infrastructure Gen 2 in North America (14th February 2020) and EMEA (2nd March 2020).
Note:
After 14th February 2020 (North America) or 2nd March 2020 (EMEA) you deploy Oracle Analytics Cloud on Oracle Cloud Infrastructure Gen 2. The deployment process is different on Oracle Cloud Infrastructure Gen 2. See Administering Oracle Analytics Cloud on Oracle Cloud Infrastructure (Gen 2).
Description of the illustration activity-page.jpg
Create a Service with Oracle Analytics Cloud Subscription
You use Oracle Cloud Infrastructure Console to set up a service with Oracle Analytics Cloud Subscription. Follow these steps if you have a non-metered subscription.
Description of the illustration activity-page_sub.jpg
After You Create a Service
After creating a service with Oracle Analytics Cloud, you must set up your users and configure 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, obtain the service URL, and then sign in to verify your Oracle Analytics Cloud service is up and running.