Avoid schedules to be launched when restarting the Cognos service

[Sunchaser]

Hi all,
First, best wishes to all for the new year.

Now, maybe a "stupid" question or something easy I missed somewhere in Cognos, let's describe:
. I have a set of report schedules, organized daily between 4.00 AM and 7.00 AM; so 2 ou 3 hours "intensive" where Cognos has to produce, store (file system), send reports, etc .. (then it can go to sleep)
. Last Friday we had to stop all services (reporting, db, etc) for maintenance purposes, and I was able to relaunched everything only on Saturday 31 end of the morning - 11.20 AM.
. Cognos restarted, and gently started to run all report schedules ... but at the same time - originally, all reports schedules are organized in small sub-sets, running every 2 or 5 minutes for example; so that I never had any problem of overload (we have 16gb of memory).
It appeared that this time, while running all schedules at the same time, Cognos was not really happy, "crashed", "blocked",etc.

So, how can I avoid this? It is possible to restart the Cognos service but without having all the schedules running automatically just after?

Thanks
KR,
Vinc.

[New_Guy]

Hi,
No, it is not possible. The only way out of this is to disable all the schedules before bringing the servers down. In the web administration and schedules you can select all the schedules and disable them all in one click. And enable them as required after the restart. Let me know if you find out a way to overcome this.

Thanks

[Sunchaser]

Hi New_Guy,

Thanks for your answer.
Well, this is what I was thinking too, to be honest. I knew that I should have thought about this before, but then I was hoping that there could be a work-around, "in case of ...".
So, next time, I just have not to forget about disabling all schedules.
But, it means that I'm screwed in case of crash of the server for example?
Here in my case, it was intentionally shut down, but in case of a crash and restart of the server (I think it happened one time, don't remember the details), I'll have to restart the Cognos service (if not automatic) and possibly I could face the same issue ...
One thing I'm thinking about in this case is - a "not conventional" way - to first go to the content store at DB level, and find the table storing the report schedules information (CMOBJPROPS2 may be) and update it in order to set all items to "disabled".
But it is not possible everywhere as our installations, we have old Cognos Express with no direct access to the content store at DB level.

Yes, if I find something, I'll post here.

KR,
Vinc

[misscognos]

google script nc_drop_yourDB.sql. understand what it does (there are plenty of technotes that explain) before doing it in prod!

[Sunchaser]

Hi misscognos,

Thanks for the hint, it sounds really good.
From what I can read here:
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014617526
cleaning the NC (Notice Cast) tables could be a good thing, for the situation I was describing.

If I understand correctly, it should prevent then Cognos from re-running all schedules at the same time after the reboot of the server and restart of the Cognos service, and schedules will continue their normal behavior the next day, etc ..

Don't hesitate to let me know if you think I'm missing something important.

Thanks again,
KR,
Vinc.

PS: sorry for the late answer