Hi Kaye! There are lots of factors that can slow DSO down but your biggest issue is the 200000 records. In addition to looking at indexing on the pending table take a long look at all the different cases that are triggering a DSO record. In particular, make sure that any filter that fires on merge includes
AND $USER$ != "Distributed Server" So you don't go back and forth between servers. Doug -- Doug Blair Sent from my iPhone4, typographic errors likely +1-224-558-5462 On Sep 26, 2010, at 8:23 PM, Kaye Bernales <[email protected]> wrote: > ** > Hi List, > > We are running on AR System 6.3 (Solaris - Sybase). We've recently been > having problems with DSO process. The DSO queue grew up to more than 200k > records and process seems to always die. AR Monitor doesn't seem to be > restarting it. The process slowed down and we got to a point where it only > processes 1000 records per hour. We tried restarting the Remedy service and > it made processing faster - however, after a few hours, it started slowing > down again. > > There are no problems with Database nor Unix servers. > > Any ideas why DSO process keeps on dying and how we could get more > information? > > Thanks! > Kaye > NOTICE > > The information contained in this email is confidential. If you are not the > intended recipient, you must not disclose or use the information in this > email in any way. If you received it in error, please tell us immediately by > return email and delete the document. We do not guarantee the integrity of > any e-mails or attached files and are not responsible for any changes made to > them by any other person. > > > > _attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
