Compile UTL_FILE PACKAGE BODY

Hi ALL,,,
I refreshed one db from PROD dump.
After that I compiled all Invalid objects .But am unable to compile UTL_FILE PACKAGE BODY
Showing all are invalid.
OBJECT_NAME OBJECT_TYPE OWNER
UTL_FILE PACKAGE BODY UTLFILE
UTL_FILE_EX PACKAGE BODY UTLFILE
UTL_FILE_ADMIN PACKAGE BODY UTLFILE
SQL> show parameter utl
NAME TYPE VALUE
create_stored_outlines string
utl_file_dir string
Please help me how to compile this.
If I tried to copile manualyy..I am gettimg Error like..PACAGE ALTERED WITH COMPILATION Errors.
Thanks
Manohar.

Invalid objects are best compiled by using
sqlplus / as sysdba
@?\rdbms\admin\utlrp
This will report the number of invalid objects when finishing.
When you still have invalid objects you should query dba_errors where name='<name of invalid object>'
All Oracle provided sources are in
%ORACLE_HOME%\rdbms\admin
You can simply find or grep for utl_file.
There always will be two files
utl<facility>.sql (or dbms<facility>.sql) and prvt<facility>.plb
You need to run them both in sqlplus connected as sysdba.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

Help required in compilation of package body.....

Hi ..
While taking the export i encounter the error message..
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00056: ORACLE error 6550 encountered
ORA-06550: line 1, column 26:
PLS-00201: identifier 'XDB.DBMS_XDBUTIL_INT' must be declared
ORA-06550: line 1, column 14:
PL/SQL: Statement ignored
EXP-00000: Export terminated unsuccessfully..
SELECT status,object_id,object_type,owner,object_name
FROM dba_objects
WHERE object_name = 'DBMS_XDBUTIL_INT';
gives the output as...
status object type owner object_name
valid synonym public DBMS_XDBUTIL_INT
valid package xdb DBMS_XDBUTIL_INT
invalid package body xdb DBMS_XDBUTIL_INT
when i try to compile the invalid object...
SQL> alter package XDB.DBMS_XDBUTIL_INT COMPILE BODY;
Warning: Package Body altered with compilation errors.
SQL> sho err
Errors for PACKAGE BODY XDB.DBMS_XDBUTIL_INT:
LINE/COL ERROR
61/7 PL/SQL: Statement ignored
61/17 PLS-00306: wrong number or types of arguments in call to
'IS_HIERARCHY_ENABLED_INTERNAL'
74/7 PL/SQL: Statement ignored
74/29 PLS-00302: component 'GENERATE_TRGNM' must be declared
108/9 PL/SQL: Statement ignored
108/37 PLS-00302: component 'TRUNCATE_NAME' must be declared
123/7 PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
123/7 PL/SQL: Statement ignored
135/9 PL/SQL: Statement ignored
LINE/COL ERROR
135/37 PLS-00302: component 'TRUNCATE_NAME' must be declared
153/9 PL/SQL: Statement ignored
153/33 PLS-00302: component 'TRUNCATE_NAME' must be declared
168/7 PLS-00201: identifier 'SYS.DBMS_SYS_SQL' must be declared
168/7 PL/SQL: Statement ignored
181/9 PL/SQL: Statement ignored
181/33 PLS-00302: component 'TRUNCATE_NAME' must be declared
Since the code is wrapped .. i cant do anything.. needs ur help.
sorry for explaining in such a detail...
Message was edited by:
437022

Hi,
In side the Package Body,
a) invalid arguments for IS_HIERARCHY_ENABLED_INTERNAL
b) invalid components GENERATE_TRGNM, etc.
First, you need to correct the above errors and then
try to compile the Package Body
Regards,
Sailaja

How to compile all package body using sqlplus ?

hi all,
How to compile all package body using sqlplus ?
Please help.
Amy

dbms_utility.compile_schema will compile all the invalid objects in a schema, including the invalid package bodies. If you only want to compile the invalid package bodies, you could write your own dynamic SQL stored procedure to do that using the user_source view, but that's a lot more effort for a very minimal benefit.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

EA 3.0 returns error on compiling of package body

Hi,
I got the following error
Error: ORA-06550: line 1, column 64:
PLS-00172: string literal too long
when I was trying to compile package body.
In previous version of SQL DEV the package is compiled without any problems.
I have a procedure in package with more than 120 parameters.
Edited by: user635344 on Oct 15, 2010 10:54 AM

