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.

Similar Messages

'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

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

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

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)

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.

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.

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.

Disk Utility: Creating a new blank image receiving "file too large" error.

Hello All!
I'm trying to create a 10GB non-encrypted, non-compressed RW blank image via the disk utility. The DU runs for a few minutes then barfs out "file too large" error. I have over 30GB free on my HDD. I tried with a smaller size of 6GB to no avail. Also tried unsuccessfully to create from a file (about 4 GB). My ultimate goal is to create a case-insensitive image to run an extremely important program needed for high priority work productivity (i.e. WoW). Thanks in advance for any advice! You will be my new best friend if you help me resolve this. =D
Hollie
"There are only 10 types of people in this world: Those who understand binary, and those who don't."

Hi Hollie, and welcome to the forums!
Have you created images before successfully?
Is this to/on your boot drive, or an external drive?
Have you done any Disk/OS maintenance lately?
We might see if there are some big temp files left or such...
How much free space is on the HD, where has all the space gone?
OmniDiskSweeper is now free, and likely the best/easiest...
http://www.omnigroup.com/applications/omnidisksweeper/
WhatSize...
http://www.macupdate.com/info.php/id/13006/
Disk Inventory X...
http://www.derlien.com/
GrandPerspective...
http://grandperspectiv.sourceforge.net/

Code too large error

Hi,
I have an enum with about 3000 values in application. When I add some more items I get "code too large" error during compilation.
Is there any workaround for that problem? (Some configuration change?)
What exactly does compiler want to say? Where can I find info about what limit do I exceed?
I will appreciate any kind of help :)
Greetings
Michal

what can you kno? Model of the form is not hardcoded, it is in DB, it is modifiable by user(admin). Only elements which have specific business validation have identifier (i mean enum identifier). They must be somehow identified, not just by number. Number may change if sone adds a question before this one.
What's better than that? The solution has been made before I came to the company, but I believe it is one of the best possible.

How to find the exact coloumn which fired the column value too large error

Hi all
I have a procedure which has a insert statement init.
I have encountered an column value too large error in that procedure.
I want to know exactly in which column the error has come
Any ideas,
Thanks
Hari

What is your insert statement? I get the exact column name here.
SQL> create table sample1(col1 number(1), col2 number(3), col3 varchar2(2))
2 /
Table created.
SQL> insert into sample1
2 select 1, 2, 'A' from dual
3 union
4 select 1,333, 'B' from dual
5 union
6 select 2, 44, 'CCC' from dual
7 /
insert into sample1
ERROR at line 1:
ORA-12899: value too large for column "ETL_USER"."SAMPLE1"."COL3" (actual: 3,
maximum: 2)
SQL> Cheers
Sarma.

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

"result too large" error when accessing files

Hi,
I'm attempting to make a backup copy of one of my folders (using tar from shell). For several files, I got "Read error at byte 0, reading 1224 bytes: Result too large" error message. It seems those files are unreadable. Whatever application attempts to access them results with the same error.
The files reside on the volume that I created a day ago. It's a non-journaled HFS+ volume on external hard drive. They are part of an Aperture Vault that I wanted to make an archive copy and store offsite. Aperture was closed (not running) when I was creating the archive.
This means two things. The onsite backup of my photos is broken, obviously (some of the files are unreadable). My offsite backup is broken, since it doesn't contain those files.
I've searched the net, and found couple of threads on some mailing lists describing same problem. But no answer. Couple of folks on those mailing lists suggested it migh point to full disk. However, in my case, there is some 450GB of free space on the volume I was getting read errors on (the destination volume had about 200GB free, and system drive had about 50GB free, so there was plenty of space all around the system too).
File system corruption?
Mac OS X (10.4.9)

