OceanBase (MySQL) Data Connection

  • Last update: September 10, 2026
  • Overview

    Version

    FineDataLink VersionFunctional Change
    4.2.1.4

    Supported connection to the OceanBase (MySQL) data source, with the following functions available:

    • Data reading and writing using Scheduled Task

    • Data writing using Real-Time Pipeline Task

    • Database Table Management

    • Data Service

    4.2.19.4Supported data writing to the OceanBase (MySQL) data source using Scheduled Pipeline Task.
    4.2.20.2

    Supported data reading from the OceanBase (MySQL) data source using Real-Time Pipeline Task and Real-Time Task.

    Added the OBCDC Wrapper Path setting to the data connection configuration.

    4.2.21.2 and 5.0.14.2Added support for data reading from OceanBase (MySQL) 4.4.2.1 clusters running on ARM64 through Real-Time Pipeline Task and Real-Time Task.

    Function Description

    FineDataLink supports connection to OceanBase (MySQL) data sources for:

    • Data reading and writing using Scheduled Task

    • Data reading and writing using Real-Time Pipeline Task

    • Data writing using Scheduled Pipeline Task

    • Database Table Management

    • Data Service

    • Data reading using Real-Time Task

    Data Connection Configuration

    Prerequisite

    For details, see Overview of Data Connection.

    Version and Driver

    Download the driver package and upload it to FineDataLink. For details about driver uploading steps, see Driver Management. Configure the data connection using either of the following connection schemes.

    iconNote:
    From FineDataLink V4.2.21.2 and V5.0.14.2, data can be read from OceanBase 4.4.2.1 clusters running on ARM64 through Real-Time Pipeline Task and Real-Time Task.
    Supported Database VersionConnection SchemeDriver PackageData Connection URL Example
    OceanBase 4.3.3.1 Enterprise Edition — MySQL Instance
    OceanBase 4.4.2.1 Enterprise Edition — MySQL Instance
    Connection scheme onemysql-connector-java-5.1.47.jarjdbc:mysql://obmt68hdqbmnbh4w.huawei-cn-north-4.oceanbase.cloud:3306/fdl
    Connection scheme twooceanbase-client-2.4.2.jarjdbc:oceanbase://obmt68hdqbmnbh4w.huawei-cn-north-4.oceanbase.cloud:3306/fdl

    Note that:

    1. When uploading a MySQL-type driver provided in connection scheme one, select com.mysql.jdbc.Driver as the driver.

    2. When uploading an OceanBase-type driver provided in connection scheme two, select com.oceanbase.jdbc.Driver as the driver.

    Connection Information Collection

    Collect the following information before connecting FineDataLink to the database:

    • IP address and port number of the database server

    • Database name

    • Username and password of the database

    • Database encoding

    Procedure

    For details about data connection steps, see Data Source Creation and Management.

    Note that when configuring the data connection, you need to select Custom from the Driver drop-down list and select the driver described in the "Version and Driver" section.

    From FineDataLink V4.2.20.2, the OBCDC Wrapper Path setting is added to the data connection configuration.

    Data Source Usage

    Scheduled Task

    Data Reading

    1. Stored Procedure in Configuration Method is unavailable, as shown in the following figure.

    2. When Configuration Method is set to Table Selection, table descriptions are displayed.

    3. Data from this data source can be written to Public Data.

    Data Writing

    1. If it is selected as the data destination, DDL change synchronization is available.

    2. Remark in Field Mapping is available.

    3. Partition Key Setting is unavailable.

    Real-Time Pipeline

    Data Reading

    LOB fields cannot be synchronized.

    1. From FineDataLink V4.2.20.2, data can be read from this data source through Real-Time Pipeline Task.

    2. Partitioned tables can be read.

    3. DDL changes can be synchronized.

    4. Grouped tables can be added.

    Data Writing

    You can write data into this data source using Real-Time Pipeline Task.

    BLOB, CLOB, and NCLOB fields are automatically excluded when data is written to the OceanBase (MySQL) data source through pipeline tasks.

    Data Service

    You can publish data in this data source as APIs using Data Service.

    Database Table Management

    You can view and manage data in this data source using Database Table Management.

    Scheduled Pipeline

    1. You can use Scheduled Pipeline Task to write data to this database, but not to partitioned tables.

    2. Target table names are case-insensitive. The database converts automatically created table names to lowercase according to its naming rules.

    3. DDL change synchronization is not available.

    4. The field mapping rules are as follows:

    Source Table TypeSource Table's Primary KeyTarget Table's Primary Key (Auto Created Table)
    Modification Not Supported
    Target Table's Indexed Field (Auto Created Table)
    Not Displayed
    Fields That Cannot Be UnmappedWrite Method
    Incremental main table__dm_key__dm_key__dm_keySource table's primary key
    • Write data into the target table directly

    • Strategy for primary key conflict: Overwrite data in the target table if the same primary key value exists

    Incremental subtableNoneNone__dm_keyMain table's primary key
    • Update matching records

    • Strategy for primary key conflict: This setting is not displayed because the target table has no primary key. If a conflict occurs, the conflicting data is recorded as dirty data.

    Full main table
    __dm_key__dm_key__dm_keySource table's primary key
    • Write data into the target table after emptying it

    • Strategy for primary key conflict: Overwrite data in the target table if the same primary key value exists

    NoneNoneNoneNone
    • Write data into the target table after emptying it

    • Strategy for primary key conflict: This setting is not displayed because the target table has no primary key. If a conflict occurs, the conflicting data is recorded as dirty data.

    Full subtable (whose main table has no primary key)NoneNoneNoneNone
    Full subtable (whose main table has a primary key)NoneNone__dm_keyMain table's primary key
    • Update matching records after emptying the target table 

    • Strategy for primary key conflict: This setting is not displayed because the target table has no primary key. If a conflict occurs, the conflicting data is recorded as dirty data.

    Real-Time Task

    From FineDataLink V4.2.20.2, data can be read from this data source through Real-Time Task.

    附件列表


    主题: Data Source Configuration
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy