Good day...we are experiencing problems with a custom report we created in Oracle Reports to be used in OTM. The purpose of the report is to gather a list of vouchers created within specific dates (usually 2-3 weeks worth) and also to be used to run daily voucher reports - a report showing vouchers created for one specific day.
The report itself works fine and because of the volume of data we deal with, we created a materialized view for this report which improved performance (takes about 10 seconds to retrieve the results). When running the report SQL direct against the DB (using PL/SQL Developer), we get all the results we expect and can export it to a csv file. We then try to do the same using the report in OTM and although we get html results, when we try to export to excel it fails.
Upon investigating this and contacting Metalink, Oracle determined that there was too much data being passed to the report and OTM or Oracle Reports could not handle it. So we cut the date parameter to just one day but even that did not work. A typical report run for 2 weeks of vouchers can return over 35,000 rows of results. Even one day of vouchers can produce 2,500 rows of data of which there is 61 columns in the report.
The issue occurs when we attempt to export to Excel which causes a new window to open but we never get prompted to save it or open it - it eventually times out. Doing this outside of OTM works fine. Oracle says they cannot provide a fix for this as it is our custom report causing this issue.
Can anyone offer any assistance here?
Thanks
The report itself works fine and because of the volume of data we deal with, we created a materialized view for this report which improved performance (takes about 10 seconds to retrieve the results). When running the report SQL direct against the DB (using PL/SQL Developer), we get all the results we expect and can export it to a csv file. We then try to do the same using the report in OTM and although we get html results, when we try to export to excel it fails.
Upon investigating this and contacting Metalink, Oracle determined that there was too much data being passed to the report and OTM or Oracle Reports could not handle it. So we cut the date parameter to just one day but even that did not work. A typical report run for 2 weeks of vouchers can return over 35,000 rows of results. Even one day of vouchers can produce 2,500 rows of data of which there is 61 columns in the report.
The issue occurs when we attempt to export to Excel which causes a new window to open but we never get prompted to save it or open it - it eventually times out. Doing this outside of OTM works fine. Oracle says they cannot provide a fix for this as it is our custom report causing this issue.
Can anyone offer any assistance here?
Thanks
Comment