Pending, Pending, Pending
Issue: While I was away for vacation, there was a problem in our IBM Cognos 8.1.2 Content Store DB and so the D/W administrator had to bounce it. Due to some reason, all the scheduled reports stopped working and were going to pending state. In fact, we could not even run the reports in the background with "Save As" option. The reports were running fine manually. I found a couple of solutions to this problem as follows:
Issue: While I was away for vacation, there was a problem in our IBM Cognos 8.1.2 Content Store DB and so the D/W administrator had to bounce it. Due to some reason, all the scheduled reports stopped working and were going to pending state. In fact, we could not even run the reports in the background with "Save As" option. The reports were running fine manually. I found a couple of solutions to this problem as follows:
- Renew the credentials for the user who owns the schedules (Thats simple..)
- Restart Cognos Services (Wow!)
- Increase the "CONTENT_STORE"."NC_TASK_QUEUE"."SCHEDULE_TYPE" from 6 to 15 (:|)
- Change the SYN attack protection to "disabled" (:})
- Run the NC_DROP script. (hmmm..)
Cause: Possibly some corrupt tables in the CS related to Scheduling...or maybe......
Well, after trying option 1 & 2, I was left with no choice but to opt for option 5. Most of the forums discussed about option 5 and how it was the most obvious path to follow. Even though some warned that this is not the permanent solution and the issue might come back :[
IBM also recommends this at http://www-01.ibm.com/support/docview.wss?uid=swg21371279
Result: Smooth script run, smooth start of cognos services and.........the schedules have all started working :)
Hurray!
Well, I would definately appreciate other cognosers out there to give their opinion on this, after all I am just a cogmesser who started in the desert ;)
Note: "If dropping the NC* tables does not resolve the issue then restore the content
store from the latest backup version." - IBM Technote
