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.

Similar Messages

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.

I get an error message File too large for formatted drive when trying to copy a large video file (~50GB) to a new 64 GB USB drive. Any thoughts?

I am copying from a MAC to the new drive - not sure the format of the USB drive, whatever the SANDISK Cruzer is default formatted to..

You state that Cruzer is formatted which is proably FAT32. FAT32 has limits on file size of 4 GB.
Since you are copying larger files then you will need to reformat.
Allan

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

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.

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

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.

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.

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

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

Hi, I updated my version of iTunes and now get the error "The program can't start because MSVCR80.dll is missing from your computer".

Hi, I hope some one can help as I updated my version of iTunes and now get the error "The program can't start because MSVCR80.dll is missing from your computer". I understand that I need to delete and reinstall iTunes but all of my music has been uploaded from CD's and I'd like to know if these are safe if I delete iTunes of if they too will be deleted. I have over 1300 songs so this is a big question for me. Many thanks.

Under normal circumstances, an uninstall/reinstall doesn't touch your content. (That being said, it's still always a good idea to maintain a current backup at all times in case of disasters of any sort.)
First try updating to iTunes 11.1.5.5, using an installer downloaded from the Apple website:
http://www.apple.com/itunes/download/
If you still get the errors after that, try the following user tip:
Troubleshooting issues with iTunes for Windows updates

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

Get an error 123 (Program Too Large)

Similar Messages

Maybe you are looking for