08-24-2014 08:16 PM - edited 03-14-2019 01:47 PM
Does anyone know if there is any adverse effect for scheduling the loggers purge jobs earlier (Say 12:15am) than the default 12:30am? - ICM 9.0.4
Is there reason Cisco chose 12:30am as the default?
08-26-2014 07:09 AM
it might be assumed that the 12:30 am will be the idle time for call centers and there will be less load on the systems.
sometimes while running purging job SQL runs out of memory, in our setup we have seen SQL memory issue and with we also seen bounce of HLGR process as its not able to write to SQL.
i don't think rescheduling purging will have any adverse effect, but also think of other load parameters while SQL is doing purging.
regards
Chintan
08-26-2014 09:20 AM
Thank you Chintan for your response! We run our ETL just after the purge jobs complete. We want to be able to run this sooner as we are noticing that the ETL is taking longer to run and going beyound the allotted window. I have been looking for a Cisco's document that shows that scheduling the purge jobs earlier does not affect anything. The customer will need this proof when we bring this to them.
08-26-2014 09:44 AM
I was also searching for the same, but unfortunately i did not find any such proof in their documentation for any adverse effect.
Cisco has mentioned below in Installation guide:
they have not given any special Note, so i think you are good to go. if there would be any effect then they would have given some special note like "changing this setting is not supported", hope you are getting what i want to convey.
regards
Chintan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide