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

Similar Messages

PL/SQL: numeric or value error: number precision too large

hi ,
i am running my script and getting this error. i created a object and and make table type on this with fraction of number(2,2). and in my script i am calling a standard API which have hour in number only .i am also using a custome table also which also having number(2,2). so plz help me to resoulve thsi error.
description below:
DECLARE
l_Return_Status VARCHAR2 (30):=NULL;
l_Msg_Count NUMBER :=0;
l_Msg_Data VARCHAR2 (2000) := NULL;
v_Sape_Sco_info_Tbl SAPE_SCO_INFO_TBL;
v_Sape_Sco_info_rec SAPE_SCO_INFO_REC;
p_assignment number:=165316; -----165688;
p_project_id number:=74538; -----81993;
sco_id number:=10371;
BEGIN
v_Sape_Sco_info_Tbl := SAPE_SCO_INFO_TBL();
v_Sape_Sco_info_rec := SAPE_SCO_INFO_REC(p_assignment,p_project_id,sco_id,'15-Oct-2009','31-Oct-2009',15.00,'17-Oct-2009','20-Oct-2009','ADD_EXISTING_RESOURCES',02.50,NULL,'Y',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);
v_Sape_Sco_info_Tbl.EXTEND;
v_Sape_Sco_info_Tbl(1) := v_Sape_Sco_info_rec;
SAPE_UPDATE_SCO_DETAILS_PKG.SCO_ROLE_INCREASE(
x_project_id =>p_project_id,
x_Assignment_Id =>p_assignment,
l_Sape_Sco_info_Tbl => v_Sape_Sco_info_Tbl,
x_called_function =>'ADD_EXISTING_RESOURCES',
x_Return_Status =>l_Return_Status,
x_Msg_Count =>l_Msg_Count,
x_Msg_Data =>l_Msg_Data
dbms_output.put_line('second Procedure executed sucessesfuly');
dbms_output.put_line('l_Return_Status '||l_Return_Status||' l_Msg_Count '||l_Msg_Count||'l_Msg_Data');
dbms_output.put_line('value'||' '||v_Sape_Sco_info_Tbl(1).Assignment_Id);
dbms_output.put_line('completed');
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line(sqlerrm(sqlcode));
END;
error :PL/SQL: numeric or value error: number precision too large
CREATE OR REPLACE TYPE SAPE_PA.SAPE_SCO_INFO_TBL IS TABLE OF SAPE_SCO_INFO_REC;
Prompt OBJECT TYPE SAPE_PA.SAPE_SCO_INFO_REC
DROP TYPE SAPE_PA.SAPE_SCO_INFO_REC;
CREATE OR REPLACE TYPE SAPE_PA.SAPE_SCO_INFO_REC AS OBJECT
( Assignment_Id NUMBER,
project_id Number,
sco_id Number,
Role_START_DATE DATE,
Role_END_DATE DATE,
avg_hrs_per_day NUMBER(2,2),
sco_role_start_date DATE,
sco_role_end_date DATE,
sco_role_mode VARCHAR2(250),
sco_hrs_per_day NUMBER(2,2),
no_of_copies Number,
Active_Flag VARCHAR2(10),
BILLABLE_UPSIDE_INDICATIOR VARCHAR2(5),
RET_CODE VARCHAR2(5),
ERROR_MSG VARCHAR2(255),
ATTRIBUTE1 VARCHAR2(240),
ATTRIBUTE2 VARCHAR2(240),
ATTRIBUTE3 VARCHAR2(240),
ATTRIBUTE4 VARCHAR2(240),
NATTRIBUTE1 NUMBER,
NATTRIBUTE2 NUMBER
CREATE TABLE SAPE_PA.SAPE_SCO_STAFFING_MAPPINGS
(     PROJECT_ID NUMBER,
          SCO_ID NUMBER,
          ASSIGNMENT_ID NUMBER PRIMARY KEY,
          SCO_ROLE_START_DATE DATE,
          SCO_ROLE_END_DATE DATE,
          SCO_ROLE_HOURS NUMBER(2,2),
          SCO_MODE VARCHAR2(80),
          ACTIVE_FLAG VARCHAR2(5),
          LAST_UPDATE_DATE DATE,
          LAST_UPDATED_BY NUMBER(15,0),
          CREATION_DATE DATE,
          CREATED_BY NUMBER(15,0),
          LAST_UPDATE_LOGIN NUMBER(15,0),
          ATTRIBUTE1 VARCHAR2(240),
          ATTRIBUTE2 VARCHAR2(240),
          ATTRIBUTE3 VARCHAR2(240),
          ATTRIBUTE4 VARCHAR2(240),
          NATTRIBUTE1 NUMBER,
          NATTRIBUTE2 NUMBER
          )

The problem here is with avg_hrs_per_day NUMBER(2,2)+ of SAPE_SCO_INFO_REC object.
user12226862 wrote:
CREATE OR REPLACE TYPE SAPE_PA.SAPE_SCO_INFO_REC AS OBJECT
( Assignment_Id NUMBER,
project_id Number,
sco_id Number,
Role_START_DATE DATE,
Role_END_DATE DATE,
avg_hrs_per_day NUMBER(2,2),
sco_role_start_date DATE,And while assigning the value it is:
user12226862 wrote:
v_Sape_Sco_info_rec := SAPE_SCO_INFO_REC(p_assignment,p_project_id,sco_id,'15-Oct-2009','31-
Oct-2009',15.00,'17-Oct-2009','20-
Oct-2009','ADD_EXISTING_RESOURCES',02.50,NULL,'Y',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL);Note that number(2,2) means maximum total of digits in that case is 2 (including scale), not 4.
E.g.
SQL> declare
2       x number(2,2);
3     begin
4       x := 02.50;
5     end;
6    /
declare
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: number precision too large
ORA-06512: at line 4However, this works:
SQL> declare
2       x number(2,2);
3     begin
4       x := .50;
5     end;
6    /
PL/SQL procedure successfully completed.Cheers,
AA

Alter mount database failing: Intel SVR4 UNIX Error: 79: Value too large for defined data type

Hi there,
I am having a kind of weird issues with my oracle enterprise db which was perfectly working since 2009. After having had some trouble with my network switch (replaced the switch) the all network came back and all subnet devices are functioning perfect.
This is an NFS for oracle db backup and the oracle is not starting in mount/alter etc.
Here the details of my server:
- SunOS 5.10 Generic_141445-09 i86pc i386 i86pc
- Oracle Database 10g Enterprise Edition Release 10.2.0.2.0
- 38TB disk space (plenty free)
- 4GB RAM
And when I attempt to start the db, here the logs:
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 150
shared_pool_size         = 209715200
control_files            = /opt/oracle/oradata/CATL/control01.ctl, /opt/oracle/oradata/CATL/control02.ctl, /opt/oracle/oradata/CATL/control03.ctl
db_cache_size            = 104857600
compatible               = 10.2.0
log_archive_dest         = /opt/oracle/oradata/CATL/archive
log_buffer               = 2867200
db_files                 = 80
db_file_multiblock_read_count= 32
undo_management          = AUTO
global_names             = TRUE
instance_name            = CATL
parallel_max_servers     = 5
background_dump_dest     = /opt/oracle/admin/CATL/bdump
user_dump_dest           = /opt/oracle/admin/CATL/udump
max_dump_file_size       = 10240
core_dump_dest           = /opt/oracle/admin/CATL/cdump
db_name                  = CATL
open_cursors             = 300
PMON started with pid=2, OS id=10751
PSP0 started with pid=3, OS id=10753
MMAN started with pid=4, OS id=10755
DBW0 started with pid=5, OS id=10757
LGWR started with pid=6, OS id=10759
CKPT started with pid=7, OS id=10761
SMON started with pid=8, OS id=10763
RECO started with pid=9, OS id=10765
MMON started with pid=10, OS id=10767
MMNL started with pid=11, OS id=10769
Thu Nov 28 05:49:02 2013
ALTER DATABASE   MOUNT
Thu Nov 28 05:49:02 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Trying to start db without mount it starts without issues:
SQL> startup nomount
ORACLE instance started.
Total System Global Area 343932928 bytes
Fixed Size                  1280132 bytes
Variable Size             234882940 bytes
Database Buffers          104857600 bytes
Redo Buffers                2912256 bytes
SQL>
But when I try to mount or alter db:
SQL> alter database mount;
alter database mount
ERROR at line 1:
ORA-00205: error in identifying control file, check alert log for more info
SQL>
From the logs again:
alter database mount
Thu Nov 28 06:00:20 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Thu Nov 28 06:00:20 2013
ORA-205 signalled during: alter database mount
We have already checked in everywhere in the system, got oracle support as well without success. The control files are in the place and checked with strings, they are correct.
Can somebody give a clue please?
Maybe somebody had similar issue here....
Thanks in advance.

Did the touch to update the date, but no joy either....
These are further logs, so maybe can give a clue:
Wed Nov 20 05:58:27 2013
Errors in file /opt/oracle/admin/CATL/bdump/catl_j000_7304.trc:
ORA-12012: error on auto execute of job 5324
ORA-27468: "SYS.PURGE_LOG" is locked by another process
Sun Nov 24 20:13:40 2013
Starting ORACLE instance (normal)
control_files = /opt/oracle/oradata/CATL/control01.ctl, /opt/oracle/oradata/CATL/control02.ctl, /opt/oracle/oradata/CATL/control03.ctl
Sun Nov 24 20:15:42 2013
alter database mount
Sun Nov 24 20:15:42 2013
ORA-00202: control file: '/opt/oracle/oradata/CATL/control01.ctl'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 79: Value too large for defined data type
Additional information: 45
Sun Nov 24 20:15:42 2013
ORA-205 signalled during: alter database mount

ERROR:number precision too large (WWV-16016)

Hi!
As I try to insert values into form items an error accurs:
ORA-06502: PL/SQL: numeric or value error: number precision too
large (WWV-16016)
P.S.-One form item inserts values into database table where
column is VARCHAR2, lenght 2000...
How can I fix this error?Thank you in advance!

Table Structure:
ID NUMBER (5,0) , DATE_T1 DATE, ID_PROFESOR NUMBER(5,0), SUBJECT
VARCHAR2(50), MESSAGE VARCHAR2(2000).
The error accurs for example if I try to insert:
ID=1,DATE_T1=6.6.2001, ID_PROFESOR=3, SUBJECT="New uniforms",
MESSAGE="bla,bla,bla..."
I'm using Oracle portal version 8.1.2.
I hope, this will help you!

ORA-06502: PL/SQL: numeric or value error: number precision too large

I am getting this error when my procedure is being invoked. I've checked if a calculation is attemting to assign an integer to a column that has a smaller data type...e.g 99 being inserted into NUMBER(2)....but this all seems fine...
any ideas where I should check?
thanks!

>Is there a way to tell which column is throwing this error
As suggested by Guido it appears to be related to your variables, not the table;
SQL> create table t (col1 number(1))
Table created.
SQL> begin
   insert into t values (11);
end;
ORA-01438: value larger than specified precision allowed for this column
ORA-06512: at line 2
SQL> declare
   n number(1);
   n2 number(2) :=11;
begin
   n:= n2;
end;
ORA-06502: PL/SQL: numeric or value error: number precision too large
ORA-06512: at line 5The error message should tell you the line of code that is causing the problem, ie;
ORA-06512: at line 5A quick way to show the values is to display them using dbms_output.put_line inline or in the exception handler.

Error 413 Header Too Large

I have recently purchased the product and tried downloading it on my Macbook Pro.
It will not let me get into the site and redirects me to a message stating "Error: 413 Header Too Large"
I tried deleting cookies and history browsing and hasn't helped.
I tried clicking the downloading button and it redirects me once again.

I'm trying to download the Photoshop Elements from Adobe.
The only Option I have to download the application is by clicking "Akamai Download"
Later, it redirects me to the 413 Error. When I refresh, it finally downloaded.
I click on the "Open bundle" button and nothing pops up.

Get an error 123 (Program Too Large)

Hi there,
I am just try to modify procedure in oracle 6i and after or while modification when we compile this program then we get an error 123 (Program Too Large) .
any one have ideal about that how can i solved it.
Haider Ali

hi,
(Program Too Large) .Please use search option about this topic. There will be lots of posts regarding this.
you can split the code into procedures and make a call in this program unit.
share the code you have written.

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?

Error message when uploading book for printing. All images are jpg and rgb. Could they be too large to upload? What size is required and how do I reduce size in Aperture?

I receive an error message when I upload my book for printing. Not sure what the problem is. All my images are jpg and rgb. Could they be too large as it takes about 15minutes to upload to Apple. How do I reduce the size of the image in Aperture?

Hi Leonie,
Thanks for your reply.
Error message below. The preview is fine . I can discount the first 2messages as its a new computer so plenty of disk space and upload doesn't seem to be interrupted. I have uploaded to iphoto before. have tried to upload 3times with the same error message. I had to photo my slides with a Kaiser Baas photo maker , which apparently doesn't scan but takes photos in megapixels of the slides. I am wondering now if the format is incompatible though they are jpg files or the colour type wrong. The image files are around 1-3 mb each and 72 ppi. I think I will now scan them properly with a scanner to 300dpi anyway to improve quality.
Apple talks about image files not being too big for uploading but gives no sizing of what too big is?
Error message
1. Upload Error. Loss of connection or file corruption during order upload may cause an incomplete order. Resubmitting your order usually resolves this issue.
2. Low Disk Space. If your computer is running on low disk space, your files may be assembled incorrectly. Create more space by deleting unused files.
3. Unreadable PDF file or image files. Files are sometimes assembled incorrectly due to CMYK or Grayscale color space. Use the RGB color space for best results.

500 Internal Server Error OracleJSP: code too large for try statement catch

We have an application which uses JSPs as front end and we are using Struts 1.1. When we run one of the JSP it shows the following error after executing .We are using OCJ4 server having version 9.0.4.0
500 Internal Server Error
OracleJSP: oracle.jsp.provider.JspCompileException:
Errors compiling:E:\oracle\product\10.1.0\AS904\j2ee\home\application-deployments\VAS3006\vas\persistence\_pages\\_Requirement .java
code too large for try statement catch( Throwable e) {
7194
code too large for try statement catch( Exception clearException) {
44
code too large for try statement try {
23
code too large public void _jspService(HttpServletRequest request, HttpServletResponse response) throws java.io.IOException, ServletException {
The JSP/application runs okay on one machine (System Tesing machine)with OCJ4 server having version10.1.2.0 but throughs an error on other machine( Development machine)with OCJ4 server having version9.0.4.0.The question is why it is running on one machine ane giving error on other machine I am aware that there can't be more than 64kB of code between try-catch block .Total size of the generated JSP class in our case is 577KB.
Is the problem because of different version of Application server OC4J?.Is it any fix for this? Or Can anyone please suggest a work around. Or is there a method by which the JSP generated code is split between different try - catch blocks rather than a single try-catch block.Utlimately We don't know the whether is it a problem with JVM or hardware .
It would be really helpful if you would provide me with some suggestion and input.
Regards
Shyam

Sir,
I am aware of the limitations of JVM that it won't allow java code more than 64Kb in method but we are using different versions of Application server .Application is working okay with OC4J application server(10.1.2.0) but gives error on Application server with version 9.0.4.0. Is this a problem with OC4J application server 9.0.4.0. I had gone through the documentation ofOC4J 9.0.4.0.application server but it does not mention about the this bug/fixes.
Please giude me on the same.
Regards,Shyam

Error Differance is too large for Customer clearning

Hi,
When I am trying to clear the customer f-32 i am getting the error as "(F5 263) The difference is too large for clearing".
Excise invoice is created in USD . when i clear the payment in indian currency the erors occurs.
Request you to please help me in resolving the same.
Thanks & Regards,
Neeraj

Hi Vivek,
There are 2533 documents with same assignment and I am trying to clear this documents.
Document currencies are in USD, HKD, GBP, JPY and there is balance in all these currencies.
Local currency is MOP total of which is zero for all this documents.
On Initial screen I am giving MOP which is local currency.
Can you explain me how to clear this through F-03, is there any other way to clear this?

DTW error message - Data too large for the field65171

Am trying to run up General Legder Accounts using DTW in Version 8.8 and have been successful with Level 2. The customer has three levels only. The total number of characters for the various segments is 18 and I have double and triple checked that the column "Code" has exactly 18 characters. Even used "=trim" in Excel several times.
When I run DTW for level 3 it errors out and it displays the above error message. What is field 65171???
I thought DTW was supposed to be so much improved with 8.8 - where are help files that tell you what the errors are???
Regards - Zal

Hi ZAL,
I am facing this error too when exporting chart of account through DTW SAP 8.8 PL 19, although some of accounts are imported but in somme accounts saying the " data too large for the filed65171".
Account code is of 7, as it reuires 9 Max,
Please suggest me on this .
Regards
rps

Ora-14036 error partition bound too large for column

Hi All,
I have a partitioned table on balance_period .. format YYYYMM .
I am trying to split the PMAX partition but get the errors :-
> ALTER TABLE ACT_MD_FOREIGNEXCHANGE SPLIT PARTITION ACT_MD_FOREIGNEX_PMAX AT (TO_DATE ('20081201', 'YYYYMMDD))
2 INTO (PARTITION ACT_MD_FOREIGNEX_200812, PARTITION ACT_MD_FOREIGNEX_PMAX);
ALTER TABLE ACT_MD_FOREIGNEXCHANGE SPLIT PARTITION ACT_MD_FOREIGNEX_PMAX AT (TO_DATE ('20081201', 'YYYYMMDD))
ERROR at line 1:
ORA-01756: quoted string not properly terminated
> ALTER TABLE ACT_MD_FOREIGNEXCHANGE SPLIT PARTITION ACT_MD_FOREIGNEX_PMAX AT (TO_DATE ('20081201', 'YYYYMMDD'))
2 INTO (PARTITION ACT_MD_FOREIGNEX_200812, PARTITION ACT_MD_FOREIGNEX_PMAX);
ALTER TABLE ACT_MD_FOREIGNEXCHANGE SPLIT PARTITION ACT_MD_FOREIGNEX_PMAX AT (TO_DATE ('20081201', 'YYYYMMDD'))
ERROR at line 1:
ORA-14036: partition bound value too large for column
What is the correct format for the AT part of the statement please ?

I believe that the partition definitions for the other partitions are not the same as the value you gave in your split statement. Check the definitions for the existing partitions.
14036, 00000, "partition bound value too large for column"
// *Cause: Length of partition bound value is longer than that of the
// corresponding partitioning column.
// *Action: Ensure that lengths of high bound values do not exceed those of
// corresponding partitioning columnsJohn

ORA-06502: PL/SQL: numeric or value error:. number precision too large, ORA-06502: PL/SQL: numeric or value error:. number precision too large

I have hit with above error and the code did run successfully before the minor change in the portion I have bolded. Appreciate your comment & help.
Attached with the code:
CREATE TABLE RPT1120B_CHANNEL_new
(SUBSCRIBER_NO NUMBER (9),
FP_CHANNEL VARCHAR2(255),
FP_DATE DATE,
FP_DYNASTY CHAR(1),
FP_MOVIE CHAR(1),
FP_FUN CHAR(1),
FP_LEARNING CHAR(1),
FP_NEWS CHAR(1),
FP_SPORTS CHAR(1),
FP_VARIETY CHAR(1),
FP_EMPEROR CHAR(1),
FP_SX1 CHAR(1),
FP_CEL CHAR(1),
LP_CHANNEL VARCHAR2(255),
LP_DATE DATE,
LP_DYNASTY CHAR(1),
LP_MOVIE CHAR(1),
LP_FUN CHAR(1),
LP_LEARNING CHAR(1),
LP_NEWS CHAR(1),
LP_SPORTS CHAR(1),
LP_VARIETY CHAR(1),
LP_EMPEROR CHAR(1),
LP_SX1 CHAR(1),
LP_CEL CHAR(1));
--truncate table RPT1120B_CHANNEL;
create or replace PROCEDURE sp_rpt1120b_new
AS
FP_CHANNEL VARCHAR2(255);
FP_DATE DATE;
LP_CHANNEL VARCHAR2(255);
LP_DATE DATE;
REC_COUNT NUMBER(3);
TYPE REC_SA IS RECORD
(AGREEMENT_NO NUMBER (9));
TYPE REC_CHANNEL IS RECORD
(CHANNEL VARCHAR2(3),
AGREEMENT_NO NUMBER (9));
BEGIN
FOR REC_SA IN (SELECT DISTINCT SUBSCRIBER_NO FROM RPT1120B_T1_new) LOOP
     FP_CHANNEL := '';
     LP_CHANNEL := '';
     REC_COUNT := 0;
     FP_DATE := '';
     LP_DATE := '';
     FOR REC_CHANNEL IN      (SELECT distinct decode(SOC,
                                   29990,'N',
                                   29991,'V',
                                   29993,'M',
                                   29988,'F',
                                   29989,'L',
                                   29992,'S',
                                   29994,'D',
                                   29995,'E',
                                   30277,'C',
                                   30293,'C',
                                   30319,'C',
                                   30359,'C',
                                   30276,'X',
                                   30331,'X',
                                   30299,'X',
                                   30380,'X')
                    AS CHANNEL,SA.EFFECTIVE_DATE as soc_sts_date
               FROM      SERVICE_AGREEMENT SA
               WHERE      SA.SOC in (          29990,
                                   29991,
                                   29993,
                                   29988,
                                   29989,
                                   29992,
                                   29994,
                                   29995,
                                   30277,
                                   30293,
                                   30319,
                                   30359,
                                   30276,
                                   30331,
                                   30299,
                                   30380) AND
                    SA.AGREEMENT_NO = REC_SA.SUBSCRIBER_NO AND
                    TRUNC(SA.EFFECTIVE_DATE) <> TRUNC(NVL(SA.EXPIRATION_DATE,SYSDATE)) AND
                    SA.EFFECTIVE_DATE = (SELECT MIN(SA1.EFFECTIVE_DATE) FROM SERVICE_AGREEMENT SA1
                              WHERE SA1.AGREEMENT_NO = SA.AGREEMENT_NO AND
                              sa1.soc in (
29990,
                                   29991,
                                   29993,
                                   29988,
                                   29989,
                                   29992,
                                   29994,
                                   29995,
                                   30277,
                                   30293,
                                   30319,
                                   30359,
                                   30276,
                                   30331,
                                   30299,
                                   30380))
                    order by DECODE(channel,'D',1,'M',2,'E',3,'C',4,'X',5,'F',6,'L',7,'N',8,'S',9,'V',10)) LOOP
               REC_COUNT := REC_COUNT + 1;
               if REC_COUNT < 254 then
                    FP_CHANNEL := FP_CHANNEL || REC_CHANNEL.CHANNEL;
               end if;
               FP_DATE := REC_CHANNEL.soc_sts_date;
     END LOOP;
     REC_COUNT := 0;
     FOR REC_CHANNEL IN      (SELECT distinct decode(sa.SOC,
                                   29990,'N',
                                   29991,'V',
                                   29993,'M',
                                   29988,'F',
                                   29989,'L',
                                   29992,'S',
                                   29994,'D',
                                   29995,'E',
                                   30277,'C',
                                   30293,'C',
                                   30319,'C',
                                   30359,'C',
                                   30276,'X',
                                   30331,'X',
                                   30299,'X',
                                   30380,'X')
                    AS CHANNEL,SA.soc_status_date as soc_sts_date
               FROM      SERVICE_AGREEMENT SA,
                    (SELECT MAX(SA1.soc_status_DATE) as soc_date, agreement_no, soc
                    FROM SERVICE_AGREEMENT SA1
                    WHERE soc in(          29990,
                                   29991,
                                   29993,
                                   29988,
                                   29989,
                                   29992,
                                   29994,
                                   29995,
                                   30277,
                                   30293,
                                   30319,
                                   30359,
                                   30276,
                                   30331,
                                   30299,
                                   30380)
                    GROUP BY agreement_no, soc) sa1
               WHERE      SA.SOC in (      29990,
                                   29991,
                                   29993,
                                   29988,
                                   29989,
                                   29992,
                                   29994,
                                   29995,
                                   30277,
                                   30293,
                                   30319,
                                   30359,
                                   30276,
                                   30331,
                                   30299,
                                   30380) AND
                    SA.soc_status_date = sa1.soc_date AND
                    TRUNC(SA.SOC_STATUS_DATE) <> TRUNC(NVL(SA.EXPIRATION_DATE,SYSDATE)) AND
                    SA.SOC_STATUS = (SELECT MIN(SA2.SOC_STATUS) FROM SERVICE_AGREEMENT SA2
                              WHERE SA2.AGREEMENT_NO = SA.AGREEMENT_NO AND sa2.soc = sa.soc
                              and SA2.soc_status_date = SA.soc_status_date)
                    order by DECODE(channel,'D',1,'M',2,'E',3,'C',4,'X',5,'F',6,'L',7,'N',8,'S',9,'V',10)) LOOP
               REC_COUNT := REC_COUNT + 1;
               if REC_COUNT < 254 then
                    LP_CHANNEL := LP_CHANNEL || REC_CHANNEL.CHANNEL;
               end if;
               LP_DATE := REC_CHANNEL.soc_sts_date;
     END LOOP;
     INSERT INTO RPT1120B_CHANNEL_new values
          (REC_SA.SUBSCRIBER_NO,
          substr(FP_CHANNEL,1 essageID=1196758, I have hit with above error and the code did run successfully before the minor change in the portion I have bolded. Appreciate your comment & help.
Attached with the code:
CREATE TABLE RPT1120B_CHANNEL_new
(SUBSCRIBER_NO NUMBER (9),
FP_CHANNEL VARCHAR2(255),
FP_DATE DATE,
FP_DYNASTY CHAR(1),
FP_MOVIE CHAR(1),
FP_FUN CHAR(1),
FP_LEARNING CHAR(1),
FP_NEWS CHAR(1),
FP_SPORTS CHAR(1),
FP_VARIETY CHAR(1),
FP_EMPEROR CHAR(1),
FP_SX1 CHAR(1),
FP_CEL CHAR(1),
LP_CHANNEL VARCHAR2(255),
LP_DATE DATE,
LP_DYNASTY CHAR(1),
LP_MOVIE CHAR(1),
LP_FUN CHAR(1),
LP_LEARNING CHAR(1),
LP_NEWS CHAR(1),
LP_SPORTS CHAR(1),
LP_VARIETY CHAR(1),
LP_EMPEROR CHAR(1),
LP_SX1 CHAR(1),
LP_CEL CHAR(1));
--truncate table RPT1120B_CHANNEL;
create or replace PROCEDURE sp_rpt1120b_new
AS
FP_CHANNEL VARCHAR2(255);
FP_DATE DATE;
LP_CHANNEL VARCHAR2(255);
LP_DATE DATE;
REC_COUNT NUMBER(3);
TYPE REC_SA IS RECORD
(AGREEMENT_NO NUMBER (9));
TYPE REC_CHANNEL IS RECORD
(CHANNEL VARCHAR2(3),
AGREEMENT_NO NUMBER (9));
BEGIN
FOR REC_SA IN (SELECT DISTINCT SUBSCRIBER_NO FROM RPT1120B_T1_new) LOOP
     FP_CHANNEL := '';
     LP_CHANNEL := '';
     REC_COUNT := 0;
     FP_DATE := '';
     LP_DATE := '';
     FOR REC_CHANNEL IN      (SELECT distinct decode(SOC,
                                   29990,'N',
                                   29991,'V',
                                   29993,'M',
                                   29988,'F',
                                   29989,'L',
                                   29992,'S',

The error message has an important hint: "number precision too large"
Change REC_COUNT's type from NUMBER(3) to NUMBER and see what happens.

Bex Report Error -- Query is Too Large

Hello I am Using Hierarchies in Rows and in Columns Company Wise, Quarter Month Wise Values
I am Using 310 Rows and 100 columns As this is Summary Report I cannot go for Filters and I cannot
Decrease Keyfigures is there any solution for this , Please give me the valuable suggestion for this query.

If the query is too large and you are running out of memory, then either you should run the report with smaller selection (may be year -wise) or increase your server parametres like memory space etc.

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

Similar Messages

Maybe you are looking for