If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Scheduling - some reports are empty

Started by Ziid, 14 Jan 2013 02:40:44 AM

Previous topic - Next topic

Ziid

Hi

I am currently working at a customer that has loads of reports that are scheduled in jobs (approx 300 report views devided on approx 50 jobs). The biggest workload is around 1-3 january each year when many schedules are running. During the rest of the year I havent found any bigger issues.

Sometimes during the "new year scheduling period" (I see no pattern) some reports are empty when e-mailed... I have the setting "All at once" and all jobs have priority 3.

Empty reports - anyone with the same problem?

Regards,

Ziid

RKMI

Hi Ziid,

When you say some reports are empty sounds more like the report view is gathering the incorrect set of data. Are you getting the same result when you create a new report view with the same parameters as in your current schedule?

Have you checked the underlying report view to see if you might have a date prompt filter or other filters might be restricting the data which might require an update such as if you are pulling member of 2012 and now being 2013 you need to update to the new member set... if its the case then all you need to do is update the report and the corsponding report views with correct parameters can kick off the schedule again.

Thanks,
RK

MMcBride

Ziid
Unfortunately I think this is a bug in the Report process...
My situation is slightly different but I have seen the same results.

I have a burst that writes approx 15,000 PDF files to a shared file system - roughly 10% of them come across 'blank'
I have the burst ID set on Agent Number - we run this process monthly.

Each month different Agents are missed, when you run the exact same report without the burst and filter down to the specific Agent number in question it runs perfectly fine and returns the expected results.

I thought perhaps it was something in my burst process causing this but I have gone over the logs in detail and see no errors...
We have a group of 60 or so Agency Managers that manage all of the Agents and our current work around is when they find a PDF that is blank they re-run the PDF manually.

If it was the same Agents each month, or if we could replicate the issue running the exact same report manually I would feel alot more comfortable with this.

I don't think it's a cube issue, I  think there is something going on when writing the PDF that is broken, but to be honest I am lost on this and I haven't found a way to fix this as of yet...

cognosonthefly

Hey all,

I know it´s been a while since this thread was started, but is there any solution for this problem? I currently face the same situation: I burst a report to around thousand instances, many of the reports were correct, but in some of them there are just elements missing (e.g. a list is empty). If I execute the report again for the same instance manually, it works fine. I tested several bursting configurations, but no make no breakthrough...

Thanks for ideas!