On Linux I look at the “ardist.log.default” log file to see the error. <DIST> Processing item number 2 (Wed Jul 02 2014 16:02:00.8825) <DIST> Pending Type -- 5 <DIST> Source Form -- MyForm <DIST> Source ID -- 000000000622195 <DIST> Pending Other -- <DIST> -e 000000000622195 -s MyForm -x MyArSvr <DIST> Perform delete (skipping from stage 1 to stage 7) <DIST> Using EXISTING cache definition for MyForm (MyArSvr) <DIST> ** ERROR ** Entry does not exist in database (ARERR 302) <DIST> ** ERROR ** Failure during delete attempt (Wed Jul 02 2014 16:02:00.9154) <DIST> ** ERROR ** Next stage: 7 (Perform mapping), Status: CANCEL (Wed Jul 02 2014 16:02:00.9155) <DIST> ** ERROR ** Pending distributed operation canceled due to error-pending entry 000000000622195, schema MyForm (Wed Jul 02 2014 16:02:00.9512) <DIST> Delete pending item -- 000000001184251 <DIST> Sleeping for 60:00 minutes (Wed Jul 02 2014 16:02:00.9609) <DIST> Get a list of items to process (stage 0) (Wed Jul 02 2014 17:02:00.4678)
In this case someone deleted the record (000000000622195) on the form (MyForm) that was supposed to be pushed before the DSO process could happen Fred From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Hicox Sent: Friday, August 22, 2014 9:41 AM To: arslist@ARSLIST.ORG Subject: Re: How to move stucked Distributed Transfer Pending records quickly ** It's possible that DSO is encountering an error (such as out of range values, index violations, workflow exceptions etc). The problem is that DSO logging is horrid, and in lots of cases will give no indication of a problem like that. One way I've worked through problems like this in the past, is to Export one of the stuck records to an arx file, and try to manually import it to the target arserver with the data import tool. This is a fairly decent analog to what DSO is doing, except it won't hide errors from you like DSO will. If you're really stuck, it might give you a clue anyhow. -Andy On Friday, August 22, 2014, Chetan Shinde wrote: ** Check the logical server defined server in the distributed logical mapping form. Since u have restored the Prod DB on the Dev DB that must be still referring to the prod Corp ITSM server Regards, Chetan Shinde On Fri, Aug 22, 2014 at 2:46 PM, onkar shinde wrote: ** Thanks Chetan, for your prompt reply. We already had restarts of AR server yesterday. Still will give one more shot. Any other better idea ? Thanks Onkar On Fri, Aug 22, 2014 at 2:32 PM, Chetan Shinde wrote: ** If they are stuck in Pending form, try restarting the AR Server service. Regards, Chetan Shinde On Fri, Aug 22, 2014 at 2:13 PM, onkar shinde wrote: ** Hello All, We have refreshed ARSystem Dev env. with Prod. DB backup. After pointing to the appropriate Dev Destination Servers in Logical mapping, we have got lot of records in DSO Distributed Pending form. (approx. 60K) The User records created on Source server are still stuck in Pending Form and not transfer on Target server yet since last 4-5 days. The Transfer Definition on User form is When To Update: Immediately Transfer, Transfer Mode: Independent Copy, Duplicate Request ID Action: Overwrite, Enforce Pattern Matching: Yes Require Required Fields: Yes, and Match by Request ID. Retries: Forever. We have 7 distributed Pools defined, and User DSO Mapping belongs to Pool 4 which has polling interval of 15 mins. The records are stuck and not moving on to the target, Kindly suggest as this is blocking us in doing further actions. Thanks in advance. -- Regards, Onkar Shinde Senior Software Engineer Vyom Labs Pvt. Ltd. BSM Solutions & Services || ITIL Consulting & Training Telephone: +91-20-6632-1000<tel:%2B91-20-6632-1000> Mobile: +91-7709008719<tel:%2B91-7709008719> Email: onkar.shi...@vyomlabs.com<javascript:_e(%7B%7D,'cvml','onkar.shi...@vyomlabs.com');> Web: www.vyomlabs.com<http://www.vyomlabs.com> _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"