Hi All,
I recently cleared out my content store by running the DB2 scripts in ${cognosInstallLocation}\configuration\schemas\content\db2\dbClean_db2.sql
After running these scripts I re-imported our backup of the entire content store (including user accounts).
I have a scheduled job which bursts a report weekly to a number of email recipients, but since the content store was cleared, my recipients are receiving reports from July 2015?! My schedule saves the report outputs, but only ever keeps the latest version. The data people are receiving in their emails doesn't exist any more in the database or the report when it is run manually. When I view the latest report outputs generated by the schedule, this shows completely different information to what the users are receiving.
So far I have:
- Made a copy of the report and saved under a new name.
Created a new job to burst the report.
Scheduled the new job
This has still produced the same result: users are receiving old emails. Even users who no longer feature in the report output are receiving old emails from when they did have data.
I am at a bit of a loose end now, as it would seem that there is a full set of old reports stored somewhere (but not under the report outputs icon next to the report) which are being emailed out, but I don't know where to progress from here.
I have a second report which is also doing the exact same thing as above.
Can anyone help?
Thanks,
Brian
Hmmm... to add further confusion to this, my new jobs didn't weren't actually scheduled properly so the old jobs are still running every week despite me deleting the schedules and them not appearing in Cognos Connection.
I have now deleted the old jobs and old reports.
Sorry to be a nuisance, but can anyone think of a solution to this? My users are still being sent reports from July every Sunday morning at 9am even though the report, burst job and schedules don't exist any more!
As a further update, I updated the email address in Cognos Configuration last week and the problematic reports are still being sent from the old address. New schedules and reports are using the correct sender email address. :o
Well... it turns out is was our DR box that was running alongside our Production environment and was emailing users old data! Problem solved!