As Frank said to tune the query. Make sure that the field on the child records you are searching by is indexed (i.e. If you have a Parent Record ID field that ties the records together, make sure it is an index).
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Tuesday, July 15, 2008 6:29 AM To: [email protected] Subject: Re: ARERR 395 ** Understand ... I would then try and tune that query to run faster. Updating 32 records should not take 1 minute. Are you utilizing indexes on the second form? Is it possible that updating the second form is triggering updates on another form (form C)? Note:The longer you make the time out the worse performance could get for other users of the system as this process is blocking a database thread. On Tue, Jul 15, 2008 at 2:12 AM, Muhammed, Siraj <[EMAIL PROTECTED]> wrote: ** Hi Frank, API process triggers with an ACL from a primary form on a record say like record-A and check for all corresponding child record of record-A in secondary form and make a status change based on status of primary record-A and selected child records. It checkes all the child records and do the change in same process. Mostly there are multiples child records come around 32. (it takes approximately a minute for completing entire process) We use get entry and set entry api calls in this process This operation works when child records are less than 32 and gives error when child records are more than 32. Regards, Siraj ________________________________ From: Action Request System discussion list(ARSList) on behalf of Frank Caruso Sent: Mon 7/14/2008 9:11 PM To: [email protected] Subject: Re: ARERR 395 ** What is the API process doing? It appears you are blocking waiting for the call to return (an active link that is using a SetFields PROCESS action). uping the Fitler timeout is not going to help. You need to tune the external process call. On Mon, Jul 14, 2008 at 8:46 AM, Muhammed, Siraj <[EMAIL PROTECTED]> wrote: ** Dear Listers, Getting this error "ARERR [395]" The System has timed out while waiting for a process that is running on the server to return a value." This happens when an Active Link which calls the API script, which in turn updates another Form, is triggered. We have increased the Filter API time out to 180 but no hope. Please share your experiences if any one met this error before. Server ARS-5.12 DB- Oracle 8.1.2 OS- Solaris 8 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
