June 23, 200619 yr Newbies Not sure if anyone has encountered this scenario before but someone may have an idea as to a solution: - we have a number of FMS hosted FMv6 files that get updated every night by an ODBC import from a set of Paradox table from an external app - works fine unless FMS starts a cache flush and tries to pause a file that is in the middle of an ODBC import - if this happens the FMS seizes up with an application error stating that it could not pause the file due to an outstanding database lock - only way out is to reboot the FMS Our FMS is presently set to flush cache every 40 minutes. It makes sense that it might encounter the above scenario from time to time. So, what I tried to do was: - turn off timed cache flush - setup a scheduled batch to run FMS "Pause" and FMS "Resume" commands in lieu to force the flush. This would run every x minutes during business hours to ensure data gets written effectively. It would not run during the time where the ODBC updates are running, avoiding seizures. This didn't work, didn't see any sign of forced file pauses or resumes and the FMS would hang. Someone suggested that I use a "start/wait" FMS command after the pause command to allow it time to complete before running the resume command. I cannot find any docs about the start/wait command. Questions: - anyone know about this command? - should I expect to see entries in our FMS app log when my substitute/force flush commands run? - what would the consequences be of simply turning off the FMS 'flush cache every x minutes' and letting it flush while idle? Could this cause grief? - does anyone have any other ideas? Thanks
Create an account or sign in to comment