Dataphin:Configure the Oracle output component

Prerequisites

• You have created an Oracle data source. For more information, see Creating an Oracle Data Source.

• The account used to configure the Oracle output component's properties must have write-through permissions on the data source. If the account does not have these permissions, you must request them. For more information, see Request, renew, or return data source permissions.

Procedure

1. In the top menu bar of the Dataphin home page, choose R&D > Data Integration.

2. In the top menu bar of the integration page, select a Project. If you are in Dev-Prod mode, you must also select an Environment.

3. In the left navigation pane, click Offline Integration. In the Offline Integration list, click the offline pipeline that you want to develop to open its configuration page.

4. In the upper-right corner of the page, click Component Library to open the Component Library panel.

5. In the navigation pane on the left of the Component Library panel, select Output. Find the Oracle component in the output component list on the right and drag it to the canvas.

6. Click and drag the icon of the target input, transform, or flow component to connect it to the Oracle output component.

7. Click the icon on the Oracle output component card to open the Oracle Output Configuration dialog box.

8. In the Oracle Output Configuration dialog box, configure the following parameters.

   Parameter		Description
   Basic Settings	Step Name	The name of the Oracle output component. Dataphin automatically generates a step name. You can also change the name as needed. The name must follow these rules: You can enter only Chinese characters, letters, underscores (_), or digits. It must be no more than 64 characters in length.
   	Datasource	From the data source drop-down list, select a data source. The list displays all Oracle data sources, including those for which you have write-through permissions and those for which you do not. Click the icon to copy the name of the current data source. If you do not have write-through permissions on a data source, click Request next to the data source to request the permissions. For more information, see Request data source permissions. If you do not have an Oracle data source, click Create Data Source to create one. For more information, see Create an Oracle data source.
   	Time Zone	Time-formatted data is processed based on the current time zone. By default, this is the time zone configured in the selected data source and cannot be changed. Note For nodes created before version 5.1.2, you can select Data Source Default Configuration or Channel Configuration Time Zone. The default is Channel Configuration Time Zone. Data Source Default Configuration: The default time zone of the selected data source. Channel Configuration Time Zone: The time zone configured for the current integration node in Properties > Channel Configuration.
   	Schema (Optional)	You can select tables across schemas. Select the schema where the table is located. If you do not specify a schema, the schema configured in the data source is used by default.
   	Table	Select the target table for the output data. You can enter a keyword to search for a table, or enter the exact table name and click Exact Search. After you select a table, the system automatically checks its status. Click the icon to copy the name of the selected table. If the target table for data synchronization does not exist in the Oracle data source, you can use the one-click table creation feature to quickly generate it. The steps are as follows: Click One-Click Table Creation. Dataphin automatically generates the code to create the target table. This includes the target table name, which defaults to the source table name, and field types, which are based on an initial conversion of Dataphin fields. Modify the SQL script to create the target table as needed, and then click Create. Important If you do not change the table name after CREATE TABLE, the system generates an uppercase table name by default. If you enclose the table name after CREATE TABLE in double quotation marks, the table name is case-sensitive. After the target table is created, Dataphin automatically uses it as the target table for the output data. Note If a table with the same name exists in the development environment, Dataphin reports an error that the table already exists when you click Create.
   	Policy for missing production table	The policy to apply when the production table does not exist. You can select Do Nothing or Automatic Creation. The default is Automatic Creation. If you select Do Nothing, the production table is not created when the node is published. If you select Automatic Creation, a table with the same name is created in the target environment when the node is published. Do Nothing: If the target table does not exist, a message is displayed when you submit the node, but you can still publish it. In this case, you must manually create the target table in the production environment before you can execute the node. Automatic Creation: You must edit the table creation statement. The creation statement for the selected table is filled in by default, which you can modify. The table name in the creation statement uses the placeholder ${table_name}. Only this placeholder is supported. It will be replaced with the actual table name during execution. If the target table does not exist, it is created according to the creation statement. If the table creation fails, the check fails during publishing. You can modify the creation statement based on the error message and try to publish again. If the target table already exists, the creation statement is not executed. Note This parameter is supported only in projects in Dev-Prod mode.
   	Loading Policy	Select the policy for writing data to the target table. Append data (insert into): If a primary key or constraint violation occurs, a dirty data error is reported. Update on primary key conflict (merge into): If a primary key or constraint violation occurs, the data of the mapped fields is updated on the existing records.
   	Write-through	The primary key update syntax in an Oracle database is not an atomic operation. If the data to be written contains duplicate primary keys, you must enable write-through. Otherwise, parallel writing is used. The performance of write-through is lower than that of parallel writing. Note This parameter is supported only when Loading Policy is set to Update on primary key conflict.
   	Batch write data volume (Optional)	The amount of data to write in a single operation. You can also set Batch write count. When writing, the system writes data when either limit is reached. The default is 32 MB.
   	Batch write count (Optional)	The default is 2048 records. When data is written, a batch writing strategy is used. The parameters include Batch write count and Batch write data volume. When the accumulated data reaches either of the set limits, the system considers a batch to be full and immediately writes it to the destination. We recommend setting the batch write data volume to 32 MB. Adjust the batch write count based on the size of a single record. A larger value is generally better. For example, if a single record is about 1 KB and you set the batch write data volume to 16 MB, set the batch write count to a value greater than 16,384 (16 MB / 1 KB). If you set it to 20,000 records, the system will write a batch each time the data volume reaches 16 MB.
   	Preparation statements (Optional)	The SQL script to execute on the database before data import. For example, to ensure continuous service availability, you can create a target table Target_A before the current step writes data. The step writes data to Target_A. After the step finishes writing, rename the service table Service_B to Temp_C, rename Target_A to Service_B, and then delete Temp_C.
   	End statements (Optional)	The SQL script to execute on the database after data import.
   Advanced Configuration	Logon timeout	If the logon time exceeds the specified duration, the system automatically disconnects and reports an error. Unit: seconds (s). Default: 600 s.
   	Query timeout	If the query time exceeds the specified duration, the system automatically disconnects and reports an error. Unit: seconds (s). Default: 1800 s.
   Field Mapping	Input Fields	Displays the input fields based on the output of the upstream component.
   	Output Fields	Displays the output fields. You can perform the following operations: Manage Fields: Click Manage Fields to select output fields. Click the icon to move a field from Selected Input Fields to Unselected Input Fields. Click the icon to move a field from Unselected Input Fields to Selected Input Fields. Batch Add: Click Batch Add to configure fields in JSON, TEXT, or DDL format. To configure in JSON format, for example: // Example: [{ "name": "user_id", "type": "String" }, { "name": "user_name", "type": "String" }] Note name indicates the name of the imported field, and type indicates the field type after import. For example, "name":"user_id","type":"String" imports the field named user_id and sets its type to String. To configure in TEXT format, for example: // Example: user_id,String user_name,String The row delimiter separates the information for each field. The default is a line feed (\n). Semicolons (;) and periods (.) are also supported. The column delimiter separates the field name from the field type. The default is a comma (,). To configure in DDL format, for example: CREATE TABLE tablename ( id INT PRIMARY KEY, name VARCHAR(50), age INT ); Create Output Field: Click + Create Output Field, enter a Column name, and select a Type. After you configure the current row, click the icon to save.
   	Mapping	You can manually map fields based on the upstream input and the target table fields. Quick Mapping includes Map by Row and Map by Name. Map by Name: Maps fields that have the same name. Map by Row: Maps fields in the same row. Use this when the field names in the source and target tables are different, but the data in the corresponding rows needs to be mapped.

9. Click Confirm to complete the configuration of the Oracle output component.