Oracle Environment Preparation (Independent Log Parser)

  • Last update: January 30, 2026
  • Overview

    Version

    FineDataLink VersionFunctional Change
    5.0.5.1

    Supported raw log parsing for Oracle databases used as the source end of real‑time pipeline tasks or real-time tasks.

    Application Scenario

    1. XStream and LogMiner, the two CDC modes of Oracle databases, consume hardware resources of the source database. Database slowdowns may occur if the hardware resources are insufficient to support business updates, affecting the operation of related business systems.

    2. If the source database handles frequent business updates, the parsing speed of LogMiner may be slow, causing:

    • Significant data delays

    • Real-time synchronization failures and costly recovery: If log parsing consistently lags behind log generation, logs may be purged before being parsed as the retention period is exceeded, causing real-time synchronization to fail. Recovery via full and incremental synchronization is often prohibitively costly.

    Function Description

    Raw log parsing is now available in real-time tasks and real-time pipeline tasks when you read data from Oracle databases, which can reduce the performance impact on the source database during log parsing while increasing the overall parsing speed.

    Prerequisite

    This function is available in FineDataLink only with a V5.0 license and a registered Oracle (Independent Log Parser) function point.

    Procedure

    Installing the Parser

    Contact technical support to obtain the parser installation package. For details about how to contact technical support, see Technical Support Channel Introduction.

    Enabling LogMiner-Based CDC

    For details about the procedure, see Oracle Environment Preparation (LogMiner).

    Assigning Database User Privileges

    Create a database user and grant necessary privileges.

    1. Create and configure a tablespace for the schema containing the tables to be synchronized. Skip this step if the tablespace already exists. In this example, the tablespace is named TBLS1. Set the initial data file size to 100 MB, enable auto‑extension, and set each extension increment to 100 MB.

    iconNote:
    You can customize the tablespace name.
    ALTER SESSION SET CONTAINER = XEPDB1;
    CREATE TABLESPACE TBLS1 DATAFILE SIZE 100M AUTOEXTEND ON NEXT 100M;
    ALTER TABLESPACE TBLS1 FORCE LOGGING;

    2. Create a user with the username USR1, password USR1PWD, and assign the TBLS1 tablespace (which will host the schema containing the tables to be synchronized).

    Grant the user USR1 an unlimited storage quota on the TBLS1 tablespace.

    iconNote:
    You can adjust the username, password, and tablespace name based on actual conditions. This user account will later be used to configure the Oracle data connection.
    CREATE USER USR1 IDENTIFIED BY USR1PWD DEFAULT TABLESPACE TBLS1 TEMPORARY TABLESPACE TEMP;
    ALTER USER USR1 QUOTA UNLIMITED ON TBLS1;

    3. Grant privileges to the user USR1.

    GRANT CONNECT TO USR1;
    GRANT RESOURCE TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.CCOL$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.CDEF$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.COL$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.DEFERRED_STG$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.ECOL$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.LOB$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.LOBCOMPPART$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.LOBFRAG$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.OBJ$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.TAB$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.TABCOMPART$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.TABPART$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.TABSUBPART$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.TS$ TO USR1;
    GRANT SELECT, FLASHBACK ON SYS.USER$ TO USR1;
    GRANT SELECT ON SYS.V_$ARCHIVED_LOG TO USR1;
    GRANT SELECT ON SYS.V_$DATABASE TO USR1;
    GRANT SELECT ON SYS.V_$DATABASE_INCARNATION TO USR1;
    GRANT SELECT ON SYS.V_$LOG TO USR1;
    GRANT SELECT ON SYS.V_$LOGFILE TO USR1;
    GRANT SELECT ON SYS.V_$PARAMETER TO USR1;
    GRANT SELECT ON SYS.V_$STANDBY_LOG TO USR1;
    GRANT SELECT ON SYS.V_$TRANSPORTABLE_PLATFORM TO USR1;
    GRANT SELECT, FLASHBACK ON XDB.XDB$TTSET TO USR1;
    DECLARE
    CURSOR C1 IS SELECT TOKSUF FROM XDB.XDB$TTSET;
    CMD VARCHAR2(2000);
    BEGIN
    FOR C IN C1 LOOP
    CMD := 'GRANT SELECT, FLASHBACK ON XDB.X$NM' || C.TOKSUF || ' TO USR1';
    EXECUTE IMMEDIATE CMD;
    CMD := 'GRANT SELECT, FLASHBACK ON XDB.X$QN' || C.TOKSUF || ' TO USR1';
    EXECUTE IMMEDIATE CMD;
    CMD := 'GRANT SELECT, FLASHBACK ON XDB.X$PT' || C.TOKSUF || ' TO USR1';
    EXECUTE IMMEDIATE CMD;
    END LOOP;
    END;

    Configuring the Oracle Data Connection

    Configure the independent log parser when configuring the Oracle data connection, as shown in the following figure.

    Setting ItemDescription
    Log Read Method

    Oracle archived logs and online redo logs may be stored either on a standard file system or within Oracle ASM.

    You must configure corresponding attributes based on the log storage method so the independent log parser can access the log files.

    Options include Remote File Mounting and ASM.

    Directory Mapping Rule

    This setting is only required when Log Read Method is set to Remote File Mounting.

    This is because when archived logs are mounted to the parser server, their access paths are likely different from the original paths on the source server.

    For example, an Oracle archive log was in /opt/olr/recovery_area/o1_mf_1_123456_abcde.arc.

    After being mounted, its actual path on the parser server becomes /oracleA/recovery_area/o1_mf_1_123456_abcde.arc.

    In this case, you must configure a mapping rule to map the original log path to a parser-accessible path.

    Multiple mapping rules are supported.

    If no mapping rules are configured, the parser will attempt to access logs using the original path. If logs cannot be found, the capture task will report an error.

    ASM Configuration

    The following settings are only required when Log Read Method is set to ASM.

    Developing the Task

    Real-Time Pipeline Task

    Set Read Mode in a real-time pipeline task to  Independent Log Parser, as shown in the following figure.

    Real-Time Task

    Set Read Mode in a real-time task to  Independent Log Parser, as shown in the following figure.

    附件列表


    主题: Real-Time Pipeline
    Previous
    Next
    • 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