Deploying Dimension give PLS-00123 error (program too large)

Hi,
I'm using OWB 10.2 with a Windows 10g 64bit environment. I successfully deployed a dimension to my target data warehouse. Later, I went back to the dimension and added 5 dimension roles to it and redeployed. When redeploying with the dimension roles, I get the following error:
ORA-06550: line 1495, column 81:
PLS-00123: program too large (Diana nodes)
The recommendation is to break up the PL/SQL code according to the error message but this is generated code so I'm out of luck there. Any suggestions or settings that might alleviate this?
TIA,
mike

In past DW efforts (Informatica, Sybase IQ/Oracle/DB2), I've used synonyms or views against a base time dimension to handle the "roles" so that each looks like a distinct dimension. I'm trying to do the equivalent from OWB. Initially the DW will be relational, but I may generate some cubes from the DW in the future.
Not sure what you mean by a "pure relational" solution. We will be using discoverer in our environment, but not exclusively. There will be other reporting tools in use as well.

Similar Messages

Program too large error

Hello Friends
I am using oracle forms 6.
I write code on button's WHEN-BUTTON-PRESSED event and then compile that trigger at that time i am getting error
"program too large"
Ofcourse on that event coding is large but what i have to do to avoid that compilation error.
i serched for solution then i got that
.ENABLE COMPILER SIZECHECK write this command but where to write or to set this property?
Can any one know then please help me.
Or if another solution then i appreciate with that solution.
Thanks in advance...

Before you play with any compiler parameters (which is not recommended) you might want to try the following first.
1- Remove all unnecessary lines from the code, like carriage returns.
2- Remove all extra spaces, or comments you do not need.
But most importantly, remove your code from the trigger and put it in an PL/SQL Program Unit in your form and call it from the WHEN-BUTTON-PRESSED trigger.
Also you can break your code into smaller procedures so you can call it separately.
Regards,
Tony

"program too large" on package compile

Hi,
I am trying to compile a package (which has around 3000+ lines), and I am getting an error "program too large".
I believe I would need to split into 2 packages, but is there any other solution than splitting the code?
I am building a dynamic package from here using system.ad_ddl. Can I use system.ad_ddl in two different packages and in the end create the object in one of the packages? (will it take the statements added from both the packages?)
Thanks,
Sharad

system.ad_ddl is not a Oracle documented program unit name. How did it get into the SYSTEM schema?
Can you post a Oracle doc link to this code unit where it is available?

Exporting from HTML DB 1.4 to 2.0 - "Program too large (Diana nodes)"

Hi
I exported an HTML DB 1.4. into a script and got an error while trying to execute it.
The script itself is over 800 kb and consists of 25 000 lines. However, it is divided into begin-end blocks.
If I start the script in HTML DB 2.0 I get an error:
"Program too large (Diana nodes)"

Sorry, it should have been HTML DB 1.4 <b>application</b>.
The application causing this problem has also a page with about 200 items, so I hope that after I have splitted this problematic page into multiple pages, this "program too large" problem would also solve.

Strange Error: PLS-00123:program too large

Hi,
I was wondering whether, when using Oracle Application Database configuration tool, anyone has seen the following:
error occured during batching: ORA- 06550: live 11024, column 1: PLS-00123:program too large.
This occured when trying to create a new OLT schema on a remote database (Oracle 10g 64 bit, running on Solaris 9).
I've never seen this particular error before......
Any ideas would be welcome
Regards
Wayne.

Hi JB,
I've created an SR....let see what happens :)
Wayne.

PLS-00123: Program too large error

Hi,
We have been getting a 'PLS-00123: Program too large' error while compiling a particularly large package on a *11g database*. The package has around 15000 lines of code. We are compiling the package using a third party IDE(PL/SQL Developer).
I went through AskTom's note (http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:571023051648) and Metalink Note#62603.1 which helped in understanding the problem. However, could not resolve the problem since modifying the structure of the package was not an option.
Someone from the team contacted a DBA regarding this who in turn suggested that we compile the package in SQL*Plus. We did as suggested on a *10g client* connected to the 11g database and the package got compiled.
I cannot understand why we encountered the error while compiling the package in PL/SQL Developer but not while doing the same from SQL*Plus. Can anyone please explain this or point out some helpful documents?
Regards,
Sujoy

Hope this link helps..
http://forums.allroundautomations.com/ubb/ubbthreads.php?ubb=showflat&Number=10265&PHPSESSID=2e3c1b028a66500ae8a1730abc88b993

'Program Too Large' error in PL/SQL

