Configuring an Oracle Connection

**Table 1** Oracle connection
Parameter	Mandatory	Description
Data Connection Type	Yes	ORACLE is selected by default and cannot be changed.
Name	Yes	Name of the data connection to create. Data connection names can contain a maximum of 100 characters. They can contain only letters, digits, underscores (_), and hyphens (-).
Tag	No	Attribute of the data connection to create. Tags make management easier. NOTE: The tag name can contain only letters, digits, and underscores (_) and cannot start with an underscore (_) or contain more than 100 characters.
Applicable Modules	Yes	Select the modules for which this connection is available. All modules are selected by default, which means this connection is available for all the modules that support the data source connected by this connection. For details about the data sources supported by each module, see Data Sources.
Basic and Network Connectivity Configuration
IP Address or Domain Name	Yes	Address for accessing the database to be connected. You can enter a public/private IP address or a domain name.
Port	Yes	The port of the database to connect.
KMS Key	Yes	KMS key used to encrypt and decrypt the authentication information for the data source
Agent	Yes	Oracle is not a fully managed service and cannot be directly connected to DataArts Studio. A CDM cluster can provide an agent for DataArts Studio to communicate with non-fully-managed services. Therefore, you need to select a CDM cluster when creating an Oracle data connection. If no CDM cluster is available, create one through the DataArts Migration incremental package. As a network proxy, the CDM cluster must be able to communicate with Oracle. NOTE: If a CDM cluster functions as the agent for a data connection in Management Center, the cluster supports a maximum of 200 concurrent active threads. If multiple data connections share an agent, a maximum of 200 SQL, Shell, and Python scripts submitted through the connections can run concurrently. Excess tasks will be queued. You are advised to plan multiple agents based on the workload.
Data Source Authentication and Other Function Configuration
Username	Yes	Username used for accessing the database This account must have the permissions required to read and write data tables and metadata. NOTE: If you have the CONNECT permission (read-only permission) and are trying to create a connection, a message is displayed indicating that the table or schema does not exist. In this case, perform the following operations to grant permissions: Log in to the Oracle node as user root. Run the following command to switch to user oracle: su oracle Run the following command to log in to the database: sqlplus /nolog Run the following command to log in as user sys: connect sys as sysdba; Enter the password of user sys. Run the following SQL statement to grant permissions: *GRANT SELECT ON GV_$INSTANCE to xxx;* In the preceding command, xxx indicates the name of the user to which the permissions will be granted.
Password	Yes	Password of the username
Connection Type	Yes	Select a connection type. SID SID indicates the ID of the Oracle database instance. One instance corresponds to only one database, but one database can correspond to multiple instances. Service Name It was introduced since Oracle8i and indicates the external service name of the Oracle database.
SID	Yes	This parameter is mandatory when Connection type is set to SID. SID indicates the ID of the Oracle database instance. One instance corresponds to only one database, but one database can correspond to multiple instances.
Service Name	Yes	This parameter is mandatory when Connection type is set to Service Name. This parameter was introduced since Oracle8i and indicates the external service name of the Oracle database.