cancel
Showing results for 
Search instead for 
Did you mean: 

XDB Replication Error: Machine1:Port:Schema, skipping it from Synchronize replication!

Adventurer

XDB Replication Error: Machine1:Port:Schema, skipping it from Synchronize replication!

  Hi All,

we have 4 node MMR xDB repliacation (v6.2).  Master node is out of replication now. Below is the snipped pubserver log file. Have you ever seen this error before?

Best regards.

Baki.  

 

Jan 20, 2019 9:15:47 PM com.edb.replication.backend.ReplicationHandler performPullReplication
SEVERE: An error occurred against target Master node Machine1Smiley TongueortSmiley Frustratedchema, skipping it from Synchronize replication!
Jan 20, 2019 9:15:58 PM com.edb.replication.backend.RepDataLoadTask call
SEVERE: An error occurred while performing conflict detection against target Master node 'Machine1Smiley TongueortSmiley Frustratedchema'.
Jan 20, 2019 9:15:58 PM com.edb.replication.backend.RepDataLoadTask call
SEVERE: Reason: {0}
com.edb.replication.common.RepException: Bad value for type int : 2156663675
at com.edb.replication.backend.ConflictController.detectConflicts(ConflictController.java:1193)
at com.edb.replication.backend.RepDataLoadTask.call(RepDataLoadTask.java:180)
at com.edb.replication.backend.RepDataLoadTask.call(RepDataLoadTask.java:33)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.edb.util.PSQLException: Bad value for type int : 2156663675
at com.edb.jdbc.PgResultSet.toInt(PgResultSet.java:2756)
at com.edb.jdbc.PgResultSet.getInt(PgResultSet.java:1989)
at com.edb.jdbc.PgResultSet.getInt(PgResultSet.java:2403)
at org.apache.commons.dbcp.DelegatingResultSet.getInt(DelegatingResultSet.java:275)
at org.apache.commons.dbcp.DelegatingResultSet.getInt(DelegatingResultSet.java:275)
at com.edb.replication.backend.ConflictController.detectConflicts(ConflictController.java:1034)
... 6 more

Tags (1)
3 REPLIES
EDB Team Member

Re: XDB Replication Error: Machine1:Port:Schema, skipping it from Synchronize replication!

Hi Baki,

 

The reported error was fixed in xDB-6.1.3. However, As you are still facing the issue can you kindly share below details:

1. Exact xDB version from xDB console.

2. Table structure on which the error is occurring and the scenario(i.e. while creating the table/while inserting the data) when it is occurring. 

3.  Exact steps to reproduce the issue from your end.

4. Complete Pubserver logs.

    Note: You can use below link to upload the logs :

   https://enterprisedb.sharefile.com/r-r130f704f4ae4678a

5. And the output of below queries :

1> select a.pub_id, b.table_id from _edb_replicator_pub.rrep_publication_tables a,
_edb_replicator_pub.rrep_tables b where a.table_id = b.table_id and b.schema_name = 'schemaname' and b.table_name = 'tablenameOnwhichErrorIsOccuring';

2> select * from _edb_replicator_pub.rrep_common_seq ;

The above information will help us to understand the issue in details.

 

Warm Regards,

Dhananjay

Adventurer

Re: XDB Replication Error: Machine1:Port:Schema, skipping it from Synchronize replication!

Hi Dhananjay,

1.6.2.3 

2. Sorry i cannot find the which table gets error on replication? Could you show us?

3. Replication is not running. After restarting xDB service, we see that master node is out of sync. another 3 node is working.

4.i uploaded the complete pubserver log.

5. We dont know which table caused this error. How can we find the table stopping replication?

 

Thank you so much.

Community Manager

Re: XDB Replication Error: Machine1:Port:Schema, skipping it from Synchronize replication!

This post is now being handled by a private support option to ensure appropriate attention. Further communication is pending.

Other comments from the PGR community members are still welcome to be added here.

PGR Administration