Query Error Information: Result set is too large; data retrieval ......

Hi Experts,
I got one problem with my query information. when Im executing my report and drill my info in my navigation panel, Instead of a table with values the message "Result set is too large; data retrieval restricted by configuration" appears. I already applied "Note 1127156 - Safety belt: Result set is too large". I imported Support Package 13 for SAP NetWeaver 7. 0 BI Java (BIIBC13_0.SCA / BIBASES13_0.SCA / BIWEBAPP13_0.SCA) and executed the program SAP_RSADMIN_MAINTAIN (in transaction SE38), with the object and the value like Note 1127156 says... but the problem still appears....
what Should I be missing ?????? How can I fix this issue ????
Thank you very much for helping me out..... (Any help would be rewarded)
David Corté

You may ask your basis guy to increase ESM buffer (rsdb/esm/buffersize_kb). Did you check the systems memory?
Did you try to check the error dump using ST22 - Runtime error analysis?
Edited by: ashok saha on Feb 27, 2008 10:27 PM

Similar Messages

WAD : Result set is too large; data retrieval restricted by configuration

Hi All,
When trying to execute the web template by giving less restiction we are getting the below error :
Result set is too large; data retrieval restricted by configuration
Result set too large (758992 cells); data retrieval restricted by configuration (maximum = 500000 cells)
But when we try to increase the number of restictions it is giving output. For example if we give fiscal period, company code ann Brand we are able to get output. But if we give fical period alone it it throwing the above error.
Note : We are in SP18.
Whether do we need to change some setting in configuration? If we yes where do we need to change or what else we need to do to remove this error
Regards
Karthik

Hi Karthik,
the standard setting for web templates is to display a maximum amount of 50.000 cells. The less you restrict your query the more data will be displayed in the report. If you want to display more than 50.000 cells the template will not be executed correctly.
In general it is advisable to restrict the query as much as possible. The more data you display the worse your performance will be. If you have to display more data and you execute the query from query designer or if you use the standard template you can individually set the maximum amount of cells. This is described over [here|Re: Bex Web 7.0 cells overflow].
However I do not know if (and how) you can set the maximum amount of cells differently as a default setting for your template. This should be possible somehow I think, if you find a solution for this please let us know.
Brgds,
Marcel

Result set is too large; data retrieval restricted by configuration

Hi,
While executing query for a given period, 'Result set is too large; data retrieval restricted by configuration' message is getting displayed. I had searched in SDN and I had referred the following link:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/d047e1a1-ad5d-2c10-5cb1-f4ff99fc63c4&overridelayout=true
Steps followed:
1) Transaction Code SE38
2) In the program field, entered the report name SAP_RSADMIN_MAINTAIN and Executed.
3) For OBJECT, entered the following parameters: BICS_DA_RESULT_SET_LIMIT_MAX
4) For VALUE, entered the value for the size of the result set, and then executed the program:
After the said steps, the below message is displayed:
OLD SETTING:
OBJECT = VALUE =
UPDATE failed because there is no record
OBJECT = BICS_DA_RESULT_SET_LIMIT_MAX
Similar message is displayed for Object: BICS_DA_RESULT_SET_LIMIT_DEF.
Please let me know as to how to proceed on this.
Thanks in advance.

Thanks for the reply!
The objects are not available in the RSADMIN table.

SAP Note: 1127156 Result set is too large

Hi,
The note 1127156 explains how to resolve the issue with removing the message "Result Set is too large." I want to check the settings in the template and it gives the following steps but i cannot find the settings on the Analysis web item of the data provider.
Can someone pls help.
Query View
The following steps describe how to change the "safety belt" for Query Views:
1. Use the context menu Properties / Data Provider in a BEx Web Application to maintain the "safety belt" for a Query View.
2. Choose the register "Size Restriction for Result Sets".
3. Choose an entry from the dropdown box to specify the maximum number of cells for the result set.
               The following values are available:
     Maximum Number
     Default Number
     Custom-Defined Number
               Behind "Maximum Number" and "Default Number" you can find the current numbers defined in the customizing table RSADMIN (see below).
4. Save the Query View and use it in another Web Template.
Many thanks

