Sys packages invalid

in oracle 9i some sys packages become invalid give solution

Did you try recompiling them with utlrp.sql script??
Count the number of invalid packages before and after running this script.
Default location of this file is as follows.
Windows: %ORACLE_HOME%/rdbms/admin/utlrp.sql
Unix/Linux: $ORACLE_HOME/rdbms/admin/utlrp.sql
Regards,
Sabdar Syed.

Similar Messages

  • Sys package invalid !!!

    hey gurus
    i'm facing a starnge problem , it's showing all packages of sys schema as in valid . i try to run
    exec dbms_stats.export_schema_stats('SCHEMANAME', 'STATS_BKP_SCHEMA', sysdate, 'PRODD');
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "SYS.DBMS_STATS", line 5173
    ORA-06512: at "SYS.DBMS_STATS", line 5185
    ORA-06512: at "SYS.DBMS_STATS", line 5587
    ORA-06512: at line 1
    following is thelist of invalid objects
    DBMS_AQ
    DBMS_AQADM
    DBMS_AQJMS_INTERNAL
    DBMS_AQ_EXP_QUEUES
    DBMS_AQ_EXP_ZECURITY
    DBMS_AQ_IMPORT_INTERNAL
    DBMS_AQ_SYS_EXP_ACTIONS
    DBMS_AQ_SYS_IMP_INTERNAL
    DBMS_CAPTURE_ADM_INTERNAL
    DBMS_CAPTURE_PROCESS
    DBMS_DDL_INTERNAL
    DBMS_DEFER
    DBMS_DEFERGEN
    DBMS_DEFERGEN_AUDIT
    DBMS_DEFERGEN_AUDIT
    DBMS_DEFERGEN_INTERNAL
    DBMS_DEFERGEN_INTERNAL
    DBMS_DEFERGEN_LOB
    DBMS_DEFERGEN_LOB
    DBMS_DEFERGEN_PRIORITY
    DBMS_DEFERGEN_RESOLUTION
    DBMS_DEFERGEN_RESOLUTION
    DBMS_DEFERGEN_UTIL
    DBMS_DEFERGEN_WRAP
    DBMS_DEFERGEN_WRAP
    DBMS_DEFER_IMPORT_INTERNAL
    DBMS_DEFER_INTERNAL_SYS
    DBMS_DEFER_QUERY_UTL
    DBMS_DEFER_REPCAT
    DBMS_DEFER_SYS
    DBMS_DEFER_SYS_PART1
    DBMS_DESCRIBE
    DBMS_IAS_CONFIGURE
    DBMS_IAS_INST_UTL_EXP
    DBMS_IAS_QUERY
    DBMS_IAS_SESSION
    DBMS_ITRIGGER_UTL
    DBMS_LOGREP_EXP
    DBMS_LOGREP_IMP_INTERNAL
    DBMS_LOGSTDBY
    DBMS_PROPAGATION_ADM
    DBMS_REDEFINITION
    DBMS_REGXDB
    DBMS_REPCAT_INSTANTIATE
    DBMS_REPCAT_RGT_ALT
    DBMS_REPCAT_RGT_CHK
    DBMS_REPUTIL2
    DBMS_SNAP_REPAPI
    DBMS_SNAP_REPAPI
    DBMS_STATS
    DBMS_STATS_INTERNAL
    DBMS_SUMMARY
    DBMS_SUMVDM
    INITJVMAUX
    LTAQ
    LTPRIV
    LT_CTX_PKG
    LT_EXPORT_PKG
    LT_REPLN
    OWA_TEXT
    OWM_MIG_PKG
    OWM_REPUTIL
    Please suggest sometthing
    p.s. database is running fine so far
    Thanks

    try to recompile with the ?/rdbms/admin/utlrp.sql script. This should set all sys packages in a valid status. If problem persists, it means somehow your data dictionary is inconsistent and you may need to run the catproc.sql script.
    ~ Madrid

  • SYS packages are invalid in oracle 10g (10.2.0.4)

    I am using Oracle 10g (10.2.0.4) in AIX 6.1 server . According to OEM advice I remove the 'utl_file' privelege
    from PUBLIC user . In that moment I get some packages of the 'SYS' schema invalid . I again give the
    grant permission of the 'UTL_FILE' to PUBLIC user but packages of the SYS schema are remain invalid .
    I compile the packages several times but the problem in not solved . If one package make valid
    then other package goes to INVALID during compiling . In this moment, How can I Enable the
    SYS user's package .The problem is related only with the packages & views now ...
    Would anybody plz help me now ...

    shipon_97 wrote:
    I am using Oracle 10g (10.2.0.4) in AIX 6.1 server . According to OEM advice I remove the 'utl_file' privelege
    from PUBLIC user . In that moment I get some packages of the 'SYS' schema invalid . I again give the
    grant permission of the 'UTL_FILE' to PUBLIC user but packages of the SYS schema are remain invalid .
    I compile the packages several times but the problem in not solved . If one package make valid
    then other package goes to INVALID during compiling . In this moment, How can I Enable the
    SYS user's package .The problem is related only with the packages & views now ...
    Would anybody plz help me now ...Try compiling all the objects with "UTLRP.sql" on the server, then check invalid objects.
    conn / as sysdba
    @?/rdbms/admin/utlrp.sql Regards
    Z.K.
    http://oracleendeavor.blogspot.com/

  • PLS-00753: malformed or corrupted wrapped unit on SYS packages

    Hello All,
    I tried to run an export today and received this error on the SYS.DBMS_AQADM_SYS package body. I tried dropping and recreating through the catalog.sql, catexp.sql, and catproc.sql scripts but the package body was recreated with the same errors. I have done exports on this instance before and it seemed to cause this problem today at random. Now several other sys packages are going invalid as a result and when I try to run an export I get the error:
    UDE-00008: operation generated ORACLE error 4063
    ORA-04063: package body "SYS.KUPV$FT_INT" has errors
    ORA-06508: PL/SQL : could not find the program unit being called: "SYS.KUPV$FT_INT"
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 2742
    ORA-04063: package body "SYS.KUPV$FT_INT" has errors
    ORA-06508: PL/SQL : could not find the program unit being called: "SYS.KUPV$FT_INT"
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 3712
    ORA-06512: at line 1
    Does anyone know what could cause this or how to fix it?
    Thanks,
    Sean

    it appears that my sys and apex_flows schema are now hosed. apex stopped working so I restarted the machine - now when I try to start Oracle it gets all the way to "database mounted" before cancelling with the "ORA-01092: ORACLE instance terminated. Disconnection forced"
    does this mean that my instance is hosed? I can restore from a backup but would lose some serious development time if this occurred.

  • Error while installing Grid Control 12c (ERROR STREAM: *sys-package-mgr*: skipping bad jar)

    Hi all,
       OS: OEL 6.3 64 bits
       DB: 11.2.0.3
       Grid: 12.1
       While installing Grid Control 12c, the following error appears to me:
    INFO: SaveInvWCCE JRE files in Scratch
    INFO: oracle.installer.mandatorySetup property is set to false, so skipping the execution of additional tools
    INFO: oracle.installer.installUpdates property is set to false, so skipping the checking of updates
    INFO: Config Initialize JRE files in Scratch
    INFO: no env vars set, no envVars.properties file is generated
    INFO: none of the components are configurable
    INFO: This is a shared oracle home or remote nodes are null. No copy required.
    INFO: Adding iterator oracle.sysman.oii.oiif.oiifw.OiifwRootShWCDE
    INFO: Updating the global context
    INFO: Path To 'globalcontext.xml' = /gridControl/WLS/jdk16/install/chainedInstall/globalcontext
    INFO: Since operation was successful, move the current OiicAPISessionDetails to installed list
    INFO: Install Finished at: 2013-07-04_11-12-49-PM
    INFO: The ARU ID found in shiphomeproperties.xml file is 226
    INFO: ARUId present in shiphomeproperties.xml matches with the 64 bit OMS Platforms ARU ID 226, so -d64 is passed for wls install.
    INFO: Executing the command /gridControl/WLS/jdk16/jdk/bin/java   -d64  -Djava.io.tmpdir=/gridControl/WLS/.wlsinstall_temp -Xms128m -Xmx1024m  -jar /u01/binaries//wls/wls1035_generic.jar -mode=silent -silent_xml=/gridControl/WLS/.wlsinstall_temp/wls.xml -log=/u01/oraInventory/logs/installActions2013-07-04_11-07-45PM.log.wls  -log_priority=debug
    INFO: Extracting 0%....................................................................................................100%
    INFO: ERROR STREAM: *sys-package-mgr*: skipping bad jar, '/u01/binaries/wls/wls1035_generic.jar'
    INFO: #
    INFO: # A fatal error has been detected by the Java Runtime Environment:
    INFO: #
    INFO: #  SIGSEGV (0xb) at pc=0x0000003a23689cdc, pid=24834, tid=139710737405696
    INFO: #
    INFO: # JRE version: 6.0_24-b50
    INFO: # Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode linux-amd64 compressed oops)
    INFO: # Problematic frame:
    INFO: # C  [libc.so.6+0x89cdc]
    INFO: #
    INFO: # An error report file with more information is saved as:
    INFO: # /tmp/hs_err_pid24834.log
    INFO: #
    INFO: # If you would like to submit a bug report, please visit:
    INFO: #   http://java.sun.com/webapps/bugreport/crash.jsp
    INFO: #
    INFO: Return value is 134
    INFO: POPUP ERROR:Installation of Oracle WebLogic Server has failed, check log files for more details.
       The line "skipping bad jar, '/u01/binaries/wls/wls1035_generic.jar'" is the one that's worring me. Can it be corrupt? Or it is something else?
       Thanks in advance.

    Its too early to conclude the issue is a bug with out looking into the logs. For the same reason i requested you to open an SR so that we can have a look at the logs and identify the cause.  If you are Oracle employee then you can share the VM details else we need logs to debug this further. If any one from your company can open an sr and share logs then that will be helpful. Can you also check if the shiphome that you downloaded is all correct and checksum/byte matches to what is mentioned on OTN.

  • When should be package invalidated?

    Hello guys,
    I would need again some help...
    My question is: When exactly should be package invalidated?
    Consider following situation:
    We have two packages, one contains constants (in its specification), the other is reading these constants. Package is reading these constants in package body and package spec as well. Now, when I add a new constant to the first package and recompile it, should this invalidate the other package??? The new added constant is not used in the other package.
    In reality, we have a Constant package, containing all constants in its specification. One package (test_pkg) is reading some constant let say form line 100. Now we add new constant let say to line 50. When we recompile the constant package, planty of packages get invalidated because they are reading from it. We recompile all invalid packages. However test_pkg is not invalidated!!! Now if we run the code from test_pkg, it is still reading the constant from line 100, so it is reading it from wrong place and the constant has wrong value! The only thing what help is to recompile the test_pkg.
    So it looks like the reference to Constant package wasn't updated.
    Why isn't test_pkg invalidated???
    Oracle version:
    SELECT * FROM V$VERSION;
    Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    "CORE     11.2.0.1.0     Production"
    TNS for Linux: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production

    From my standard library of responses...
    Packages tend to fail because of their "package state". A package has a "state" when it contains package level variables/constants etc. and the package is called. Upon first calling the package, the "state" is created in memory to hold the values of those variables etc. If an object that the package depends upon e.g. a table is altered in some way e.g. dropped and recreated, then because of the database dependencies, the package takes on an INVALID status. When you next make a call to the package, Oracle looks at the status and sees that it is invalid, then determines that the package has a "state". Because something has altered that the package depended upon, the state is taken as being out of date and is discarded, thus causing the "Package state has been discarded" error message.
    If a package does not have package level variables etc. i.e. the "state" then, taking the same example above, the package takes on an INVALID status, but when you next make a call to the package, Oracle sees it as Invalid, but knows that there is no "state" attached to it, and so is able to recompile the package automatically and then carry on execution without causing any error messages. The only exception here is if the thing that the package was dependant on has changes in such a way that the package cannot compile, in which case you'll get an Invalid package type of error.
    And if you want to know how to prevent discarded package states....
    Move all constants and variables into a stand-alone package spec and reference those from your initial package. Thus when the status of your original package is invlidated for whatever reason, it has no package state and can be recompiled automatically, however the package containing the vars/const will not become invalidated as it has no dependencies, so the state that is in memory for that package will remain and can continue to be used.
    As for having package level cursors, you'll need to make these local to the procedures/functions using them as you won't be able to reference cursors across packages like that (not sure about using REF CURSORS though.... there's one for me to investigate!)
    This first example shows the package state being invalided by the addition of a new column on the table, and causing it to give a "Package state discarded" error...
    SQL> set serveroutput on
    SQL>
    SQL> create table dependonme (x number)
      2  /
    Table created.
    SQL>
    SQL> insert into dependonme values (5)
      2  /
    1 row created.
    SQL>
    SQL> create or replace package mypkg is
      2    procedure myproc;
      3  end mypkg;
      4  /
    Package created.
    SQL>
    SQL> create or replace package body mypkg is
      2    v_statevar number := 5; -- this means my package has a state
      3
      4    procedure myproc is
      5      myval number;
      6    begin
      7      select x
      8      into myval
      9      from dependonme;
    10
    11      myval := myval * v_statevar;
    12      DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
    13    end;
    14  end mypkg;
    15  /
    Package body created.
    SQL>
    SQL> exec mypkg.myproc
    My Result is: 25
    PL/SQL procedure successfully completed.
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        VALID
    SQL>
    SQL>
    SQL> alter table dependonme add (y number)
      2  /
    Table altered.
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        INVALID
    SQL>
    SQL> exec mypkg.myproc
    BEGIN mypkg.myproc; END;
    ERROR at line 1:
    ORA-04068: existing state of packages has been discarded
    ORA-04061: existing state of package body "SCOTT.MYPKG" has been invalidated
    ORA-06508: PL/SQL: could not find program unit being called: "SCOTT.MYPKG"
    ORA-06512: at line 1
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        INVALID
    SQL>
    SQL> exec mypkg.myproc
    PL/SQL procedure successfully completed.
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        VALIDAnd this next example shows how having the package variables in their own package spec, allows the package to automatically recompile when it is called even though it became invalidated by the action of adding a column to the table.
    SQL> drop table dependonme
      2  /
    Table dropped.
    SQL>
    SQL> drop package mypkg
      2  /
    Package dropped.
    SQL>
    SQL> set serveroutput on
    SQL>
    SQL> create table dependonme (x number)
      2  /
    Table created.
    SQL>
    SQL> insert into dependonme values (5)
      2  /
    1 row created.
    SQL>
    SQL> create or replace package mypkg is
      2    procedure myproc;
      3  end mypkg;
      4  /
    Package created.
    SQL>
    SQL> create or replace package mypkg_state is
      2    v_statevar number := 5; -- package state in seperate package spec
      3  end mypkg_state;
      4  /
    Package created.
    SQL>
    SQL> create or replace package body mypkg is
      2    -- this package has no state area
      3
      4    procedure myproc is
      5      myval number;
      6    begin
      7      select x
      8      into myval
      9      from dependonme;
    10
    11      myval := myval * mypkg_state.v_statevar;  -- note: references the mypkg_state package
    12      DBMS_OUTPUT.PUT_LINE('My Result is: '||myval);
    13    end;
    14  end mypkg;
    15  /
    Package body created.
    SQL>
    SQL> exec mypkg.myproc
    My Result is: 25
    PL/SQL procedure successfully completed.
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        VALID
    SQL>
    SQL> alter table dependonme add (y number)
      2  /
    Table altered.
    SQL>
    SQL> select object_name, object_type, status from user_objects where object_name = 'MYPKG'
      2  /
    OBJECT_NAME
    OBJECT_TYPE         STATUS
    MYPKG
    PACKAGE             VALID
    MYPKG
    PACKAGE BODY        INVALID
    SQL>
    SQL> exec mypkg.myproc
    My Result is: 25
    PL/SQL procedure successfully completed.

  • Combination of support packages invalid.

    I am getting the following error in RSPOR_SETUP, but according to note 1013369
    this stack is supported. This system is a fresh SR2 install , then I applied
    SPS12 , then finally applied SAPKW70014.
    Is the error referring to the version 11 of the java classes? How did those even get there?
    The Systeminfo shows all java components correctly at SPS12....
    Status for Step 2 - Create RFC Destination for Portal
       Status 1: Create RFC Destination In J2EE Engine         Okay
       Status 2: Create RFC Destination for Portal             Different ABAP and Java support packages. Combination of support packages invalid.
       Status 3: Maintain Portal Server Settings for Portal    Okay
       Status 4: Maintain Single Sign-On in BI                 Okay
       Status 5: Export BI Certificate into BI                 Okay
       Status 6: Import BI Certificate into Portal             Okay
       Status 7: Create BI Sytem in Portal                     Existence of BI System in Portal cannot be checked automatically.
       Status 8: Configure User Management in Portal           Okay
       Status 9: Export Portal Certificate into Portal         Okay
       Status 10: Import Portal Certificate into BI            Okay
       Status 11: Set Up Repository Manager for BI in Portal   Setup of Repository Manager for BI in Portal cannot be checked automatically.
       Status 12: Maintain User Assignment in Portal           Okay
       Status 13: Import SAP NetWeaver Plug-In into BI         Okay
    Entries for Step 2 - Create RFC Destination for Portal
    BI Transaction Display and Maintenance of RFC Destinations (SM59)
    Create
    Name of RFC destination:             (redacted)
    Connection type:                     T (TCP/IP connection)
    Description of RFC destination:      (redacted)
    Technical settings
    Activation type:                     Registered Server Program
    Program ID:                          (redacted)
    Gateway host:                        (redacted)
    Gateway service:                     (redacted)
    Logon/security
    Send SAP Logon Ticket                active
    Checks for Step 2 - Create RFC Destination for Portal
    1. Check existance of RFC destination
       Check of RFC destination  (redacted)  with RFC_READ_TCPIP_DESTINATION successful
    2. Check RFC destination with RFC Call
       RFC Call RFC_PING, destination  (redacted)  successful
    3. Check Number of registered Processes
       GWY_GET_NO_REG_PROGRAMS
       Number of registered processes:       20
    4. Check existance of com.sap.ip.bi Java classes
       RFC Call RSWR_RFC_SERVICE_TEST, destination  (redacted)  successful
        BI test service for user (redacted) called successfully with parameter RSPOR_SETUP.
    5. Check version information of com.sap.ip.bi Java classes
       RFC Call RSWR_RFC_VERSION_INFO_GET, destination  (redacted) successful
       com.sap.ip.bi.base.application.par           7.0012.20070801085802.0000
       com.sap.ip.bi.base.par                       7.0012.20070801085802.0000
       com.sap.ip.bi.base.portal.par                7.0012.20070801085802.0000
       com.sap.ip.bi.bics.cmi.par                   7.0012.20070426205038.0000
       com.sap.ip.bi.bics.os.impl.par               7.0011.20070131173855.0000
       com.sap.ip.bi.bics.os.par                    7.0011.20070131173855.0000
       com.sap.ip.bi.bics.par                       7.0012.20070801085802.0000
       com.sap.ip.bi.broadcasting.base.par          7.0012.20070801085802.0000
       com.sap.ip.bi.broadcasting.par               7.0011.20070131173855.0000
       com.sap.ip.bi.conv.backendaccess.par         7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.bi.os.par         7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.bi.par            7.0012.20070801085802.0000
       com.sap.ip.bi.conv.dac.res.dll.par           7.0011.20070131173855.0000
       com.sap.ip.bi.conv.dac.res.oqqv.par          7.0012.20070801085802.0000
       com.sap.ip.bi.conv.dac.res.trex.par          7.0011.20070131173855.0000
       com.sap.ip.bi.dataaccessservice.par          7.0012.20070426205038.0000
       com.sap.ip.bi.export.lib.par                 7.0012.20070426205038.0000
       com.sap.ip.bi.export.model.par               7.0012.20070801085802.0000
       com.sap.ip.bi.export.office.par              7.0012.20070801085802.0000
       com.sap.ip.bi.export.printformats.par        7.0012.20070801085802.0000
       com.sap.ip.bi.export.xfa.par                 7.0012.20070801085802.0000
       com.sap.ip.bi.folderpickerpcd.par            7.0012.20070426205038.0000
       com.sap.ip.bi.km.base.par                    7.0012.20070801085802.0000
       com.sap.ip.bi.km.documentmigration.par       7.0012.20070426205038.0000
       com.sap.ip.bi.km.integration.par             7.0012.20070801085802.0000
       com.sap.ip.bi.km.propertyrenderer.par        7.0011.20070201072627.0000
       com.sap.ip.bi.km.repositorymanager.par       7.0012.20070801085802.0000
       com.sap.ip.bi.metadata.par                   7.0012.20070426205038.0000
       com.sap.ip.bi.objectservices.oqqv.par        7.0011.20070201072627.0000
       com.sap.ip.bi.objectservices.par             7.0011.20070201072627.0000
       com.sap.ip.bi.offlinenavigation.par          7.0011.20070201072627.0000
       com.sap.ip.bi.portal.rfc.dispatcher.par      7.0012.20070426205038.0000
       com.sap.ip.bi.portalheartbeat.par            7.0010.20061024165340.0000
       com.sap.ip.bi.portallogger.par               7.0010.20061024165340.0000
       com.sap.ip.bi.portalnavigation.par           7.0011.20070131173855.0000
       com.sap.ip.bi.portalrfc.par                  7.0010.20061024165340.0000
       com.sap.ip.bi.portalrfctest.par              7.0010.20061024165340.0000
       com.sap.ip.bi.ranges.par                     7.0012.20070801085802.0000
       com.sap.ip.bi.repositorymanager.par          7.0010.20061024165340.0000
       com.sap.ip.bi.service.bics.par               7.0012.20070426205038.0000
       com.sap.ip.bi.service.generic.par            7.0012.20070801085802.0000
       com.sap.ip.bi.service.km.os.par              7.0012.20070426205038.0000
       com.sap.ip.bi.service.portal.os.par          7.0010.20061024142635.0000
       com.sap.ip.bi.supportdesk.par                7.0013.20070620182001.0000
       com.sap.ip.bi.web.advancedcontrols.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.broadcasterstart.par       7.0011.20070201072627.0000
       com.sap.ip.bi.web.composites.par             7.0011.20070201072627.0000
       com.sap.ip.bi.web.dataprovider.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.deploytime.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.dialogs.conditions.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.exceptions.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.formula.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.dialogs.generic.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.dialogs.opensave.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.selector.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.statistic.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogs.variablescreen     7.0012.20070801085802.0000
       com.sap.ip.bi.web.dialogsframework.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.analysis.par         7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.bodyattributes.p     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.broadcastindex.p     7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.buttongroup.par      7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.chart.par            7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.command.par          7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.container.par        7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.contextmenu.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.dataproviderinfo     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.filter.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.filterpane.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.generic.par          7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.group.par            7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.hierarchfilter.p     7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.htmlattributes.p     7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.infofield.par        7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.inputfield.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.km.par               7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.map.par              7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.menu.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.messageslist.par     7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.mime.par             7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.navigation.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.persistency.par      7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.properties.par       7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.report.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.structural.par       7.0011.20070201072627.0000
       com.sap.ip.bi.web.items.text.par             7.0012.20070801085802.0000
       com.sap.ip.bi.web.items.ticker.par           7.0012.20070426205038.0000
       com.sap.ip.bi.web.items.variables.par        7.0011.20070201072627.0000
       com.sap.ip.bi.web.objectservices.par         7.0011.20070201072627.0000
       com.sap.ip.bi.web.pageexport.par             7.0011.20070201072627.0000
       com.sap.ip.bi.web.portal.deployment.par      7.0011.20070201072627.0000
       com.sap.ip.bi.web.portal.integration.par     7.0012.20070801085802.0000
       com.sap.ip.bi.web.portal.mimes.par           7.0012.20070801085802.0000
       com.sap.ip.bi.web.preexecution.par           7.0012.20070426205038.0000
       com.sap.ip.bi.web.runtime.par                7.0012.20070801085802.0000
       com.sap.ip.bi.web.runtime.scripting.par      7.0012.20070801085802.0000
       com.sap.ip.bi.web.runtime.template.par       7.0012.20070426205038.0000
       com.sap.ip.bi.web.scripting.par              7.0012.20070426205038.0000
       com.sap.ip.bi.web.ui.dragdrop.par            7.0012.20070426205038.0000
       com.sap.ip.bi.web.ui.queryviewactions.pa     7.0012.20070426205038.0000
       com.sap.ip.bi.web.uiframework.par            7.0012.20070426205038.0000
       com.sap.ip.bi.web.uiitem.par                 7.0011.20070201072627.0000
       com.sap.ip.bi.web.unifiedrendering.par       7.0012.20070801085802.0000
       com.sap.ip.bi.webdynpro.alv.pdf.par          7.0011.20070201072627.0000
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
       ABAP Support Package:                  14
       Java Support Package:                  11

    Hi,
    I have the same problem. I´ve installed a fresh netweaver SR3, and the patch level is the next,
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package(SAP BI)
    ABAP Support Package:           19
    Java Support Package:              16
    More thanks

  • Java Package Invalid?

    Recently I have upgraded Oracle database to 10g from 9i.
    How to check whether any java code is invalid in backend

    Here:
    Re: Java Package Invalid?

  • WLST in Eclipse: sys-package-mgr + Failed to get environment

    Hello.
    Due to recent CEAL blog post: https://blogs.oracle.com/pa/entry/getting_started_with_weblogic_scripting
    I decided to try out Oracle Enterprice Pack for Eclipse - for writing WLST scripts.
    We have OBIEE 11.1.1.7.140415 installed on Windows Server 2008 R2 64-bit. It uses JDK 1.6 so I installed OEPE 12.1.2.3 - the last version that supports JDK 1.6.
    Then when I try to run simple WLST script I get two following errors:
    1) *sys-package-mgr*: can't create package cache dir, 'C:\OracleBI11\wlserver_10.3\server\lib\weblogic.jar\cachedir\packages'
    2) Failed to get environment, environ will be empty: (0, 'Failed to execute command ([\'sh\', \'-c\', \'env\']): java.io.IOException: Cannot run program "sh": CreateProcess error=2, The system cannot find the file specified')
    About the first one googling says I need to set python.cachedir.skip = true but my efforts on this didn't succeed - I don't understand where can I set this parameter / variable.
    About the second googling says it could be caused by jython-modules.jar doesn't know about my platform. But my playing with _osTypeMap didn't succeed too.
    Please help me avoid both these errors.

    More information would be helpful. . .are you PXE booting? Using media?
    THis thread is similar:
    https://social.technet.microsoft.com/Forums/en-US/0d877b49-0823-4d59-8a08-3ced41602b6f/setting-wizard-error-an-error-occurred-while-retrieving-policy-for-this-computer-0x80004005?forum=configmanagerosd
    Jeff

  • INVALID SYS PACKAGES

    Oracle 8i (8.1.7.4.1) Windows 2000 Server
    Using DBNS_UTILITY.COMPILE_SCHEMA('SYS', FALSE) some objects compile and others become invalid.
    Help please

    Please use
    @?\rdbms\admin\utlrp.sql
    in sqlplus connected as SYS, instead of dbms_utility.compile_schema.
    If you still have invalid objects,
    look in dba_errors for the error messages which were generated and resolve them.
    If you want assistance only posting something failed, without posting error messages, is insufficient and should be avoided.
    Sybrand Bakker
    Senior Oracle DBA

  • Some Objects owned by SYS became invalid due wrong deletion from OBJ$ table

    Hi,
    While cleaning up streams from source database,we have found some rules and stream queue name was still present, so we tried to delete those records from obj$ table, but by mistake we have deleted all records from obj$ table related to streams.Actually we executed the following sql statement:
    DELETE FROM OBJ$ WHERE NAME LIKE '%STREAM%';COMMIT;
    For this fault some problem arrise.After this we have found lots of SYS owner objects (VIEW,PACKAGE,TYPE) are become invalid.This situation happened in a remote database.For this remote database there is missing a TYPE "AQ$_JMS_STREAM_MESSAGE".
    We have created a dummy database in local and executed the same delete statement, and after this We have executed (after shutdown immediate & startup migrate)catpatch.sql & (after shutdown immediate & startup) utlrp.sql but still there are some objects exists invalid.
    e.g. one object is "_DBA_APPLY_ERROR" which is invalid.While I have tried to open the table "APPLY$_ERROR" for this view it showing an error message "ORA-00600: internal error code, arguments: [kkdlusr1], [30813], [], [], [], [], [], []"
    We are using ORACLE 9.2.0.5 and Windows XP for our work.
    Now please tell me what is it`s remedy.
    Thanks in advance.

    I had exec utlirp.sql..
    Well you were asked to run utlrp.sql. I can't speak about the time that it will take to get complete. For the invalid objects, there are two ways to make them valid,one run utlrp.sql and see how many become valid and the other ( painful one) is to manually look for the errors in their compilation and sort it out.
    Aman....

  • Sys.deferror : invalid ...

    Hi all,
    I am doing replication for my Oracle 10g r2 server. while installing on one of the servers i ran the catrep.sql which told some views erronous. one such view is sys.deferror. Now when i watch the definition of the view it refers to a table which is not existing. Now i want to know that is there some package needed to install explicitly for replication to activate or its there by default ?
    I read a lots of replication docs .... we have some preexisting scripts that we ran on 8.1.7 earlier . now we are having 10g. So replication needs to be setup on it ........ but the deferror view is showing errors ... even recompiling also didn't work ....
    Any help is appreciated
    -Ankur

    I manually created my DB....Did you run CATALOG.SQL and CATPROC.SQL scripts after you created the database?
    This is the o/p of the query u told ....
    OWNER TABLE_NAME STATUS
    SYSTEM DEF$_TEMP$LOB VALID
    SYSTEM DEF$_PUSHED_TRANSACTIONS VALID
    SYSTEM DEF$_PROPAGATOR VALID
    SYSTEM DEF$_LOB VALID
    SYSTEM DEF$_AQERROR VALID
    SYSTEM DEF$_AQCALL VALIDThere are five more objects missing:
    SYSTEM.DEF$_ORIGIN
    SYSTEM.DEF$_ERROR
    SYSTEM.DEF$_DESTINATION
    SYSTEM.DEF$_DEFAULTDEST
    SYSTEM.DEF$_CALLDEST
    These tables are created by catdefrt.sql script located in <ORACLE_HOME>/rdbms/admin directory. This script is invoked by catdefer.sql which is invoked by catproc.sql.
    Therefore you either didn’t run catproc.sql after you created the database, or you ran it, but it didn’t go well.
    where can i read this metalink ????Metalink is Oracle Web Support Portal. In order to use it your company must have Support Contract with Oracle. URL: http://metalink.oracle.com
    Other Info: http://www.oracle.com/support/premier/metalink.html
    If you haven’t ran CATPROC.SQL yet, you have to make sure you run this script. This script invokes CATREP.SQL. The same applies for CATALOG.SQL (run it before CATPROC.SQL).
    If you are sure you have ran CATALOG.SQL and CATPROC.SQL after you created the database, you may just run CATDEFER.SQL followed by CATREP.SQL
    Before you do anything, you have to answer the following questions and be aware of some restrictions:
    Is this database your production database?
    If yes, then if you decide to run CATPROC.SQL, you have to do it very carefully.
    Also it is important to know that running catproc will require some downtime because no users should be connected to the database while running the script. (the best way to ensure that no one is connected is to start the database in restricted mode)
    Again, if we are talking about production system here, you have to think about database availability.
    If this is not your production database, than you just have to make sure no other users are connected to the database when you run the script.
    In any case, make sure you run each of the scripts connected as SYS.
    If you haven’t ran CATALOG.SQL neither, you make sure you run it before you run CATPROC.SQL
    These scripts are essential to build Data Dictionary Views after the database has been created manually.
    For more info refer to http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref254
    Once you make sure CATALOG.SQL and CATPROC.SQL scripts ran correctly, that should be enough since CATPROC.SQL invokes CATREP.SQL (starting from 9i).
    During the execution, you may get errors that many of the objects already exist, which can be ignored.
    Once you have all of the scripts ran, you have to run UTLRP.SQL script to recompile the invalid objects, if any.
    All of the scripts I mentioned are located in <ORACLE_HOME>/rdbms/admin directory.
    And again, if the database is the production one, make sure you know what you are doing, otherwise ask some experienced DBA for help, or contact Oracle Support (Metalink) and of course read the docs.
    --Mihajlo                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Executing security_pkg.create_secu_owner causes sys objects invalid?

    Hi everyone,
    Just trying to confirm.
    We've been investigating why the SYS owned UTL_FILE and other packages suddenly became invalid on the database (9.2.0.5)
    The only activiy we can find based on the audit logs during the time when the utl_file became invalid is this command:
    BEGIN security_pkg.create_secu_owner('XXXXXX','aaaaa'); END;
    *input parameters have been changed for security purposes.
    can executing the security_pkg.create_secu_owner really cause the UTL_FILE to become invalid?
    thanks,

    I had exec utlirp.sql..
    Well you were asked to run utlrp.sql. I can't speak about the time that it will take to get complete. For the invalid objects, there are two ways to make them valid,one run utlrp.sql and see how many become valid and the other ( painful one) is to manually look for the errors in their compilation and sort it out.
    Aman....

  • Error while deploying a Cube * OLAPSYS packages invalid

    Hi,
    I'm really new with OWB, I'm using a Oracle 10.2.0.4, and OWB 11gR1 (Windows Server).
    I'm having a problem while trying to deploy a Cube (a simple cube, that I made to try to understand how this works).
    The error is:
    ORA-04063: package body "OLAPSYS.CWM2_OLAP_MANAGER" has errors
    ORA-06508: PL/SQL: could not find program unit being called: "OLAPSYS.CWM2_OLAP_MANAGER"
    ORA-06512: at "OLAPSYS.CWM2_OLAP_CUBE", line 127
    ORA-06512: at line 2
    I check the OLAPSYS schema I found a lot of package (including CWM2_OLAP_MANAGER) Invalid, I try to compile them but without success, and I didn't see what is missing (cause it is encrypted).
    I didn't Installed this database, so I don't know what they did to upgrade it from 10.2.0.1 to 10.2.0.4, but:
    There is a way to re-create or reload all this packages?
    I really appreciate your help!
    Thanks
    Erick Dennis.

    Hi,
    I'm having problems to deploy this cube (this was the origin of my problem), when I change it to "Deploy Data Object Only", It don't generate code and the cube is not created. This is what I get:
    -- Product : Oracle Warehouse Builder
    -- Generator Version : 11.1.0.6.0
    -- Created Date : Wed May 12 08:41:59 CST 2010
    -- Modified Date : Wed May 12 08:41:59 CST 2010
    -- Created By : edennis
    -- Modified By : edennis
    -- Generated Object Type : TABLE
    -- Generated Object Name : FACT_TMP_SALDOS
    -- Comments :
    -- Copyright © 2000, 2007, Oracle. All rights reserved.
    WHENEVER SQLERROR EXIT FAILURE;
    Ideas?
    Thanks for your help!

  • SYS PACKAGE DBMS_DEFER_IMPORT_INTERNAL NOT ACCESSIBLE

    We are trying to import a dmp file to Oracle 10.2.0.1 database. This is a full import and ignore=y has been given. We found the following error for one particular user
    ORA-06550: line 2, column 5:
    PLS-00302: component 'DBMS_DEFER_IMPORT_INTERNAL' must be declared
    ORA-06550: line 2, column 1:
    PL/SQL: Statement ignored
    We observed that this is being executed when connected as a user FIDILEO, and on a standalone sql session too, we are getting the same error when executing the package
    BEGIN
    SYS.DBMS_DEFER_IMPORT_INTERNAL.QUEUE_IMPORT_CHECK('XXXXXX','IBMPC/WIN_NT-8.1.0');
    END;
    After much research on web, I have now done a GRANT command after logged in as SYS user, as
    GRANT EXECUTE ON SYS.DBMS_DEFER_IMPORT_INTERNAL TO FIDILEO;
    GRANT EXECUTE ON SYS.DBMS_DEFER_IMPORT_INTERNAL TO PUBLIC;
    Still, we cannot execute this procedure when logged in as FIDILEO and continues to give the same error message. However, new users and other users are able to execute the PLSQL Block. I have verified that the package and it's body is VALID.
    Basic overlook of the privileges shows that all seems right, still not able to execute this PLSQL block. This issue is happening for 3 packages
    1. SYS.DBMS_DEFER_IMPORT_INTERNAL
    2. SYS.DBMS_EXPORT_EXTENSION
    3. SYS.DBMS_LOGREP_IMP
    These issues were not in 11g import. Only in 10g. Can anyone help?
    Message was edited by:
    user636365

    Version 10.2.0.1 is several years old and apparently never patched.
    This may not solve your specific issue but based on your comment about not having the issue in 11g I would be reasonable, as a first step, to apply the available patches or at least determine if they address the issue before proceeding.

Maybe you are looking for