Large Objects
-
BINARY -
IMAGE -
TEXT -
UNITEXT -
VARBINARY
Limitations of Support
-
TEXT,UNITEXTandIMAGEare supported up to 2 GB in length. -
Large objects that are replicated from other databases (such as Oracle
BLOBandCLOB) can be mapped to SybaseCHAR,VARCHAR,BINARY, andVARBINARYcolumns. To prevent Replicat from abending if the replicated large object is bigger than the size of the target column, use theDBOPTIONSparameter with theALLOWLOBDATATRUNCATEoption in the Replicat parameter file. For more information, see Reference for Oracle GoldenGate for Windows and UNIX. -
To move data to a Sybase target from a source database that permits empty
LOBcolumns, use theDBOPTIONSparameter with theEMPTYLOBSTRINGoption in the Replicat parameter file. This parameter accepts a string value and prevents Replicat from setting the target column toNULL, which is not permitted by Sybase. For more information, see Reference for Oracle GoldenGate for Windows and UNIX. -
When a source table contains multiple identical rows, it can cause
LOBinconsistencies in the target table. This occurs when the source table lacks a primary key or other unique row identifier. The rows are inserted by Replicat on the target, but if theLOBdata is updated in a subsequent source operation, it will only be replicated to the first row that was inserted on the target. -
Do not use
NOT NULLconstraints on the in-row LOB column. If you want to useNOT NULLconstraints, use them on the off-row LOB column. -
If you need to fetch the in-row LOB data directly from the table you must use
FETCHCOLS/FETCHMODCOLS. -
Oracle GoldenGate for Sybase 15.7 does not support the in-row LOB column replication (however, it can still push the data into the in-row LOB column at in the Replicat database). This means tables included in the replication cannot have any in-row LOB columns. Oracle GoldenGate will abend if any replication table includes an in-row LOB column. If you need in-row LOB support, contact Oracle Support for further information.