This topic describes the FAQ and considerations of OceanBase Change Data Capture (obcdc).
Why can't I synchronize tables with LOB columns?
The current version does not support synchronizing tables with LOB columns. If the target table contains LOB columns (such as TEXT, BLOB, and JSON), obcdc cannot synchronize the change data of that table.
How do I determine if the startup timestamp is too small?
obcdc allows you to configure a log-pulling point in time. obcdc pulls logs that are committed later than this point in time, which is referred to as the startup timestamp.
Considerations
- obcdc supports cluster-level (multi-tenant) synchronization. When logs are synchronized in the entire cluster, make sure that the clocks on all machines are synchronized. Otherwise, a significant Global Timestamp Service (GTS) time difference between tenants may cause obcdc to exit due to the rollback of a safe checkpoint. For the current obcdc 4.x version, we recommend that you configure obcdc to synchronize the data of only one tenant at a time.
- At present, obcdc does not support synchronizing the data of a cluster that has a standby tenant.
- Logs can be consumed completely offline only when
fetching_log_mode=directandmeta_data_refresh_mode=data_dict. In other mode combinations, obcdc must send requests to the OBServer node, so you must configure the parameters for accessing the OBServer node, includingcluster_urlorrootserver_list.
Limitations for startup timestamps
When obcdc pulls data of a single tenant, if the pulling timestamp is too small, obcdc may fail to start. The following limitations apply:
Startup timestamp limitations for synchronizing the data of a single tenant
When
fetching_log_mode=integratedArchiving is disabled
The startup timestamp specified for obcdc must be greater than the largest
BEGIN_SCNvalue of all log streams of the tenant. You can execute the following SQL statement in the tenant to query this checkpoint:SELECT CEIL(MAX(BEGIN_SCN)/1000) AS START_TS_US FROM oceanbase.GV$OB_LOG_STAT;Archiving is enabled
The pulling timestamp specified for obcdc must be greater than the smaller of the following two values:
The largest
BEGIN_SCNvalue of all log streams of the tenant.The value of
START_SCN, which indicates the time when archiving is enabled for the tenant. You can execute the following SQL statement in the tenant to query this time:SELECT CEIL(MAX(START_SCN)/1000) as START_TS_US FROM oceanbase.DBA_OB_ARCHIVELOG;
When
fetching_log_mode=direct, only single-tenant synchronization is supported. Make sure that the startup timestamp of obcdc is later than the point in time when log archiving is enabled.If you use the data dictionary mode, make sure that the startup time is greater than the smallest
snapshot_scnvalue in the data dictionary of the tenant. You can execute the following SQL statement in the tenant to query the smallestsnapshot_scnvalue:SELECT CEIL(MIN(snapshot_scn)/1000) FROM oceanbase.DBA_OB_DATA_DICTIONARY_IN_LOG;Note
You can also specify
tenant_idin the sys tenant to query theoceanbase.CDB_OB_DATA_DICTIONARY_IN_LOGview.
Startup timestamp limitations for synchronizing the data of multiple tenants
When you pull the data of multiple tenants in a cluster, make sure that each tenant meets the preceding single-tenant conditions at the specified startup timestamp.