This reference provides answers to common questions asked by administrators creating and managing services for Oracle Analytics Cloud - Classic.
Top FAQs for Administration and Configuration
The top FAQs for Oracle Analytics Cloud - Classic administration and configuration are identified in this topic.
What do I use the Oracle Cloud Infrastructure Console for? Is this the same as the Console I see in the service?
Oracle Cloud Infrastructure Console — You use the Oracle Cloud Infrastructure Console to manage lifecycle tasks such as create, delete, patch, and scale services.
To access the Oracle Analytics Cloud Classic page in Oracle Cloud Infrastructure Console, sign in to your Cloud Account, click Navigation menu icon in the top left corner, under More Oracle Cloud Services, go to Platform Services, and click Analytics Classic.
Console — When you sign in to a particular service, you see a different administrative console where you manage the environment for that service only.
To access the Console for a service, sign in to the service, open the Navigator, and then click Console.
What is an OCPU?
An OCPU provides CPU capacity equivalent of one physical core of an Intel Xeon processor with hyper-threading enabled. Each OCPU corresponds to two hardware execution threads, known as vCPU.
How can I determine the right compute size for my initial deployment?
A good starting point is to pick a size that closely matches your on-premises hardware for business intelligence.
For more sizing guidelines, see http://support.oracle.com.
How do I access my service once it is created?
It’s accessible from Oracle Cloud Infrastructure Console. Navigate to the Oracle Analytics Cloud - Classic page and click the name of the service you want to access. Click the Manage this service menu, and then click Oracle Analytics Cloud URL.
How do I patch or upgrade my service?
You can patch or upgrade your service from Oracle Cloud Infrastructure Console.
Do I need to patch the service on a specific schedule?
No. Functional and critical security enhancements are delivered through patches. You can apply these patches within your organization’s preferred schedule.
Can I manually update software packages running in my service instance?
Analytics Cloud is based on an Oracle Linux image. You must update the packages that are already installed using the
yum update command. If you want to make any other custom changes to the image, log a service request with Oracle Support to check supportability.
You don't have to log a service request to run any of the approved scripts available under
I want to connect to the database where my organization’s analytics data is stored? Do I do this from the Oracle Cloud Infrastructure Console?
No. You connect to the data you want to analyze within a given service that you created. See How do I access my service once it is created?.
What network options can I use to manage access into and out from my service?
By default, you access Oracle Analytics Cloud - Classic through public IPs. If you want to use private IPs, you can configure an IP network and VPN as a Service (VPNaaS). See Deploy Oracle Analytics Cloud on an IP Network and Using Oracle Cloud Infrastructure Compute Classic.
How do I configure VPN connectivity for my service to my network?
VPN is a separate feature from your service and is available to use with some Oracle Cloud services. Contact your Oracle representative for more information.
Is IPv6 supported?
No, not currently.
How do I get support for Oracle Analytics Cloud?
You create a service request in the same way as for on-premises software.
Is there a charge for Oracle Support in addition to my subscription fee?
No. Support is included in your subscription fee.
Do I have direct access to the file system associated with my service?
Yes. You can use the SSH keys, generated at the time of provisioning, to access your service’s file system. However, modifications that you make to the file system might not be saved after you perform routine lifecycle operations, such as patching, and might even prevent you from performing lifecycle operations.
My service currently uses the embedded LDAP server for identity management. What’s the maximum number of users?
The performance of the embedded LDAP server is best with fewer than 10,000 users. If you have more users, use Oracle Identity Cloud Service. See Migrate LDAP-Based Services to Oracle Identity Cloud Service.
What do I need to back up?
To ensure you can restore Oracle Analytics Cloud - Classic if something goes wrong, you must back up your service and the database associated with your service. If you deployed Oracle Analytics Cloud - Classic with the data visualization or business intelligence service, then you can also back up the content that users create.
Oracle Analytics Cloud - Classic user content: (data visualization and business intelligence services only) You can back up the content that users create to a separate file, called a snapshot. User content includes data models and catalog items such as reports, dashboards, data visualization projects, data sets, data flows, security roles, service settings, and more. If something goes wrong with your content or service, then you can revert to the content you saved in a snapshot. Snapshots are also useful if you want to move or share content from one service to another.
To back up user content, see Take a Snapshot.
To restore user content, see Restore from a Snapshot.
Note:For Essbase services, you back up the entire service; you can't back up only the content.
Oracle Database Classic Cloud Service: Oracle Analytics Cloud - Classic stores various schemas and information in a cloud database that you select when you set up . You can back up this database from Oracle Cloud Infrastructure Console.
To back up the database instance, see Create an On-Demand Backup.
To schedule a database instance backup, see Disable and Re-enable Scheduled Backups.
What can I use the various backups for?
Oracle Analytics Cloud - Classic service backup: Use to recover your service if the virtual machine crashes or your service is corrupted.
Oracle Analytics Cloud - Classic user content snapshot: Use to revert to a prior snapshot that you may have taken as a checkpoint. You can also use snapshots to migrate user content from one Oracle Analytics Cloud - Classic service to another.
Oracle Database Classic Cloud Service backup: Use to recover from a database failure or crash. If the database is entirely dedicated to a single Oracle Analytics Cloud - Classic service, then you can use this backup to recover the content users create in that service.
How often should I back up?
Oracle Analytics Cloud - Classic service backup: Schedule weekly full backups and daily incremental backups. In addition, take a full, on-demand backup before you patch your service or before you make any significant changes to your service, for example, if you scale up, scale down, and add storage.
Oracle Analytics Cloud - Classic user content snapshot: Take snapshots before making major changes to your content. You can take regular weekly snapshots or at your defined frequency based on the rate of change of the business intelligence environment and rollback requirements.
Oracle Database Classic Cloud Service backup: Schedule weekly full backups and daily incremental backups. In addition, take a full backup before you patch.
How do I find the version of a service instance backup?
In Oracle Cloud Infrastructure Console, backups are listed by the timestamp when the backup was created. If you compare the timestamp of a particular backup with your service’s patch history, you can determine the version of the service in that backup.
For example, you create a service on 4/14/2018 with Oracle Analytics Cloud - Classic version 18.2.1 and take backups on 4/16/2018 and 4/18/2018. On 5/14/2018, you apply patch version 18.2.3 and take a backup on 5/16/2018. In this case, backups taken on 4/16/2018 and 4/18/2018 are from service version 18.2.1, whereas the backup taken on 5/16/2018 is from service version 18.2.3.
Do I need to back up and restore the actual data associated with my data sets separately?
If you import a snapshot to a different environment, then you must upload or import the data from data sets again after restoring from a backup.
Where are backups stored?
Backups for Oracle Analytics Cloud - Classic and Oracle Database Classic Cloud Service are stored on Oracle Cloud Infrastructure Object Storage, in two, separate storage containers.
Oracle Analytics Cloud - Classic service backups: When you create a service with Oracle Analytics Cloud, you select the container you want to use for backups.
Oracle Analytics Cloud - Classic user content snapshots: Snapshots are stored in the same container as your Oracle Analytics Cloud - Classic service backups.
Oracle Database Classic Cloud Service backups: When you create a database with Oracle Database Classic Cloud Service, you select the container you want to use for backups. You can’t store database backups in the same container as you store the Oracle Analytics Cloud - Classic service backups.
Can I use my database backup to restore user content instead of my Oracle Analytics Cloud - Classic snapshot?
Yes, but only if the database is dedicated to a single Oracle Analytics Cloud - Classic service. If you share the database across multiple services or use the database to store other data, you must use snapshots to recover user content for individual services.
Before you restore from a database backup, verify that the version of Oracle Analytics Cloud - Classic you’re currently using and the version in the backup are the same.
Is there a specific order that I must follow while restoring?
In the unlikely event you need to restore everything, restore the database first, and then restore Oracle Analytics Cloud - Classic. If you have user content that you must restore from a snapshot, then restore that content last.
Does the same version of Oracle Analytics Cloud - Classic run on Oracle Cloud and Oracle Cloud at Customer?
No. Oracle Analytics Cloud - Classic is available to select Oracle Cloud at Customer users. The version of Oracle Analytics Cloud - Classic available on Oracle Cloud at Customer might not be the same as the version available on Oracle Cloud. As a result, some features of this service may not be available on Oracle Cloud at Customer. For more information, contact your Oracle representative.