Invalidated Packages ORA-04068

I'm using 7.0 sp2 with Oracle 9.2.0.2 thin driver and am frequently getting the
below exception. Typcially I will run a unit test (junit), find a problem with
an Oracle package, fix it and then rerun without bouncing WebLogic. In previous
versions this worked fine.
Typically Oracle gives you get this message when you are holding onto a reference
to an Oracle object (stored proc, etc.) that Oracle has invalidated due to a change
you have made. For example, if you have an open cursor you would be forced to
close and reopen.
My guess was that now WebLogic is caching some of the statements this was causing
the problem so I set the preparedstatementcachesize to 0 but it has not helped.
This has been slowing my development as now I have to either retry N times (N
varies) until the problem goes away or bounce the server after each Oracle change.
Any help would be appreciated. Thanks.
<JDBCConnectionPool ConnLeakProfilingEnabled="true"
DriverName="oracle.jdbc.driver.OracleDriver" MaxCapacity="10"
Name="TuscanyJDBCPool" PreparedStatementCacheSize="0"
Properties="user=tuscany;password=qqq;dll=ocijdbc8;protocol=thin"
RefreshMinutes="5" Targets="myserver" TestTableName="dual" URL="jdbc:oracle:thin:@foxlau36:1521:ITVD3"/>
<JDBCTxDataSource EnableTwoPhaseCommit="false"
JNDIName="TuscanyJtsDataSource" Name="TuscanyJtsDataSource"
PoolName="TuscanyJDBCPool" RowPrefetchEnabled="true" Targets="myserver"/>
java.lang.RuntimeException: ORA-04068: existing state of packages has been discarded
ORA-04061: existing state of package body "TUSCANY.TITLE_INSTALLMENT" has been
invalidated

After talking with BEA support it looks like this is an Oracle issue. Any open
connection in the pool that has made a such a call will be marked as invalid by
Oracle. To get rid of the invalid connections you can reset the connection pool
(or bounce the server).
java weblogic.Admin -url t3://localhost:7001 -username %WLS_USER% -password %WLS_PW%
RESET_POOL poolname
Oracle suggests catching the exception ard retrying.
Thanks.
"Paul Krinsky" <[email protected]> wrote:
>
I'm using 7.0 sp2 with Oracle 9.2.0.2 thin driver and am frequently getting
the
below exception. Typcially I will run a unit test (junit), find a problem
with
an Oracle package, fix it and then rerun without bouncing WebLogic. In
previous
versions this worked fine.
Typically Oracle gives you get this message when you are holding onto
a reference
to an Oracle object (stored proc, etc.) that Oracle has invalidated due
to a change
you have made. For example, if you have an open cursor you would be forced
to
close and reopen.
My guess was that now WebLogic is caching some of the statements this
was causing
the problem so I set the preparedstatementcachesize to 0 but it has not
helped.
This has been slowing my development as now I have to either retry N
times (N
varies) until the problem goes away or bounce the server after each Oracle
change.
Any help would be appreciated. Thanks.
<JDBCConnectionPool ConnLeakProfilingEnabled="true"
DriverName="oracle.jdbc.driver.OracleDriver" MaxCapacity="10"
Name="TuscanyJDBCPool" PreparedStatementCacheSize="0"
Properties="user=tuscany;password=qqq;dll=ocijdbc8;protocol=thin"
RefreshMinutes="5" Targets="myserver" TestTableName="dual" URL="jdbc:oracle:thin:@foxlau36:1521:ITVD3"/>
<JDBCTxDataSource EnableTwoPhaseCommit="false"
JNDIName="TuscanyJtsDataSource" Name="TuscanyJtsDataSource"
PoolName="TuscanyJDBCPool" RowPrefetchEnabled="true" Targets="myserver"/>
java.lang.RuntimeException: ORA-04068: existing state of packages has
been discarded
ORA-04061: existing state of package body "TUSCANY.TITLE_INSTALLMENT"
has been
invalidated

