Getting Started with Resource Analytics

Get started with Resource Analytics.

Prerequisites

The prerequisites required to use Resource Analytics.

The subnet must have DNS enabled for Resource Analytics to be created.
Use DNS hostnames in this Subnet is selected with a label.

About Resource Analytics Releases

For LA, the schema might be updated periodically. Schemas might change periodically, Oracle will notify you of any backward-incompatible changes. Although it should not be common, it's possible that columns are added, changed, or removed.

Usage Guidelines for Autonomous Data Warehouse Associated with Resource Analytics

Resource Analytics provisions instances of Oracle Autonomous Data Warehouse to store data. As part of Resource Analytics, Oracle doesn't let you perform, or recommend, certain Oracle Autonomous Data Warehouse administration tasks.

As a service administrator, you can access the Oracle Autonomous Data Warehouse instance associated with Resource Analytics using the Oracle Cloud Infrastructure Console. The following table outlines the tasks that aren't allowed or recommended.


Task	More information
Database lifecycle management	You can stop, delete, pause, and restart the database . Resource Analytics controls these activities for the instance. We recommend that you don't rename the database and don't use the Start or Stop options in the Scheduled Maintenance feature for the Oracle Autonomous Data Warehouse instance associated with Resource Analytics.
Changes to auto-provisioned resources	You can scale up resources such as OCPUs for more capacity or terabytes for extra storage. However, you can't scale down such resources to levels under those automatically provisioned with Resource Analytics. Autoscale for OCPUs is turned on by default by Resource Analytics and you can't turn it off.
Autonomous Data Guard	Even though you can turn on Autonomous Data Guard, this isn't recommended because Resource Analytics doesn't support failover to the instance populated through Data Guard.
Restore from backups	Oracle Autonomous Data Warehouse provides daily backups. While restoring to a new instance might be useful to view or copy data from backup, it isn't recommended to restore backups against the Oracle Autonomous Data Warehouse instance associated with Resource Analytics. Doing so might put the data pipelines and factory content in an inconsistent state.

The Oracle Autonomous Data Warehouse instance created by Resource Analytics is shared between you and the service. Be aware of the impact certain user actions and configurations can have on the performance of queries and service-provided updates. While you can insert custom data and query the database, it has an impact on the database storage and compute. The following are some guidelines:


Custom Usage	Guidance
Adding data to custom schemas	You can add as many as 50 GB of custom data to the service. For more than 50 gigabytes, you must scale up the storage through the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account. If you intend to do compute-intensive queries and transformations on your custom data, then you can scale up more OCPUs using the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account. See Scale Up Oracle Autonomous Data Warehouse.
Adding extra CPUs	Ensure that you have adequate CPUs configured in Oracle Autonomous Data Warehouse (and corresponding sessions) to run custom ETL. For every CPU that's allocated as part of the Resource Analytics instance creation, you shouldn't exceed five low service concurrent sessions for custom ETL. Exceeding this can impact the ETL or reporting performance and therefore isn't supported. If you need to run more sessions, then ensure that extra CPUs are added to the Oracle Autonomous Data Warehouse instance. Each extra CPU that you add this way gives as many as 300 low sessions. You must avoid Medium or High sessions in all cases because they block the ETL pipeline.
Adding database connections	See Tutorial. Follow these guidelines: Aim for fewer than 10 concurrent database connections. When you configure the connections, ensure that you select the service with the low suffix in its name. Don't select the service with the high prefix because it can lead to performance issues in reports and delays in completion of daily data refreshes in Resource Analytics. Close unused sessions in a timely manner to ensure no adverse impact on the performance of Resource Analytics. If you plan to run compute-intensive queries or create many concurrent database connections, then you can scale up extra OCPUs through the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account.

Region Availability

Resource Analytics is available in all Oracle Cloud Infrastructure commercial regions.

For more information, see About Regions and Availability Domains for the list of available regions for Oracle Cloud Infrastructure, along with associated locations, region identifiers, region keys, and availability domains.

Billing Metrics of Autonomous Data Warehouse Associated with Resource Analytics

Oracle Autonomous Database uses the ECPU billing metric.

ECPUs provide the same price-performance as OCPUs with continuous improvements over time. Updating to the ECPU and storage billing metrics provides the following other benefits:

Lower entry cost.
Finer granularity for scaling the data warehouse.
Lower storage costs.

See the ECPU billing metric FAQ for more details about ECPUs and associated benefits.