Discoverer Hangs on large export to Excel

Was wondering if anyone had seen this "hang" and had some possible workarounds?
The Discoverer process on the Application Server starts to swallow all of the CPU time and the DBAs much abort the process.
I can export the same report results to a comma-delimited file in about 6 seconds.
Thanks for any help,
Bob Larsen

Hello,
We are also facing the same issue. We recently migrated our Application Server to Linux. After the migration the export from Discoverer Viewer to excel is running very slow. We are trying to export approx 30,000 records. Before the migration to Linux we were using Sun Solaris. We didn't face this problem in that platform. We are using Discoverer 4.1.48.08 and our DB is 10.1.
Any help/solution would be highly appreciated.
Thanks in Advance.
Thanks & Regards,
Badri.

Similar Messages

Discoverer Plus OLAP (D4O) - Export to Excel vs. Open Office

Hej dear experts,
following issue: we`re using D4O (Version 10.1.2.54.25) and have many users, who want to use the "Export to Excel" function.
As we don`t run MS Office, but Open Office, the function "Export to Excel" is not available (greyed out).
I`ve been searching forums and web for any hint, how to use Open Office instead of MS Office for this, but no hits so far.
* associating xls file with Open Office doesn`t help
* extracting the content of d4o.jar gives me the structure, in which I was searching for a kind of configuration file, but no success (expecting xml file?)
Obviously D4O is looking for the "EXECL.EXE" somewhere in the registry?
Has anyone of you experiences or an idea, how to make it work with Open Office?
Any hints and comments highly appreciated!
Thanks,
Thomas

