Hi,
I happened to delevlop a report and then clicked With Run options in Cognos Connection . I was using the burst functionality and submitted the report. Then I went to Tools - > Schedule Management and then checked the status of the report.It showed as "Executing"
Meanwhile I received the e-mail of the burst report .So I assume the report has run successfully. But why is that the Schedule Managerment still shows the status as "Executing".?
How to get rid of this ?
Please help me to get out of this.
Thanks
I actually have a ticket with Cognos about the same issue in 8.2. We deployed packages but it was taking hours for the update to change from Executing to Successful.
For the moment, unless anyone knows the reason for the error, I would assume that after a certain expected period time, that the job completed.
If you do find out the root cause, please share as we are curious ourselves.
Thanks and good luck.
Specifically to bursting, the email may be sent even before finishing all the report sets.
For example, if the burst creates 400 reports, the status is still executing after finishing 200 reports and if the receiver is supposed to get the report that is already finished, he may get the email before all the 400 reports are bursted.
But as suggested above, if the status is 'executing' after hours, may be a bug in application.
To resolve the issue of the executing status never changing to successful, do the following:
1.) Stop all C8 Services
2.) Find the appropriate NC_DROP script for your content store, this is found under ../configuration/schemas/delivery/<dbtype>/NC_DROP_*.sql
3.) Execute this script against your content store
4.) Verify the NC_ tables were successfully droped from the Content Store
5.) Start all C8 services
6.) Verify the NC_ tables were successfully recreated
7.) Re-test burst/import
8.) If this does not resolve it, a full content store export will need to be done and the content store will need to be deleted and recreated using the backup.
Has this been tried? If so, I'm game and will give it a go.
I have had to actually perform these steps for several of my customers. In my experience i have only really noticed this issue when my customers upgrade from one major release to another (e.g 8.1 BI to 8.2 BI).