Result set too large

Hi Experts,
When I run BI report on SAP portal, it shows me the message : Result set too large...., I had changed BICS_DA_RESULT_SET_LIMIT_MAX and BICS_DA_RESULT_SET_LIMIT_DEF, but I don't know how to(and where) config "safety belt", somebody can teach me that!? thanks a lot!

Note 1127156 - Safety belt: Result set is too large
Oops too late...!!! did not see earlier reply
Edited by: Arun Varadarajan on Jul 6, 2010 9:31 PM

Similar Messages

BW Web Report Issue - Result set too large

Hi,
When I execute a BEx Query on Web I am getting “Result set too large ; data retrieval restricted by configuration (maximum = 500000 cells)”.
Following to my search in SDN I understood we can remove this restriction either across the BW system globally or for a specific query at WAD template.
In my 7x Web template I am trying to increase default max no of rows parameters, As per the below inputs from SAP Note: 1127156.
But I can’t find parameter “Size Restriction for Result Sets” for any of the web items (Analysis/Web Template properties/Data Provider properties)….in the WAD Web template
Please advise where/how can I locate the properites
Instructions provided in SAP Note…
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:
o Maximum Number
o Default Number
o 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.
Thanks in advance

Hi Yasemin,
Thanks for all help...i was off couple of days.
To activate it I can suggest to create a dummy template, add your query in it, add a menu bar component add an action to save the query view. Then you run the template and change the size restriction for result set then you can save it by the menu.
Can you please elaborate on the solution provided,I created dummy template with analysis and Menu bar item...i couldn't able to configure menu bar item...
Thanks in advance

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

Result set too large in BI report; Safety belt settings in WAD

Hello All,
When we run a BI report, the error " Result set is too large; data retrieval restricted by configuration" appears. We did a search on SAP portal and found the SAP note 1127156, whics recommends the configuaration of safety belt to limit memory used.
Acoordingly the cust table RSADMIN has been configured. But on the web template side, we need to configure the changes as well. The note says:
"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."
I am trying to locate these options in the context menu in Web Applications designer but in vain.
Can anyone help...

This option is not available in WAD, it will be available when you run the web template under settings, Data Provider for the standard template 0ANALYSIS_PATTERN.
If you have a custom template you will have to use the Dataprovider settings web item in your custom template to change the values during runtime.

Warning: Cache size set too large?

I've recently installed a SSD to work as a dedicated cache drive, and I've directed the 3 cache settings in AE (CS6) to it.
The drive is 240GB, but I can't put the cache size over 150GB without getting a warning that it's set too high. Is this true? Am I wasting almost 100GB?

Use your drive for something else. 150GB is a huge huge cache. The CS6 disk cache is glitchy anyway. I have mine turned off most of the time.

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

Unable to run reports due to too large set size

Hello guys
I am creating a report with almost 12 columns. I know it has a lot of data. When I tried to add one more column which is day column, it gives me the following errors:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. Essbase Error: Internal error: Set is too large to be processed. Set size exceeds 2^32 tuples. (HY000)
SQL Issued: SELECT Brand."Brand Name" saw_0, Brand.Product saw_1, Offer."Offer Name" saw_2, "Subscription Offer_Cost"."Offer Cost" saw_3, "Continuity Cycle"."Cont Cycle" saw_4, "Acquisition Date"."Acquisition Month" saw_5, "Acquisition Date"."Acquisition Day" saw_6, "Retention Status".Status saw_7, Level."Subscription Leve" saw_8, SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name") saw_9, CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END saw_10, (CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END/SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name"))*100 saw_11 FROM retention_cube WHERE ("Acquisition Date"."Acquisition Month" BETWEEN '2009 Feb' AND '2009 Jan') ORDER BY saw_7 DESC
It's probably because the data size is too big for querry to return. Is there a way I can fix this error and still get the report with the new columns?
Any pointers will be greatly appreciated..

Well of course it is. (Set too large I mean)
SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name") saw_9,
CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END saw_10,
(CASE WHEN Level."Subscription Leve" > '0' THEN retntion."Count Of Orders" ELSE 0 END/SUM(CASE WHEN Level."Subscription Leve" = '0' THEN retntion."Count Of Orders" ELSE 0 END by "Acquisition Date"."Acquisition Month", Offer."Offer Name"))*100 saw_11
THAT is the way to kill a query going against Essbase. Just check out the MDX that generates in the background (i.e. read the log!) and try to fire that through SmartView. It will work until you hit a low grain on one of the dimensions. The time dimension being a perfect example.
Stuff like what you're trying to do should either be
- account members in Essbase,
- MDX EVALUATE_AGGR expressions in the RPD with the correct aggragation level set or
- MDX EVALUATE expressions in answers.
Push the number crunching and aggregating as far down the foodchain as you can. Everything will almost automatically result in failures.
Cheers,
Christi@n

BEx Broadcaster configuration - maximum number of cells in result set

Hi all,
I've got an error message when runnig a BEx Broadcaster setting to send query output as xls file.
Query was running, but empty xls sheet was sent.
Message was: result set to large (1.5 Mio cells); data retrieval restricted by configuration (maximum 1 Mio cells).
How can this configuration be changed to enable 1.5 Mio cells ?
Many thanks
Andreas

This is excel restriction for maximum of 1million cells. If you split the query with smaller results set lesser than 1 million cells, this error will not come.

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

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 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.

Setting kern.ipc.maxsockbuf above MB errors with "Result too large"

