Clear Log of Multiple Instance jobs
Moderators: chulett, rschirm, roy
Clear Log of Multiple Instance jobs
Hi to all,
I have two multiple instance jobs that are executed daily 300 times each. That means that 600 hundrends instances are created daily in the director making it very difficult to trace it. Is it possible to delete these automatically without loosing the log records that is under the main job?
Thanks in advance
I have two multiple instance jobs that are executed daily 300 times each. That means that 600 hundrends instances are created daily in the director making it very difficult to trace it. Is it possible to delete these automatically without loosing the log records that is under the main job?
Thanks in advance
The 'official' answer is to recompile the base job, that will remove all instances of the invocation runs from the Director but not clear the log information. This can be problematical, however, if it is read only as most people have their production jobs, I would think.
Unofficially, there's been some discussion here but I don't recall if anyone came up with a viable option. I remember that issuing a 'Clear Status File' from the Director on an instance will remove it from the list but don't know off-hand how one would do that programmatically. Besides, I'm sure you'd prefer to pull the trigger once rather than 300 times.
Perhaps others will have some suggestions...
![Confused :?](./images/smilies/icon_confused.gif)
Unofficially, there's been some discussion here but I don't recall if anyone came up with a viable option. I remember that issuing a 'Clear Status File' from the Director on an instance will remove it from the list but don't know off-hand how one would do that programmatically. Besides, I'm sure you'd prefer to pull the trigger once rather than 300 times.
Perhaps others will have some suggestions...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I would turn on the automatic clearing of logs after 3 runs instead of days or something like that. That will help.
I posted a SQL statement which will delete RT_STATUSnnn records using instance id. Search for this post. I will post the link if you cannot find it. I know Director slows down a lot when you have this many instances.
I posted a SQL statement which will delete RT_STATUSnnn records using instance id. Search for this post. I will post the link if you cannot find it. I know Director slows down a lot when you have this many instances.
Mamu Kim
But the log records are accumulated under main job only. The 300 instance are just the representation of it.without loosing the log records that is under the main job
You may use something like
Code: Select all
DELETE RT_LOGnnn where EVAL "@ID" NOT LIKE '//%'
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'