OMS全量+增量传输数据 卡在全量数据初始化中

[kill9]

由于业务调整需要把oceanbase一部分表进行迁移至MySQL的操作
进行oceanbase->mysql全量+增量
OMS版本:社区4.2.3
oceanbase版本:社区4.2.2.0
mysql版本:8.0.20

其中 libobcdc.log
libobcdc.log (527.3 KB)
store.log (357 字节)
congo.log (16.4 KB)
日志中有明显报错 但我不知如何解决 请大佬们解答

2
[2025-08-28 16:26:09.068469] ERROR issue_dba_error (ob_log.cpp:1875) [11777][][T0][Y2D09AC11200D-0000000000300001-0-0] [lt=41][errcode=-4388] Unexpected internal error happen, please checkout the internal errcode(errcode=-4016, file="ob_log_start_lsn_locator.cpp", line_no=928, info="request start lsn from all server fail")
3
[2025-08-28 16:26:09.068507] EDIAG [TLOG.FETCHER] get_result (ob_log_start_lsn_locator.cpp:928) [11777][][T0][Y2D09AC11200D-0000000000300001-0-0] [lt=37][errcode=-4016] request start lsn from all server fail(tls_id={tenant_id:1012, ls_id:{id:1}}, start_tstamp_ns=1756297316397904000, svr_cnt=3, svr_list_consumed=3, result_svr_list_idx=-1, svr_list=[{svr:"172.17.0.3:2882", rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-9026, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y2D09AC11200D-0000000000501F89-0-0}, {svr:"172.17.0.11:2882", rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-4233, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y2D09AC11200D-0000000000601F89-0-0}, {svr:"172.17.16.5:2882", rpc_executed:true, rpc_err:0, svr_err:0, ls_err:-9026, start_lsn:{lsn:18446744073709551615}, start_log_tstamp:18446744073709551615, trace_id:Y2D09AC11200D-0000000000701F89-0-0}]) BACKTRACE:0x1860ef10 0x9c403b5 0x9d5df6d 0x9d5d99f 0x9d5d8e8 0x9bbaae7 0xc3ce420 0xc1f73e6 0xc18233a 0xc181723 0xc180b78 0xc25e86f 0x7f99eda1bea5 0x7f99ed035b0d
4
[2025-08-28 16:26:09.068545] ERROR issue_dba_error (ob_log.cpp:1875) [11777][][T0][Y2D09AC11200D-0000000000300001-0-0] [lt=37][errcode=-4388] Unexpected internal error happen, please checkout the internal errcode(errcode=0, file="ob_log_ls_fetch_ctx.cpp", line_no=933, info="start lsn locate fail")

[周雄]

clog被回收了，ob有没有开启归档
ob系统租户下执行这个，查询一下位点
WITH palf_log_stat AS (
SELECT
tenant_id,
MAX(begin_scn) AS palf_available_start_scn,
MIN(end_scn) AS palf_available_latest_scn,
SCN_TO_TIMESTAMP(MAX(begin_scn)) AS palf_available_start_scn_display,
SCN_TO_TIMESTAMP(MIN(end_scn)) AS palf_available_latest_scn_display
FROM GV$OB_LOG_STAT
WHERE tenant_id & 0x01 = 0 or tenant_id = 1
GROUP BY tenant_id
),
archivelog_stat AS (
SELECT
a.tenant_id AS tenant_id,
MIN(b.start_scn) AS archive_start_scn,
a.checkpoint_scn AS archive_latest_scn,
a.checkpoint_scn_display AS archive_available_latest_scn_display
FROM CDB_OB_ARCHIVELOG a
LEFT JOIN CDB_OB_ARCHIVELOG_PIECE_FILES b
ON a.tenant_id = b.tenant_id AND a.round_id = b.round_id
AND b.file_status != ‘DELETED’ AND a.STATUS = ‘DOING’
GROUP BY a.tenant_id
)
SELECT
pls.tenant_id,
pls.palf_available_start_scn,
pls.palf_available_latest_scn,
pls.palf_available_start_scn_display AS palf_available_start_scn_display,
pls.palf_available_latest_scn_display AS palf_available_latest_scn_display,
als.archive_start_scn AS archive_available_start_scn,
als.archive_latest_scn AS archive_available_latest_scn,
CASE WHEN als.archive_start_scn IS NOT NULL THEN SCN_TO_TIMESTAMP(als.archive_start_scn) ELSE NULL END AS archive_available_start_scn_dispalay,
als.archive_available_latest_scn_display
FROM palf_log_stat pls
LEFT JOIN archivelog_stat als ON pls.tenant_id = als.tenant_id
GROUP BY pls.tenant_id, pls.palf_available_start_scn;

[kill9]

tenant_id	palf_available_start_scn	palf_available_latest_scn	palf_available_start_scn_display	palf_available_latest_scn_display	archive_available_start_scn	archive_available_latest_scn	archive_available_start_scn_dispalay	archive_available_latest_scn_display
1	1,752,746,449,379,608,004	1,756,373,087,564,623,000	2025-07-17 18:00:49.379608	2025-08-28 17:24:47.564623	[NULL]	[NULL]	[NULL]	[NULL]
1,002	1,754,681,951,663,025,078	1,756,373,087,367,434,002	2025-08-09 03:39:11.663025	2025-08-28 17:24:47.367434	[NULL]	[NULL]	[NULL]	[NULL]
1,012	1,756,359,033,356,266,005	1,756,373,087,403,358,000	2025-08-28 13:30:33.356266	2025-08-28 17:24:47.403358	[NULL]	[NULL]	[NULL]	[NULL]
1,016	1,756,360,632,937,259,005	1,756,373,087,461,558,000	2025-08-28 13:57:12.937259	2025-08-28 17:24:47.461558	[NULL]	[NULL]	[NULL]	[NULL]

您好结果如上

[周雄]

增量同步的位点必须在palf_available_start_scn_display之后
clog被清理了，ob也没有开启归档。这种情况得重新建任务全量+增量了，或者是把增量位点改到palf_available_start_scn_display后面。增量同步ob要把归档打开

[kill9]

好的谢谢 我去找找怎么开启归档

[Sunshining]

学习一下