Skip to main content
📓 Tibero Online Manual Click here 📓

Search

Welcome to Tibero GTS!

Constraints When Building Oracle Prosync

Document TypeㅣTechnical Information

CategoryㅣInstallation

Applicable Product Versionsㅣ 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 5SP1FS01, 5SP1FS02, 5SP1FS03, 5SP1FS04, 5SP1FS06, 6FS01, 6FS02, 6FS03, 6FS04, 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02

Document NumberㅣPINTI001

 

Overview

When building Oracle Prosync, it is not possible to build in an RAC environment using ASM and CDB structures. Additionally, various constraints related to synchronization such as DML, DDL, and data types are described.


 

Method

Caution

In ASM environments, Redo/Archive Logs cannot be read, so building is only possible in ACFS environments.

CDB environments are not supported; building is only possible in Non-CDB environments.

 

DML Synchronization Constraints

DML synchronization is not supported for the following tables and structures.
  • Materialized View
  • Clustered tables, Indexed Organized tables (IOT) (when Source DB is Oracle), encrypted tables (when Source DB is Oracle), compressed tables (when Source DB is Oracle)
  • Data included in dynamically created partitions by the DB when Interval Partitioning is applied to the target table and the range is not specified
  • DML on tables with NOLOGGING option enabled
  • Tables with names starting with BIN$
  • External tables, Global Temporary tables

Note

DML recorded with the same transaction ID by DDL triggers may be skipped during extraction by the log reader.

When multi-updating columns with PK or Unique Key defined, some rows may not be synchronized.

 

DDL Synchronization Precautions

DDL synchronization is performed on a per-DB basis, and the schema of the target must be explicitly specified in the DDL statements as shown below.
CREATE TABLE TEST_TABLE_2 ... foreign key (c1) references [schema must be specified].TEST_TABLE_1(c1)

 

Client Tool Installation

For synchronization between Oracle and Tibero, both client tools (tbsql, SQLPLUS) must be installed.

 

Supported Oracle Data Types

  • VARCHAR2, NVARCHAR2, NUMBER, FLOAT, LONG, DATE, TIMESTAMP, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND, RAW, CHAR, NCHAR, CLOB, NCLOB, BLOB
  • NUMBER, CHAR, VARCHAR, RAW, DATE, TIME, TIMESTAMP INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND, LONG, BLOB, CLOB, NCHAR, NVARCHAR, NCLOB
Note
NUMBER type synchronization supports up to 38 digits only.
  • BINARY_FLOAT, BINARY_DOUBLE, GEOMETRY, TIMESTAMP WITH TIMEZONE
 

DDL Rule

When the Source DB is Oracle, '%' (wildcard) cannot be used in [DDL OPERATION] and [DDL OBJECT].
Supported Types)
  • CREATE / ALTER / DROP : TABLE / INDEX / VIEW
  • TRUNCATE : TABLE
 

SAM File

In TAC/RAC environments, the SAM FILE feature cannot be used.
Supported Types)
  • NUMBER, CHAR, VARCHAR, DATE, TIME, TIMESTAMP, INTERVAL YEAR TO MONTH, INTERVAL DAY TO SECOND, CLOB
 
 
 

Related to