This problem is a bug : SQL*Developer 3EA1 - Not Compiling package Body
regards Karsten

ORA-12571 --- Error while compiling any package body...

Recently I am having this error when I try to compile a pacakge body it terminates my oracle session and my SQLPlus on windows NT generates a application error and shuts down. When I compile the same package body from a unix box it just goes fine. Do any of you guys encountered any similar things like this, please share your findings. I have attached the error message in the end of the message for further information.
Thanks
Divakar.R
SQL> @C:\Divakar\FEA_SSR_AUTO.SQL
Input truncated to 1 characters
CREATE OR REPLACE Package Body FEA_SSR_Auto Is
ERROR at line 1:
ORA-12571: TNS:packet writer failure
ORA-24323: value not allowed
Error accessing package DBMS_APPLICATION_INFO
ERROR:
ORA-03114: not connected to ORACLE
null

if you look into sql.bsq in your oracle_home/rdbms
directory, table IDL_UB2$ has storage parameter
extents defined as maxextents.
check out the parameter of your IDL_UB2$ table.
By the way what is your oracle version?
For a long time, modifying the sql.bsq file was
frowned upon, but there is a section in the Tuning
guide about modifying this file now.
Reference chapter 15.
Jaffar
Message was edited by:
The Human FlyBut why do you need to modify the sql.bsq file when this problem can be analyzed by checking the availability of free space in SYSTEM tablespace.
And what benefit will you get by modifying this file after the database has been already created?
This file is the seed of the database and I think careful consideration must be taken before even thinking of touching this file. Also you must be fully aware of the aftermath.

Package body does not compile in Object Browser

Hi there,
I am trying to compile a package body using the Apex Object Browser. However, when I click the "Compile" button no message is displayed in the box above the package body code. I reduced the amount of code by removing comments and extra carriage returns and it then compiled ie the message "PL/SQL code successfully compiled (18:35:55) " was displayed. After trial and error I found that by adding just one character to the end of a comment line would cause this problem and by removing it the problem would dis-appear.
I raised this issue back on 19th June, and sspadafo responded by suggesting that I upgrade from Apex 2.1 to Apex 3.2. (Thanks by the way). This I have now done but the problem is still occurring. Is there some parameter that I have to increase in order to compile packages greater than a couple of kilobytes in size?
Database is 10.2 XE running on Windows Vista Home Premium.
Thanks.
John.

What would you say is a large package that sometimes causes the compilation to fail? For example, in excess of 10000 lines of code.
I've just tried a package with the minimal amount of code, with as many comments as required to demonstrate the problem as follows:
Note: The last comment is on line number 108!
create or replace package body "TEST_PACKAGE" is
--Comments comments comments comments comments
--Comments comments comments comments comments
--Comments comments comments comments comments
--Comments comments comments comments comments
--Comments comm...
... comments comments comments
--Comments comments comments comments comments
--Comments comments comments comments commen
procedure TEST_PROC
as
begin
null; /* insert procedure code */
end TEST_PROC;
end "TEST_PACKAGE";
{end code}
You will notice that the last comment line is truncated. The above compiles everytime, but by adding one more character to the last comment line will cause it not to compile everytime. Downloading the above to disk gives a size of 5134 bytes, which is twice the size of the other package, which has a little more code, that I was trying to compile. When I say a "a little more code", I mean two procedures and one function of approximately 20 lines each!
Oh well! Looks like I'll have to give SQLDeveloper a try as I don't fancy going through the "edit file/action file" loop in SQL*Plus or the "submit script/wait for results/examine results" loop in SQL Scripts.
(For info, I am using Internet Explorer 7)
Thanks.

30EA1: PLS-00172 when compiling package body

Hi there,
I'm having a strange bug when compiling a package body in SQL Developer 3.0 EA1, while the same package body compiles well in production version (2.1).
The error code returned is Error: ORA-06550: line 1, column 64: PLS-00172: string literal too long
Does anyone have the same problems?

yes: SQL*Developer 3EA1 - Not Compiling package Body
Hope that helps,
K.

Bind variable issue in Package Body

When I try to compile my package body, I get an error on the variables declared within the procedure. Bind variable not allowed. Any thoughts?

Apparently the error was related to something else, and the message was mis-leading. When I re-structured the code for other reasons, the 'error' was no longer showing up. Sorry for the confusion.

Function call in procedure within Package Body

