For SQL statements about Oracle databases:
If you enclose table names in double quotes, table name matching is case-sensitive.
If you do not enclose table names in double quotes, table name matching is case-insensitive, where table names will be converted to uppercase by default for matching.
After configuring the data source, you can use it in Scheduled Task. For details, see Overview of Scheduled Task.
From FineDataLink V4.2.7.4, Transaction Control is available when the target end is an Oracle database.
After configuring the data source, you can use it in Data Service. For details, see Overview of Data Service.
After configuring the data source, you can use it in Real-Time Task. For details, see Overview of Real-Time Task.
1. Setting Incremental Sync Start Point to Custom Time is supported from FineDataLink V 4.2.11.4 when the source end is an Oracle database with Read Mode and Synchronization Type set to LogMiner and Incremental Synchronization Only, respectively, as shown in the following figure.
The earliest selectable time (left boundary) for the custom time range is the minimum of the following two values:
The earliest time of the capture task events for this database in the data-sharing center
The earliest time of the database logs
2. The check items of Data Source Permission Check have included Active Transaction Check if the source end is an Oracle database since FineDataLink V4.2.11.4.
When the earliest start time of all currently active transactions is earlier than the earliest log time, the check result displays an alert, with the message: "The start time of a currently active transaction predates the earliest available archive log, which may cause synchronization failures. Resolve the active transactions manually. The ID of the abnormal transaction is as follows: Transaction ID list."
3. From FineDataLink V5.0.5.1, row log parsing is supported if the source end of a real-time task is an Oracle database. For details, see Oracle Environment Preparation (Independent Log Parsing).
After configuring the data source, you can use it in Real-Time Pipeline. For details, see Overview of Real-Time Pipeline.
1. If you want to read data from a pluggable Oracle database (PDB) using pipeline tasks, modify the database in this data connection to the corresponding PDB.
2. To use Oracle databases in FineDataLink pipeline tasks, you must enable supplemental logging at all levels. For details, see Oracle Environment Preparation. However, supplemental logging does not supplement log information for fields of the LOB or LONG data type.
Therefore, in FineDataLink pipeline tasks with Oracle databases, fields of the following data types are automatically excluded from synchronization: BLOB, CLOB, NCLOB, LONG, RAW, LONG RAW, and BFILE
3. Source table fields of the BLOB, CLOB, NCLOB, LONG, RAW, LONG RAW, and BFILE data types are marked as deleted in the field mapping area and cannot be manually mapped. During task execution, these fields will not be used for synchronization or table creation.
1. In FineDataLink of versions earlier than V4.2.11.3, field mapping can only be adjusted when the target table is first configured. From V4.2.11.3, modifying field mapping is supported. For details, see Real-Time Pipeline Task Management.
2. From FineDataLink V4.1.1, synchronization without a primary key is supported if the source end is an Oracle database.
4. Setting Incremental Sync Start Point to Custom Time is supported from FineDataLink V 4.2.11.4 when the source end is an Oracle database with Read Mode and Synchronization Type set to LogMiner and Incremental Synchronization Only, respectively, as shown in the following figure.
5. From FineDataLink V5.0.5.1, row log parsing is supported if the source end of a real-time pipeline task is an Oracle database. For details, see Oracle Environment Preparation (Independent Log Parsing).
From FineDataLink V4.2.10.4, the data destination of scheduled pipeline tasks supports Oracle databases. For details, see Scheduled Pipeline Overview.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy