That should be the setting on a production server anyway. Unless code is changing, why have the client check to see if it did?
Rick On Apr 2, 2013 1:55 PM, "Greg Donalson" <cdonal...@slb.com> wrote: > Hi Jamie, > > I have received a hotfix from BMC that is supposed to fix the cache > corruption. I plan to apply this next week to see if it helps. But the > way that I am getting by without having to flush the cache as much is to > turn off the Perform Check of the Definition Change Check Interval within > the MidTier settings on the Cache Settings page. This has made a world of > difference for me and have not had any corruption since. The only time you > would need to worry about this is if you are making changes in production > and in that case you would just need to flush the cache for everyone to see > the changes, unless of course they are just filter/escalation changes and > then you do not need to flush the cache. > > Greg > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] On Behalf Of Jamie > Sent: Tuesday, April 02, 2013 3:42 PM > To: arslist@ARSLIST.ORG > Subject: Re: Remedy 7.6.04 -Corrupt Cache / Corrupt Fields > > Jayesh - Are you referring to ARS or ITSM? We are on ARS 7.6.04 SP3 and > ITSM 7.6.04 SP2 and we are facing the same issues of cache corruption and > having to flush the cache almost every other day. > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