How to get rid of 'PLS-00123 - Program Too Large' error ? This comes when the program to be compiled goes more than a certain limit.
One way is to make the program modular by splitting the logic in several Procedures/functions and packaged procedures.
Is there any other way to fix this problem ? Any variable or parameter which we can set to get rid of this error.
Thanks.

There are some linits on program size and so the obvious thing to do (as the error suggests) is to break the program unit. It makes it a lot easier to maintain as well.
Regards
Grant Ronald
Forms product Management

Any workaround for Program too large error?

Dear All,
When a program of size 5432 lines compiled(it is having 4 cursor definitions attached to huge select statement from multiple tables), getting an error "PLS-00123 Program too large". Oracele error manual suggests to split the program. Is there any other way to make it work without splitting? (I mean setting some system variables?)
Thanks
Sheeba

What it means by splitting can be achieved by somethingon the lines of changing
PROCEDURE one is
command1;
command2;
command3;
command4;
command5;
command6;
END;
PROCEDURE one is
PROCEDURE onea IS
command1;
command2;
command3;
END
PROCEDURE oneb IS
command4;
command5;
command6;
END
onea;
oneb;
END;
If the problem is the size of the cursors all in the declare section, then you may be able to declare them initially as ref cursors, then having four separate sub procedures opening them so that the text of the cursors are in the subprocedures.
Alternatively, stick the selects into views.

ORA-06553: PLS-123: program too large on import

Hi,
I import a dump file from a 9.2.0.4 to an other 9.2.0.4 database.
On some importing table, I have this error :
. . importing table "PS_TL_PAYABLE_HIST" 0 rows imported
IMP-00017: following statement failed with ORACLE error 6540:
"DECLARE SREC DBMS_STATS.STATREC; BEGIN SREC.MINVAL := NULL; SREC.MAXVAL :="
" NULL; SREC.EAVS := 0; SREC.CHVALS := NULL; SREC.NOVALS := DBMS_STATS.NUMAR"
"RAY(); SREC.BKVALS := DBMS_STATS.NUMARRAY(); SREC.EPC := 0; DBMS_STATS.SET_"
"COLUMN_STATS(NULL,'"PS_TL_PAYABLE_HIST"','"TL_QUANTITY"', NULL ,NULL,NULL,0"
",0,0,srec,0,0); END;"
IMP-00003: ORACLE error 6540 encountered
ORA-06540: PL/SQL: compilation error
ORA-06553: PLS-123: program too large
IMP-00017: following statement failed with ORACLE error 6540:
"DECLARE SREC DBMS_STATS.STATREC; BEGIN SREC.MINVAL := NULL; SREC.MAXVAL :="
" NULL; SREC.EAVS := 0; SREC.CHVALS := NULL; SREC.NOVALS := DBMS_STATS.NUMAR"
"RAY(); SREC.BKVALS := DBMS_STATS.NUMARRAY(); SREC.EPC := 0; DBMS_STATS.SET_"
"COLUMN_STATS(NULL,'"PS_TL_PAYABLE_HIST"','"BILLABLE_IND"', NULL ,NULL,NULL,"
"0,0,0,srec,0,0); END;"
IMP-00003: ORACLE error 6540 encountered
ORA-06540: PL/SQL: compilation error
ORA-06553: PLS-123: program too large
IMP-00017: following statement failed with ORACLE error 6540:
"DECLARE SREC DBMS_STATS.STATREC; BEGIN SREC.MINVAL := NULL; SREC.MAXVAL :="
" NULL; SREC.EAVS := 0; SREC.CHVALS := NULL; SREC.NOVALS := DBMS_STATS.NUMAR"
"RAY(); SREC.BKVALS := DBMS_STATS.NUMARRAY(); SREC.EPC := 0; DBMS_STATS.SET_"
"COLUMN_STATS(NULL,'"PS_TL_PAYABLE_HIST"','"OPRID"', NULL ,NULL,NULL,0,0,0,s"
"rec,0,0); END;"
IMP-00003: ORACLE error 6540 encountered
ORA-06540: PL/SQL: compilation error
ORA-06553: PLS-123: program too large
IMP-00017: following statement failed with ORACLE error 6540:
"DECLARE SREC DBMS_STATS.STATREC; BEGIN SREC.MINVAL := NULL; SREC.MAXVAL :="
" NULL; SREC.EAVS := 0; SREC.CHVALS := NULL; SREC.NOVALS := DBMS_STATS.NUMAR"
"RAY(); SREC.BKVALS := DBMS_STATS.NUMARRAY(); SREC.EPC := 0; DBMS_STATS.SET_"
"COLUMN_STATS(NULL,'"PS_TL_PAYABLE_HIST"','"CLASS_FLD"', NULL ,NULL,NULL,0,0"
",0,srec,0,0); END;"
IMP-00003: ORACLE error 6540 encountered
ORA-06540: PL/SQL: compilation error
ORA-06553: PLS-123: program too largeThe import command is simple :
NLS_LANG=american_america.utf8
export NLS_LANG
/etc/mknod /data/ora/P97RPRD/e01/tube p
uncompress -c /data/ora/P97RPRD/e01/backup.dmp.Z > /data/ora/P97RPRD/e01/tube &
imp SYSTEM/MANAGER FROMUSER=P97RPPRD TOUSER=P97RPRD FILE=/data/ora/P97RPRD/e01/tube LOG=/data/ora/P97RPRD/adm/dbalog/importP97RPRD.logFrom where does it come ?
If I well understand, this is the import of statistics, but why this error ?
Is I can avoid this error if I import with STATISTICS=none ?
Thanks in advance,
Nicolas.

