View Issue Details

IDProjectCategoryView StatusLast Update
0004355SymmetricDSBugpublic2020-05-21 12:34
Reporterrichard@squarepeg.co.zaAssigned Toelong 
Prioritynormal 
Status feedbackResolutionopen 
Product Version3.11.3 
Target VersionFixed in Version 
Summary0004355: Duplicate Extract Files
DescriptionWhen doing an initial extract on one of the schemas in my database, one of the tables (same one each time) is extracted twice. Result is of course duplicate entries on the receiving database. I have checked that the triggers are only registered once. I have cleaned the TEMP directories.

Here is the sym log show the table is extracted twice:
2020-04-18 10:34:28,819 INFO [home] [DataExtractorService] [home-extract-default-6] Starting request 30385 to extract table medical_exam_work_site into batches 9900016 through 9900037 for node IZIN3DVW.30-9C-23-A1-88-77.3
2020-04-18 10:34:34,415 INFO [home] [DataExtractorService] [home-extract-default-6] Done with request 30385 to extract table medical_exam_work_site into batches 9900016 through 9900037 for node IZIN3DVW.30-9C-23-A1-88-77.3
2020-04-18 10:34:34,416 INFO [home] [DataExtractorService] [home-extract-default-6] Starting request 30386 to extract table medical_exam_work_site into batches 9900038 through 9900059 for node IZIN3DVW.30-9C-23-A1-88-77.3
2020-04-18 10:34:36,422 INFO [home] [DataExtractorService] [home-extract-default-6] Done with request 30386 to extract table medical_exam_work_site into batches 9900038 through 9900059 for node IZIN3DVW.30-9C-23-A1-88-77.3
Steps To ReproduceUnfortunately, I have no way to create this scenario. It just one day started on a database that has been running without issue on the same version for months.
Additional InformationCentOS7, Postgres 9.2
Tagsdialect: postgresql

Activities

richard@squarepeg.co.za

2020-04-18 05:01

reporter   ~0001703

sym queries showing contents of sym_trigger and sym_extract_request for this table.

sym_trigger.csv (965 bytes)
sym_extract_request.csv (2,447 bytes)

elong

2020-05-21 12:34

developer   ~0001719

There are two extract requests for same table, and they have the same load_id and appear to have come from the same table reload request. If you have the trigger associated with multiple trigger routers, it would behave that way. You can see what trigger routers are configure like this:

select * from sym_trigger_router where trigger_id = 'IZIN3DVW/medical_exam_work_site';

Issue History

Date Modified Username Field Change
2020-04-18 04:46 richard@squarepeg.co.za New Issue
2020-04-18 04:46 richard@squarepeg.co.za Tag Attached: dialect: postgresql
2020-04-18 05:01 richard@squarepeg.co.za File Added: sym_trigger.csv
2020-04-18 05:01 richard@squarepeg.co.za File Added: sym_extract_request.csv
2020-04-18 05:01 richard@squarepeg.co.za Note Added: 0001703
2020-05-21 12:34 elong Assigned To => elong
2020-05-21 12:34 elong Status new => feedback
2020-05-21 12:34 elong Note Added: 0001719