Maneshii

Is there any update?

Is there any update?

Any update on this? Thanks

I noticed there was an additional trigger named as <tablename>_etl_modtime_UT</tablename> only on the tables of the node that triggered initial load correctly. Is there any specific step I missed for not having that on tables of other nodes? Thanks

I attached the symmetric.log herewith. Steps done : 1. Executed create-sym-tables for each engine. 2. Set rev_initial_load_enabled=1 for each node on SYM_NODE_SECURITY in source db. 3. Updated sym_channel, sym_trigger and sym_trigger_router in source db. 4. Then started the service. sudo bin/sym_service.bat stop sudo bin/sym_service.bat uninstall sudo bin/sym_service.bat install sudo ./bin/sym.bat

Any clue on this? Thanks

Any clue on this? I noticed there was an additional trigger named as <tablename>etlmodtimeUT</tablename> only on the tables of the node that triggered initial load correctly. Is there any specific step I missed for not having that on tables of other nodes? Thanks

Any clue on this? I noticed there was an additional trigger named as <tablename>_etl_modtime_UT</tablename> only on the tables of the node that triggered initial load correctly. Is there any specific step I missed for not having that on tables of other nodes? Thanks