Hi,
I was facing the same issue in BEx analyzer 7.0. The query was working fine in BW 3.5 analyzer but gave error in BEx 7.0.
When executed in web, it gave error result set is too large.
The maximum no of cells that can be displayed is 750000.
Please check the result set returned by the query. Also check note Note 1040454 - Front-end memory requirement of the BEx Analyzer.
Some enhancement are planned to be delivered in enhancement package 1.
Regards,
Niraj

Result Set Too Large : Data Retrieval restricted by configuration

Hi Guys,
I get the above error when running a large dataset, with a hierarchy on - but when I run without a hierarchy I am able to show all data.
The Basis guys increased the ESM buffer (rsdb/esm/buffersize_kb) but it still causes an issue.
Anyone any ideas when it comes to reporting large volumes with a hierarchy?
Much appreciated,
Scott

Hi there
I logged a message on service marketplace andg got this reply from SAP:
' You might have to increase the value for parameters
BICS_DA_RESULT_SET_LIMIT_DEF and BICS_DA_RESULT_SET_LIMIT_MAX as it
seems that the result set is still too large. Please check your
parameters as to how many data cells you should expect and set the
parameter accordingly.
The cells are the number of data points that would be send from abap
to java. The zero suppression or parts of the result suppression are
done afterwards. As a consequence of this, the number of displayed
data cells might differ from the threshold that is effective.
Starting with SPS 14 you get the information how many data cells are
rejected. That gives you better ways to determine the right setting.
Currently you need to raise the number to e.g. 2.000.000 to get all
data.
If BICS_DA_RESULT_SET_LIMIT_MAX is set to a lower value than
BICS_DA_RESULT_SET_LIMIT_DEF, it would automatically cut the value of
BICS_DA_RESULT_SET_LIMIT_DEF down to its own..
Please note that altough this parameter can be increased via
configuration, you should do a proper system sizing according to note
927530 to ensure that the system can handle the number of users and
resultset sizes you are expecting."
Our basis team have subsequently apllied these changes, and I will be testing today.
Thx

Essbase Error:Set is too large to be processed. Set size exceeds 2^64 tuple

Hi,
we are using obiee 11.1.1.6 version with essbase 9.3.3 as a data source . when I try to run a report in obiee, I am getting the below error :
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Internal error: Set is too large to be processed. Set size exceeds 2^64 tuples (HY000)
but if I run the same query in excel add in, I am just getting 20 records . wondering why I am getting this error in obiee . Does any one encountered the same issue ?
Thanks In advance,

Well if you want to export in I think you have to manually do it.
The workaround it to open your aperture library by right clicking it and show contents...
Then go into your project right click show contents...
In here there are sub folders on dates that the pictures were added to those projects. If you open the sub folder and search for your pictures name it should be in that main folder.
You can just copy it out as you would any normal file to any other location.
Voila you have manually exported out your file.
There is a very similar post that has been close but again you can't export the original file that you are working on - FYI http://discussions.apple.com/thread.jspa?threadID=2075419

Snapshot refresh error: ora-01401 inserted value too large for column

I have an error ora-01401 "Inserted value too large for column" when I try to do a refresh on a group at the materialized view site.
My model is 1 master replicating to a readonly materialized view site. I have 2 refresh groups for separate sets of tables. 1 refresh group work fine...the other I got the above error.
I have doubled the rbs and system tablespace without any help thinking that I must be running out of default rollback segment space.
Anyone has this before?

The error is related to a field, not to any tablespace. This normaly happens to me when I change the lenght or resolution of a field in the base tables. The structure changes don't "flow" to the materialized view! I must "regenerate" them. Normally droping and creating it again to make them receive the new lenght of that field.
Sometimes, when the field changed is not part of any primary key I have changes directly the field in the materialized view as if it was a normal table.
Hope this helps
Luis

Error formatting page : Page Area too large

Hello,
I use Crystal Reports X1 for my reports design and my report was generated successfully. I also use JRC to generate the report in my Java application and I get this error. "Error formatting page : Page Area too large" for the same report.
Could you please help me with this error.
Many thanks
Marilyn

Hi,
Please provide the environment details along with the web browser version information.
Before that my suggestion is to upgrade to CR 2008 as XI is out of support and also you can download lestest version of CR Java SDK's from below link
http://www.businessobjects.com/campaigns/forms/downloads/crystal/eclipse/datasave.asp
on this page select the link below Runtime Libraries.
Thanks,
Nilesh Benke

