They should have the DBA check for any blocking in the db. Also have them check to see if there is any triggers or calls to an outside system that fire on create to this form. I remember a case where a company had a db trigger on insert to the H table of a form (so they could push data to a different system in real-time). It turned out that the outside system had problems and it was causing Remedy to be slow. The Remedy logs showed the same slowness in the ARSCHEMA update.
Fred From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of William Rentfrow Sent: Wednesday, November 04, 2009 12:39 PM To: arslist@ARSLIST.ORG Subject: Looooooooooong update times on ARSCHEMA ** Listers... I was helping a person who contacted me look at a performance problem. I do not have access to the system. It appears the update to ARSCHEMA that is called by the CE API call is taking forever for just ONE record. In other words when this executes: UPDATE arschema SET nextId = nextId + 1 WHERE schemaId = xxx ...it works fine for all but 1 row. Most rows complete in 0.01 seconds or less. The troublesome row update can take 90 seconds or more. I've never seen that. Has anyone else? I thinking rebuilding the indexes on that table is the first thing to try. William Rentfrow Principal Consultant, StrataCom Inc. wrentf...@stratacominc.com<mailto:wrentf...@stratacominc.com> Corporate Website, www.stratacominc.com<http://www.stratacominc.com/> Blog, www.williamrentfrow.com<http://www.williamrentfrow.com/> 715-410-8156 C _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