I am a novice in PL/SQL so that I can't find out where the problem is. I am testing a function call in procedure within a Package Body.
But the PL/SQL Complier doesn't compile the package body but I don't know what I do wrong. Plz let me know how to call a function in procedure within a Package Body?
Here are the Packaget test programs..
CREATE OR REPLACE PACKAGE manage_students
IS
PROCEDURE find_sname;
PROCEDURE find_test;
PROCEDURE find_test_called;
FUNCTION GET_LASTMT
RETURN SEQUENCE_TEST.SEQ_NO%TYPE;
END manage_students;
CREATE OR REPLACE PACKAGE BODY manage_students AS
v_max_nbr SEQUENCE_TEST.SEQ_NO%TYPE;
PROCEDURE find_sname
IS
BEGIN
BEGIN
SELECT MAX(SEQ_NO)
INTO v_max_nbr
from SEQUENCE_TEST;
DBMS_OUTPUT.PUT_LINE('MAX NUMBER is : '||v_max_nbr);
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
RETURN;
END;
COMMIT;
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
END find_sname;
PROCEDURE find_test
IS
BEGIN
BEGIN
DBMS_OUTPUT.PUT_LINE('MAX NUMBER Called from another procedure : '||v_max_nbr);
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
RETURN;
END;
COMMIT;
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
END find_test;
FUNCTION GET_LASTMT
RETURN SEQUENCE_TEST.SEQ_NO%TYPE
IS
v_max_nbr SEQUENCE_TEST.SEQ_NO%TYPE;
BEGIN
SELECT MAX(SEQ_NO)
INTO v_max_nbr
from SEQUENCE_TEST;
RETURN v_max_nbr;
EXCEPTION
WHEN OTHERS
THEN
DECLARE
v_sqlerrm VARCHAR2(250) :=
SUBSTR(SQLERRM,1,250);
BEGIN
RAISE_APPLICATION_ERROR(-20003,
'Error in instructor_id: '||v_sqlerrm);
END;
END GET_LASTMT;
PROCEDURE find_test_called
IS
BEGIN
BEGIN
V_max := Manage_students.GET_LASTMT;
DBMS_OUTPUT.PUT_LINE('MAX_NUMBER :'|| V_max);
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
RETURN NULL;
END;
COMMIT;
EXCEPTION
WHEN OTHERS
THEN DBMS_OUTPUT.PUT_LINE('Error in finding student_id: ');
END find_test_called;
END manage_students;
DECLARE
v_max SEQUENCE_TEST.SEQ_NO%TYPE;
BEGIN
manage_students.find_sname;
DBMS_OUTPUT.PUT_LINE ('Student ID: Execute.');
manage_students.find_test;
manage_students.find_test_called;
END;
-----------------------------------------------------------------------------------------------

Hi,
Welcome to the forum!
You'll find that there are a lot of people willing to help you.
Are you willing to help them? Whenever you have a problem, post enough for people to re-create the problem themselves. That includes CREATE TABLE and INSERT statements for all the tables you use.
Error messages are very helpful. Post the complete error message you're getting, including line number. (It looks like your EXCEPTION sections aren't doing much, except hiding the real errors. That's a bad programming practice, but probably not causing your present problem - just a future one.)
Never post unformatted code. Indent the code to show the extent of each procedure, and the blocks within each one.
When posting formatted text on this site, type these 6 characters:
\(all small letters, inside curly brackets) before and after each section of formatted test, to preserve the spacing.
For example, the procedure find_test_called would be a lot easier to read like this:PROCEDURE find_test_called
IS
BEGIN
     BEGIN
          V_max := Manage_students.GET_LASTMT;
          DBMS_OUTPUT.PUT_LINE ('MAX_NUMBER :' || V_max);
     EXCEPTION
          WHEN OTHERS
          THEN
               DBMS_OUTPUT.PUT_LINE ('Error in finding student_id: ');
               RETURN      NULL;
     END;
     COMMIT;
EXCEPTION
     WHEN OTHERS
     THEN
          DBMS_OUTPUT.PUT_LINE ('Error in finding student_id: ');
END find_test_called;
It's much easier to tell from the code above that you're trying to return NULL from a procedure. Only functions can return anything (counting NULL); procedures can have RETURN statements, but that single word"RETURN;" is the entire statement.

Loosing Package Body after Save As to file