Hi please check this,
Select * from dba_objects where object_name = 'DBMS_STANDARD';
The standard package may be invalid.
reran catproc.sql This caused the dbms_standard package to become valid once again.
HTH,
Thomas.

ORA-06553: PLS-123: Program too large

Hi,
I have 2 databases, the development database (9i) and pruction database (10g). I have the same programs on the databases, but when I try to execute the package1.program1 for 3000 records in 10g, result in a error:
ORA-06540: PL/SQL Compilation error
ORA-06553: PLS-123: Program too large
9i is OK.
The program package1.program1 have a lot of DYNAMIC-SQL.
I need help. (Sorry for my English)
Thanks,
Ivan

Hi please check this,
Select * from dba_objects where object_name = 'DBMS_STANDARD';
The standard package may be invalid.
reran catproc.sql This caused the dbms_standard package to become valid once again.
HTH,
Thomas.

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.

How to fix the PLS-00123 error?

I construct about the oracle spatial sql as follow:
declare
ord sdo_ordinate_array := sdo_ordinate_array();
begin
begin for i IN 1 ..5624 LOOP
ord extend;
end LOOP;
ord(1) := number1;
ord(2) := number2;
ord(3) := number3;
ord(4) := number4;
insert into table(shape,....) values(SDO_GEOMETRY(2002,NULL,NULL,SDO_ELEM_INFO_ARRAY(1,2,1),ord));
END;
Because the count of geometry node is very long. I got the PLS-00123 error when I execute the state? somebody help me fix the problem?????
Message was edited by:
user646459

It seems more on PL/SQL error to me. Have you posted your question in PL/SQL forum?
Ming Man

Error :Value Too large for DEF_VALUE of SNP_REV_COL

I am getting the following error while I am importing my work repository .
Error : Value Too large for DEF_VALUE of SNP_REV_COL
Can any one pls let me know the root cause of the issue.
I found the following work around to resolve the issue.
I am changing the 'DEF_VALUE' column length in both 'SNP_REV_COL' and 'SNP_COL' tables.
I am using the ODI 10.1.3.5 version.
alter table SNP_REV_COL modify DEF_VALUE VARCHAR2 (400);
alter table SNP_COL modify DEF_VALUE VARCHAR2(400);
I am able to import the work_rep with out any issues after changing the above columns.
I am looking for the reason why this issues is occurring.
Thanks,
Yellanki
Edited by: Yellanki on Feb 7, 2011 3:18 AM

Ankit,
I am trying to move my Dev WR to Test. And my Source Technologies are SQL Server and Oracle.
Target is Oracle. I got the work around for this issue And I am looking for the root cause of the issue.
Any help is greatly appreciated.
Thanks,
Yellanki

HELP!!! Error "code too large"

Hello, I am working on a program that has become very large... and apparently it is too large now...
When I try to compile the program it generates an error, "code too large", the code has exceeded 10000 lines and now I dont know what to do. Anyone that has any ideas? Thankful for any response...

Let's say, for instance, that I wnat to initialize an array instance variable that will contain 7462 integer values in my constructor, just as an example. I'm not really sure if this exceeds the maximum size for a java array, but if it does that would be just as useless a restriction as this "code too large" thing. If I write huge code that means I need huge code. [ goes to write program in C, which would be my advice here. :) ]

Program too large

Hi, I am using Forms Developer 6.o and i encountered a "program too large" error on one of my program units. How can I resolve this? Does the size pertain to the number of commands used or the lines used in the program units? Thanks

Read Metalink note 99882.1: PL/SQL Size Limits Explained
Solution would be to split your program unit.

Deploying Dimension give PLS-00123 error (program too large)

Similar Messages

Maybe you are looking for