Thanks to a hint from Oracle support experts it`s working now...
D4O checks during startup following keys in the registry:
HKEY_LOCAL_MACHINE\software\Classes\Applications\Excel.exe\shell\Open\command<fileName>
(or)
HKEY_LOCAL_MACHINE\software\Classes\Applications\Excel.exe\\shell\Edit\command <fileName>
I`ve created a registry key:
HKEY_LOCAL_MACHINE\software\Classes\Applications\Excel.exe\shell\Open\command\
(Type: REG_SZ) and entered the path to scalc.exe.
It didn`t work with scalc.exe, but after I`ve copied scalc.exe to excel.exe and changed the registry key to point to it, it works now.
Note: it obviously needs capital letters, so I wrote it like "C:\Program Files\OpenOffice.org 2.0\program\EXCEL.EXE" , with small letters it didn`t do anything.
Now "Export to Excel" is avalible in D4O.
Tested successfully, the only sour note is that graphs are not properly exported or readable by OO, but this may depend on OO version 2.
regards,
Thomas

Syatem will hange if we Export to excell Balance sheet S_ALR_87012284

Warm Greeting !!
Dear group members while exporting Balance sheet report to Spread sheet system gets hanged
we are using GUI Release 720 Final release File version 7200.2.4.1057 Patch level 4
Help me to fix this small issue
Regards
Shamul heq

Hi:
Welcome to SDN,Please try the path....once you executed S_ALR_87012284 then please go to menu...list....export...local file...spreadsheet. Hopefully it will let you download. If it does not get resolved then your BASIS guy will tackle the issue for you.
Regards

Large Export To Excel Fails

In a worksheet ran a statement that selected almost a million rows. Then attempted an export in .xls format. The export didn't even create a .xls file. When a second attempt was made to export in csv format the data file got the column headings, but not any data.
Found a posting on a list that said the java heap size is defaulted at 64MB and that it needed to be increased. But the command given (i.e.: java -Xmx256m -jar sqldeveloper.jar; increasing to 256MB) doesn't appear to work.
Any thoughts? SQL*Developer version is 1.5.1.

To find out exactly what is failing, you can start SQL Developer from <SQLDevHome>\sqldeveloper\bin\sqldeveloper.exe (instead of <SQLDevHome>\sqldeveloper.exe), which will display the JVM console output in a separate window. The error that is occurring should be reported on the console.
theFurryOne

Discoverer Plus4i - Exporting to Excel - Your server is running low

We are currently running Discoverer Plus 4i.
We have a couple of large reports that we want to export to Excel.
We retrieve the report and then carry out the 'Export to Excel' action. The export starts to run but during the 'sort' phase we are getting the error "Your server is running low on virtual memory".
The largest report is currently retrieving about 64K rows but will grow by at least another 20K.
I appreciate we could restrict the retrieval through parameters but we were wondering if anyone had encountered this before and if there are any solutions out there.

Hi,
Any chance any of your items are created using custom functions/packages that return varchar's? If so, check you max char fetched (admin edition - properties tab, each item in folder(s) used by the report). The columns created by custom functions/packages will probably be 4000 characters. Excel doesn't like this. This also slows down your report. Wrap your custom function call in a substr and reduce to the correct size. This might fix your problem.
If you don't use custom functions/packages in this report, oh well, just a thought.
Regards,
Nancy

Export to Excel in Discoverer - Is this a Bug ???

Hi all, thanks for all your helping and sharing thoughts.
I have one issue when exporting to EXcel:-
If you create a calculated field in Discoverer and 1 or more of the values used in the calculation has a NULL value, Discoverer will show a NULL value for the calculated field, which is correct. However when the report is exported to Excel, the calculation for this field is done as if the NULL is a zero causing the calculation to be incorrect. For example:
Ordered_Qty = 20,487
Contract_Amount = NULL
Calculation for new field 'Contract_amt_Remaining' is Contract_Amount - Ordered_ Qty = NULL (since you can not subtract something from nothing , ie NULL - 20,487= NULL) this is fine.
When the new field is exported to Excel the value shows -20,487 as if the Contract_Amt = 0 and not NULL, actually it supposed to show NULL, I don't know why its happening like this.
can anyone help me on this, that would be greatly appreciated.
Thanks in advance,
skat

Hi puppethead,
Thanks for your response,
Here what I am asking is, calculation working fine in Discoverer Plus lik the difference between 2 items, when it is null ie NULL - 3435= NULL this is working well and good in Disc PLUS, but when we export that worksheet to Excel it is giving as ie NULL-3435 = -3435 instead of NULL.
so you guys asking me to use CASE statement in Calculation, but this is not with our calculation part right in Disco Plus, coz we are getting correct result, only when we exporting to Excel getting incorrect value thats it.
Also i tried that CASE statement in calculation, saying syntax error, is that right syntax or not, i used as it is from this post.
Can you make sure that CASE statement is right or not in the above post, do you want me change anything over there, coz I am getting syntax Error.
Thanks again and for your helping.
--skat

Discoverer issues exporting to excel

i'm using OracleBI Discoverer Viewer Version 10.1.2.48.18 and some users claim that when they try to export to excel they get the following message: The exported document no longer exists. An exported document is not maintained after the first download. If you wish to view the document again, please perform the export again.
I'm able to replicate the error but only after I export and then I closed the workbook in excel. If I re-run the report I can export but for the users whith the problem they can not even export the first time.
any idea of what the problem is?

Hi,
I am using Discoverer Viewer .....
Wherein there are few parameters based on which we can drill down to reports
BUT
when i click on Export to Excel option it displayin all d reports one after d other
But can't it display in d same way like hierarchy and allow user to drill down based on parameters
Any suggestions please....
Thanks in Advance

Discoverer 10g unable to export the rows more that 65000 in excel

Hi All,
Earlier discoverer 10g used to export tmore that 65000 rowd data in to excel in multiple sheets. Suddenly it stopped.
Any suggestions
Regards,
Swapnil

What version are you working on ?
is it happen in plus as well as in viewer ?
I just tested the case.
I am on discoverer 10.1.2.55.26 (10.1.2.3 with CP5)
java version 1.4.2_06
I exported a report with ~700K rows
in the excel it exported all the records devided to 65K records in each worksheet
Tamir
Edited by: Tamir-L on Jan 5, 2010 5:11 PM

Discoverer: Export to Excel not working properly on XP sp2

Hi,
In Discoverer, after exporting to Excel the spreadsheet should be displayed automatically. It works fine on Windows 2000, XP sp1, but not on XP sp2.
Any suggestions on how to fix that problem?
Thanks,

Sonal,
Did you try using the context menu to export the results?
I faced the same problem. I could not export using the export functionality but worked when i used the context menu.
Left click on any result area --> Enhanced Menu --> Export to.
hope this helps
Mustafa

Export large field to Excel

I'm attempting to export large field defined as 4000 characters(but not always this size) to Excel. I'm not using the builtin export. I'm using custom csv export. The problem I have is trying to keep the formatting(cr return, line feeds) when data is in excel.

You may want to look at using XML Publisher to create an export to Excel. Perhaps someone else has a good way to do it natively in APEX. In any case you can do some fancy stuff with XML Publisher.
Mike

Export to Excel using URL in Discoverer Plus

Using Discoverer 4i Plus.
Using URL arguments I want to export to Excel automatically. I see that if I was using Discoverer Viewer it would be something like fm=xls. Is there similar code for doing this with Plus?
Thanks!

Maybe it's possible, but I doubt it.
Reason is that you're asking the URL to run the report and then once done export out the values and I just don't think the 'i' - or now 'g' versions support this.
This was why the command line interface with the Desktop version was so popular as this is exactly the kind of thing you can do, plus much more.
I checked the documentation for Plus and can find nothing about doing this in the URL. Maybe someone will say otherwise, but with Plus I don't think it's possible.
Russ

Export to excel formatting

I'm working on a quote report which has narrative sections as well as a table. I can get the report to look great in the application but it has formatting problems once exported to excel.
In one of my narrative reports I have a simple table with a few columns. Once exported to excel the first narrative column is the entire width of the report table below it. The large cell row is also merged cells in excel.
Is there anything that can be done to help force how the report goes into excel?
I have also tried creating the report in a narrative html table to export into excel.

Can someone explain if they face similar issues as I am when you export a report output on portal to Excel it takes huge size. I assume it because of all the color formatting etc. but is there a way to reduce this size. 3.5 Bex Analyzer same report takes only 3 MB while if I export it from portals it takes 32 MB.

Automated exports to excel

is there anyway to have a scheduled report - automatically export to excel and email the attachment to a distribution list?
is there another tool i can use in conjunction with discoverer to get this to work.
pareena

Hi Pareena
Please do the folowing...
1. Install Discoverer on a server/ PC which will never be shut down
2. Install a programm called WINAT (or any other Event scheduler ) also on the server.
3. Create a batch file which will invoke Discoverer, open an wbook and sheet from the databse, execute it and get it to export the result as an EXCEL to a folder on the Server. Sample code is ...
C:\orant\discvr31\DIS31USR.EXE /APPS_GWYUID APPLSYSPUB/PUB /APPS_FNDNAM APPS /APPS_USER /APPS_RESPONSIBILITY "ABCD" /connect login/password@connect string /batch /opendb "WorkBook Name" /sheet Number /export XLS C:\report_name.xls.
4. Create yet an another batch file which will pick up this excel file and email it to an email group.
We have been successfully sending out Excel version of a critical report to a set of people every week day morning at 5:00 am using the above route.
All the best.
Thanks
-Uma

Timeout when using ALV build-in functionality: exporting to Excel

Hello,
I have the following problem within one of my web dynpro abap applications:
I need to be able to display data in a table that preferably should be via alv component.
Then I shall also be able to download the displayed data via Excel.
So I have embedded the ALV component I added to the component within a view and activated the export to excel button.
Downloading small amount of data does no lead to any problem, but when trying to process a larger amount of data (in this case 22500 entries), I get a timeout.
Does anybody have any idea if it is possible to increase performance here without reducing the amount of data to be downloaded?
thanks a lot ion advance!
Ana

Hello,
coming back to the UI element download.
I managed to get the data being saved to the desktop, but unfortunately, the data remains being displayed as in chines letters.
Anybody got an idea, what parameters I might have set wrong? Or if I have to do an additional encoding before generating the XString?
Here is the supply method code and the parameters I have set in the UI element:
The Supply method
method GEN_EXCEL_DOWNLOAD_DATA .
data: wa_cmx_line type zksb_cmxshowline.
data: lt_excel type zksb_cmx_excel_download_t.
data: wa_excel type zksb_cmx_excel_download.
data: l_guid type guid_32.
data: l_url type string.
* read context-------------------------------------------------------------------------------------
data lo_nd_z_ksb_get_prcm type ref to if_wd_context_node.
data lo_nd_exporting type ref to if_wd_context_node.
data lo_nd_rt_zksb_cmx_show type ref to if_wd_context_node.
data lo_el_rt_zksb_cmx_show type ref to if_wd_context_element.
data lt_rt_zksb_cmx_show type table of wd_this->element_rt_zksb_cmx_show.
data wa_rt_zksb_cmx_show like line of lt_rt_zksb_cmx_show.
*   navigate from <CONTEXT> to <Z_KSB_GET_PRCM> via lead selection
lo_nd_z_ksb_get_prcm = wd_context->get_child_node( name = wd_this->wdctx_z_ksb_get_prcm ).
*   navigate from <Z_KSB_GET_PRCM> to <EXPORTING> via lead selection
lo_nd_exporting = lo_nd_z_ksb_get_prcm->get_child_node( name = wd_this->wdctx_exporting ).
*   navigate from <EXPORTING> to <RT_ZKSB_CMX_SHOW> via lead selection
lo_nd_rt_zksb_cmx_show = lo_nd_exporting->get_child_node( name = wd_this->wdctx_rt_zksb_cmx_show ).
*   @TODO handle not set lead selection
if lo_nd_rt_zksb_cmx_show is initial.
endif.
* get static attributes table
lo_nd_rt_zksb_cmx_show->get_static_attributes_table( importing table = lt_rt_zksb_cmx_show ).
* reduce data to only the data that shall be displayed----------------------------------------
loop at lt_rt_zksb_cmx_show into wa_rt_zksb_cmx_show.
    move-corresponding wa_rt_zksb_cmx_show to wa_excel.
    append wa_excel to lt_excel.
endloop.
* populate data as tab separated strings-----------------------------------------------------
data l_str type string.
data lv_struct type extdfiest.
data itab type ref to zksb_cmx_excel_download_t.
data r_xstring type xstring.
data s(256) type c.
field-symbols <wa_desc> like line of lv_struct.
field-symbols: <tab> type table.
field-symbols: <wa> type any.
field-symbols: <f> type any.
* populate the column headers----------------------
get reference of lt_excel into itab.
* assign lt_excel to <tab>.
assign itab->* to <tab>.
lv_struct = wd_this->get_table_structure( itab = itab ).
loop at lv_struct assigning <wa_desc>.
    concatenate wa_cmx_line
                <wa_desc>-coltitle
                cl_abap_char_utilities=>horizontal_tab
                into wa_cmx_line.
endloop.
concatenate wa_cmx_line
              cl_abap_char_utilities=>cr_lf
              into wa_cmx_line.
* loop through the data table-----------------------
loop at <tab> assigning <wa>.
    loop at lv_struct assigning <wa_desc>.
      assign component sy-tabix of structure <wa> to <f>.
      check sy-subrc = 0.
      if <wa_desc> is assigned and <wa_desc>-convexit is not initial.
* Process any output conversion routines
        concatenate 'CONVERSION_EXIT_' <wa_desc>-convexit '_OUTPUT' into wa_cmx_line.
        call function wa_cmx_line
          exporting
            input = <f>
          importing
            output = s.
      else.
        concatenate wa_cmx_line
                 <f>
                  cl_abap_char_utilities=>horizontal_tab
                  into wa_cmx_line.
      endif.
    endloop.
    concatenate wa_cmx_line
                cl_abap_char_utilities=>cr_lf
                into wa_cmx_line.
endloop.
*Convert the strings to Binary strings (UTF-16le)------------------------------------------------
call function 'SCMS_STRING_TO_XSTRING'
    exporting
      text     = wa_cmx_line
      mimetype = ''
    importing
      buffer   = r_xstring.
*Add the UTF-16 Little Endian Byte Order Mark to the begining of the file
concatenate cl_abap_char_utilities=>byte_order_mark_little
               r_xstring
               into r_xstring in byte mode.
* set context
DATA lo_nd_excel_download TYPE REF TO if_wd_context_node.
DATA lo_el_excel_download TYPE REF TO if_wd_context_element.
DATA ls_excel_download TYPE wd_this->element_excel_download.
DATA lv_excel_download_data LIKE ls_excel_download-excel_download_data.
* navigate from <CONTEXT> to <EXCEL_DOWNLOAD> via lead selection
lo_nd_excel_download = wd_context->get_child_node( name = wd_this->wdctx_excel_download ).
* get element via lead selection
lo_el_excel_download = lo_nd_excel_download->get_element( ).
* set single attribute
lo_el_excel_download->set_attribute( name = `EXCEL_DOWNLOAD_DATA` value = r_xstring ).
endmethod.
and the parameters to the UI are as follows
behaviour: allowSave
data: <data that was created by supply method>
fileName: CMX.xls          also tried CMX.cvs
mime-type: ms-excel     also tried /vnd.ms-excel
text: $OTR:SOTR_VOCABULARY_BASIC/DOWNLOAD
textDirection: inherit
type: navigation
visible: Visible
Any suggestion of what I might have to change would be great!
Tx
Ana

ALV Export to Excel

Does anyone know the row/column limit on exporting an ALV grid to Excel? I am getting a message that "list object is too large to be exported".

Hi Janet,
Please find the following SAP Note 700206.
Symptom
Excel export gives error "List object is too large to be exported" when a large list object is exported. This message comes only on usage of function module XXL_FULL_API for Export to Excel functionality.
Other terms
Excel Export, XXL Export, i_oi_spreadsheet, Size Limit,
Reason and Prerequisites
Older technology used and old MS Office release has limitaion of exporting only 16384 lines of data. This change is valid only for the SAP R3 release higher than 4.6C and MS Office release higher than Office 97.
On The pop-up dialog "Export list object to XXL" with three options
"Excel SAP macros", "Table" and "Pivot table", this change is valid only
for "Table" and "Pivot table" option and not for "Excel SAP macros".
Choice of "Excel SAP macros" option is not linked with this change for any R3 relaese.
This correction is done in function module XXL_FULL_API and is only valid when XXL_FULL_API is called for Exporting the list to Excel.
Solution
Increased the Max Size Limit to 65536 rows and 256 columns. For Table and Pivot Table option of Excel Export. This change is available for office integration technology only and no adaption is possible to old SAP
Macros. Import the relevant ABAP patch.
NOTE: If you Export a Large list object there could be a performance problem and the same will be dirctly proportional to the amount of DATA (size of list object) Exported. The Maximum limits with XXL Export: Number of Rows - 65536. Number of Columns - 256. Size of individual cell - 255 Characters.
Hope this will help.
Regards,
Ferry Lianto

Discoverer Hangs on large export to Excel

Similar Messages

Maybe you are looking for