5/7/2024 2:35:48 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
|
|
|
|
Cancelling sync transactions?
Posted: 13 Jun 06 11:24 AM
|
fiogf49gjkf0d I have a client on SLX 6.1.2 with 25 remote users. They have a nightly process that inserts/updates sales information from their mainframe into some custom tables via Scribe. Normally there are around 800 records that get imported, however this past weekend due to an error in the export from the mainframe there were over a million records (ouch!). Many of the changes were simply overwrites of existing rows in SLX with the same data. This has put a big hurt on syncing. Sooooo...
I need a good way to clear these erroneous transactions from the system, or at least stop them from syncing out, without having to re-cut 25 databases. On the downside, 8 of the users have synced at least once since "the incident", but not all of the transactions have been processed yet. We had thought about exporting legit changes to the main database, restoring from backup, ditching the wglogs, and re-inserting the legit changes, but I'm afraid that will just wind up hosing things even more. Another option, of course, is to just let the sync process continue as normal, but some of the users are or will be looking at 12+ hours of syncing to slog through everything.
Does anyone have any recommendations on the best way to handle this situation? Many thanks in advance!
|
|
|
|
Re: Cancelling sync transactions?
Posted: 13 Jun 06 1:30 PM
|
fiogf49gjkf0d Assuming that the imports happened in the middle of the night when nothing else was happening on the system, then the wglogs created would contain only the unwanted transactions, and the outfiles that were created for the remotes would also contain only the unwanted transactions. So you can delete the TEF files from OUTFILES and ARCHIVES (archives has a copy of TEFs in outfiles and must be deleted). This will effectively cancel things.
It will take several host/remote syncs to clear things up but here is what will happen...
-The remotes will sense the missing TEFs and ask for replacements (note: you will need to sync the remote a 2nd time to send the request to the syncserver).
-The syncserver will receive the request and look in archives for the missing files. When it does not find the file it will send a dummy files (which are empty) to the remote.
-The remote will pick the dummy files, process them and proceed with life as if it had gotten the real TEFs.
|
|
|
| |
|
Re: Cancelling sync transactions?
Posted: 16 Jun 06 12:14 PM
|
fiogf49gjkf0d I just got confirmation this morning that the transactions had been cleared out and everything is working well. Your solution did the trick - thanks for the help! |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|