Hi. I purchased Adobe Acrobat Xi Pro from a store (card). I submitted the number (under the scratch area on the card) on the adobe website, with my personal details etc. When I submitted the form, I got an error message: 413 header length too large (a

Hi. I purchased Adobe Acrobat Xi Pro from a store (card). I submitted the number (under the scratch area on the card) on the adobe website, with my personal details etc. When I submitted the form, I got an error message: 413 header length too large (and on top the page reads JRun Servelet Error). What does this mean? What should I do next?

Hi. I purchased Adobe Acrobat Xi Pro from a store (card). I submitted the number (under the scratch area on the card) on the adobe website, with my personal details etc. When I submitted the form, I got an error message: 413 header length too large (and on top the page reads JRun Servelet Error). What does this mean? What should I do next?

EXEC SQL Error: ORA-01401: Inserted value too large for column

Getting this SQL Error: ORA-01401: Inserted value too large for column..on an EXEC SQL Insert statement when writing to an
external Oracle DB from SAP.
On further analysis..it appears that this happens to the fields..when the string length matches the field length.
Example: Plant field is defined as char(4) on the SAP side and it is a Varchar2(4) on the Oracle side.
When a value like '1015' is passed thru a variable in the insert statement then this ORA-01401 error pops up.
No error:
   - if the value '1015' is passed directly in the insert statement to the external table (or)
   - when a value with 3 chars or less(like the first three chars..101) is passed thru a variable defined as 'Plant(4) type c'.
   - when using EXEC sql within SAP
   - when reading from the external db table
This was working ok until the Oracle Patch P9147110 was installed recently.
Any suggestions !

Hello Dvas,
what's the characterset of your external database?
What's the column definition in your external database (byte or character based)?
If you use a characeterset like UTF8 it is possible, that one character needs more than one byte and then you will run into such kind of issues if the definition is too small.
Regards
Stefan

Error: f14627469cba51.pdf file is too large for attachment

Hi,
Recently we migrated lot of crystal reports from BO XI R2 environment to BO 3.1 SP2 FP 2.5 environment, these crystal reports are integrated with the application.
Input parameters are given through the application using the Open Document URL and the report will open through the infoview.
This particular error arises when we try to open the report as PDF using Open Document URL,
Please find the URL below
http://bodev.com/OpenDocument/opendoc/openDocument.jsp?sIDType=CUID&iDocID=AUwcueYTQwtLhWDlil29Nvc&sOutputFormat=P&lsS@INVOICEDATE=1/31/2010&lsS@REFSERVICEID=1&lsS@BILLINGCYCLE=1&lsS@INVPREFIX=SC1001&lsS@GUID=99b18bcb-9470-4a49-948d-73961c149f5e
But we are getting the following error
"f14627469cba51.pdf file is too large for attachment"
Please help me out to resolve the issue.
Thank You,
Palani Kumar
+91-9840865865

Hi Jeff,
Did you figure out the solution to this problem?
I also getting the same problem while refreshing crystal report from 3rd party tool using dswsbobje service session
"Failed to retrieve binary view of the report. 14546ada1c151418.pdf File is too large for attachment. (WRE 02527)"
Please let me know if you find any solution.

Error in result set from join query

I get a SQL exception from the JDBC thin driver when I make a getXXX( "string" ) call on a result set object when the query is a join. Aliases don't seem to help.
Below is the stack trace.
Anybody have any ideas?
matt
ResultSet.findColumn
java.sql.SQLException: Invalid column name: get_column_index
at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:427)
at oracle.jdbc.driver.OracleStatement.get_column_index(OracleStatement.java, Compiled Code)
at oracle.jdbc.driver.OracleResultSet.findColumn(OracleResultSet.java:680)
at person.PersonMgr.getForEdit(PersonMgr.java:114)
at person.PersonMgr.getForView(PersonMgr.java:168)
at person.PersonMgr.getPersonForView(PersonMgr.java:164)
at nwsession.NWSession.login(NWSession.java:224)
at jsp.dologin._jspService(dologin.java:241)
at com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
at com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:129)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
at com.livesoftware.jrun.JRun.runServlet(JRun.java, Compiled Code)
at com.livesoftware.jrun.JRunGeneric.handleConnection(JRunGeneric.java:116)
at com.livesoftware.jrun.service.proxy.JRunProxyServiceHandler.handleRequest(JRunProxyServiceHandler.java, Compiled Code)
at com.livesoftware.jrun.service.ThreadConfigHandler.run(ThreadConfigHandler.java, Compiled Code)

