I do it frequently, whenever I refresh my dev from prod.
It doesn't delete or drop any actual schedules but basically just the "quick list" that Cognos uses to know what to run next, so it doesn't have to constantly scour the entire content store. It basically just causes it to rebuilt the "Upcoming Activities" list.
The only downside is all the schedules then have the same Modified date (the date/time you start up after doing the delete), so it makes it hard to determine if it's a schedule that was disabled a LONG time ago or recently.
Most likely your upgrade will change that modified date anyway so it wouldn't hurt to do it yourself.
This is also a fix IBM has you do if you end up with schedules that linger out there still saying executing, Waiting, or generally hanging when they are in fact long done.
Wayne
------------------------------
Wayne Westlake
------------------------------
Original Message:
Sent: Wed April 27, 2022 05:48 AM
From: Vic Nicholls
Subject: Drop NC (Notice Cast) tables when upgrade?
My understanding is that this gets rid of anything that is orphaned, etc. We have used it and have not had to recreate anything.
------------------------------
Vic Nicholls
Original Message:
Sent: Tue April 26, 2022 04:00 PM
From: Michael Sullivan
Subject: Drop NC (Notice Cast) tables when upgrade?
Hi folks,
I'm planning our upgrade to Cognos 11.2 from 11.1.7
Do people out there drop the NC tables when upgrading? I've never done that before but see that IBM suggests it might be good to do. I think these hold schedules, right? Would dropping them mean recreating the schedules manually? On the other hand, would not dropping them mean that the new instance would immediately execute pending or overdue schedules? That may not be ideal either
Thoughts?
Thanks
Michael
--
Michael Sullivan
North Shore Community College
#CognosAnalyticswithWatson