Hi,
loosing File and Package Body in
after Compiling a package body, I've tried to save this body to file via Save As.
(I've changed the directory and accepted the default filename). The file already exits in this directory, so I've accepted the overwrite dialog box.
Then the Package Body was removed from Database (not shown in the list of packages - also after several refreshs and filter changes) and the saved file contains only
CREATE OR REPLACE PACKAGE BODY
NULL
What I've done wrong?
Matthias

We need a few more details to replicate. Are you using 1.0.0.14.67 and which db version are you running against.
Then, was this an existing package body or one you were just creating. If just creating, did you already have a package spec and were creating the body? Did you do a right-click 'New Package Body'? If you compiled code, it would go into the database. I can't imagine that a Save As could possible drop that code.
-- Sharon

3.0EA4: NPE when open package body from file.

What I did:
1. start sqldeveloper
2. goto Files tab
3. dblclick a package body file (a_pkg.pkb) in recent file list.
4. dblclick another package spec file (a_pkg.pks) in recent file list.
5. error !
Here is the stack trace.
java.lang.NullPointerException
     at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1420)
     at oracle.ideimpl.editor.EditorManagerImpl.createEditor(EditorManagerImpl.java:1337)
     at oracle.ideimpl.editor.EditorManagerImpl.openEditor(EditorManagerImpl.java:1263)
     at oracle.ideimpl.navigator.OpenEditorController.whenOpenEditor(OpenEditorController.java:41)
     at oracle.ideimpl.navigator.OpenEditorContextMenuListener.handleDefaultAction(OpenEditorContextMenuListener.java:51)
     at oracle.ide.controller.ContextMenuListenersHook$LazyContextMenuListener.handleDefaultAction(ContextMenuListenersHook.java:200)
     at oracle.ide.controller.ContextMenu.fireDefaultAction(ContextMenu.java:434)
     at oracle.ideimpl.explorer.BaseTreeExplorer.fireDefaultAction(BaseTreeExplorer.java:1835)
     at oracle.ideimpl.explorer.BaseTreeExplorer.dblClicked(BaseTreeExplorer.java:2176)
     at oracle.ideimpl.explorer.BaseTreeExplorer.mouseReleased(BaseTreeExplorer.java:2205)
     at oracle.ideimpl.explorer.CustomTree.processMouseEvent(CustomTree.java:211)
     at java.awt.Component.processEvent(Component.java:5806)
     at java.awt.Container.processEvent(Container.java:2059)
     at java.awt.Component.dispatchEventImpl(Component.java:4413)
     at java.awt.Container.dispatchEventImpl(Container.java:2118)
     at java.awt.Component.dispatchEvent(Component.java:4244)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916)
     at java.awt.Container.dispatchEventImpl(Container.java:2102)
     at java.awt.Window.dispatchEventImpl(Window.java:2441)
     at java.awt.Component.dispatchEvent(Component.java:4244)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

I have several schemas but let us just look at the 2 .
I have open connections to both of the 2 schemas.
I do some work in the A schema and then returns
to the B-Schema, but forget to change the connection in the connection drop down list.
So now my connection points at the A-schema.
I open a package body file (from the file system !!!! not from the database)
do some corrections in the package body and then compiles the package body (belonging to the B-schema)
erroneously in the A-schema. I do not do this on purpose, but because i forgot to change the connection
and the connection in the "drop-down connection list" still points to the A-schema and I'm not prompted for
a password as the connection is open.)
The compiler compiles my package body in the A-schema with an error and tells me "package spec"
does not exist which is true - the package spec exists in the B-schema and not in the A-schema.
Therefore I choose the B-schema connection in the connection drop-down list in order to compile
the package body in the right schema (the B-schema).
Now I receive a message "your priviliges are insufficient" - which they are not.
The only way I can get back into business is to close down sqldeveloper re-open it and now
compile the package body in the right schema.
Sqldeveloper compiles the pck-body in the A-schema as it was told to do, it is not a random schema
I have to remove the pck-body afterwards !!
The annoying thing about this is I have to close down sqldeveloper in order to be able to compile my package.
I do not have explicit schema object reference in my declaration
regards

Compiling package body problem

hello
i have a problem with portal 9.0.2.2.22(win2k server). When i try to log in i get the error
Error: Could not open web cache connection. The portal use-web-cache setting is set to ON while web cache may be down. (WWC-40019)
after that i run oracle enterprise manager console, logged into iasdb and tried to compile different package bodies(dbe_build_sql, wwv_qbe,...) and get the error:
Line # = 0 Column # = 0 Error Text = PLS-00801: internal error [56106]
inside this package body there is only one word
wrapped
and nothing else
on a different machine i have in the same package body tons of code(dbe_build_sql consists of 20622 lines), inside my package only one word
wrapped
where is the problem?
can anybody help me? please
need help
thanks
Marjan

