allow group <group_name> to use object-family in compartment <compartment-name>
allow any-user to read buckets in compartment <compartment-name> where ALL {request.principal.type = 'disworkspace', request.principal.id = '<workspace_ocid>', request.operation = 'GetBucket'}
allow any-user to manage objects in compartment <compartment-name> where ALL {request.principal.type = 'disworkspace', request.principal.id = '<workspace_ocid>'}
To use Oracle Autonomous Data Warehouse as a target:
Copy
allow any-user to manage buckets in compartment <compartment-name> where ALL {request.principal.type = 'disworkspace', request.principal.id = '<workspace_ocid>', request.permission = 'PAR_MANAGE'}
On the Select Data asset type panel, for Connector Type select All. Then select the OCI
Object Storage icon.
If you don't see OCI
Object Storage, enter obj in the search field.
On the Create data asset page, complete the fields in the General information section:
For Name, enter Data_Lake without any spaces. You can use alphanumeric characters, hyphens, periods, and underscores only.
For Description, enter a description about the data asset.
The Type menu already shows OCI
Object Storage selected.
The Tenancy OCID and Namespace fields are automatically filled for you.
Note
This procedure assumes that the workspace and Object Storage resources are within the same tenancy.
The namespace value is based on the tenancy OCID value. If the Namespace field isn't automatically filled, you can enter the tenancy name.
For OCI region, select the region for the Object Storage resource, or start typing a name to filter the list and then select a region from the filtered list.
Important
The Object Storage data source that you set up as a Source or Target data asset in Data Integration is identified using the region ID, namespace, and bucket name. You don't encounter issues if the Source and Target data assets have different region IDs, different namespaces, and different bucket names. If the Source and Target have the same bucket name but different region IDs and namespaces, or if they have the same namespace but different region IDs and different bucket names, then also you won't encounter any issues. However, if only the Source and Target data asset region ID is different and the namespace and bucket name are the same, the Data Integration tasks would fail.
Ignore the Enable policies to use data asset information box, if you have already added the required policies. Otherwise, select Show more information to view the details of the policy name and policy statements required to use the Object Storage data asset. Add or copy the policies, specifying the group name and compartment in the statements.
In the Default connection information section, enter a name and description (optional).
(Optional) Select Test connection.
A successful test isn't required to create the data asset.
Select Create.
2. Preparing the Target Database 🔗
To complete all the tutorials in this series, configure the target autonomous database to add a schema and a table.
To prepare the target autonomous database with the BETA schema:
In the Console
navigation menu, select Oracle Database, and then select Autnomouse Database.
Select the compartment that has the autonomous database you're going to use.
From the list of autonomous databases, select the database.
Under Database Actions, select SQL.
If prompted, log in with the administrator credentials for the autonomous database.
To create the BETA user, enter and then run the following script in the SQL worksheet:
Copy
create user BETA identified by "<example-password>";
grant DWROLE to BETA;
alter user BETA quota 200M on data;
Note
Ensure that you enter a password in place of <example-password>.
Run the following SQL statements to create the CUSTOMERS_TARGET table.
On the Select Data asset type panel, for Connector Type select RDBMS. Then select the Oracle ADW icon.
On the Create data asset page, complete the fields in the General information section:
Name:Data_Warehouse (You can use alphanumeric characters, hyphens, periods, and underscores only).
Identifier: A generated identifier based on the value you enter for Name. You can change the generated value, but after you save the data asset, you aren't allowed to update the identifier.
Description: Optional
Type: The Type menu already shows Oracle Autonomous Data Warehouse selected.
Upload wallet and Wallet file: Drop or browse to select the wallet file for accessing the database.
In the Default connection information section, enter or select the
following:
Name: Default connection (Optionally, you can rename the
connection)
Description: Optional (For example, Connect with BETA
user)
Username: BETA
Use password: The password you created for BETA.
We recommend that you create a vault secret, and then select Use vault secret OCID for the BETA user password. See Vault, Keys, and Secrets.
TNS alias: The database service to use
In the Default staging location section, enter or select the
following:
Object Storage data asset: The Object Storage data asset that has the bucket you want to use as the default staging location
Connection: The connection
Compartment: The compartment
Bucket: The bucket name
(Optional) Select Test connection.
A successful test isn't required to create the data asset.