Usage Guidelines for Autonomous Data Warehouse Associated with Fusion Data Intelligence

Oracle Fusion Data Intelligence provisions instances of Oracle Autonomous Data Warehouse to store data. As part of the integrated SaaS offering of Oracle Fusion Data Intelligence, Oracle doesn't allow or recommend certain Oracle Autonomous Data Warehouse administration tasks.

As a service administrator, you can access the Oracle Autonomous Data Warehouse instance associated with Oracle Fusion Data Intelligence 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't stop, delete, pause, or restart the database. Oracle Fusion Data Intelligence controls these activities for the instance. Oracle recommends 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 Oracle Fusion Data Intelligence.
Changes to auto-provisioned resources	You can scale up resources such as OCPUs for additional capacity or terabytes for additional storage. However, you can't scale down such resources to levels below those automatically provisioned with Oracle Fusion Data Intelligence. Auto-scale for OCPUs is turned on by default by Oracle Fusion Data Intelligence and you can't turn it off.
Autonomous Data Guard	Even though you can turn on Autonomous Data Guard, this isn't recommended because Oracle Fusion Data Intelligence doesn't currently 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 may 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 Oracle Fusion Data Intelligence. Doing so may put the data pipelines and factory content in an inconsistent state.

The Oracle Autonomous Data Warehouse instance created by Oracle Fusion Data Intelligence is primarily for use by the service. While you can insert custom data and query the database, it has an impact on the database storage and compute. Following are some guidelines:

Custom Usage	Guidance
Adding data to custom schemas	You can add as many as 50 gigabytes 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 additional OCPUs using the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account. See Scale Up Oracle Autonomous Data Warehouse.
Adding additional CPUs	Ensure that you have adequate CPUs configured in Oracle Autonomous Data Warehouse (and corresponding sessions) to be able to run custom ETL. For every CPU that's allocated as part of the Oracle Fusion Data Intelligence instance creation, you shouldn't exceed 5 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 you've additional CPU added to your Oracle Autonomous Data Warehouse instance. Each additional CPU that you add this way allows 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 prefix 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 Oracle Fusion Data Intelligence. Close unused sessions in a timely manner to ensure no adverse impact on the performance of Oracle Fusion Data Intelligence. If you plan to run compute-intensive queries or create many concurrent database connections, then you can scale up additional OCPUs through the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account.