# [26ai] DBMS_CLOUD — Chapter Two

*If you prefer to read in Spanish* [***Spanish version***](https://dbaenlasombra.com/26ai-dbms-cloud-capitulo-dos)*.*

Cointinuing with the last article, where we looked at how to set up *DBMS\_CLOUD* in our database and took the firsts steps., today, we're going to see how to use *DBMS\_CLOUD* with Oracle Datapump.

Below, you can see the first chapter:

[\[26ai\] DBMS\_CLOUD — Capitulo Uno](https://dbaenlasombra.com/26ai-dbms-cloud-capitulo-uno)

Our lab will have two sections, as follows:

*   Export a table to a *Bucket.*
    
*   Import into the table the information from the previous step.
    

### **Export to a *Bucket***

Let's create a table. We'll use this table in order to perform the export :

```sql
SQL> 
  Create Table My_Grants As  
   Select TABLE_SCHEMA,TABLE_NAME,PRIVILEGE  
     From All_Tab_Privs;

 Table created.

SQL> set linesize 1000 pages 1000
SQL> col TABLE_SCHEMA format a20
SQL> col table_name format a20
SQL> col privilege format a20
SQL> r
  1* Select * From My_Grants FETCH FIRST 10  ROWS ONLY

TABLE_SCHEMA         TABLE_NAME                     PRIVILEGE
-------------------- ------------------------------ --------------------
SYS                  DUAL                           SELECT
SYS                  SYSTEM_PRIVILEGE_MAP           READ
SYS                  TABLE_PRIVILEGE_MAP            READ
SYS                  USER_PRIVILEGE_MAP             READ
SYS                  STMT_AUDIT_OPTION_MAP          READ
SYS                  FINALHIST$                     INSERT
SYS                  DM$EXPIMP_ID_SEQ               SELECT
SYS                  MODELGTTRAW$                   SELECT
SYS                  MODELGTTRAW$                   INSERT
SYS                  PMAPGTT$                       SELECT
```

Moreover, we're going to use the **DEFAULT\_CREDENTIAL** property in order to set our credential as the default.

```sql
SQL> 
ALTER DATABASE PROPERTY SET DEFAULT_CREDENTIAL = 'TEST.DBA_IN_THE_SHADOW';

Database altered.

SQL> 
Select PROPERTY_NAME,PROPERTY_VALUE 
  From database_properties  
 Where PROPERTY_NAME= 'DEFAULT_CREDENTIAL';

PROPERTY_NAME        PROPERTY_VALUE                           
-------------------- ---------------------------------------- 
DEFAULT_CREDENTIAL   TEST.DBA_IN_THE_SHADOW                    
```

Let's create a parfile in order to perform the export:

```sql
SQL> ! vi export_to_bucket.par
SQL> ! cat export_to_bucket.par
DUMPFILE=<location_uri>/<TABLE>.dmp
LOGFILE=<TABLE>.log
TABLES=<SCHEMA>.<TABLE>
CONTENT=DATA_ONLY
LOGTIME=ALL
METRICS=YES
FLASHBACK_TIME=SYSTIMESTAMP
ENCRYPTION_PASSWORD=hari
```

Our parfile is as follows:

*   DUMPILE: *Bucket* URL in order to save the export.
    
*   LOGFILE: Log name.
    
*   TABLES: Here, we fill in the parameter with the name of the table that we created in the previous step.
    
*   CONTENT=DATA\_ONLY: Export Data only.
    
*   LOGTIME/METRICS: Time Metrics .
    
*   FLASHBACK\_TIME: Consistent data export.
    
*   ENCRYPTION\_PASSWORD: Encrypt our **dmp** file.
    

Let's execute the *export*:

![](https://cloudmate-test.s3.us-east-1.amazonaws.com/uploads/covers/65605419d28f19cc44df7ef1/abcbe616-5049-4a34-b90e-db8f57914a8c.png align="center")

Let's check our **dmp** in our*Bucket*:

```sql
SQL> 
Select object_name, trunc(bytes / (1024*1024),2) MB
  From 
   dbms_cloud.list_objects('DBA_IN_THE_SHADOW', '<location_uri>'); 

OBJECT_NAME                                      MB
---------------------------------------- ----------
ORA7445pf_20260205085710_COM_1.zip            57.35
Wallet_OF2BAP.zip                               .02
Wallet_OF2BCE.zip                               .02
grant.dmp                                         0
grant.dmp_segments/aaaaaa                         2
grant.dmp_segments/aaaaab                       .86

6 rows selected.
```

Regarding our **dmp** inside out *Bucket*, we can see three files even though we haven't used any wildcards, such as **%L**, **%l**, **%U,** or **%u**. Moreover, the size of our **dmp** is zero, while the DMP fragments have weigth. How come? Because Data Pump splits the dmp into smaller pieces in order to improve load performance.

### **ImportIng from a *Bucket***

Before executing the import , we need to create a table in order to store the data:

```sql
SQL> CREATE TABLE MY_GRANTS_BCK AS SELECT * FROM MY_GRANTS WHERE 2 = 1;

Table created.
SQL> ! vi import_to_bucket.par
SQL> ! cat import_to_bucket.par
DUMPFILE=<location_uri>/<TABLE>.dmp
LOGFILE=MY_GRANTS.log
LOGTIME=ALL
METRICS=YES
REMAP_TABLE = TEST.MY_GRANTS:MY_GRANTS_BCK
encryption_password=yes
```

Our parfile is as follows:

*   DUMPILE: *Bucket* URL in order to get the export.
    
*   LOGFILE: Log name.
    
*   LOGTIME/METRICS: Time Metrics.
    
*   REMAP\_TABLE: We want to store the information in another table, so we need to use the REMAP\_TABLE parameter.
    
*   ENCRYPTION\_PASSWORD= Our **dmp** is encrypted.
    

Let's execute the *import*:

![](https://cdn.hashnode.com/uploads/covers/65605419d28f19cc44df7ef1/1f70eaba-7bce-42eb-befe-5fcb06d93874.png align="center")

Perfect, we have been able to use our *Bucket* with **Oracle Data Pump**.

Looking forward to seeing you in the next article :)