Hi, Sounds like something is seriously wrong...
Mid-Tier has nothing to do with it, as it is a client. Filters are run on the server. I presume that the admin server should signal the other servers to re-cache as soon as the change has been committed to the DB. Best Regards - Misi, RRR AB, http://www.rrr.se (http://www.rrr.se) (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13) * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs Find these products, and many free tools and utilities, at http://rrr.se (http://rrr.se) March 31, 2017 12:24 PM, "Dave Barber" wrote: ** All, We've recently moved our in-house applications from Remedy 7.6 (running on Solaris/Oracle - 2 user facing servers, with one of those handling admin functions) to Remedy 9.1.02 (running on RHL/Oracle - 2 x user facing servers, 1 x admin/integration server). On the "old" servers, we never had any issues with code sync - amend a filter, and it was pretty much updated on both production servers right away. On the new servers, we're experiencing inconsistent delays - amend a filter on the admin/integration server, and it can be anything up to 90 minutes before that filter update is reflected on the other two production servers. Similar issues have been experienced on forms too. The application is not (yet) updated for the mid-tier, so access is still via the WUT. Any suggestions? (We're expecting the mid-tier update to be ready later in the year) Regards Dave Barber _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
