symmetricds：マスターノードのsym_dataテーブルがいっぱいですが、sym_data_eventが空です

Question

masterノードの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) 

Answer 1

SymmetricDSは、エンジンが動作していないようです。 sym_dataテーブルにデータベース・トリガーが設定されていれば、対称エンジンは実行する必要はありません。しかし、データイベントと送信バッチテーブルに対称エンジンを実行し、抽出データをルーティングする必要があります。

Answer 2

sym_data_eventの行は、「ルーティング」ジョブを実行するときにSymmetricDSエンジンによって生成されます。これは、sym_dataテーブルの最後に新しい行を探し、それらをバッチに割り当てます。ルーティングが実行中であることを確認してください。これは、ログまたはsym_lockテーブルで確認できます。

ルーティングでは、sym_data_gapテーブルをsym_dataへのポインタとして使用します。 SymmetricDSを停止し、sym_data_gapからすべての行を削除してから、もう一度起動してください。これによりsym_dataのすべてが処理され、まだルーティングされていないデータが特定され、正しいsym_data_gapが再構築されます。

ところで、postgresqlログのエラーは、通常、SymmetricDSの起動時に、そのテーブルに行を挿入してそのデータが確実に入力されるようにするために発生します。