Hi
I'm running Snow Leopard 10.6.4 on a machine that has 16GB memory.
When I attempt to increase the kern.ipc.maxsockbuf above 4MB I get an error that states "Result too large". I don't have this problem on my 10.5 machines. Anyone know where this limitation comes from? Is it some hard limit on Smow Leopard?
Regards - Tim
# setting to 4MB works fine.
sudo sysctl -w kern.ipc.maxsockbuf=4194304
kern.ipc.maxsockbuf: 500000 -> 4194304
# setting to 1 above 4MB starts the error.
sudo sysctl -w kern.ipc.maxsockbuf=4194305
kern.ipc.maxsockbuf: 4194304
sysctl: kern.ipc.maxsockbuf: Result too large

Firstly, there's no such thing as Apache 9.3, there's Apache 1 (and subversions) and Apache 2 (and subversions). Your error message -
Oracle-HTTP-Server/1.3.28Shows you're using Apache 1.3.28
Secondly, I'm confused by your comment -
I do not have Apache 9.3 or higher but I think oracle should offer this in its companion CDOracle does offer the Apache server, if you're saying you didn't get it from Oracle then where did your Apache server come from?
Thirdly, I notice from your config file -
ErrorLog "|E:\oracle\product\10.1.0\Companion\Apache\Apache\bin\rotatelogs logs/error_log 43200"That you're piping the logs through rotatelogs, are you sure the logfiles haven't just been renamed?

With Adobe Flash, the image is looking for a "zoom" setting and does not find it. The result is that the imbedded image is too large for the space allowed. Is there a zoom setting for Firefox?

When running FB game apps, the image loaded is too large for the FB space. The program looks for a "zoom" setting and does not find it. This was from the error screen. I have not been able to locate where the image zoom is located (found the font adjustment). I am new to FireFox and would like to sort this out please.
Your installed plug in assume Shockwave Flash 10.3, but I thought it was Adobe Flash 10.3. Are they one and the same?
Below is the warning message from the Error Console

I'm not sure the CSS warning is relevant to Flash. Maybe adjust your overall zoom level on Facebook manually from the View menu?
View > Zoom
If you have the orange Firefox button, tap the Alt key to display the classic menu bar.

How to handle large result sets?

Hi All,
I have a large result set to be displayed to user using jsp's. Problem is that result set is too big, so I can't display all the records in a single push. I want to show the results page by page say 25 per page. Now for every page I have to fetch data from database, means there are going to be many database calls which is not advisable. Or i can cache data in a CachedRowSet to reduce database calls, but in this case you have to store all the data in memory which is not a good solution in case you have very large data sets. Can anybody suggest me a solution to this problem?

The best thing for you to do is to implmeneting paging logic in conjunction with a scrollable resultset (JDBC 2.0+).
The logic would go like this assuming 30 rows per page:
- keep track of which page the user is on (e.g. page 3)
- issue the full sql
- scroll thru only the rows in the current page (e.g. rows 90-120)
- copy the page's rows to value objects
- close the resultset, statement, and connection
In the above example, you would scroll to row 90 using rs.absolute(90).
The efficiency comes from the fact that you're using a scrollable resultset. By using this, only the rows that you scroll thru are extracted out from the database. I performed some simple testing and with my data, and the scrollable resultset was about 10x in performance.
Good luck!

The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.

The below function is giving me the hours difference what I wanted, but today it is giving us the below error:
Msg 535, Level 16, State 0, Line 1
The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.
Please Help..
ALTER FUNCTION [dbo].[GetHoursExcludingWeekdays](@StartDate datetime2,@EndDate datetime2)
returns decimal(12,3)
as
begin
if datepart(weekday,@StartDate) = 1
set @StartDate = dateadd(day,datediff(day,0,@StartDate),1)
if datepart(weekday,@StartDate) = 7
set @StartDate = dateadd(day,datediff(day,0,@StartDate),2)
-- if @EndDate happens on the weekend, set to previous Saturday 12AM
-- to count all of Friday's hours
if datepart(weekday,@EndDate) = 1
set @EndDate = dateadd(day,datediff(day,0,@EndDate),-2)
if datepart(weekday,@EndDate) = 7
set @EndDate = dateadd(day,datediff(day,0,@EndDate),-1)
declare @return decimal(12,3)
set @return = ((datediff(second,@StartDate,@EndDate)/60.0/60.0) - (datediff(week,@StartDate,@EndDate)*48))
return @return
end
ReportingServices

You'll get this error if the difference between the start and end date is greater that about 68 years due to the "second" DATEDIFF specification. Perhaps the dates are greater than the expected range due to a data quality issue.
Taking the advice from the error message, you could use minutes instead of seconds like the example below the version below. This could still result in the error of the difference is greater than a couple of hundred years, though. You might consider
validating the dates and returning NULL if outside expected limits.
ALTER FUNCTION [dbo].[GetHoursExcludingWeekdays](@StartDate datetime2,@EndDate datetime2)
returns decimal(12,3)
as
begin
if datepart(weekday,@StartDate) = 1
set @StartDate = dateadd(day,datediff(day,0,@StartDate),1)
if datepart(weekday,@StartDate) = 7
set @StartDate = dateadd(day,datediff(day,0,@StartDate),2)
-- if @EndDate happens on the weekend, set to previous Saturday 12AM
-- to count all of Friday's hours
if datepart(weekday,@EndDate) = 1
set @EndDate = dateadd(day,datediff(day,0,@EndDate),-2)
if datepart(weekday,@EndDate) = 7
set @EndDate = dateadd(day,datediff(day,0,@EndDate),-1)
declare @return decimal(12,3)
set @return = ((datediff(minute,@StartDate,@EndDate)/60.0) - (datediff(week,@StartDate,@EndDate)*48))
return @return
end
GO
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Result set too large

Similar Messages

Maybe you are looking for