Is this in IR Studio or IRWC?
What OS are you running?
SQL queries (straight or derivable) or local results queries?
I have some complicated client-side queries that would fail in IR (WC and Studio) in Win 7 64-bit because it would use too much RAM. They used less than half as much (and completed) if I ran it as an admin.
Just as a test...
Log on as an admin, turn off UAC and run the query.
Oracle says 126.96.36.199 uses more memory because it has more features. Using up 8GB and only when running as a non-admin is not due to new features -- it's the new bugs.
There are many different conditions in which this error may appear:
(1) Upon opening a legacy non-Unicode BQY file in a Unicode compatible version of Interactive Reporting.
(2) When processing a query multiple times against a BLOB.
(3) When querying against Red Brick version 6.3 with ODBC/ODBC setting and there is processing to convert string column to integer type (before IR 9.3.0).
(4) When processing with DB2 9.1 against a bigint data type.
(5) Repeated opening, processing, closing, and re-opening of BQY documents with 'not equal' joins and high volumes
Sometimes this is due to excessive data which brings the size of the BQY file up around one gigabyte uncompressed in size (for processing may take twice as actual RAM, plus the memory space space for the plugin, and the typical memory limit on a 32-bit system is 2 gigabytes).
There have been a number of unpublished bugs which can result in the same error.
To avoid excessive BQY size exceeding memory availability:
(a) Ensure that your computer has at least 2Gb of free RAM before he runs IR Studio.
(b) Put a limit to the number of rows that can be pulled down: Right click on Request label of Query section and put a value in Return First xxx Rows (and check the check box).
(c) Do not pull down more than 750 MB of data (remember it may be duplicated while processing).
(d) Place limits or aggregations in Query section (as opposed to Result section) to limit data entering the BQY