Your reference to NS.REQDATE is too deep. Oracle will only allow you to reference a column from the main query one level deep.
I think you can just change that query into this:
(Select AVG(((cpath.REQUESTDATETIME)- NS.REQDATE)*1440) AvgTime
FROM usersessiondetails cpath
Where cpath.Userkey=(Select Userkey from ods_user where userid=NS.UserId and namespace=NS.Namespace)
   and cpath.acctnum=aCCTNUM
   and cpath.transactionname IN (AUTH_LOGOFF' )
   and cpath.REQUESTDATETIME = NS.REQDATE )You do not need the extra query level to do the AVG.

I wrote a query -- HTMLDB can't parse it, too large.

I would attach it here but I see no ways to attach items.
I wrote a query that, as I said, is too long for HTML DB to accept. When I submit it, I an http error 400.
the thing is, the query is only ~27700 bytes, according to the file system information. So is the query parser set to a lower maximum length than the import capabilities for data imports?
Thanks.

Don't know what you mean by data imports exactly but different mechanisms may be at work for different situations. modplsql has a 30,000 byte limit (I think) on the size of textareas. Keep in mind that the byte count it sees may be larger than the character count your text editor reports due to UTF-8 or other transformations and also that some of this information is probably only partially correct. If the query is too large, use a packaged pl/sql function returning sql query.
Scott

BPC 7M SP4 EVDRE missing rows - Error is "1004-Selection is too large.}

Hello,
On a customer who installed BPC 7 Ms SP4 I have on client Exception log the error:
===================[System Error Tracing]=====================
[System Name] : BPC_ExcelAddin
[Job Name] : clsExpand::applyDataRangeFormula
[DateTime] : 2009-07-17 09:44:13
[Exception]
 Detail<sg : {1004-Selection is too large}
===================[System Error Tracing End ]=====================
When I see this error there is an EVDRE input schedule expanding which have some of the rows missing rows descriptions.
This means there is a gap of missing row header formulas stating from second row to somewhere in the middle of the report.
If I reduce the number of the resulting rows for the same EVDRE input schedule results are ok.
Do you know some setting to fix this?
I tried increasing the Maximum Expansion Limit for rows and columns in Workbook Options without success.
Thank you.

Hi all,
I have the same problem with 7.0MS SP07. With 59 expanded members it works. With 60 expanded members it fails.
Mihaela, could you explain us what is the purpose of the parameters you talk about?
thanks,
Romuald

Query Performance and Result Set Query/Sub-Query

Hi,
I have an infoset with as many as 15 joins with different ODS and Master Data..The ODS are quite huge with 20 million, 160 million records)...Its taking a lot of time even for a few days and need to get atleast 3 months data in a reasonable amount of time....
Could anyone please tell me whether Sub-Query or Result Set Query have to be written against the same InfoProvider (Cube, Infoset, etc)...or they can be used in queries
on different infoprovider...
Please suggest...Thanks in Advance.
Regards
Anil

Hi Bhanu,
Needed some help defining the Precalculated Value Set as I wasnt succesful....
Please suggest answers if possible for the questions below
1) Can I use Filter Criteria for restricting the value set for the characteristic when I Define a Query on an ODS. When i tried this it gave me errors as below ..
"System error in program CL_RSR_REQUEST and form EXECUTE_VTABLE:COB_PRO_GET_ALWAYS.... Error when filling value set DELIVERY..
Job cancelled after system exception ERROR_MESSAGE"
2) Can I create a create a Value Set predefined on an Infoset - Not Succesful as Infoset have names such as "InfosetName_F000232" and cannot find the characteristic in Paramter Tab for Value Set in Reprting Agent.
3) How does the precalculated value Set variable help if I am not using any Filtering Criteria and is storing the List of all values for the Variable from the ODS which consists of 20 millio records.
Thanks for your help.
Kind Regards
Anil

Query Error Information: Result set is too large; data retrieval ......

Similar Messages

Maybe you are looking for