03-19-2014 02:20 AM
we have an issue regarding the incident management modules, incidents take too much time to be saved. it might take up to 50 seconds on save or save $ exit and sometimes it times out.
have done some indexing on the database level, but still have this issue.
any one experiencing the same issue, would appreciate your help.
03-19-2014 03:43 AM
There might a script written which is taking alot of time to execute.
You can put print statements in format control of "probsummary", "im.update.incident".
You may also check the triggers which are associated with "probsummary" table.
03-19-2014 11:02 PM
Add more indexes on database will reduce the performance of “Save” operations. It is better to find out the bottle-neck before made changes to them.
Please research the SM log with level "rtm:3", and you might find which script/table is slow.
03-19-2014 11:48 PM
Many reasons may result in this problem, like, ir corrupt, calculate outage record, a specific script, a specific table...
Suggest to get a debug of "RTM:3" "debugdbquery:999". We may need to get more detailed debug after this one is reviewed.
Yan Tong (Serene), HP Software Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution; and give kudo if you like it :)
04-01-2014 03:32 AM
thank you all for your suggestions.
I have been facing such performance issue for some time now, I first started by adding indexes on some fields in the database, but that did not help a lot specially when it comes to the "Saving".
as being recommened by HP Support engineer, I have removed the field "update.action" from the probsummary IR Keys, that really helped and reduced the consumed time significantly.
what also helped is that I archieved and purged a big deal of the records.