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)

Similar Messages

  • Can't see package body in SQL Developer version 2.1.1.64

    When I go to the object browser, I can see all of the package specs but can't seem to get to the package body. I can access the package body just fine through Toad, so I don't think it is an Oracle user issue. Help?

    I can see any user's Package Body when I'm logged into the database as a DBA, so it must be some privilege that you need. The privilege I would have guessed you need is SELECT ANY DICTIONARY but you say you have that privilege. If you were granted that privilege through a role, make sure that the role is active, or that it is a default role.
    Another role it might be looking for is EXECUTE ANY PROCEDURE, but I'm not sure. See if you can do these selects, since these are probably the views that SQL Developer is using:
    select * from dba_objects where owner = 'some owner' and object_type = 'PACKAGE BODY';
    select * from dba_source where owner = ' some owner' and type = 'PACKAGE BODY';Of course, if your database administrator is willing to grant you the DBA role, that ought to do the trick - works for me. Otherwise, you and your DBA may have to try different system privileges until you find the one that works.

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

  • 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

  • BUG 1.5:Can't edit package body in other user.

    This is getting ridiculous. I didn't really have time to do anything with pl/sql development during the EA period and now that I do, nothing seems to work.
    I have a package and package body owned by user x. I am connected as system.
    I can edit the package, but not the body. The edit window opens, and I can compile it but I can't make any changes in the editor.
    1.5 prod with jre
    windows xp sp2
    Oracle 11.1.0.6.0

    We don't have a date scheduled for the patch release. We're working on the key issues and will release the patch when these are done. We do not plan to make this a long drawn out process.
    Sue

  • BUG 1.5 : Can't create package body.

    I'm getting this stack dump in the console trying to create a package body.
    I'm logged in as a dba.
    executed 'alter session set current schema=x';
    created package in the worksheet.
    opened package from Other users|x|packages.
    Edited and compiled package.
    Tried to create body from connection tree context menu.
    I have both viewer and edit window open on the package. The stack dump occurs regardless of which one had focus before I go to the tree to create the body.
    Exception while performing action Create Body
    java.lang.IllegalStateException: Not in compound edit
            at oracle.javatools.buffer.AbstractTextBuffer.endEdit(AbstractTextBuffer.java:1126)
            at oracle.ide.model.TextNode$FacadeTextBuffer.endEdit(TextNode.java:1074)
            at oracle.dbtools.raptor.dialogs.actions.CreateBodyAction.launch(CreateBodyAction.java:94)
            at oracle.dbtools.raptor.controls.sqldialog.ObjectActionController.handleEvent(ObjectActionController.java:140)
            at oracle.ide.controller.IdeAction.performAction(IdeAction.java:524)
            at oracle.ide.controller.IdeAction.actionPerformedImpl(IdeAction.java:855)
            at oracle.ide.controller.IdeAction.actionPerformed(IdeAction.java:496)
            at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
            at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
            at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
            at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
            at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
            at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
            at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
            at java.awt.Component.processMouseEvent(Component.java:5488)
            at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
            at java.awt.Component.processEvent(Component.java:5253)
            at java.awt.Container.processEvent(Container.java:1966)
            at java.awt.Component.dispatchEventImpl(Component.java:3955)
            at java.awt.Container.dispatchEventImpl(Container.java:2024)
            at java.awt.Component.dispatchEvent(Component.java:3803)
            at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
            at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
            at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
            at java.awt.Container.dispatchEventImpl(Container.java:2010)
            at java.awt.Window.dispatchEventImpl(Window.java:1774)
            at java.awt.Component.dispatchEvent(Component.java:3803)
            at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
            at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
            at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
            at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
            at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

    This has been fixed for the patch release 1.5.1.
    Sue

  • I can't compile packages created by NetBeans

    Hello guys
    for the previous weeks, I was developing my project using Notepad for editing, and javac from the command prompt. Recently I moved my work into NetBeans 3.6, and i modified my code greatly, by arranging my java files into packages and I thought I had accomplished a great step by making my job easier. what I found later is that I can no longer compile my code using the normal javac command, because it's unable to reach the packages in the same way netbeans do.
    My java files are distributed inside the senior directory :
    senior \ Senior.java
    senior \ menu \ menuBar.java
    senior \ menu \ toolsBar \ *.*
    senior \ Buttons \ *.java
    senior \ images
    The Senior.java conatins the following imports:
    import senior.menu.menuBar;
    import senior.Buttons.*;These imports are located fine in NetBeans, but Javac command can't locate them.
    Please advise me, should I continue working with NetBeans, or should I use a format that is compatible with javac?
    and what other differences I might face in the future between NetBeans and Javac?

    I have a similar problem. I'm using NetBeans 3.5. I have 2 java files in a package called mypac. The first one is a JavaBean (implements Serializable) and the second one is a servlet (extends HttpServlet). The JavaBean contains a class called user and the servlet has a private data member of type user. Both files have the "package mypac;" statement at the first line.
    I can build the JavaBean successfully but when I tried to build the servlet, it happened that the user class is unrecognised in the servlet. (Cannot resolve symbol error)
    What should I do to solve this problem?

  • Can not compile package

    Hi,
    I have package and it is invalid. When I try to compile it starts to compile but not stop. I think it is locked or something else. I renamed it and compiled and it worked. Functions in package runned also.
    But I want the orginal package to run.
    Does anyone has idea about this problem?
    Thanks in advance.

    If you have killed all the session using this package, it may take sometime to rollback the transactions. Mean while also make changes in the package, so that it commits its transaction at the end of logical transaction end otherwise you will face this issue again. After sometime you can compile the package.
    Other option may be to restart the database in restricted mode. Make your changes, compile the package and then put the database in normal mode.
    Regards
    Edited by: skvaish1 on Apr 9, 2010 10:27 AM

  • Can't see package body in SQL Developer version 3.1

    Hello,
    Have been scouring the boards and google for this issue for quite some time now. I think I have discovered the issue, but would like to see if a work around exists.
    Problem:
    I am unable to view packages, procs, VIEW DDl, etc. of other users. When a colleague of mine uses Toad, with the EXACT same connection ID and setting, they are in fact able to see all the source code...
    What I've found:
    Looking around, apparently Toad and SQL Dev work in different ways. Toad apparently uses DBA_SOURCE and DBA_OBJECTS to generate everything.
    SQL Dev uses the META_DATA package to retrieve everything. Further, in order to use the meta_data package, I need the grant catalog role, or something like that.
    Is there a way to set up SQL Developer to use the same method as Toad to retrieve the code? It's a fact that I WILL NOT receive the catalog permission per the DBAs... I can write out the
    select text from DBA_SOURCE where OWNER = 'OWNER' and NAME = 'OBJECT NAME';
    But, I would prefer to just be able to use the tree nodes and click on objects to generate all this. Anyone know of any setting for this?

    Hi,
    No doubt SQL Developer wants to be competitive with Toad but, in terms of raising red flags over inconsistencies in basic functionality, any difference versus SQL*Plus would be more surprising than versus Toad.
    DBA_SOURCE and DBA_OBJECTS are public synonyms available in any standard Oracle installation, but you also need the SELECT ANY DICTIONARY privilege to get maximum benefit from them. That lets you view code in another user's schema without having an explicit privilege (like EXECUTE) on a package/procedure/function.
    If you already do have such privileges (either SELECT ANY DICTIONARY, or EXECUTE or DEBUG on specific executable objects), and the Code tab is empty, then you will need to provide a test case, as Vadim indicates.
    In terms of any case where SQL Developer utilizes DBMS_METADATA, my understanding is the API relies on the SELECT_CATALOG_ROLE privilege if a user does not own or otherwise have an explicitly granted privilege on an object. Developers like to use this API wherever possible in place of writing a script that might break or need maintenance to deal with future versions of the Oracle database.
    I have no idea how Toad works, and I probably shouldn't speculate, but here is one scenario that could explain the case you mention without the connection user having any of the privileges noted above. Let's say the Toad client software calls a PL/SQL package that selects from DBA_SOURCE and is installed in a schema that has the SELECT ANY DICTIONARY privilege. All Toad users are granted EXECUTE on this package and therefore inherit SELECT ANY DICTIONARY in the context of running the package. This will work, but at the price of complicating installation of Toad. Also, it doesn't afford an administrator fine-grained control over metadata security.
    Regards,
    Gary
    SQL Developer Team

  • PLS-00801: internal error [1401] while compiling Package body

    I am getting the error PLS-00801: internal error [1401] while compiling the package.
    recently upgraded to version 11.1.0.7 database .
    Any pointer to this ..

    935026 wrote:
    I am also getting the same error while compiling a procedure which use a remote object over db_link.
    Let me know if this needs to be run on source db or destination db
    1. RUN as SYS
    $ORACLE_HOME/rdbms/admin/utlirp.sql
    $ORACLE_HOME/rdbms/admin/utlrp.sql
    RegardsYES
    post results from SQL below from both DBs
    SELECT * FROM V$VERSION;

  • 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

  • && Substitution Variable in Package Body using SQL Developer

    Hi Folks,
    I've moved over to working to in SQL Developer (its a very early version - 1.0.0) from a combination of SQL*Plus command line and a text editor. I'm trying to get this upgrgraded, but I think the question will be the same with a newer version anyway.
    I am creating a package, and in the package body I have some &&my_var substitutions that I was previoulsy prompted for when calling the .sql from the command line SQL*Plus. I need this as the variable needs to be different for the development and live environment.
    When working in SQL Developer, I can load the package body from Connection->Packages->My Package->My Package Body, and click the edit button to edit the code, however, when I click the Compile button in the top of the window my code error's because of the substituion variablle. An example is:
    CREATE OR REPLACE
    PACKAGE BODY MY_PACKAGE AS
    PROCEDURE MY_PROCEDURE
    BEGIN
    my_variable := &&my_function_from_live_or_dev_database
    END MY_PROCEDURE
    Can anyone tell me if there is a way of defining a compiler variable within the IDE widow while editing a package body stored in the database, without manually copying the code into the Worksheet and running it as a script?
    Thanks,
    AM

    953104 wrote:
    Thanks for the reply, the code was just quickly typed to show the sort of thing I am doing, it wasn't actual code form my project.
    I've come from a C background so what I would have done would be create a #define and changed to when on live or development - or passed the variable to the build environment from the IDE or makefiles and the change would have reflected through my whole project.
    What I want to be able to do is alter a definition of some sort that will reflect throughout my whole project, so I can change it in one location to minimize code changes before going live. I don't really want to be prompted at all. On one system it needs to be DEV_10 and on the other it needs to be LIVE_10.Is there a possibility to elimiante this difference at all?
    For example if DEV_10 is the oracle schemauser on the development database and LIVE_10 would be the one on the production system. THen you could just remove all references to the schema from your code.
    IF you are already connected to this schema, then you don't need to specify the schema name anymore.
    example
    instead of
    create or replace package dev_10.myPackage
    ...you can simply use
    create or replace package myPackage
    ...If needed you can alter the cuurently connected user just before you run the script.
    alter session set current_schema = LIVE10;
    create or replace package myPackage
    ...This would be a different working window in the developer (script worksheet, instead of direct pl/sql editor).
    Substitution variables are allowed there.

  • Issue with viewing Package Body in SQL Developer 2.1 EA1

    I was able to view the package body from different schemas after I log in with user account in SQL Developer 1.5.5.
    But with SQL Developer 2.1 EA1, I could view only spec and I can see the package body only if I log in with DBO account.
    Is there any setting that needs to be configured to be able to view the package body?
    Thanks!

    Thanks for replying my message.
    It's Oracle 9i.
    What I meant 'spec' is you can see only the headers you defined in spec. You can expend the package and be able to see the all functions and procedures but you won't be able to see the '%packagename% Body' where all the detail code were written.
    As I mentioned in my previous post, with SQL Developer 1.5.5 version, you can see spec and package body if you expend the package.

  • OLE2 Package body

    Dear all,
    Could any one please guide me where I can find the package body gfor OLE2 package?
    Or if someone has it, could you plaease send it across to me at [email protected]
    Thanks in advance !!
    Regards
    Anuj

    Got it in webutil.pll
    Regards
    Anuj

Maybe you are looking for