Thanks for your comment, but that would replicate or not replicate full rows, what I want is to replicate all columns except price columns on specific rows, for all other rows I want to replicate all columns.
I want to report that your sugestion had worked well the last two weeks, I changed init.d/SymmetricDS stop) "$JAVA" -jar "$JARFILE" stop rm tmp/*.pid ;; I had not seen any problem in 15 days.
I want to report that your sugestion had workes well the last two weeks, I change initi.d/SymmetricDS stop) "$JAVA" -jar "$JARFILE" stop rm tmp/*.pid ;; I had not seen any problem in 15 days.
I need direction on the requirement to replicate product price conditionally. Let me explain: we have two locations, but some special products are selled with diferent price in each location, so we want to replicate all columns for most products but for some not to replicate sell price. We can add a column to flag products that we do not want the price sell replicated. I need directions with this. Thanks.
This problem persist after declaring dependency on my dbms. How can I test wrapper.pid and server.pid, and delete them if they are wrong ?
Today the problem happened another time, I reviewed the processes and they does not exists. I will try to configure service dependencies between symmetricds and my dbms to see it this solve the problem.
Yes, I followed the documented steps, and as I said, it runs ok most of the days, but sometimes, like today in one of my machines, the service (deamon) does not start automatically, this is the status: SymmetricDS.service - LSB: SymmetricDS Loaded: loaded (/etc/init.d/SymmetricDS; bad; vendor preset: enabled) Active: failed (Result: exit-code) since mié 2017-05-24 09:21:39 CDT; 1h 32min ago Docs: man:systemd-sysv-generator(8) Process: 1252 ExecStart=/etc/init.d/SymmetricDS start (code=exited, status=5)...
I have three machines with Ubuntu 16.04 Desktop, ocasionally SysmmetriDS deamon does not start on power on, neither manually wiht systemctl start SymmetricDS, systemctl status SymmetricDS complains that the service is already started, but that is not true... If I reboot Sysmmetric refuse to start with samee error. To start it, I have to delete tmp/server.pid and tm/wrapper.id, after than all goes fine. This happend every some days. This machines are turnned off every night, I have reviewed all config...