Stack limit error when creating job with DMT

2012-12-01 Thread Victor
Hello Listers, When creating a job from the Data Management Job Console the process timed-out with Timeout during database update -- the operation has been accepted by the server and will usually complete successfully : ONC/RPC call timed out (ARERR 92) . The arerror.log showed the following

Re: OFFLIST - Incident Submitter and License terms - Dear BMC have you mislead us?

2012-12-01 Thread Wallace, Kelvin
We run a customized Incident app here and we allow anyone to modify – but when they do, it triggers a notification (to the assigned tech) of the changes. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Sent: Friday, November 30, 2012 4:57

Re: Stack limit error when creating job with DMT

2012-12-01 Thread Tauf Chowdhury
Victor, I think you should really consider going to 64 bit for this fresh installation. Arserver processes have been chewing up more and more memory every version and with version 8, I don't see it changing. Since you have the full ITSM stack, you are probably getting this error because of your 32

Re: Remedy archiving methods

2012-12-01 Thread Vishal Navale
Thanks Vaibav. Do you know how to delete the data from database? How to find out all relationships for IM/CM/PM/SRM/SLM etc Data is huge and we want to delete from database. Thanks Vishal On Thu, Nov 29, 2012 at 11:43 PM, vaibhav wadekar wadekar.vaib...@gmail.com wrote: ** DSO is one of the

Re: Remedy archiving methods

2012-12-01 Thread Kulkarni, Vikrant
hi Vishal, And to find the relationship between objects we can always enable object relationships on the test servers and find out the relations of each form. Once that's done we can use this list of forms for DSO mappings and data transfers. Using a time ranged escalation you can delete the

Re: Stack limit error when creating job with DMT

2012-12-01 Thread Kulkarni, Adhwari
Hi Victor, This kind of error is usually observed when you are creating the first job using the 'job console'. That is the time when the UDM engine builds the complete dependency data required for UDM to work which takes a lot of resources. Do you see the same error while creating all the jobs?