symmetricds：主节点中的sym_data表已填满，但sym_data_event为空

时间：2016-10-18 14:31:48

标签： postgresql synchronization symmetricds

我们遇到问题，主节点中的sym_data表填充了数据，但sym_data_event为空，sym_outgoing_batch也为空。日志文件中没有任何错误，对称版本为3.4.2。前一天一切正常，对称配置文件没有改变。

postgresql日志：

23643 1 2016-10-18 17:20:38 MSK [unknown] [unknown]  [unknown] 00000LOG:  connection received: host=192.168.0.111 port=36888
23643 2 2016-10-18 17:20:38 MSK century symmetricds 192.168.0.111 [unknown] 00000LOG:  connection authorized: user=symmetricds database=century
23643 3 2016-10-18 17:20:38 MSK century symmetricds 192.168.0.111 [unknown] 42P01ERROR:  relation "gp_id" does not exist at character 20
23643 4 2016-10-18 17:20:38 MSK century symmetricds 192.168.0.111 [unknown] 42P01STATEMENT:  select gpname from gp_id
23643 5 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 6 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(ROUTE) already exists.
23643 7 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 8 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 9 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PULL) already exists.
23643 10 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 11 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 12 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PUSH) already exists.
23643 13 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 14 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 15 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(HEARTBEAT) already exists.
23643 16 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 17 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 18 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PURGE_INCOMING) already exists.
23643 19 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 20 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 21 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PURGE_OUTGOING) already exists.
23643 22 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 23 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 24 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PURGE_STATISTICS) already exists.
23643 25 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 26 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 27 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(SYNCTRIGGERS) already exists.
23643 28 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 29 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"ф
23643 30 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(PURGE_DATA_GAPS) already exists.
23643 31 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 32 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 33 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(STAGE_MANAGEMENT) already exists.
23643 34 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 35 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 36 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(WATCHDOG) already exists.
23643 37 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 38 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 39 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(STATISTICS) already exists.
23643 40 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 41 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 42 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(FILE_SYNC_PULL) already exists.
23643 43 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 44 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 45 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(FILE_SYNC_PUSH) already exists.
23643 46 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 47 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 48 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(FILE_SYNC_TRACKER) already exists.
23643 49 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 50 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_lock_PK"
23643 51 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (lock_action)=(INITIAL_LOAD_EXTRACT) already exists.
23643 52 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_lock (lock_action) values($1)
23643 53 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_sequence_PK"
23643 54 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (sequence_name)=(outgoing_batch) already exists.
23643 55 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_sequence (sequence_name, current_value, increment_by, min_value, max_value, cycle, create_time, last_update_by, last_update_time) values($1,$2,$3,$4,$5,$6,current_timestamp,$7,current_timestamp)
23643 56 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505ERROR:  duplicate key value violates unique constraint "sym_sequence_PK"
23643 57 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505DETAIL:  Key (sequence_name)=(outgoing_batch_load_id) already exists.
23643 58 2016-10-18 17:20:43 MSK century symmetricds 192.168.0.111 [unknown] 23505STATEMENT:  insert into sym_sequence (sequence_name, current_value, increment_by, min_value, max_value, cycle, create_time, last_update_by, last_update_time) values($1,$2,$3,$4,$5,$6,current_timestamp,$7,current_timestamp)

2 个答案:

答案 0 :(得分：4)

sym_data_event中的行由SymmetricDS引擎在运行“路由”作业时生成。它在sym_data表的末尾查找新行并将它们分配给批处理。确保路由正在运行，您可以在日志或sym_lock表中验证。

路由使用sym_data_gap表作为指向sym_data的指针。尝试停止SymmetricDS，从sym_data_gap中删除所有行，然后再次启动它。这将导致它遍历所有sym_data并确定尚未路由的数据，然后重建正确的sym_data_gap。

顺便说一句，postgresql日志中的错误可能是正常的，并且在SymmetricDS启动期间发生，当它尝试在该表中插入行以确保它已填充时。

答案 1 :(得分：1)

似乎对称引擎无法正常工作。 sym_data表由数据库触发器填充，不需要运行symmetricds引擎。但要填充数据事件和传出批处理表，必须运行对称引擎并路由提取数据

相关问题
最新问题