修改flysync.ini
安装
服务启动成功
BINAR搬迁后精度丢失
2.
2.
分析:这是v2v2版本问题
解决:安装v2r2c4版本 后成功安装
分析:host文件没配对
解决:配置host文件
分析:一个节点部署了两个拓扑,资源不够用了
解决:删除一个拓扑后正常
解决:源端目标端kufl不对应,在服务管理模块,重置源端
分析:图形界面没加这个过滤条件
property=replicator.extractor.dbms.tablePatterns 进行表过滤,FSTEST_430.*,TEST.T2 表示同步。FSTEST_430 模式下所有表和TEST 模式下T2 表多个规则采用逗号(,) 分割
解决一:在flysync.ini文件里面添加表过滤条件。
解决二:图形化部署勾选tableParttern过滤
这三个地方不能输入空格,建议使用trim()去空格
Table20个; 数据1.6GB; 主键约束20个; 索引5个; view5个,存储过程5个,
图: KES中一张表的字段图:
ddlscan -target.service s_kes_3112 -source.user system -source.pass abc123 \
-source.db HGC_O -source.dbtype kingbase8 -source.host 10.12.14.132 \
-source.port 54321 -source.tables hgc.TABLE4 \
-target.db mydevelop -mgType 0
ddlscan -target.service s_kes_3112 -source.user system -source.pass abc123 \
-source.db HGC_O -source.dbtype kingbase8 -source.host 10.12.14.132 \
-source.port 54321 -source.tables hgc.TABLE5 \
-target.db mydevelop -mgType 0
ddlscan -source.service m_kes_3113 -source.user system -source.pass abc123 \
-source.db HGC_O -source.dbtype kingbase8 -source.host 10.12.14.132 \
-source.port 54321 -source.tables hgc.TABLE6 \
-target.db mydevelop -source.rmiHost 10.12.14.132 -source.rmiPort 11000 \
-target.service s_kes_3112 -mgType 2
loader -source.user system -source.pass abc123 -source.db HGC_O \
-source.dbtype kingbase8 -source.host 10.12.14.132 -source.port 54321 \
-source.tables hgc.TABLE4 -target.service s_kes_3112 \
-mgType 0
loader -source.service m_kes_3113 -source.user system -source.pass abc123 \
-source.db HGC_O -source.dbtype kingbase8 -source.host 10.12.14.132 \
-source.port 54321 -source.tables hgc.TABLE5 \
-source.rmiHost 10.12.14.132 -source.rmiPort 11000 \
-target.rmiHost 10.12.14.132 -target.rmiPort 11000 \
-target.service s_kes_3112 -mgType 1 –clean
loader -source.service m_kes_3113 -source.user system -source.pass abc123 \
-source.db HGC_O -source.dbtype kingbase8 -source.host 10.12.14.132 \
-source.port 54321 -source.tables hgc.TABLE6 \
-source.rmiHost 10.12.14.132 -source.rmiPort 11000 \
-target.service s_kes_3112 -mgType 2 -clean
构建错误:
1.修改flysync.ini,在源端添加新模式
2.更新文件,下线服务
replicator stop
fspm update
replicator start offline
3.搬迁出错
4.查看错误日志,目标端不存在err模式
5.在目标端数据库新建err模式,进行二次搬迁,成功了!
日志:
Unable to prepare plugin: class name=com.kingbase.flysync.replicator.filter.RenameFilter message=[Invalid definition, use "-" on the right side to identify objects that are not changed: hgc.*.* -> hgc.-.-]
解决:模式一样,不添加映射 hgc,*,*,hgc,-,-
文档写的命令不全 (少-service 目标端服务)
| [ - main] INFO ddlscan.DDLScanWorker Connect to source database with url: jdbc:kingbase8://10.12.14.132:54321/HGC_O
| | [ - main] INFO database.AbstractDatabase Loading database driver: com.kingbase8.Driver
| | [ - main] ERROR ddlscan.SourceDDLScanWorker Please put the target service collection result information to "/home/flysync/service.json"
| Fatal error: Please put the target service collection result information to "/home/flysync/service.json"
| inital data migration of null ignore all tables
解决 fsrepctl -service s_kes_3112 properties > service.json
地址:
/FTP/数据库/内部版本/KingbaseFlySync/daily-build/V2R2C4/V002R002C004B20230607