Packages invalid in DMSYS

I have noticed a number of package bodies to be invalid in DMSYS schema.
I have tried to recompile but still invalid
What is the simplest way to around this?
The version of Oracle is 10.2.0.40

Please list objects which are invalid in DMSYS schema. Was the database upgrade from 10.1 release?

Similar Messages

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

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

  • [solved] Package invalid errors

    I'm trying to fix a system that died in the middle of a `pacman -Syu` (via `pacman -Qenq | -S -`) and I'm having a ton of problems with packages begin invalid. I've set my clock and cleared the cache several times, and I'm still getting invalid signature errors. Here's the debug output from one invalid package:
    debug: found cached pkg: /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz
    debug: sig data: iQEcBAABAgAGBQJS9WIIAAoJEPmf/g/q6Zm9av8H+wTWd7jkBVIBLKxdkqr5mFon9pyrh5ArxG5xmEI+mcozz1v1uzC+id35NXySFnb5kK+I5l1P4SO3SGCZeLbmO6ESDa9VVgiK9E5zFvniCcYF1bdRib1bs9i95V009krF6BRyLKRJdegyA6hT4wligU34NdIa/xnh48n3/ONwSe+YavJieY/2eZoSHLO73+4Lv68mzXPzZbUNm1J/XQXVnTLsy7fnpKwP4N2u8MnQI0RC7UGKtCNLTzVMiLXO/Vid4i4vcis/CeoJrdVk2g3HyxrZxZwnTmdygbuCyyAdFEC5F4H6pV4YzQ7QhhlCmrnB0GH+LnC+Vc3aZdJZk88FbZc=
    debug: checking signature for /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz
    debug: 1 signatures returned
    debug: fingerprint: F99FFE0FEAE999BD
    debug: summary: red
    debug: status: Bad signature
    debug: timestamp: 0
    debug: exp_timestamp: 0
    debug: validity: unknown; reason: Success
    debug: key: 6645B0A8C7005E78DB1D7864F99FFE0FEAE999BD, Allan McRae <[email protected]>, owner_trust unknown, disabled 0
    debug: signature is not valid
    In stdout, that's:
    error: gcc: signature from "Allan McRae <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/gcc-4.8.2-8-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n]
    When the validity check doesn't fail, the unpack often will, implying the same package is still bad.
    It could be a bad mirror, in theory, except it's intermittent (albeit frequent), and my top mirror is kernel.org.
    EDIT: Looks like the failure hosed something basic- reinstalling pacman's dependencies (including glibc) ended up triggering "illegal instruction" errors (and ultimately segfaults), and rebooting caused the same behavior in systemd.
    When in doubt, boot install media, mount target and `pacstrap -cM base`.
    This (pacstrapping base and then reinstalling everything) appears to have fixed the root problem, although I'm still experiencing echoes of the problem.
    Last edited by STUART (2014-04-21 10:55:15)

    karol wrote:Have you read the wiki https://wiki.archlinux.org/index.php/Pa … 9.22_error ?
    Thanks a lot. Solved by that.

  • 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

  • Package Invalid after Upgrade

    Hi All,
    I have recently upgraded one of my databases to Oracle 10.2.0.3 after which one of the package has become invalid.
    when I try to re-compile the package, its breaking at the follwoing line :
    -- Constants
         C          Constants := Constants(0);
    NOTE : The Package valid in the other envirionment where the database is still in oracle 9.2.0.5

    What is it 'breaking' with? an error? what error?
    What is "constants"? Where has that object type been declared?

  • Trouble with Package Invalidating Itself:

    Hello All,
    First, please let me know if this is not the place for this.
    Second, I'm trying to create a generic pivot table package such that developers can call it from ColdFusion. I've implemented it by having the package generate and execute DDL (using EXECUTE IMMEDIATE) but the problem is the tables that are being created are dependencies of the package causing it to generate this error each time it is run.
    ORA-04068: existing state of packages has been discarded ORA-04061: existing state of package body "HRPAYROLL.ORA_TOOLS" has been invalidated ORA-06508: PL/SQL: could not find program unit being called ORA-06512: at line 1
    It runs fine after automatic recompilation (refreshing the web page) but this won't work so well for users. Any suggestions would be greatly appreciated. I've attached the code for the package and the procedure call from CF.
    Package:
    CREATE OR REPLACE PACKAGE BODY ORA_TOOLS is
    procedure PIVOT (
    p_MAIN_DESC IN varchar2,
    p_PIV_FIELD IN varchar2,
    p_AGG_FUNC IN varchar2,
    p_AGG_FIELD IN varchar2,
    r_RESULT_SET IN OUT RESULT_SET
    ) is
    v_PIV_FIELD varchar2(50):= p_PIV_FIELD;
    v_AGG_FUNC varchar2(50):= p_AGG_FUNC;
    v_AGG_FIELD varchar2(50):= p_AGG_FIELD;
    v_PIV_FIELD_DT varchar2(50);
    v_PIV_FIELD_SZ varchar2(50);
    v_DATE date;
    v_MAIN_DATA varchar2(2000):= 'create table main_data as ( ';/*Will equal p_MAIN_DESC*/
    v_TABLE_NAME varchar2(50);
    -- usage exec ora_tools.pivot('1','em_sex','COUNT','em_employee_id')
    /* Create distinct list of values to use as piv column headings */
    v_DIST_VALUES varchar2(2000):=
    'create table dist_values as
    select distinct nvl('||v_PIV_FIELD||',''UNKNOWN'') as piv_fields from MAIN_DATA';
    /* Create pivot/aggregate tables */
    v_CREATE_PIVOT varchar2(4000);
    v_CREATE_AGG varchar2(4000);
    v_GROUP_BY varchar2(4000);
    /* Create Pivot_Table insert text */
    v_INSERT_FIELDS varchar2(4000);
    v_INSERT_TEXT varchar2(4000);
    v_PIVOT_INSERT varchar2(250);
    v_INSERT_FIELDS_COUNT number;
    v_PIV_COL_NUM number;
    v_COUNTER number := 1;
    /* Drop temporary tables */
    v_DROP_MAIN_DATA varchar2(50):='drop table MAIN_DATA';
    v_DROP_DIST_VALUES varchar2(50):='drop table DIST_VALUES';
    v_DROP_PIV_TABLE varchar2(50):='drop table PIV_TABLE';
    v_DROP_AGG_TABLE varchar2(50):='drop table AGG_TABLE';
    /* Create cursors */
    cursor c_MAIN_DATA_FIELDS is
    select COLUMN_NAME,
    DATA_TYPE,
    DATA_LENGTH,
    DATA_PRECISION
    from user_tab_columns
    where TABLE_NAME='MAIN_DATA' and
    upper(COLUMN_NAME) != upper(v_PIV_FIELD) and
    upper(COLUMN_NAME) != upper(v_AGG_FIELD);
    v_MAIN_DATA_FIELDS c_MAIN_DATA_FIELDS%rowtype;
    cursor c_PIVOT_FIELDS is
    select nvl(PIV_FIELDS,'UNKNOWN') as PIV_FIELDS from DIST_VALUES;
    v_PIVOT_FIELDS c_PIVOT_FIELDS%rowtype;
    cursor c_TRANSFORM_DATA is
    select * from AGG_TABLE;
    v_TRANSFORM_DATA c_TRANSFORM_DATA%rowtype;
    cursor c_GET_TABLE_NAME is
    select table_name from user_tables where table_name = v_TABLE_NAME;
    v_GET_TABLE_NAME c_GET_TABLE_NAME%rowtype;
    begin
    /* Creates the MAIN_DATA sql */
    v_MAIN_DATA := v_MAIN_DATA ||p_MAIN_DESC;
    v_MAIN_DATA := v_MAIN_DATA||')';
    /*Parse the statements to drop the temp tables*/
    execute immediate v_DROP_MAIN_DATA;
    execute immediate v_DROP_DIST_VALUES;
    execute immediate v_DROP_PIV_TABLE;
    execute immediate v_DROP_AGG_TABLE;
    /*Parse the statement to create the temp tables*/
    execute immediate v_MAIN_DATA;
    execute immediate v_DIST_VALUES;
    /* sets the datatype for the aggregate field in the piv_table */
    if upper(v_AGG_FUNC) in ('SUM','AVG','COUNT') then
    v_PIV_FIELD_DT := 'NUMBER';
    v_PIV_FIELD_SZ := '10,5';
    else
    select data_type, data_length into v_PIV_FIELD_DT, v_PIV_FIELD_SZ
    from user_tab_columns
    where table_name='DIST_VALUES';
    end if;
    /* Add Main Data Elements */
    open c_MAIN_DATA_FIELDS;
    v_CREATE_PIVOT := 'create table PIV_TABLE ('; /* Create Pivot Table */
    v_CREATE_AGG := 'create table AGG_TABLE as select '; /* Create Agg Table */
    v_INSERT_FIELDS_COUNT := 0;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    while c_MAIN_DATA_FIELDS%found loop
    v_CREATE_PIVOT := v_CREATE_PIVOT||' '||v_MAIN_DATA_FIELDS.column_name||' '||v_MAIN_DATA_FIELDS.data_type||' ('||v_MAIN_DATA_FIELDS.data_length||')';
    v_CREATE_AGG := v_CREATE_AGG||' '||v_MAIN_DATA_FIELDS.column_name;
    v_GROUP_BY := v_GROUP_BY||' '||v_MAIN_DATA_FIELDS.column_name;
    v_INSERT_FIELDS := v_INSERT_FIELDS||' '||v_MAIN_DATA_FIELDS.column_name; /* Used to create the pivot insert record */
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    v_CREATE_PIVOT := v_CREATE_PIVOT||',';
    v_CREATE_AGG := v_CREATE_AGG||', ';
    v_GROUP_BY := v_GROUP_BY||', ';
    v_INSERT_FIELDS := v_INSERT_FIELDS||', ';
    v_INSERT_FIELDS_COUNT := v_INSERT_FIELDS_COUNT + 1;
    end loop;
    close c_MAIN_DATA_FIELDS;
    /* Add Pivot Data Elements */
    open c_PIVOT_FIELDS;
    fetch c_PIVOT_FIELDS into v_PIVOT_FIELDS;
    v_CREATE_PIVOT := v_CREATE_PIVOT||' "'||nvl(v_PIVOT_FIELDS.piv_fields,'UNKNOWN')||'" '||v_PIV_FIELD_DT||' ('||v_PIV_FIELD_SZ||')';
    fetch c_PIVOT_FIELDS into v_PIVOT_FIELDS;
    while c_PIVOT_FIELDS%found loop
    v_CREATE_PIVOT := v_CREATE_PIVOT||',"'||nvl(v_PIVOT_FIELDS.piv_fields,'UNKNOWN')||'" '||v_PIV_FIELD_DT||' ('||v_PIV_FIELD_SZ||')';
    fetch c_PIVOT_FIELDS into v_PIVOT_FIELDS;
    end loop;
    close c_PIVOT_FIELDS;
    /* End the Create Table */
    v_CREATE_PIVOT := v_CREATE_PIVOT||' )';
    /* End Create Pivot Table */
    /* debugging code */
    insert into debug_stuff (stuff) values (v_CREATE_PIVOT);
    commit;
    execute immediate v_CREATE_PIVOT;
    /* Aggregate functions COUNT, SUM, AVG, MAX, MIN */
    v_CREATE_AGG := v_CREATE_AGG||v_PIV_FIELD||',';
    If upper(v_AGG_FUNC) = 'COUNT' then
    v_CREATE_AGG := v_CREATE_AGG||' COUNT('||v_AGG_FIELD||') as AGG_DATA FROM MAIN_DATA GROUP BY '||v_GROUP_BY;
    elsif upper(v_AGG_FUNC) = 'SUM' then
    v_CREATE_AGG := v_CREATE_AGG||' SUM(to_number('||v_AGG_FIELD||')) as AGG_DATA FROM MAIN_DATA GROUP BY '||v_GROUP_BY;
    elsif upper(v_AGG_FUNC) = 'AVG' then
    v_CREATE_AGG := v_CREATE_AGG||' AVG(to_number('||v_AGG_FIELD||')) as AGG_DATA FROM MAIN_DATA GROUP BY '||v_GROUP_BY;
    elsif upper(v_AGG_FUNC) = 'MAX' then
    v_CREATE_AGG := v_CREATE_AGG||' MAX('||v_AGG_FIELD||') as AGG_DATA FROM MAIN_DATA GROUP BY '||v_GROUP_BY;
    elsif upper(v_AGG_FUNC) = 'MIN' then
    v_CREATE_AGG := v_CREATE_AGG||' MIN('||v_AGG_FIELD||') as AGG_DATA FROM MAIN_DATA GROUP BY '||v_GROUP_BY;
    end if;
    v_CREATE_AGG := v_CREATE_AGG||v_PIV_FIELD; /* Adds the pivot field to the group by list */
    --insert into debug_stuff (stuff) values (v_CREATE_AGG); commit;  
    /* Generates the table containing aggregate data */
    execute immediate v_CREATE_AGG;
    /*Example of the query that is constructed below
    select em_payroll_unit, pud_payroll_unit_name,
    max( decode( em_employee_status,'TR', AGG_DATA, null )),
    max( decode( em_employee_status,'AC', AGG_DATA, null )),
    max( decode( em_employee_status,'LV', AGG_DATA, null ))
    from ( select *
    from agg_table
    group by em_payroll_unit, pud_payroll_unit_name;
    /*Construct the Pivot Query*/
    v_INSERT_TEXT := 'insert into piv_table select ';
    open c_MAIN_DATA_FIELDS;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    v_INSERT_TEXT := v_INSERT_TEXT||' '||v_MAIN_DATA_FIELDS.COLUMN_NAME;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    while c_MAIN_DATA_FIELDS%FOUND loop
    v_INSERT_TEXT := v_INSERT_TEXT||', '||v_MAIN_DATA_FIELDS.COLUMN_NAME;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    end loop;
    close c_MAIN_DATA_FIELDS;
    open c_PIVOT_FIELDS;
    fetch c_PIVOT_FIELDS into v_PIVOT_FIELDS;
    while c_PIVOT_FIELDS%FOUND loop
    v_INSERT_TEXT := v_INSERT_TEXT||', max(decode(nvl('||v_PIV_FIELD||',''UNKNOWN''), '''||nvl(v_PIVOT_FIELDS.PIV_FIELDS,'UNKNOWN')||''', AGG_DATA, null)) ';
    fetch c_PIVOT_FIELDS into v_PIVOT_FIELDS;
    end loop;
    close c_PIVOT_FIELDS;
    v_INSERT_TEXT := v_INSERT_TEXT||' from (select * from agg_table) group by ';
    open c_MAIN_DATA_FIELDS;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    v_INSERT_TEXT := v_INSERT_TEXT||' '||v_MAIN_DATA_FIELDS.COLUMN_NAME;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    while c_MAIN_DATA_FIELDS%FOUND loop
    v_INSERT_TEXT := v_INSERT_TEXT||', '||v_MAIN_DATA_FIELDS.COLUMN_NAME;
    fetch c_MAIN_DATA_FIELDS into v_MAIN_DATA_FIELDS;
    end loop;
    close c_MAIN_DATA_FIELDS;
    /* debugging code */
    /*insert into debug_stuff (stuff) values (v_INSERT_TEXT);
    commit;
    execute immediate v_INSERT_TEXT;
    commit;
    OPEN r_RESULT_SET for SELECT * FROM PIV_TABLE;
    --RETURN;
    /*------------- Exception Handling ------------------------*/
    exception
    WHEN OTHERS THEN
    v_ErrorNumber := SQLCODE;
    v_ErrorText := SUBSTR(SQLERRM, 1, 200);
    insert into errors
    values (sysdate,
    v_ErrorNumber||' , '||v_ErrorText||' ORA_TOOLS');
    commit;
    v_TABLE_NAME := 'MAIN_DATA';
    open c_GET_TABLE_NAME;
    fetch c_GET_TABLE_NAME into v_GET_TABLE_NAME;
    if c_GET_TABLE_NAME%NOTFOUND then
    execute immediate 'create table MAIN_DATA (field1 varchar2(50))';
    end if;
    close c_GET_TABLE_NAME;
    v_TABLE_NAME := 'DIST_VALUES';
    open c_GET_TABLE_NAME;
    fetch c_GET_TABLE_NAME into v_GET_TABLE_NAME;
    if c_GET_TABLE_NAME%NOTFOUND then
    execute immediate 'create table DIST_VALUES (PIV_FIELDS varchar2(50))';
    end if;
    close c_GET_TABLE_NAME;
    v_TABLE_NAME := 'AGG_TABLE';
    open c_GET_TABLE_NAME;
    fetch c_GET_TABLE_NAME into v_GET_TABLE_NAME;
    if c_GET_TABLE_NAME%NOTFOUND then
    execute immediate 'create table AGG_TABLE (field1 varchar2(50))';
    end if;
    close c_GET_TABLE_NAME;
    v_TABLE_NAME := 'PIV_TABLE';
    open c_GET_TABLE_NAME;
    fetch c_GET_TABLE_NAME into v_GET_TABLE_NAME;
    if c_GET_TABLE_NAME%NOTFOUND then
    execute immediate 'create table PIV_TABLE (field1 varchar2(50))';
    end if;
    close c_GET_TABLE_NAME;
    end PIVOT;
    END ORA_TOOLS;
    CF Call code:
         <cfstoredproc procedure="ora_tools.pivot" datasource="hrpayroll">
         <!--- The query the generates the raw data set --->
         <cfprocparam
              value = "select emf.em_payroll_group,
                        emf.em_payroll_unit,
                        pud.pud_payroll_unit_name as pud_name,
                        emf.em_employee_id
                   from emf, pud
                   where emf.em_payroll_unit = pud.pud_payroll_unit
                   and em_employee_status = 'AC'"
              cfsqltype = "cf_sql_varchar">
         <!--- The field that you want to pivot on --->
         <cfprocparam
              value = "em_payroll_group"
              cfsqltype = "cf_sql_varchar">
         <!--- The aggregate function you want included can be one of COUNT, SUM, AVG, MAX, MIN --->
         <cfprocparam
              value = "COUNT"
              cfsqltype = "cf_sql_varchar">
         <!--- Field that you want to perform the aggregate function upon --->
         <cfprocparam
         value = "em_employee_id"
              cfsqltype = "cf_sql_varchar">
         <cfprocresult name="result">
         </cfstoredproc>
         <cfdump var="#result#">
    Thank you for your help,
    Mike

    I've implemented it by having the package generate and execute DDL (using EXECUTE IMMEDIATE)
    but the problem is the tables that are being created are dependencies of the package causing it to generate this error each time it is run.No the problem is creating and dropping objects in code, the invalidation is an expected result of doing that.
    You want something like this
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:15151874723724

  • MIGRATION package invalid

    Hello all!
    Every time I try I use the migration tool I get an error saying the migration package is invalid. I have dropped and recreated the repository a few times and have just completed a recreation of the repository schema owner. Additionally I have attempted to compile the package again with no luck and granted just about every permission I can think of at this point. :)
    Thank you for your time.
    Daryl
    db - 10.2.0.1 Enterprise Ed.
    os - Red Hat Enterprise Linux AS release 4 (Nahant Update 4)

    Daryl, There is a problem with the wrapping of the PLSQL code for 10.2.0.1. This is fine on XE, but doesnt compile on 10.2. Log a support ticket and we'll get you a unwrapped version of the packages.

  • Package invalid

    El paquete DBMS_ASYNCRPC_PUSH aparece descompilado genera el siguiente error:
    PLS-00753: malformed or corrupted wrapped unit.
    ya se ha ejecutado los siguientes scripts ( utlrp.sql and utlprp.sql), se ha ejecutado los siguiente comandos
    Exec dbms_ddl.alter_compile ( type , schema, name);,
    exec dbms_ddl.alter_compile ('PACKAGE','SYS','DBMS_ASYNCRPC_PUSH ');,
    EXECUTE UTL_RECOMP.RECOMP_SERIAL();,
    alter package DBMS_ASYNCRPC_PUSH compile body; ,
    EXEC DBMS_UTILITY.compile_schema(schema => 'SYS');
    ALTER PACKAGE DBMS_ASYNCRPC_PUSH COMPILE BODY;
    PACKAGE BODY DBMS_ASYNCRPC_PUSH Errors !
    Line :0, Position :0 PLS-00753: malformed or corrupted wrapped unit
    El error del paquete descompilado continua, no se que mas hacer, espero por favor su pronta ayuda....
    Gracias...

    Hello,
    The Package DBMS_ASYNCRPC_PUSH is used for Replication.
    Try to execute the following scripts:
    sqlplus /nolog
    connect / as sysdba
    @ORACLE_HOME/rdbms/admin/catrep.sql
    @ORACLE_HOME/rdbms/admin/utlrp.sql If it doesn't solve the problem then, I advise you to open a Service Request to My Oracle Support.
    Hope this help.
    Best regards,
    Jean-Valentin

  • Problem packaging epubs - Invalid UUID

    Hi All,
    We have some epubs that will not package. There are various messages but the epubs seem valid when checked on epub validators.
    error xmlns="http://ns.adobe.com/adept" data="E_PACK_ERROR http://<url>/packaging/Package Invalid UUID string: 9789525912173"
    error xmlns="http://ns.adobe.com/adept" data="E_PACK_ERROR http://<url>/packaging/Package Invalid UUID string: 9789525912159"
    error xmlns="http://ns.adobe.com/adept" data="E_PACK_ERROR http://<url>/packaging/Package Invalid UUID string: 9789525912128"
    error xmlns="http://ns.adobe.com/adept" data="E_PACK_ERROR http://<url>/packaging/Package Invalid UUID string: 9789525912166"
    etc
    The string that ACS is complaining about is the ISBN of the book. This could possibly be coming from the file name which is <ISBN>.epub.
    What does the Invalid UUID mean?
    If we change from epub to pdf the file works fine which suggests its something to do with the epub.
    Any help appreciated.

    The package command is similar to the following:
    Which as you can see doesn't contain a dc:identifier composite. Or do you mean there is an identifier within the epub file that I need to check?
    Thanks

  • Copy from Fact: "Invalid selection passed"

    Using OS5.0 SP2, has anyone received this error while running a standard copy from fact table package---"invalid selection passed"? Odd thing is, the copy package will work with the exact same parameters.
    I didn't find anything about this in the sap notes.

    Can you list out the source and destination settings you're using?  I cannot remember the last time I ran that particular package but can try and run it with similar setting in apshell.

  • RSPOR_SETUP  = Different ABAP and Java support packages.

    Hi all,
    We have an ECC 6.0 system with abap+java stacks. When we run the RSPOR_SETUP report we get this error:
    Different ABAP and Java support packages. Combination of support packages invalid
    And with some more clicking we find this:
    6. Compare version information of Java support package (com.sap.ip.bi classes) with ABAP support package (SAP BI)
       ABAP Support Package:                  13
       Java Support Package:                   0
    On the Java stack we see (among others) these components:
    sap.com        BI-IBC        7.00 SP12 (1000.7.00.12.0.20070509050058)
    sap.com        BI_MMR        7.00 SP12 (1000.7.00.12.0.20070507084106)
    sap.com        BI_UDI        7.00 SP12 (1000.7.00.12.0.20070507084125)
    sap.com        BI-BASE-S        7.00 SP12 (1000.7.00.12.11.20080324092518)
    sap.com        BI-WDALV        7.00 SP12 (1000.7.00.12.1.20071105133039)
    sap.com        BI-REPPLAN        7.00 SP12 (1000.7.00.12.3.20080104101916)
    So I believe all components are correctly installed.
    What are we doing wrong?

    Hello.
    Please be aware, that report RSPOR_SETUP should NOT be used with a Netweaver 04s system. This report has been replaced by the support desk tool. I request you to run the support desk tool as per note 937697 to check if there are any configuration issues in your system.You can resolve any red traffic lights that might be reported by the tool by following the corresponding actions suggested.
    I hope I can be helpful.
    Thanks,
    Walter Oliveira.

Maybe you are looking for