Marjan,
Try to post your question in the Portal Caching forum.

SQL*Developer 3EA1 - Not Compiling package Body

Don't know if this is best place to post this, if not tell me where.
In some packages i'm getting: Error: ORA-06550: linha 1, coluna 64:PLS-00172: literal de cadeia de caracteres demasiado extenso; Sorry about the portuguese error message but it's cpopy paste from compiler log.
The strange about this is that the package is compiling with no errors on Version 2.1.1.64 and also on others editors. In both packages i had this was after formatting the code.
So far is the only bug i got, keep on the good work.
António Cunha

Just tried from pl/sql node. The package body does not compile from there either. The issue seems to be the size of the package. The package size is 35,000 characters and spaces. I can remove any combination of source lines to get it down to 32,000 characters and spaces and it will compile.
Edited by: dagtech on Oct 21, 2010 9:34 AM

Can't compile package body

hello. i ran in to little issue today. After patch 13839550 was applied to one of our test enviroments, we get one invalid package body. but when i try to compile it shows warrning!
SQL> alter package APPS.AP_ACCTG_DATA_FIX_PKG compile body;
Warning: Package Body altered with compilation errors.
SQL>
SQL> show err
Errors for PACKAGE BODY APPS.AP_ACCTG_DATA_FIX_PKG:
LINE/COL ERROR
3899/3 PL/SQL: SQL Statement ignored
3899/3 PLS-00394: wrong number of values in the INTO list of a FETCH
statement
Could you please explain what should i do?
Database - 11.2.0
eBS - 12.1
Linux x86
Thx

i dont understand how can ichange something here?In this case, you can't.
If this is one of the standard packages built into an Oracle Apps database, you need to log a tar/sr with Oracle support. (which will probably result in more patches)

R12 - Compile Invalid objects (Fast Formula, Package Body and View) Urgent

Invalid objects about 43, in this Fast Formula 2 AP Package object, and 1 view
OWNER     OBJECT_TYPE     COUNT(*)
APPS     PACKAGE BODY     37.00
APPS     PROCEDURE     1.00
SCOTT     PACKAGE BODY     1.00
APPS     VIEW     1.00
APPS     FUNCTION     3.00
any one can give idea to make it valid.
Awaiting for your reply.
FYI
the object list is below.
OWNER     OBJECT_NAME
APPS     FFP52474_01010001
APPS     FFP61059_01010001
APPS     FFP56168_01010001
APPS     FFP56167_01010001
APPS     FFP58579_01052004
APPS     FFP56169_01010001
APPS     FFP56170_01010001
APPS     FFP56171_01010001
APPS     FFP56172_01010001
APPS     FFP56173_01010001
APPS     FFP60309_01010001
APPS     FFP60306_01010001
APPS     FFP60308_01010001
APPS     FFP60310_01010001
APPS     FFP60307_01010001
APPS     AP_IMPORT_VALIDATION_PKG
APPS     FFP58576_01011951
APPS     FFP60357_01011951
APPS     FFP57511_01010001
APPS     FFP57510_01010001
APPS     FFP52473_01010001
APPS     FFP60305_01010001
APPS     FFP60545_01042004
APPS     FFP60342_01010001
APPS     FFP58887_01042004
APPS     FFP58888_01042004
APPS     FFP58870_01042004
APPS     FFP58885_01042004
APPS     FFP58907_01010001
APPS     FFP58906_01010001
APPS     FFP58861_01042004
APPS     FFP61122_01010001
APPS     FFP58871_01042004
APPS     FFP58857_01042005
APPS     FFP60917_01032006
SCOTT     MK_PLS_XML_REP_TEST
APPS     MK_PLS_XML_REP_TEST
APPS     AP_FSX_PAYMENT_ADVICE
APPS     RA_SITE_USES
APPS     ZDBAR_CONTACT
APPS     ZDBAR_FAX
APPS     ZDBCLOAD
APPS     ZDBAP_DV_PAYMENT_TYPE
Advanced thanks for reading and giving solution for this.
Thamaraiselvan

any one can give idea to make it valid.Run "Compile APPS Schema" from adadmin.
For Fast Formulas, refer to:
Note: 155737.1 - How To Compile Oracle Fast Formulas
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=155737.1

Compile UTL_FILE PACKAGE BODY

Similar Messages

Maybe you are looking for