I think the max is about 2 minutes. However, maybe increasing the timeout is not the solution but trying to figure out why it takes so long to close\update 1500 tickets. Check your SQL logs and see where it is spending most of its time. You did not mention whether the process actually completes; do all 1500 tickets get closed even when you get the timeout?
On Dec 13, 2007 8:45 AM, Conrad Pereira <[EMAIL PROTECTED]> wrote: > ** Hi, > > Does anyone know how to increase the database timeout? I have some > workflow where there is one parent ticket and 1500 child tickets on the same > form. The resolution of the parent ticket must resolve all the associated > child tickets. I get the following error > > ARERR [92] Timeout during database update -- the operation has been > accepted by the server and will usually complete successfully : <Server > Name> > > The database is Oracle. Does anyone know how to solve this error? > Although it completes the update of all records I want to get rid of this > error. > > Regards, > Conrad > __20060125_______________________This posting was submitted with HTML in > it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
