We had this same problem. Make sure you check the two following things, both of which pertain to Oracle. 1.) If you are using a remote Oracle database convert the DB instance to store all CLOBS in-row. BMC has a white paper on how to do this - if you can't find it support can get it for you. You also have the change the ar.conf file. 2.) Make sure your db cursor-sharing is set and matches the configuration you have in your ar.conf cursor-sharing. Search the list here for that term and you'll find plenty of information. William Rentfrow Principal Consultant, StrataCom [EMAIL PROTECTED] O 952-432-0227 C 701-306-6157
________________________________ From: Action Request System discussion list(ARSList) on behalf of Joe DeSouza Sent: Thu 9/11/2008 11:21 AM To: arslist@ARSLIST.ORG Subject: Re: Fwd: Incident Management 7.x Slow ** Can you take an AL and Filter log including an SQL log and see if the system is performing any searches to a form that might have a large number of records? Also what about your thread settings? Have you configured your Fast and List threads appropriately? What database are you on? MS-SQL?? If so have you backed up and truncated your transaction logs? These are the few things that come to my mind.. Cheers Joe D'Souza Remedy Developer / Consultant, Shyle Networks, New Jersey. ----- Original Message ---- From: Koyb P. Liabt <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, September 11, 2008 12:12:59 PM Subject: Fwd: Incident Management 7.x Slow ** Forgot to mention - this hanging when submitting tickets to Incident Management also happening in Production - and there has not been any customizations to the Production Incident Management application - its straight out of the box. -----Original Message----- From: [EMAIL PROTECTED] To: ARSLIST@ARSLIST.ORG Sent: Thu, 11 Sep 2008 12:06 pm Subject: Re: Incident Management 7.x Slow We have maybe 23 records in Incident Management because it still new. We have not done much at all in terms of customization. I created one permission group and one active link that is disabled. -----Original Message----- From: Joe DeSouza <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thu, 11 Sep 2008 11:52 am Subject: Re: Incident Management 7.x Slow ** Whats the size of your system? Meaning number of records etc? Any customizations? I would check on things like indexes.. Maybe some customizations you have done runs a bad search? Joe D'Souza Remedy Developer / Consultant, Shyle Networks, New Jersey. ----- Original Message ---- From: Koyb P. Liabt <[EMAIL PROTECTED]> To: arslist@ARSLIST.ORG Sent: Thursday, September 11, 2008 11:43:12 AM Subject: Incident Management 7.x Slow ** Hello all, We are on ITSM 7.0.3, patch 7. We are having issues with the Incident Management application only. When the user presses SAVE to create the ticket - it takes 5 minutes to process the transaction, and then the error message comes back and says: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully : server XYZ The process does not hang when submitting tickets via Asset, or Change Management. I generated logs and nothing jumped out. I noticed the latency happens when modify an incident record ticket also. Is there some bug with Incident Management? __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"