Similar Messages

  • Continous ORA-04068 con VALID package

    Hi,
    At a customer's site we are facing a flood of ORA-04068 errors on a valid pl/sql package.
    The package is valid and so are all his dependencies.
    The db version in 10.2.0.4 on windows platform.
    It is the same situation described in metalink note #835792.1:
    - the pl/sql package involved in the error message and all his dependencies are valid.
    - the db is 10.2.0.4 so it should have the fix for bug 6136074
    I've followed the workaround described in the note which is:
    - running this sql
    select do.obj# d_obj,do.name d_name, do.type# d_type,
    po.obj# p_obj,po.name p_name,
    to_char(p_timestamp,'DD-MON-YYYY HH24:MI:SS') "P_Timestamp",
    to_char(po.stime ,'DD-MON-YYYY HH24:MI:SS') "STIME",
    decode(sign(po.stime-p_timestamp),0,'SAME','*DIFFER*') X
    from sys.obj$ do, sys.dependency$ d, sys.obj$ po
    where P_OBJ#=po.obj#(+)
    and D_OBJ#=do.obj#
    and do.status=1 /*dependent is valid*/
    and po.status=1 /*parent is valid*/
    and po.stime!=p_timestamp /*parent timestamp not match*/
    order by 2,1;
    - in the output check if there are synonyms: there was indeed a synonym pointing to the offending package
    I thought I 've found the problem
    so I dropped and recreated the synonym (as indicated).
    for a while the system runs but after some hours the error come up again.
    What else can I do ?
    Thanks
    Bye
    Nicola

    I've tried and it works for 80% of the cases.
    Unfortunately it gives the error:
    ORA-06534 cannot access serially reusable package.
    when called from a pl/sql anonymous block
    This is very annoying. This package hasn't a state at all. It only contains constants in the body...

  • ORA-04068: existing state of packages has been discarded

    I work on an order entry system that is up 24x7 running Oracle version 8.0.5. I want to compile a fix to a procedure contained in a package body. I only will be recompiling the package body. Since the package body has no dependent objects, I should not invalidate any stored procedures that call this procedure in my package. However, should I worry about causing an "ORA-04068: existing state of packages has been discarded" error? What causes this error and when does it occur?

    Please ensure that DBMS_ROWID is created in SYS schema and not in any ordinary user's schema. If it exists in any user's schema drop it from there.
    If the problem persists, drop the package from sys schema as well and run two script files in the following order:
    1) ORACLE_HOME\rdbms\admin\dbmsutil.sql
    2) ORACLE_HOME\rdbms\admin\prvtutil.plb

  • ORA-04068 on 11g RAC does not resolve automatically !

    Did you ever get the combination of these three ORAs?
    ORA-04068: Existing state of package has been discarded
    ORA-04065: Not executed, altered or dropped stored procedure <PROCEDURE_NAME>
    ORA-06508: PL/SQL: Could not find program unit being called: <PROCEDURE_NAME>
    *1st I checked for invalid objects in the database, there are none!*
    *2nd Then I checked the metalink note 1058873.1 that describes a similar error:*
    In hecheck output, we see that the objects affected are listed as "Dependency$ p_timestamp > > mismatch for VALID objects".
    Also, the following script can be used for finding the mismatches:
    set pagesize 10000
    column d_name format a20
    column p_name format a20
    select do.obj# d_obj,do.name d_name, do.type# d_type,
    po.obj# p_obj,po.name p_name,
    to_char(p_timestamp,'DD-MON-YYYY HH24:MI:SS') "P_Timestamp",
    to_char(po.stime ,'DD-MON-YYYY HH24:MI:SS') "STIME",
    decode(sign(po.stime-p_timestamp),0,'SAME','*DIFFER*') X
    from sys.obj$ do, sys.dependency$ d, sys.obj$ po
    where P_OBJ#=po.obj#(+)
    and D_OBJ#=do.obj#
    and do.status=1 /*dependent is valid*/
    and po.status=1 /*parent is valid*/
    and po.stime!=p_timestamp /*parent timestamp not match*/
    order by 2,1;However, the query returned 0 rows.
    *3rd Then I read about similar errors on http://oraclequirks.blogspot.com/2007/03/ora-04061-existing-state-of-package-has.html*
    The article describes the state of package being invalidated when one user calls a procedure in a package that has a global variable and changes the value of the global variable and then when a developer compiles that package, another user will get the error ORA-04061: existing state of package has been invalidated the first time he calls the procedure, but the second time it will work without returning errors.
    However, my error is persistant and Oracle can't resolve it automatically.
    Here's how the error occurs:
    - I have a PACKAGE that has a global variable and procedures
    - User1 connects to Instance1 and calls a procedure inside the PACKAGE. The procedure sets the value of the global variable by calling a function outside the package.
    For example: L_GLOBAL_VAR := OUTSIDE_FUNCTION(30);
    - The developer compiles the PACKAGE
    - User1 can continue working normaly - he receives the 1st error by Oracle informing him that the value of the global variable has changed (normal behaviour), but the second time he calls the procedure inside the PACKAGE, no errors are reported.
    - User2 connects to the second instance of the RAC (Instance2)
    - When User2 tries to call the same procedure, he constantly gets ORA errors (ORA-04068, ORA-04065, ORA-06508), like this:
    ORA-04068: Existing state of package has been discarded
    ORA-04065: Not executed, altered or dropped stored procedure "OUTSIDE_FUNCTION"
    ORA-06508: PL/SQL: Could not find program unit being called: "OUTSIDE_FUNCTION"
    ORA-06512: at "PACKAGE2", line 1920
    ORA-06512: at "PACKAGE2", line 265The PACKAGE2 has a procedure which is being called at line 265, and that procedure calls the function OUTSIDE_FUNCTION at line 1920.
    Symptoms:
    - User2 cannot correct the error by repeatingly calling the PACKAGE procedure.
    - The developer cannot resolve the issue by recompiling the PACKAGE.
    - The developer can only temporarily resolve the issue by recompiling the OUTSIDE_FUNCTION. After doing it, the User2 does not receive errors. However, if the User2 reconnects, the error returns.
    - The solution is to recompile the PACKAGE2. After doing it, the User2 does not receive errors.
    However, I'm totally confused by this Oracle behaviour.
    I told the developers that they shouldn't compile packages while there are users working on the database (a possible solution), but as a developer I know that is very very hard on a 24/7 production database, especially if there are some urgent bugs to resolve etc.
    We were working on a single instance Oracle 9i database before upgrading to Oracle 11g RAC (11.2.0.1.0), and we never had similar problems.
    I would be very grateful for any suggestions regarding this issue.
    Thanks,
    Daniel

    Hi P. Forstmann,
    Thanks for your answer. I've read about the edition based redefinition but if I understand it correctly, that's not exactly what I'm looking for.
    For example, if a connected user reports a bug that prevents her from doing her work, the developers should resolve that bug ASAP and recompile the objects in question, which should affect the connected users.

  • Invalid package status

    Hi all,
    I have following problem:
    To speed up some checking I created a cache inside package body. But everytime portal uses different session to serve show request I get ORA-04068 error.
    It's saying something about invalid state. I thought that
    private data in package body remain same tgrough a session
    and that each session has it's own copy. But it looks like some session change state of the package and others receive mentioned error. When I try it second time within same session it's ok.
    I tried to find some information in PL/SQL Guide, but there is nothing about this error.
    Can you help me with this problem?
    Is it my fault or is this "normal" behaviour?
    Thanks
    David

    Hi David,
    YES it's your fault. Answer is hidden inside your question. Portal is using different sessions to server your requests. After you made some change and recompiled the package . Most of the sessions had old information and thus rised the error message. So be patient and try all sessions to get uptodate information.
    Sorry for wasting your time.
    David

  • Webservice based on PL/SQL function - ORA-04068

    Hi,
    we have a problem here with PL/SQL based webservices. If the PL/SQL package gets invalid then the very first request to the webservice results in:
    java.sql.SQLException:
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "TUG_NEW.WBSERVICES" has been invalidated
    ORA-04065: not executed, altered or dropped package "TUG_NEW.WBSERVICES"
    ORA-06508: PL/SQL: could not find program unit being called ORA-06512: at line 1
    Any workarounds? Shouldn't the package become recompiled automatically when it was invalid?
    Thanks, Christian

    the caller gets an error on the first request. from the second request on it works ... indicates the package is not yet recompiled when the first request is sent. When the second request is sent, the package has been recompiled.

  • BPEL - Invalidated package

    Hello,
    I am developing a BPEL process and I call a package procedure but I sometimes get this error, existing stage of packages has been invalidated. The problem is, the package is valid and when I redeploy the process it works again...
    Do you know where the probleme could be?
    Here is the stack trace :
    file:/D:/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_BPELSendMailProcess_1.0_b7b09386eee8d285712893ecd7082686.tmp/MyLeadReferences.wsdl [ MyLeadReferences_ptt::MyLeadReferences(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'MyLeadReferences' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the MYLEAD.PCK_BPEL.F_GET_ALL_REFERENCE API. Cause: java.sql.SQLException: ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "MYLEAD.PCK_BPEL" has been invalidated
    ORA-04065: not executed, altered or dropped package "MYLEAD.PCK_BPEL"
    ORA-06508: PL/SQL: could not find program unit being called: "MYLEAD.PCK_BPEL"
    ORA-06512: at line 1
    [Caused by: ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "MYLEAD.PCK_BPEL" has been invalidated
    ORA-04065: not executed, altered or dropped package "MYLEAD.PCK_BPEL"
    ORA-06508: PL/SQL: could not find program unit being called: "MYLEAD.PCK_BPEL"
    ORA-06512: at line 1
    ; nested exception is:
         ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the MYLEAD.PCK_BPEL.F_GET_ALL_REFERENCE API. Cause: java.sql.SQLException: ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "MYLEAD.PCK_BPEL" has been invalidated
    ORA-04065: not executed, altered or dropped package "MYLEAD.PCK_BPEL"
    ORA-06508: PL/SQL: could not find program unit being called: "MYLEAD.PCK_BPEL"
    ORA-06512: at line 1
    [Caused by: ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package "MYLEAD.PCK_BPEL" has been invalidated
    ORA-04065: not executed, altered or dropped package "MYLEAD.PCK_BPEL"
    ORA-06508: PL/SQL: could not find program unit being called: "MYLEAD.PCK_BPEL"
    ORA-06512: at line 1
    Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.

    Hi,
    As mentioned correctly in the previous post this problem happens due to database caching in the OAS level,however everytime restarting opmn is not good workaround.Instead the connection pool can be refreshed using MBean.
    Refer to the following URL on how to do this: http://chintanblog.blogspot.com/2008/06/refreshing-connection-pool-via-mbeans.html
    Rdgds.

  • Causes of invalidated package

    Hi,
    I've found on the forums some information about why a package could become invalidated.
    We are encountering the 'ORA-04068: existing state of packages has been discarded' error (see stack trace at the bottom of this message).
    We get this error at random (not at a specific moment in time). And always with the same package.
    I found on the forums that a cause could be:
    - a view, used in the package, that gets renamed (this is not the case).
    - package level variables (I can not check this myself. Our client, who runs the Oracle instance, is doing that now).
    1. Are there any other causes of a package becomming invalid?
    2. Related: does a synonym become invalid when it's underlying package is invalid, or can a synonym be invalid, while it's underlying package is not?
    3. Can our client, who is reluctant in accepting the fact that the problem lies with their Oracle database (i.e. packages being invalidated), check the exact reason of the invalidation in more detail (logs, ...)?
    Thanks in advance for any insights,
    Vincent
    Stack:
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package body "MYCLIENT.THEPACKAGE" has been invalidated
    ORA-04065: not executed, altered or dropped package body "MYCLIENT.THEPACKAGE"
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1

    Packages become invalidated when any database object (table, view etc.) that that package has dependecies on is altered in any way.
    When a Package is being used it is loaded into memory and a "session state" is created for that package. This session state holds all of the package level variables for that session (different sessions running the same package will have their own copy of the package variables). If a dependency object is altered then the package is invalidated automatically by Oracle. If the package doesn't have any package level variables then Oracle will automatically recompile the package when the next call is made to anything within it by the session in question, but if variables exist then Oracle determines that these variables are now out of date because of the need for it to recompile the package. Because of this it has to discard the session state, which is why you get the error saying that the state has been discarded.
    One way to get around this is to not have any package level variables.
    If you need to have some variables (constants and types too) that are accessible by many procs/fns inside your package then a way to do this is to create another package spec containing these variables and alter the package to reference them in that package. That way, the package that has the dependencies and needs recompiling can do so without having any "state" to worry about being discarded and the variables in the other package are just variables and don't have any dependencies so that other package doesn't get invalidated or need recompiling.
    Hope that's clear.
    Edit:
    Examples...
    With package variables in dependency package...
    SQL> create table a (x number);
    Table created.
    SQL> create package pkg_a is
      2    procedure mydependantproc;
      3  end;
      4  /
    Package created.
    SQL> create package body pkg_a is
      2    state_var number;
      3    procedure mydependantproc is
      4      local_var number;
      5    begin
      6      select x into local_var from a;
      7      state_var := local_var;
      8    end;
      9  end;
    10  /
    Package body created.
    SQL> insert into a values (1);
    1 row created.
    SQL> exec pkg_a.mydependantproc;
    PL/SQL procedure successfully completed.
    SQL> alter table a add (y number);
    Table altered.
    SQL> exec pkg_a.mydependantproc;
    BEGIN pkg_a.mydependantproc; END;
    ERROR at line 1:
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package body "CRISP_INTELL.PKG_A" has been invalidated
    ORA-06508: PL/SQL: could not find program unit being called: "CRISP_INTELL.PKG_A"
    ORA-06512: at line 1
    SQL>And with the package variables dissassociated into another package spec...
    SQL> create table a (x number);
    Table created.
    SQL> create package pkg_a is
      2    procedure mydependantproc;
      3  end;
      4  /
    Package created.
    SQL> create package pkg_b is
      2    state_var number;
      3  end;
      4  /
    Package created.
    SQL> create package body pkg_a is
      2    procedure mydependantproc is
      3      local_var number;
      4    begin
      5      select x into local_var from a;
      6      pkg_b.state_var := local_var;
      7    end;
      8  end;
      9  /
    Package body created.
    SQL> insert into a values (1);
    1 row created.
    SQL> exec pkg_a.mydependantproc;
    PL/SQL procedure successfully completed.
    SQL> alter table a add (y number);
    Table altered.
    SQL> exec pkg_a.mydependantproc;
    PL/SQL procedure successfully completed.
    SQL>;)
    Message was edited by:
    blushadow

  • ORA-20006: ORA-01722: invalid number ORA-06512: at "APPS.WF_NOTIFICATION"

    Hi,
    I am having a wft program, which checks a function activity and depending on the value returned sends difference notifications.
    The package body completed successfully from backend and while running the workflow program it sends a notification also. But while opening the notification it gives the following error,
    ORA-20006: ORA-01722: invalid number ORA-06512: at "APPS.WF_NOTIFICATION", line 5328 ORA-06512: at line 5
    I have 3 procedures in my package body and all the 3 procedures have exceptions defined as follows, if they are using any workflow activities.
    ==========================================================
    EXCEPTION
         WHEN OTHERS THEN
              WF_CORE.context (
              'WFCustCheck',
              'MisCustDataFromTableDoc',
              document_id,
              display_type,
              document,
              document_type,
              SQLERRM
    RAISE_APPLICATION_ERROR (-20006, SQLERRM);
    ==========================================================
    But I am not able to figure out what is causing this error. What does this "line 5328 ORA-06512: at line 5" in the error message indicate?. My package body has only 600 lines. And why is the error message not displaying the procedure name? though I have defined the procedure name in the exception.
    What is the best way to get the procedure name in the error message? So that it becomes easier for identifying which procedure is causing the erro?
    Please let me know.
    Thanks

    Hi,
    Instead of the RAISE_APPLICATION_ERROR command, just replace that with RAISE;
    The error is coming out of the package that is sending the notification (WF_NOTIFICATION), which is invoked when you open the notification. I'm guessing that line 5 is the line in your code though.
    Are you using documents to send the notification, or are they purely defined in the .wft file?
    Matt
    Alpha review chapters from my book "Developing With Oracle Workflow" are available on my website:
    http://www.workflowfaq.com
    http://forum.workflowfaq.com
    NEW! - WorkflowFAQ Blog at http://thoughts.workflowfaq.com

  • Compile all invalid packages together + connect as sysdba only

    Hi
    I've installed a Ora 10.2, and imported a dump. This dump contained some users, a lot of tables and stored procs.
    My first question: There is an imported user with I can connect as sysdba only. I can't connect as normal... it is problem because there is an application upper the db and I can't tell the applicataion that connect as sysdba. (it is only a sandbox for me...) What should I modify on this user to connect as normal user?
    The second question: The schema (upper) contains lot of invalid packages. I have only the free Toad and I can't compile all of them only step by step... (I don't want do this step by step because there are about 300 packages...). How could I complile all of them e.g. from Sqlplus? Any other solution?
    Thanks in advance!
    Alex

    ok, there is a user e.g. "xxxx"
    I can connect with this user as sysdba only. "CONNECT xxxx/yyyy@db as sysdba". Without "as sysdba" I got "ORA-01017: invalid username/password; logon denied" So I can connect only as sysdba... but this is a simple user so I don't want to connect as sysdba...

  • Apex, ORA-04068 and pragma SERIALLY_REUSABLE

    Hi there,
    (Apex 4.0.2 and Oracle 11g)
    What are your views on using PRAGMA SERIALLY_REUSABLE on application packages called by Apex?
    It is not very clear to me the implications this would have and the performance gains it could yield, but reading the technical documentation it seems perfect for the sessionless nature of Apex.
    In a more complex scenario, what about using it in packages called by Apex via a web service?
    Now and then we get ORA-04068 after deployments and that pragma could help, that is why I started looking into it. In a "normal" (e.g. client/server) application it could have serious side effects but it seems harmless for Apex apps.
    Any comments are welcome.
    Thanks
    Luis

    Hi Luis ;-)
    I was thinking the same thing a while ago, but when I read up on it I came to the conclusion that defining packages as serially reusable for Apex would probably degrade performance.
    I have no metrics on this, nor am I sure how to measure it. I'd be curious if others have feedback.
    Scott

  • DBMS_SESSION.RESET_SELF() + ORA-04068

    Hi all,
    as I was looking through the new features guide of 11.2 release I ran across
    the following section which raised my interest:
    2.1.1.5 Improvements to Reduce the Occurrences of "Existing State of Packages
    Discarded" Errors
    When the body of a stateful package is recompiled by session A, then a
    different session B which has already instantiated that package will
    experience the ORA-04068 existing state of packages… has been discarded family
    of errors on its next reference to that package following the recompilation.
    The result is severe disruption for the user of session B.
    Two improvements in this release now reduce the likelihood of these ORA-04068
    errors:
    * A package, whose global variables is marked constant; and where the
    initial value can be computed at compile time, is now considered to be
    stateless.
    * The new procedure DBMS_SESSION.RESET_SELF(), whose invocation must
    be in the package of interest, allows you to preempt the problem when it is
    safe to reinitialize the package state.
    The advantage is that packages (and especially those that are not editioned)
    can be "hot patched" (that is, recompiled) when other sessions are using them
    with a greatly reduced likelihood of disrupting those sessions.
    As I wanted to try out the DBMS_SESSION.RESET_SELF() procedure I did not find
    it in the dbms_session package ? There is also no documentation in the Types
    and Packages book. Any hints ? Do I miss something ?
    Very best regards
    Michael

    Can you please post a URL to that doc ref?
    Also had a look and there's no trace of this call (11gr2). Searched the contents of +$ORACLE_HOME/rdbms/admin+ for the keywork reset_self and no hits.
    Metalink note +PACKAGE DBMS_SESSION Specification [ID 67594.1]+ also does not list this call.
    Keen on this type of feature myself - I have 24x7 code running and its a pain to interrupt this, shut it down, in order to perform a basic package update (where interface spec remains unchanged).

  • Package load Failed! Invalid package Title, manifest file cannot be found

    Greetings. I am new to UPK and am seeking guidance on an upgrade to 11.1.
    A little background on what we are trying to do:
    We have two machines:
    Windows 2003 machine in domain 'X' | UPK 11.0.0.1.
    Windows 2008 R2 virtual machine in domain 'Y' | UPK 11.0 on the new machine first, install the 11.0.0.1 patch, and then upgrade to 11.1.
    We are using the same database as the old machine. Developer Server is Standard Authentication, Knowledge Center is Windows authentication.
    ==========================================================================================
    So far we have installed 11.1 with the respective database upgrades, but are lost as to how to migrate the old Content Root data. We have copied all the content to the new Content Root, added it to IIS like the old machine, and verified that the UPK database Content Root path is correct and working.
    For the rest of the post, I am remoted into the server from my local workstation, and then using IE to access KCenter on the server's FQDN, not via localhost.
    Since I am green, so I presumed that I would need to import the titles under Manager in KCenter. I zipped each content folder individually (they are named "1", "9", etc), and then attempted to import each zip file.
    NOTE: At this stage sometimes we are prompted to authenticate again. When it does, sometimes the credentials that we know work, get rejected and we are prompted again. This will repeat until we get a 401 and we have to start over. We have verified that the Windows account currently in session with the site is valid and has administrator authority within KC.
    NOTE2: On the first few tries, .NET complained that maxRequestLength was not large enough. I had our servers team increase it on the actual server in order for us to proceed.
    Provided we don't have to authenticate again, or that it actually accepts our credentials, we get to the 30% mark and then receive the error: *"Package load Failed! Invalid package Title, manifest file cannot be found"*
    Does anyone have any wisdom for this process? The title importation section in the deployment manual is not helping, and the administrator from whom I am taking over this software has not had to deal with this before.
    Thank you,
    Ian
    Edited by: 986290 on Feb 5, 2013 10:21 AM

    Hi Marc, thanks for the post,
    I have gone through an extensive troubleshooting process with Oracle, including their development team, in order to fully complete our project setup. As a supplemental bit of information, we also were having connection errors when attempting to publish directly to the knowledge center.
    As far as the context of this post, here is the solution in brief:
    1) Verify that the package being imported was published from the same version of the Developer Client as the Knowledge Center installation's.
    2) Check for database consistency issues. In our case we were using a database that was built in another domain. After numerous attempts with Oracle support on the line to determine the inconsistency, it was decided to completely reinstall and build a new database from scratch in the new domain.
    3) Check application pool identities and access (while we had some inconsistencies here, correcting them did not change the behavior of the import/publish errors)
    In review, a lot of what we had setup was correct. Our primary point of failure, we feel, was using the old database. Technically this should not have been a problem, but Murphy likes to get his way sometimes.
    Cheers,
    Ian

  • Invalid Package error (limits?) - SQL*Loader

    I seem to have reached a limit on SQL*Loader in 8.1.6 on the number of columns I am trying to load. The table has 97 columns - if I try to specify more than 92 columns I get an invalid package error - it doesn't matter which column I pick. The row width is close to 2K bytes. Does anyone know the max size - and is there a default that can be increased somehow?

    It maybe your BUFFER size.
    Buffer Size = Rows in Array * Max row size
    this is the formula to estimate your BUFFER size for the import.
    Look in your Parameter File for 'INCTYPE' this is the parameter name for Buffer for importing with SQL*Loader.
    Hope this helps.
    Tony

  • PL/SQL : Error: invalid path ORA-29280

    I'm trying to get this work but what can I do ? does anybody know how to resolv this problem
    code : (for the exemple)
    DECLARE
         fich     UTL_FILE.FILE_TYPE;
    BEGIN
         fich := UTL_FILE.FOPEN('e:\','test.lst','W');
         UTL_FILE.PUT(fich,'something');
         UTL_FILE.FCLOSE(fich);
    EXCEPTION
         WHEN utl_file.invalid_path THEN
              DBMS_OUTPUT.PUT_LINE('Error: invalid path ' || SQLERRM);
              UTL_FILE.FCLOSE(fich);
         WHEN utl_file.write_error THEN
              DBMS_OUTPUT.PUT_LINE('Error: write error ' || SQLERRM);
              UTL_FILE.FCLOSE(fich);
         WHEN others then
              DBMS_output.put_line('other error : '||SQLERRM);
              UTL_FILE.FCLOSE(fich);
    END;
    Always return :
    ERROR at ligne 1 :
    ORA-29280: invalid path
    ORA-06512: at "SYS.UTL_FILE", line 18
    ORA-06512: at "SYS.UTL_FILE", line 424
    ORA-06512: at line 4
    If someone can tell me where's the fault. thanks in advance

    Also note, that directories you want to have access to should be listed in UTL_FILE_DIR server parameter (you edit it in your init.ora and restart the server for changes to take effect.) Setting it to * (everything everywhere) is NOT recommended as it opens whole file system for access and may lead to security problems.

Maybe you are looking for