View Issue Details

IDProjectCategoryView StatusLast Update
0001130SymmetricDSBugpublic2021-08-13 19:34
Reporterrotten Assigned Torudiejd  
Status resolvedResolutionfixed 
Product Version3.3.4 
Summary0001130: can't reload a table under a "*" trigger
DescriptionI have a wild card trigger on a schema in PostgreSQL 9.1, replicating all of the tables in that schema to another, identical PostgreSQL 9.1 database. There are no other SymmetricDS (or otherwise) triggers on tables in that schema.

Today I had a need to reload one of the tables in that schema:

$ ../bin/symadmin reload-table -p -n the_other_node my_table
Log output will be written to ../logs/my_node.log
Reloading table to node 'the_other_node'
An exception occurred. Please see the following for details:
java.lang.RuntimeException: Cannot find history for trigger all_in_my_schema, *
        at org.jumpmind.symmetric.service.impl.DataService.lookupTriggerHistory(
        at org.jumpmind.symmetric.service.impl.DataService.insertReloadEvent(
        at org.jumpmind.symmetric.service.impl.DataService.insertReloadEvent(
        at org.jumpmind.symmetric.service.impl.DataService.insertReloadEvent(
        at org.jumpmind.symmetric.service.impl.DataService.reloadTable(
        at org.jumpmind.symmetric.service.impl.DataService.reloadTable(
        at org.jumpmind.symmetric.SymmetricAdmin.reloadTable(
        at org.jumpmind.symmetric.SymmetricAdmin.executeWithOptions(
        at org.jumpmind.symmetric.AbstractCommandLauncher.execute(

A glance at the history table shows that entries were made for each table's trigger, but no entry was made for the "*" trigger definition itself.

Steps To Reproducereplicate a schema with a "*" trigger and then try to reload an individual table
Tagsinitial/partial load, symadmin



2013-03-20 20:17

reporter   ~0000228

Oh, the work around is to use dbexport/dbimport, which works just fine to reload individual tables, which is why I marked it as a low priority bug.


2021-08-13 18:18

developer   ~0001989

Can you provide the contents of your sym tables, or some more details? I was not able to reproduce by following your steps on the lastest patch of 3.12. It may be that we've fixed the issue since then - let us know if this is still an issue.


2021-08-13 19:30

reporter   ~0001991

I haven't used symmetricds in 5 or 6 years. Sorry, I can't tell if this is still an issue or not. Lets assume you've fixed it, and close this.

Issue History

Date Modified Username Field Change
2013-03-20 20:01 rotten New Issue
2013-03-20 20:17 rotten Note Added: 0000228
2019-04-22 12:57 elong Tag Attached: symadmin
2019-04-22 12:58 elong Tag Attached: initial/partial load
2021-08-13 18:18 rudiejd Note Added: 0001989
2021-08-13 18:19 rudiejd Assigned To => rudiejd
2021-08-13 18:19 rudiejd Status new => feedback
2021-08-13 19:30 rotten Note Added: 0001991
2021-08-13 19:30 rotten Status feedback => assigned
2021-08-13 19:34 rudiejd Status assigned => resolved
2021-08-13 19:34 rudiejd Resolution open => fixed