Huge DeskI XI R2 report in Infoview

Hi All,

I have one (actually few but tested only one) DESKI report with prompts. The user selected prompt values fetch abt 8 million rows across 7 data providers. The report runs fine in thick client in abt 2.5 hrs and shows the data.

In Infoview I have following scenarios:

  1. Schedule to DeskI (.rep format):
    An instance gets created successfully. However when I open the instance it keeps showing the progress eventually failing with errors like “Page cannot be displayed”, “The document has no reports”, etc

  2. Schedule to Excel, PDF, Text or HTML:
    Fails with the error "Object failed to run due to an error while processing on the Job Server. "

The users need the ability to schedule the report to Excel through Infoview.

Please suggest.

Regards,

Devang


devang808 (BOB member since 2007-05-28)

Any suggestions on the 2 points?


devang808 (BOB member since 2007-05-28)

Hi,
Are you sure that your report runs for 2.5 hours?
If it is then what kinf odata you are showing on the report? becuase this much time is too much.
You may need to tune the queries.


Omkar Paranjpe :us: (BOB member since 2006-02-13)

Hi,

Actually this is a BO 5.0.3 report migrated to XI R2. Difficult to convince the users that the report is inefficient one. Also the 5.0.3 report took the same time and users are fine with it as these reports are used once in 2-3 months.

The problem is Infoview is not able to display the report; neither on VOD nor the scheduled instance. Also schedule to Excel and text files is failing.

I am expecting some configuration changes to help XI R2 handle such reports.

Regards,

Devang


devang808 (BOB member since 2007-05-28)

:crazy_face: :blue: “Inefficient” is an understatement! 8 million records? What on earth are the users doing with it??? Print it and present it to their manager?
Is the report their own datawarehouse on which they filter to find what they need :?:

You’d better start all over on this: plan a session with the user(s) and write down their requirements. Ignore the statements like “we need this like it was” (this is NOT a good specification :cuss: ), but go to the bottom: what they need, how they use it, where do they send the results (if any!?), etcetera.

HenkK


HenkK :netherlands: (BOB member since 2004-03-02)

Hi,
By letting the report run for a long time, you are actually screwing up the database as well.

It’s now your nack that instead of getting the existing report scrapped you can tell them that you are doing something extra.


Omkar Paranjpe :us: (BOB member since 2006-02-13)