https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/backup- manual.html#GUID-D95E5D6A-C470-4A68-9545-CC99D937E7D1

Optimizer Hints Ignored by default in ADW, where honored by default in ATP When migrating data to Autonomous Database, table statistics are gathered automatically during direct path load operations. If direct path load operations are not used, such as with SQL Developer loads, the user can gather statistics manually as needed. When migrating an existing database that uses optimizer in parallel hints, ADB will ignore those by default. Because ADB runs in a highly tuned exadata environment, most database operations should run faster or at least as well as database tune with lots of hints to perform faster. Should hints be required for some reason, they can be explicitly re-enabled.
Autonomous Data Warehouse ignores optimizer hints and PARALLEL hints in SQL statements by default

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dwhsg/overview-analytic- views.html#GUID-6F948948-6AE6-4A89-8AAC-5B8952CEF41D

In the Restore prompt, select Specify Timestamp or Select Backup to restore to a point in time or to restore from a specified backup.
https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/backkup- recover.html#GUID-78C28C41-AA87-4AD7-BEB6-693235C73F3C

Predefined Database Service Names for Autonomous Transaction Processing The tnsnames.ora file provided with the credentials zip file contains five database service names identifiable as tpurgent, tp, high, medium, and low. The predefined service names provide different levels of performance and concurrency for Autonomous Transaction Processing.
* tpurgent: The highest priority application connection service for time critical transaction processing operations. This connection service supports manual parallelism.
* tp: A typical application connection service for transaction processing operations. This connection service does not run with parallelism.
* high: A high priority application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing.
* medium: A typical application connection service for reporting and batch operations. All operations run in parallel and are subject to queuing. Using this service the degree of parallelism is limited to four (4).
* low: A lowest priority application connection service for reporting or batch processing operations. This connection service does not run with parallelism.
https://docs.oracle.com/en/cloud/paas/atp-cloud/atpug/manage-priorities.html#GUID-80E464A7-8ED4-45BB-A7D6-E201DD4107B7