Here's the tar command with the output:
$ tar cf /Volumes/WINNIPEG\;TOPORKO/MacBackups/2007-05-27/aperture.tar Alex\ -\ External\ HD.apvault
tar: Alex - External HD.apvault/Library/2003.approject/2007-03-24 @ 08\:17\:52 PM - 1.apimportgroup/IMG0187/Thumbnails/IMG0187.jpg: Read error at byte 0, reading 3840 bytes: Result too large
tar: Alex - External HD.apvault/Library/2006.approject/2007-03-24 @ 08\:05\:07 PM - 1.apimportgroup/IMG2088/IMG2088.jpg.apfile: Read error at byte 0, reading 1224 bytes: Result too large
tar: Alex - External HD.apvault/Library/Jasper and Banff 2006.approject/2007-03-25 @ 09\:41\:41 PM - 1.apimportgroup/IMG1836/IMG1836.jpg.apfile: Read error at byte 0, reading 1224 bytes: Result too large
tar: Alex - External HD.apvault/Library/Old Scanned.approject/2007-03-24 @ 12\:42\:55 AM - 1.apimportgroup/Image04_05 (1)/Info.apmaster: Read error at byte 0, reading 503 bytes: Result too large
tar: Alex - External HD.apvault/Library/Old Scanned.approject/2007-03-24 @ 12\:42\:55 AM - 1.apimportgroup/Image16_02/Info.apmaster: Read error at byte 0, reading 499 bytes: Result too large
tar: Alex - External HD.apvault/Library/Vacation Croatia 2006.approject/2007-03-25 @ 09\:47\:17 PM - 1.apimportgroup/IMG0490/IMG0490.jpg.apfile: Read error at byte 0, reading 1224 bytes: Result too large
tar: Error exit delayed from previous errors
Here's the "ls -l" output for one of the files in question:
$ ls -l IMG_0187.jpg
-rw-r--r-- 1 dijana dijana 3840 Mar 24 23:27 IMG_0187.jpg
Accessing that file (or any other from the above list) gives same/similar error. The wording differes from command to command, but basically it's the same thing (read error, or result too large, or both combined). For example:
$ cp IMG_0187.jpg ~
cp: IMG_0187.jpg: Result too large
The console log doesn't show any related errors.

File too large error message

I have an iBook G4 and I am running Numbers '08. I tried to open my budget document today and got an 'The document can't be opened because it is too large' error message. I just opened it a few days ago and it was fine, and my other Numbers documents are opening fine. It is a spreadsheet with about 5 sheets - not really THAT big, especially considering some of the Excel spreadsheets I deal with at work. Any ideas? This is (of course) the most important document on my computer...

(1) comparing to Excel documents size is meaningless.
Given the fact that Numbers uses xml, its files are huge.
(2) Try to close every application including Numbers then, double click your document.
Doing that you will have the maximum memory available for the document.
(3) check the quantity of space available on your HD.
Numbers make an heavy use of virtual memory so, it need a lot of free space available on the HD.
If these tracks don't help, you may send the document to my mailbox (use the free YouSendit if it's too big for a attachment)
I would try to open it and scan it to see if there is a way to reduce its memory requirements.
Click my blue name to get my address.
Don't worry if it contains personal infos, i'm neither the KGB, nor the CIA.
Yvan KOENIG (VALLAURIS, France) dimanche 1 août 2010 10:42:09

Page Too Large Error with JHS 10.1.3.2

Hi,
I have migrated to the new version of JHS (10.1.3.2). According to the JHS documentation the “page to large error” has been fixed in this version but I am still experiencing this problem.
I have checked the boxes for Generate Group in Region File and Generate Search Area in Region File in the app def for the large page that I have in my app. With this done the “page too large” error occurs. I then tried checking the box for Generate in Region File on each item group region on my page but the “page too large” error still happens. None of my item group regions contain that many items (average is about 10 items).
Is any one having the same issues?
Regards
Bar

josealej,
Have you spilt up your items into different regions and selected the option to generate the groups in a region file? If so then you can try setting the "generate in region file" option on each region container. Check out section 4.6.2 in the JHS developers manual.
Sandra,
Unfortunately I don't have enough free time to debug the problem. I will look into it when my schedule is not as hectic.
Bar

Any workaround for Program too large error?

Similar Messages

Maybe you are looking for