Oracle Connection Parameters

**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 (-).
Description	No	A description which can help identify the data connection more easily. It can contain a maximum of 100 characters.
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. NOTE: When offline or real-time data migration jobs are enabled, you can select the DataArts Migration module. Then you can select this data connection when creating a data migration job in DataArts Factory. You can use offline or real-time data migration jobs only after you apply for the whitelist membership. To use this feature, contact customer service or technical support.
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 data source authentication information. Select a default or custom key. NOTE: When you use KMS for encryption through DataArts Studio or KPS for the first time, the default key dlf/default or kps/default is automatically generated. For more information about default keys, see What Is a Default Master Key?. Only symmetric keys are supported. Asymmetric keys are not supported.
Agent	Yes	DataArts Studio cannot be directly connected to non-fully managed services. 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 first by referring to Creating a CDM Cluster. As a network proxy, the CDM cluster must be able to communicate with Oracle.
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.
Data Migration Configuration
Driver Name	Yes	Select oracle.jdbc.OracleDriver for Oracle.
Driver file source	Yes	Select the source of the driver file.
Driver File Path	Yes	This parameter is mandatory when Driver file source is set to OBS path. Path of the driver file in the OBS bucket. You need to download the .jar driver file from the corresponding official website and upload it to the OBS bucket. To download the driver package, visit https://repo1.maven.org/maven2/com/oracle/database/jdbc/ojdbc8/. ojdbc8 12.2.0.1 is recommended. NOTE: To update the driver, you must restart the CDM cluster in DataArts Migration and then edit the data connection to upload the driver.
Driver File	Yes	This parameter is mandatory when Driver Source is set to Local file. Select a driver version that adapts to the database type.
Fetch Size	No	Set the number of rows obtained by each request. Set this parameter based on the data source and the job's data size. This parameter is optional. If the value is either too large or too small, the job may run for a long time. The default value is 1,000.
Link Attributes	No	(Optional) Click Add to add the JDBC connector attributes of multiple specified data sources. For details, see the JDBC connector document of the corresponding database. The following are some examples: connectTimeout=360000 and socketTimeout=360000: When a large amount of data needs to be migrated or the entire table is retrieved using query statements, the migration fails due to connection timeout. In this case, you can customize the connection timeout interval (ms) and socket timeout interval (ms) to prevent failures caused by timeout. useCursorFetch=false: By default, useCursorFetch is enabled, indicating that the JDBC connector communicates with relational databases using a binary protocol. Some third-party systems may have compatibility issues, causing migration time conversion errors. In this case, you can disable this function.
Reference Sign	No	(Optional) Delimiter between the names of the referenced tables or columns. For details, see the product documentation of the corresponding database. The default value is ".