Explanation
One of the most productive tools to use with Autonomous Database is SQL Developer, which is included for free with Autonomous Database. In this section, we show how to connect the Autonomous Database with SQL Developer. SQL developer fully supports connectivity to Autonomous Database and is Autonomous Database aware. To establish a connection to Autonomous Database, select the Connections green plus sign at the top left corner of the tool.
A new connection screen will appear, the same for an autonomous or non-autonomous database. In the top three lines, you will want to name the connection and fill in the appropriate username and password for the user you will be connecting to. Under Connection Type, the type to use for Autonomous Database is Cloud Wallet. When using this connection type, which is the only connection type supported for Autonomous Database, the location of the downloaded wallet must be specified in the configuration file entry.
Navigate to and select the downloaded wallet file. If the correct wallet file is selected, the service drop down will list all the services available to the Autonomous Database. Select the one that most appropriately provides the ser vice level your connection will require. Please refer to the section on user connections and services in another module for more information on this. Finally, to establish a connection, click Connect.
https://docs.oracle.com/en/cloud/paas/autonomous-data-warehouse-cloud/user/connect-sql-dev182.html#GUID-1

Explanation
DELETE_FILE Procedure
This procedure removes the specified file from the specified directory on Autonomous Data Warehouse.
CREATE_CREDENTIAL Procedure
This procedure stores Cloud Object Storage credentials in the Autonomous Data Warehouse database. Use stored credentials for data loading or for querying external data residing in the Cloud.
PUTJDBJECT Procedure
This procedure copies a file from Autonomous Data Warehouse to the Cloud Object Storage. The maximum file size allowed in this procedure is 5 gigabytes (GB).
VALIDATE EXTERNAL TABLE Procedure
This procedure validates the source files for an external table, generates log information, and stores the rows that do not match the format options specified for the external table in a badfile table on Autonomous Data Warehouse.
CREATE_EXTERNAL_TABLE Procedure
This procedure creates an external table on files in the Cloud. This allows you to run queries on external data from Autonomous Data Warehouse.
To use Data Pump from ADB, a credential identifying the Object Storage bucket to use must be defined with a DBMS_CLOUD.CREATE_CREDENTIAL function. This will allow ADB to access objects that are stored in the object store , including dump files. To export an existing database to prepare for import into ADB, use the XTP command and add the ex elude option for database functionality that is not recommended or supported in ADB. This will prevent errors during the imp oil process.
This process is not automatic. And if the logs are not moved, you will receive a warning when running the MDB that the logs are not there. In this example, we're moving the log import.log to object store with a DBMS_CLOUD.PUT_OBJECT command.
VALIDATE_EXTERNAL_TABLE Procedure
This procedure validates the source files for an external table, generates log information, and stores the rows that do not match the format options specified for the external table in a table on Autonomous Database. The overloaded form enables you to use the operation_id parameter.
PUT_OBJECT Procedure
This procedure copies a file from Autonomous Database to the Cloud Object Storage. The maximum file size allowed in this procedure is 5 gigabytes (GB) DELETE FILE Procedure This procedure removes the specified file from the specified directory on Autonomous Database.
CREATE_EXTERNAL_TABLE Procedure
This procedure creates an external table on files in the Cloud. This allows you to run queries on external data from Autonomous Database.