1 person found this helpful
This is from Oracle Support:
"Using Smart View Gives the Error: Essbase Error (1020034): Binary Spreadsheet Table Token Error" [ID 1471947.1]
Thank you Mehmet. I have tested your workaround and it does do the trick.
That said, when can we expect Oracle address this unpublished bug?
Workaround does not work for us. Any other solution?
It's just today that I ran into that error in a file processed by a macro and after some testing found a workaround. So maybe it will help some of you out there...
Smart View 126.96.36.199
XLS 2010 using Citrix (I suppose W2008?)
Here is how:
- Make all members present on the worksheet, i.e. no POV is used.
- Then select the entire retrieval area, meaning select ALL members (page, row, column) which are present on the sheet.
- After that select 'ad-hoc analysis' in the Smart View connection pane (right-click on the database you want to connect to get there) and choose the alternative 'use sheet for multiple grid ad-hoc'. One drawback may be that the sheet gets into the multiple-grid mode, which can be a hinder fo further analysis...
Why does it work?
By using the alterantive above we show Essbase where to find the actual retrieval area. Essbase assigns a name to the Excel area you selected and identifies it by its name. To manipulate the area Essbase uses/recognizes, use Excel's >Formula >Name Manager. Some more interesying testing can be done with that....
The binary spreadsheet table token error is caused by passing more than 65,535 consecutive blank cells to the Essbase Grid API (which is used under the covers by Smart View). By defining a name for the retrieval range, you no longer have that many consecutive blank cells.
Applied OLAP, Inc
Thanks for the information and insight on this error. I'm sure the Essbase community will appreciate that.
We have started to advise the following steps:
- Place all POV-members manually into one single row above the refresh area, i.e. eliminate all members from the POV window in case this holds four your analysis
- Add a new worksheet to your workbook in Excel (you may even want to start with an entirely new workbook)
- Connect the new worksheet to the database in question and select ad-hoc analysis (or refresh) to establish an active connection and to test it. Delete all members from the sheet. (This step may seem superfluous, but helped to prevent a new Binary-error in some of the cases we had.)
- Copy the entire refresh area from the 'corrupted' sheet with the Binary error to the newly added sheet. Be sure to include all members from the header, the columns and the rows.
- Run a refresh
Issue is fixed in Essbase 188.8.131.52.104 and APS 184.108.40.206.104.