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.
| 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 ECPUs 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 ECPUs 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. |
| 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 ECPUs using the Oracle Cloud Infrastructure Console, which is charged to your Oracle Cloud account. See Scale Up Oracle Autonomous Data Warehouse. |
| Adding additional ECPUs | Ensure that you have adequate ECPUs configured in Oracle Autonomous Data Warehouse (and corresponding sessions) to be able to run custom ETL. For every ECPU 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 ECPUs added to your Oracle Autonomous Data Warehouse instance. Each additional ECPU 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:
|