Create an Oracle Autonomous Database connection to load data to an Oracle Autonomous Database target.
Prerequisites
Before you create an Oracle Autonomous Database connection to read from or write to Oracle Autonomous Database, be sure to complete the prerequisites.
Memory requirements
You can configure INFA_MEMORY and JVM options for the Secure Agent to optimize performance and avoid Java heap and memory-related errors when working with Oracle Autonomous Database Connector. Define these properties on the agent details page in Administrator.
For more information about the configurations required for the Secure Agent and detailed steps, see INFA_MEMORY and JVM options in the Data Integration Performance Tuning documentation.
Prepare for object storage authentication
You can configure the following object storage authentication methods for Oracle Autonomous Database Connector:
ConfigFile authentication
The ConfigFile authentication uses identity credentials of Oracle Cloud Infrastructure (OCI) account provided through a configuration file for authentication. This authentication method is based on the profile selected in the configuration file.
You can create a configuration file in the following format:
You require the user OCID, fingerprint, and tenancy OCID information from the OCI account for the configuration file.
For more information about the steps to extract the identity credentials from the Oracle Cloud Infrastructure Console, see the Oracle Cloud Infrastructure documentation.
By default, the OCI configuration file is located at ~/.oci/config on the Secure Agent machine. The ~/.oci/config file can contain several profiles. The default profile name is DEFAULT. You can change the default profile name to any new profile names based on the profiles that you add to the ~/.oci/config file. The ~/.oci/config file cannot contain two profiles with the same name.
Simple authentication
The simple authentication uses API keys for authentication. You can provide the authentication details in the Oracle Autonomous Database connection. You need to place the private key file in the Secure Agent machine.
You require the user OCID, fingerprint, and tenancy OCID information from the Oracle Cloud Infrastructure account to create an Oracle Autonomous Database connection.
For more information about the steps to extract the identity credentials from the Oracle Cloud Infrastructure Console, see the Oracle Cloud Infrastructure documentation.
Connect to Oracle Autonomous Database
Let's configure the Oracle Autonomous Database connection properties to connect to Oracle Autonomous Database hosted on Oracle Cloud Infrastructure.
Before you begin
Before you get started, complete the following prerequisites:
•Configure the memory requirements for the connector.
•Get the required information from your Oracle Cloud Infrastructure account based on the object storage authentication type that you want to configure.
Check out Prerequisites to learn more about this task.
Connection details
When you create an Oracle Autonomous Database connection, configure the connection properties.
The following table describes the basic connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Description
Description of the connection. Maximum length is 4000 characters.
Use Secret Vault
Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.
This property appears only if secrets manager is set up for your organization.
This property is not supported by Data Ingestion and Replication and the Data Access Management services.
When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.
Note:
If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option.
The name of the runtime environment where you want to run tasks.
User Name
The user name to access the Oracle Autonomous Database. It is used to authenticate the connection.
Password
The password associated with the user name.
Authentication types
You can configure TLS or mutual TLS authentication to connect to Oracle Autonomous Database. Select the required authentication type and then configure the authentication-specific parameters.
Default is mutual TLS authentication.
Mutual TLS authentication
The following table describes the basic connection properties for mutual TLS authentication:
Property
Description
Service Name
The specific database service accessed for the secured connection.
Wallet Path
The location of the wallet file for the secured connection.
TLS authentication
The following table describes the basic connection properties for TLS authentication:
Property
Description
TNS Name
The TNS name defined in the tnsnames.ora file.
For example, String tnsEntry = "(description= ... (security=(ssl_server_dn_match=yes)))"
Object storage authentication types
You can configure ConfigFile or simple authentication for staging the connection when you connect to Oracle Autonomous Database. Select the required authentication type and then configure the authentication-specific parameters.
Default is ConfigFile authentication.
ConfigFile authentication
The following table describes the basic connection property for ConfigFile authentication:
Property
Description
Region
The Oracle Cloud Infrastructure region where the object storage bucket resides.
Select the Oracle Cloud Object Storage region from the list.
Advanced settings
The following table describes the advanced connection properties for ConfigFile authentication:
Property
Description
Configuration File Location
The absolute path of the configuration file on the Secure Agent machine.
If you do not enter the value, the Secure Agent uses the following configuration file path: ~/.oci/config
Profile Name
The name of the profile in the configuration file that you want to use.
Default is DEFAULT.
Simple authentication
The following table describes the basic connection properties for simple authentication:
Property
Description
User OCID
The unique identifier of the user in Oracle Cloud Infrastructure.
For example, ocid1.user.oc1..aaaaaaaaherdgpjknqzrwbdc7n5ksokkot7c5jngtx3pgolr7oqbw7xzksza
Fingerprint
The fingerprint of the public key.
Tenancy OCID
The unique identifier of the tenancy in Oracle Cloud Infrastructure. The tenancy is the globally unique name of the Oracle Cloud Infrastructure account.
For example, ocid1.tenancy.oc1..aaaaaaaaba3pv6wkcr4jqae5f44n2b2m2yt2j6rx32uzr4h25vqstifsfdsq
Private Key File Location
The location of the private key file in .PEM format on the Secure Agent machine.
Region
The Oracle Cloud Infrastructure region where the object storage bucket resides.
Select the Oracle Cloud Object Storage region from the list.