You can export data to Oracle Data Pump dump files by specifying a query.
Note:To export a schema to another database, use one of the alternative methods. See Moving Data from Autonomous Database to Other Oracle Databases for more information.
With this export method you use the
DBMS_CLOUD.EXPORT_DATA procedure to specify a query to select the
data to export, as follows:
- Connect to your database.
- Store your object store credentials using the procedure
DBMS_CLOUD.CREATE_CREDENTIAL( credential_name => 'DEF_CRED_NAME', username => 'email@example.com', password => 'password' ); END; /
This operation stores the credentials in the database in an encrypted format. You can use any name for the credential name. Note that this step is required only once unless your object store credentials change. Once you store the credentials you can then use the same credential name.
See CREATE_CREDENTIAL Procedure for information about the
passwordparameters for different object storage services.
- Export data from Autonomous Database to your
Cloud Object Store as Oracle Data Pump dump file(s) by calling
DBMS_CLOUD.EXPORT_DATA. For example:
DBMS_CLOUD.EXPORT_DATA( credential_name =>'DEF_CRED_NAME', file_uri_list =>'https://objectstorage.us-phoenix-1.oraclecloud.com/n/namespace-string/b/bucketname/o/export1.txt', format => json_object(''type' value 'datapump'), query => 'SELECT warehouse_id, quantity FROM inventories' ); END; /
The parameters are:
credential_name: is the name of the credential created in the previous step.
file_uri_list: is a comma delimited list of the export file(s). Use of wildcard and substitution characters is not supported in the
format: specifies the required
typeparameter with the value
datapump, and optionally defines the options you can specify for the export with the
query: specifies a
SELECTstatement so that only the required data is exported. The query determines the contents of the dump file(s).
In this example,
namespace-stringis the Oracle Cloud Infrastructure object storage namespace and
bucketnameis the bucket name. See Understanding Object Storage Namespaces for more information.
DBMS_CLOUD.EXPORT_DATAprocedure creates the dump file(s) that you specify in the
file_uri_list. The procedure does not overwrite files. If a dump file in the
DBMS_CLOUD.EXPORT_DATAreports an error.
DBMS_CLOUD.EXPORT_DATAdoes not create buckets.
For detailed information about the parameters, see EXPORT_DATA Procedure.
- Perform the required steps to use Oracle Data Pump import and clean up. See Download Dump Files, Run Data Pump Import, and Clean Up Object Store for more details.
Notes for exporting data with
The dump files you create with
DBMS_CLOUD.EXPORT_DATAcannot be imported using Oracle Data Pump
impdp. Depending on the database, you can use these files as follows:
On an Autonomous Database instance on Shared Infrastructure, you can use the dump files with the
DBMS_CLOUDprocedures that support the
typewith the value '
datapump'. You can import the dump files using
DBMS_CLOUD.COPY_DATAor you can call
DBMS_CLOUD.CREATE_EXTERNAL_TABLEto create an external table.
On any other Oracle Database, such as Oracle Database 19c on-premise, you can import the dump files created with the procedure
ORACLE_DATAPUMPaccess driver. See Unloading and Loading Data with the ORACLE_DATAPUMP Access Driver for more information.
The number of dump files that
DBMS_CLOUD.EXPORT_DATAgenerates is determined when the procedure runs. The number of dump files that are generated depends on the number of file names you provide in the
file_uri_listparameter, as well as on the number of Autonomous Database OCPUs available to the instance, the service level, and the size of the data.
For example, if you use a 1 OCPU Autonomous Database instance or the
lowservice, then a single dump file is exported with no parallelism, even if you provide multiple file names. If you use a 4 OCPU Autonomous Database instance with the
highservice, then the jobs can run in parallel and multiple dump files are exported if you provide multiple file names.
queryparameter value that you supply can be an advanced query, if required, such as a query that includes joins or subqueries.