Remedy Server Group issues

Hello everybody, We have Remedy in server group environment. Everytime when we migrate objects to Remedy database locking happens and users are not able to use Remedy. I guess this is due to server sync or cache issue. Remedy documentation suggest couple of points. Anybody has implemented

Re: Remedy Server Group issues

System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jeyaprakash Sent: Friday, November 04, 2011 2:09 PM To: arslist@ARSLIST.ORG Subject: Remedy Server Group issues Hello everybody, We have Remedy in server group environment. Everytime when we migrate objects to Remedy database

FW: Remedy Server Group issues

:16 PM Subject: Re: Remedy Server Group issues Yeah make sure you don't have dev-cache mode switched on. Our Delay-Recache-Time: 300 You also may want to try adding: Select-Query-Hint: NOLOCK Regards, Andrew Goodall Software Engineer 2 | Development Services | jcpenney . www.jcp.com

Re: FW: Remedy Server Group issues

: Andrew C Goodall [mailto:ago...@jcpenney.com] Sent: Friday, November 04, 2011 1:16 PM Subject: Re: Remedy Server Group issues Yeah make sure you don't have dev-cache mode switched on. Our Delay-Recache-Time: 300 You also may want to try adding: Select-Query-Hint: NOLOCK Regards, Andrew

Re: FW: Remedy Server Group issues

-Original Message- From: Andrew C Goodall [mailto:ago...@jcpenney.com] Sent: Friday, November 04, 2011 1:16 PM Subject: Re: Remedy Server Group issues Yeah make sure you don't have dev-cache mode switched on. Our Delay-Recache-Time: 300 You also may want to try adding: Select-Query-Hint

Re: FW: Remedy Server Group issues

, 2011 4:01 PM To: arslist@ARSLIST.ORG Subject: Re: FW: Remedy Server Group issues ** Thanks Andrew, I guess we have to add these parameters in all server ar.conf file. Delay-Recache-Time: 300 Select-Query-Hint: NOLOCK When we set this does all secondary servers (we have 3 secondary