As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
I had 30lakh records and trying to split 10lakh records into each sheet. I tried splitting the records using ROWLIMIT=1000000, It was generating a corrupted excel.This message has been edited. Last edited by: FP Mod Chuck,
Originally posted by venkatesh emandi: It is a business requirements, And the data is for one year.
You must get more information (or provide us with more info) regarding the goal behind this :
- What is the purpose of having one year of detailed data where over 3M rows are extracted and included in an Excel file ? - What they want to do with that ? - Can you provide something different then their requirement to better answer their needs ?
Nobody can work with that number of data as a BI POV. This looks more like a data dump and sure that Excel is probably not the good platform to dump in. It also looks like we are missing a lot of information...
Please update your signature to let us know which WF version you are working with. That may help us helping you in future.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2410 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
I've never attempted to do this, so I can't tell if it should or shouldn't work but like MartinY says, you've probably hit a limitation.
Test 1: Dump this data into a CSV and see if Excel can open that CSV file. That'll give you an idea if in fact Excel is choking on the size of your output.
Test 2: Try running the request on the reporting server (with ON TABLE HOLD FORMAT XLSX) to see if it still corrupts the excel file. That eliminates the WebFOCUS client and any client memory limitations as a potential issue.
Ultimately, if your requirements aren't flexible, the only thing left is to open a case with IB tech support to get their official response. But I'm pretty sure tech support will ask you to try these two tests so you may want to have this information before you call them as they help narrow down where the issue is.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015