CATPROC invalid in DBA_REGISTRY

DBAs,
When iam querying DBA_REGISTRY view in my Production Server, Its showing that,component CATPROC's status is invalid.
My Database is configured on Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production.
Can anybody tell me what will be the impact of this invalidation on my Database?
If iam running CATPROC again,should i need to run CATPATCH.SQL ? If so what all are the steps need to follow ?
Regards,
Raj

Metalink Note 300056.1 discuss methods to recompile your application, but its not discussing about invalidations of component like CATPROC.SQL

Similar Messages

  • Catproc invalid after catupgrd --- 11g Manual Upgrade

    Hi All,
    I hv upgraded database from 9i to 11g.
    After upgrade i checked
    select comp_id,status,version from dba_registry;
    CATPROC shows me INVALID.
    Waiting for your reply
    Thanks in advance

    user9161658 wrote:
    HI,
    I tried but now it shows me catproc,catalog invalid.
    i shutdown & startup with upgrade.
    ran @?/rdbms/admin/utlrp.sql
    even now it showing me
    catalog
    catproc invalid
    Regards,There should be a log file from the steps that you ran. That should point you to the original error. You'll likely need to correct that first before proceeding with rerunning your manual upgrade. Assuming that you have a support contract then the best advice would be to contact them. If you don't you essentially have 2 options now.
    1) Restore the backup you took of the 9i database, determine the cause of the upgrade failure, correct for it, and repeat the upgrade.
    2) determine the cause of the upgrade failure, correct for it and resume your current upgrade - likely means rerunning catupgrd.sql again.
    Niall Litchfield
    http://www.orawin.info/

  • Oracle Xml Database Invalid On Dba_registry in Oracle 9i

    Hi All,
    We are facing some issue with XML DB status of this component is showing INVALID in dba_registry
    and we try to validate it with below step
    connect / as sysdba
    execute dbms_regxdb.validatexdb;
    but it gives us below error
    SQL> execute dbms_regxdb.validatexdb;
    BEGIN dbms_regxdb.validatexdb; END;
    ERROR at line 1:
    ORA-06550: line 1, column 7:
    PLS-00201: identifier 'DBMS_REGXDB.VALIDATEXDB' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Thanks in advance
    Regards,
    Bhanu Chander

    Hello,
    If XMD DB is not currently used you can try to reinstall XML DB by executing the following scripts as sysdba:
    To deinstall:
    @OH/rdbms/admin/catnoqm.sql
    To reinstall:
    @?/rdbms/admin/catqm.sql
    @?/rdbms/admin/catxdbj.sql Before doing that you should set the following parameter as follows:
    shared_pool_size =150 MB
    java_pool_size =150 MB And, Turn on AUTO EXTEND on the XDB tablespace.
    For more details please look at the Notes *243554.1* of My Oracle Support.
    Hope it can help.
    Best regards,
    Jean-Valentin

  • DBMS_SQLPA - PACKAGE BODY - INVALID ?

    In list of SYS invalid objects I have DBMS_SQLPA - PACKAGE BODY with INVALID status…
    What could cause this problem if I don’t make it VALID?
    Someone else upgrade database from 10.2.0.1 to 10.2.0.4… Can this be the problem?
    Can I make this object VALID with this:
    SQL>sqlplus / as sysdba
    SQL>drop table plan_table;
    SQL>@?/rdbms/admin/utlxplan
    SQL>@?/rdbms/admin/prvtspao.plb
    SQL>@?/rdbms/admin/utlrp.sql
    Thanks!

    What could cause this problem if I don’t make it VALID?CATPROC will be INVALID in dba_registry. The steps you are describing are the ones descibed in MOS note ERROR IN CATUPGRD: ORA-00904 IN DBMS_SQLPA ID 565600.1*
    And utlrp recompile any remaining stored PL/SQL and Java code+
    step 15 of upgrade guide - http://download.oracle.com/docs/cd/B19306_01/server.102/b14238/upgrade.htm#CACGGHJC
    Nicolas.

  • Database registry status invalid

    hi
    I got status of catproc as invalid in my dba_registry.
    I have tried with (DBMS_REGISTRY_SYS.VALIDATE_CATPROC)
    procedure but not posative.
    I have also used catproc.sql script but agian no effect.
    Is there any way to make it valid?

    Pl post details of OS and database versions. Have you opened an SR ? Pl see if these MOS Docs can help
    560893.1 - Oracle Xml Database Invalid On Dba_registry
    1105245.1 - XDB Is INVALID In DBA_REGISTRY After Having Revoked Privileges: What Privileges Are Needed?
    753041.1 - How To Diagnose Components With NON VALID Status In DBA_REGISTRY After an Upgrade
    HTH
    Srini

  • 9.2.0.7 Catpatch.sql hangs

    Windows 2000
    9.2.0.1
    I've applied the 9.2.0.7 to my db successfully, but when I run catpatch.sql in migrate mode, the system gets to a certain point and hangs. I thought maybe since the db was a 15G db restored from a cold backup that maybe it was a db size issue, but I let it run for well over 30 hours and no dice. If I reboot the server to see if it processed, this is what I get:
    SQL> column comp_id format a15
    SQL> column status format a10
    SQL> column version format a10
    SQL> column comp_name format a35
    SQL> select comp_id, status, version, comp_name from dba_registry order by 1;
    COMP_ID STATUS VERSION COMP_NAME
    AMD INVALID 9.2.0.1.0 OLAP Catalog
    APS LOADED 9.2.0.1.0 OLAP Analytic Workspace
    CATALOG VALID 9.2.0.1.0 Oracle9i Catalog Views
    CATJAVA VALID 9.2.0.1.0 Oracle9i Java Packages
    CATPROC INVALID 9.2.0.1.0 Oracle9i Packages and Types
    CONTEXT VALID 9.2.0.1.0 Oracle Text
    JAVAVM VALID 9.2.0.1.0 JServer JAVA Virtual Machine
    ODM LOADED 9.2.0.1.0 Oracle Data Mining
    ORDIM LOADED 9.2.0.1.0 Oracle interMedia
    OWM VALID 9.2.0.1.0 Oracle Workspace Manager
    SDO LOADED 9.2.0.1.0 Spatial
    COMP_ID STATUS VERSION COMP_NAME
    WK VALID 9.2.0.1.0 Oracle Ultra Search
    XDB INVALID 9.2.0.1.0 Oracle XML Database
    XML VALID 9.2.0.2.0 Oracle XDK for Java
    XOQ LOADED 9.2.0.1.0 Oracle OLAP API
    15 rows selected.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Disabled
    Archive destination C:\oracle\ora92\RDBMS
    Oldest online log sequence 1984
    Next log sequence to archive 1984
    Current log sequence 1986
    SQL> show parameter shared_pool_size;
    NAME TYPE VALUE
    shared_pool_size big integer 50331648
    SQL> show parameter java_pool_size;
    NAME TYPE VALUE
    java_pool_size big integer 33554432
    SQL> show parameter job_queue_processes;
    NAME TYPE VALUE
    job_queue_processes integer 10
    However, if I create a new empty 9.2.0.1 db, I can patch that to 9.2.0.7 and run catpatch with no problems. I've upgraded before with no issues, so I don't know what the problem is now.
    Thanks!!!

    I don't follow you. Your db was currently in archivelog mode, but not in automatic. Which seems to implies hang issue.
    If your db is not in archivelog mode at all, so, you don't have to put it in archivelog mode.
    Nicolas.

  • Data pump: by using dbms_datapump

    I wrote a pl/sql procedure that compiles and there is no error. But when I execute the procedure, I got follwing error
    ERROR at line 1:
    ORA-31623: a job is not attached to this session via the specified handle
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 911
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 4710
    ORA-06512: at "DO_EXPORT.RCAT_EXPDP", line 59
    ORA-06512: at line 1
    I went to metalink and there I found that if there is any compnent invalid in dba_registry then this error will occur. I found that spatial is invalid in dba_registry. I run utlrp several times, but still spatial is in-valid. Does any one one work around this so that I can use pl/sql code which i wrote.
    thanks

    I also got this error when I run this job in a database where all components are valid.
    Source code which I am using is this.
    CREATE OR REPLACE procedure DO_EXPORT.rcat_expdp (
    strJobName in varchar2 , strDumpFileName in varchar2,
    strLogFileName in varchar2, strDirectory in varchar2,
    strSchemaName in varchar2)
    is
    d1 number;
    v_ind number; v_sts ku$_Status; v_le ku$_LogEntry;begin
    begin
    dbms_output.put_line ('in code');
    d1 := dbms_datapump.open (
    operation => 'EXPORT',
    job_mode => 'SCHEMA',
    job_name => strJobName,
    version => 'COMPATIBLE');
    end;
    dbms_output.put_line ('handle created');
    begin
    dbms_datapump.add_file(handle => d1,
    filename => strDumpFileName,
    directory => strDirectory,
    filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_DUMP_FILE);
    end;
    dbms_output.put_line ('dmup file');
    begin
    dbms_datapump.add_file(handle => d1,
    filename => strLogFileName,
    directory => strDirectory,
    filetype => DBMS_DATAPUMP.KU$_FILE_TYPE_LOG_FILE);
    end;
    dbms_output.put_line ('log file');
    begin
    dbms_datapump.metadata_filter(handle => d1,
    name => 'SCHEMA_EXPR',
    value => 'IN ( '|| '''strSchemaName''' || ')');
    end;
    dbms_output.put_line ('schema added');
    begin
    dbms_datapump.start_job(handle => d1, skip_current => 0);
    end;
    dbms_output.put_line ('job started');
    begin
    dbms_datapump.detach(handle => d1);
    end;
    dbms_output.put_line('Export job submitted successfully.');
    exception
    when others then
    v_sts:=dbms_datapump.get_status(d1,dbms_datapump.ku$_status_job_error,0);
    v_le := v_sts.error;
    if v_le is not null then
    v_ind := v_le.FIRST;
    while v_ind is not null loop
    dbms_output.put_line(v_le(v_ind).LogText);
    v_ind := v_le.NEXT(v_ind);
    end loop;
    end if;
    begin dbms_datapump.stop_job(handle => d1); end;
    end;
    /

  • Invalid objects after running catalog.sql and catproc.sql

    I have a db 10.1.0.3.0. standard edition with the 10.1.0.4.0 patch installed.
    After executing catalog.sql and catproc.sql the database contains lots of invalid objects in the public, olapsys and xdb schemas.
    I have executed utlrp.sql, the script completes successfully, but lots of invalid objects remain.
    Does anyone know how to fix this?
    Thanks in advance.
    Below is the output of
    select owner, object_name, object_type from dba_objects where status like 'INVALID';
    OWNER OBJECT_NAME OBJECT_TYPE
    XDB DBMS_XDBUTIL_INT PACKAGE
    XDB SETMODFLG PROCEDURE
    XDB DBMS_XDBZ0 PACKAGE BODY
    XDB DBMS_XDBUTIL_INT PACKAGE BODY
    PUBLIC DBMS_XDBUTIL_INT SYNONYM
    XDB XDB$PATCHUPSCHEMA PROCEDURE
    OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
    PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
    PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
    OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
    PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBES VIEW
    PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
    OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
    PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
    PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
    OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
    PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
    OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
    PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
    OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
    OLAPSYS DBMS_AWM PACKAGE BODY
    OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY

    This note explains 80% of the problem: 42 invalid objects are normal, I have 52 invalid objects.
    I have re-executed the catpatch.sql script, I couldn't find any errors in the output. At the end Oracle Intermedia and Oracle Expression Filter remain invalid.
    last lines of catpatch.sql output:
    COMP_NAME STATUS VERSION
    OLAP Analytic Workspace OPTION OFF 10.1.0.3.0
    Oracle OLAP API OPTION OFF 10.1.0.3.0
    Oracle Database Catalog Views VALID 10.1.0.4.0
    Oracle Database Packages and Types VALID 10.1.0.4.0
    JServer JAVA Virtual Machine VALID 10.1.0.4.0
    Oracle XDK VALID 10.1.0.4.0
    Oracle Database Java Packages VALID 10.1.0.4.0
    Oracle XML Database VALID 10.1.0.4.0
    Oracle interMedia INVALID 10.1.0.4.0
    Oracle Text VALID 10.1.0.4.0
    Oracle Ultra Search VALID 10.1.0.4.0
    Oracle Expression Filter INVALID 10.1.0.4.0
    Oracle Enterprise Manager VALID 10.1.0.4.0
    Oracle Workspace Manager VALID 10.1.0.2.0
    Oracle Data Mining OPTION OFF 10.1.0.3.0
    OLAP Catalog OPTION OFF 10.1.0.3.0
    Spatial OPTION OFF 10.1.0.3.0
    SQL> select owner, object_name, object_type from dba_objects where status like 'INVALID';
    OWNER OBJECT_NAME OBJECT_TYPE
    WK_TEST BIN$9oUB6zbaOP/gMCzPA4J5+w==$0 TRIGGER
    OLAPSYS ALL$OLAP2_AW_CATALOGS VIEW
    PUBLIC ALL_OLAP2_AW_CATALOGS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CATALOG_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CATALOG_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ SYNONYM
    OLAPSYS ALL$OLAP2_AW_PHYS_OBJ_PROP VIEW
    PUBLIC ALL_OLAP2_AW_PHYS_OBJ_PROP SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIMENSIONS VIEW
    PUBLIC ALL_OLAP2_AW_DIMENSIONS SYNONYM
    OLAPSYS ALL$OLAP2_AW_ATTRIBUTES VIEW
    PUBLIC ALL_OLAP2_AW_ATTRIBUTES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBES VIEW
    PUBLIC ALL_OLAP2_AW_CUBES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_DIM_USES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_DIM_USES SYNONYM
    OLAPSYS ALL$AW_DIM_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_DIM_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_VIEWS VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_VIEWS SYNONYM
    OLAPSYS ALL$AW_CUBE_ENABLED_HIERCOMBO VIEW
    PUBLIC ALL_AW_CUBE_ENABLED_HIERCOMBO SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_LEVELS VIEW
    PUBLIC ALL_OLAP2_AW_DIM_LEVELS SYNONYM
    OLAPSYS ALL$OLAP2_AW_DIM_HIER_LVL_ORD VIEW
    PUBLIC ALL_OLAP2_AW_DIM_HIER_LVL_ORD SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_MEASURES VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_SPECS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_SPECS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_MEAS VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_MEAS SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_LVL VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_LVL SYNONYM
    OLAPSYS ALL$OLAP2_AW_CUBE_AGG_OP VIEW
    PUBLIC ALL_OLAP2_AW_CUBE_AGG_OP SYNONYM
    OLAPSYS MRAC_OLAP2_AW_DIMENSIONS_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBES_V VIEW
    OLAPSYS MRAC_OLAP2_AW_CUBE_MEASURES_V VIEW
    PUBLIC MRV_OLAP2_AW_DIMENSIONS SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBES SYNONYM
    PUBLIC MRV_OLAP2_AW_CUBE_MEASURES SYNONYM
    OLAPSYS CWM2_OLAP_METADATA_REFRESH PACKAGE BODY
    OLAPSYS OLAP_SYS_AW_ACCESS_DIM_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ACCESS_CUBE_VIEW VIEW
    OLAPSYS OLAP_SYS_AW_ENABLE_ACCESS_VIEW VIEW
    PUBLIC OLAP_SYS_AW_ACCESS_CUBE_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ACCESS_DIM_VIEW SYNONYM
    PUBLIC OLAP_SYS_AW_ENABLE_ACCESS_VIEW SYNONYM
    OLAPSYS CWM2_OLAP_OLAPAPI_ENABLE PACKAGE BODY
    OLAPSYS DBMS_AWM PACKAGE BODY
    OLAPSYS CWM2_OLAP_CUBE PACKAGE BODY
    53 rows selected.

  • OID is INVALID when query dba_registry

    Hi Everyone.
    I have a problem with OAS in Development environment... when I query dba_registry (as follows) I got the following output:
    SQL> l
    1 select comp_id, comp_name, version, status, modified
    2 from dba_registry
    3* where status = 'INVALID'
    SQL> /
    COMP_ID COMP_NAME VERSION STATUS MODIFIED
    OID Oracle Internet Directory 10.1.2.3.0 ; INVALID 07-AUG-2008 02:11:20
    I also ran @?/rdbms/admin/utlrp.sql and no errors were found
    SQL> @?/rdbms/admin/utlrp
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_BGN 2009-09-02 11:15:26
    PL/SQL procedure successfully completed.
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_END 2009-09-02 11:16:12
    PL/SQL procedure successfully completed.
    Invoking Ultra Search Install/Upgrade validation procedure VALIDATE_WK
    Ultra Search VALIDATE_WK done with no error
    PL/SQL procedure successfully completed.
    And also check opmctl status, and OID process is ALIVE:
    --> opmnctl status
    Processes in Instance: INSTANCE.server.domain
    ------------------------------------------------+---------
    ias-component | process-type | pid | status
    ------------------------------------------------+---------
    LogLoader | logloaderd | N/A | Down
    dcm-daemon | dcm-daemon | 2505 | Alive
    OC4J | OC4J_SECURITY | 7134 | Alive
    HTTP_Server | HTTP_Server | 7100 | Alive
    OID | OID | 7104 | Alive
    DSA | DSA | N/A | Down
    Do you have any idea on how to solve OID INVALID status???
    I'd really appreciate your time and help

    Check if any ODS components are invalid
    # Review $ORACLE_HOME/ldap/admin/LOGS/ldapupgrade.log
    Check for any errors or messages.
    - If any significant problems are seen, correct them and rerun oidiugrd.sql
    - If no problems are found, or invalid status persists after rerunning, continue with the following steps:
    # Check the ODS schema for invalid objects and correct as necessary
    % sqlplus / as sysdba
    SQL> select owner,object_name,object_type from dba_objects
    2> where owner='ODS' and status='INVALID';
    # Cut the final validation portion of oidiugrd.sql and run it by itself:
    alter session set current_schema = SYS;
    execute DBMS_IAS_VERSION.SET_COMPONENT_UPGRADED(COMPONENT_ID=>'OID');
    declare
    rc integer;
    begin
    rc := ods.ldapUpgUtls.validateODS();
    if rc = 0 then
    DBMS_IAS_VERSION.SET_COMPONENT_VALID(COMPONENT_ID=>'OID');
    else
    DBMS_IAS_VERSION.SET_COMPONENT_INVALID(COMPONENT_ID=>'OID');
    end if;
    end;
    -SRP

  • Component XML database is in INVALID state, while quering dba_registry,

    How to make the component XML valid

    Did You performed recently any upgrade?
    Was upgrade sucessfull? No errors?
    Please reffer to metalink note 243554.1 - How to Deinstall and Reinstall XML Database (XDB).
    If You are using XDB, then You will have to reinstall it.

  • Upgrade oracle 9.06.0 to 10.0.4.0  with invalid sys objs  in window

    Hi Friends,
    We made a cold copy and upgrade database to 10.0.4.0 from 9.0.6.0 in 32 bit window 2003.
    I just find lots of invalid objects in DB even I run these codes (utlrp.sql ,utlprp.sql or EXEC DBMS_UTILITY.compile_schema).
    The invalid objects are still in DB as
    SQL> select owner, OBJECT_TYPE , count(*)from all_objects
    2 where status='INVALID'
    3 group by owner, OBJECT_TYPE
    4 order by owner, OBJECT_TYPE ;
    OWNER OBJECT_TYPE COUNT(*)
    ODM VIEW 1
    OLAPSYS FUNCTION 1
    OLAPSYS PACKAGE 49
    OLAPSYS PACKAGE BODY 47
    OLAPSYS TRIGGER 48
    OLAPSYS VIEW 122
    PUBLIC SYNONYM 146
    OWNER OBJECT_TYPE COUNT(*)
    QS_ADM PACKAGE BODY 1
    SYS PACKAGE BODY 1
    WKSYS FUNCTION 3
    WKSYS PACKAGE 19
    WKSYS PACKAGE BODY 17
    WKSYS PROCEDURE 3
    WKSYS TRIGGER 23
    WKSYS VIEW 2
    based on above SQL results, how to fix this issue?
    Thanks
    JIm

    Hi Friends,
    I check db_registory and all is valid.
    SQL> select COMP_ID , COMP_NAME, VERSION ,STATUS ,
    2 MODIFIED ,NAMESPACE,CONTROL, SCHEMA ,PROCEDURE , STARTUP , PARENT_ID , OTHER_SCHEMAS
    3 from dba_registry;
    COMP_ID COMP_NAME VERSION STATUS
    EM Oracle Enterprise Manager 10.2.0.4.0 VALID
    SDO Spatial 10.2.0.4.0 VALID
    ORDIM Oracle interMedia 10.2.0.4.0 VALID
    AMD OLAP Catalog 10.2.0.4.0 VALID
    XDB Oracle XML Database 10.2.0.4.0 VALID
    CONTEXT Oracle Text 10.2.0.4.0 VALID
    EXF Oracle Expression Filter 10.2.0.4.0 VALID
    RUL Oracle Rules Manager 10.2.0.4.0 VALID
    OWM Oracle Workspace Manager 10.2.0.4.3 VALID
    ODM Oracle Data Mining 10.2.0.4.0 VALID
    CATALOG Oracle Database Catalog Views 10.2.0.4.0 VALID
    COMP_ID COMP_NAME VERSION STATUS
    CATPROC Oracle Database Packages and Types 10.2.0.4.0 VALID
    JAVAVM JServer JAVA Virtual Machine 10.2.0.4.0 VALID
    XML Oracle XDK 10.2.0.4.0 VALID
    CATJAVA Oracle Database Java Packages 10.2.0.4.0 VALID
    APS OLAP Analytic Workspace 10.2.0.4.0 VALID
    XOQ Oracle OLAP API 10.2.0.4.0 VALID
    17 rows selected.
    So what should I need to do for these invalid objects?
    Thanks
    JIM

  • INVALID Oracle Database Catalog Views 10.1.0.5.0

    I am trying to resolve an INVALID state on the Oracle Database Catalog Views component of an Oracle 10.1.0.5.0 database.
    I was trying to resolve an issue with Data Pump by running: catalog.sql, catproc.sql and catexp.sql as SYS to add the EXFSYS schema.
    Doing this made the Oracle Database Catalog Views go INVALID.
    I have 61 invalid objects after running utlrp.sql, 26 of these are owned by SYS.
    Anyone know of a good way to resolve this issue or a metalink note, other link they can guide me to? I would like to avoid having to rebuild the database.
    Thanks!!!

    Anyway .... this is how to resolve this issue:
    Note: Ensure that the SHARED_POOL_SIZE and JAVA_POOL_SIZE parameters are set to at least 150M each, and then restart the instance in MIGRATE mode and execute catpatch as detailed in the following steps:
    Before starting this process, notify users of database that the database will be unavailable for approximately 2 hours. Proceed with proper notification procedures before shutting down the database.
    1.     sqlplus /nolog
    2.     spool $ORACLE_HOME/rdbms/log/catpatch_ddmmyy.log
    3.     connect / as sysdba
    4.     alter system set shared_pool_size = 200M scope=spfile; (if necessary)
    5.     alter system set java_pool_size = 150M scope=spfile; (if necessary)
    6.     shutdown immediate
    7.     startup migrate
    8.     @$ORACLE_HOME/rdbms/admin/catpatch.sql
    9.     spool off
    10.     shutdown immediate
    11.     startup
    12.     (validate): select comp_name,version,status from dba_registry;

  • Invalid PUBLIC objects in the database

    Hi,
    I have a 11.1.0.7.10 database running on a Linux EL5 machine.
    OWNER           OBJECT_NAME                    OBJECT_TYPE
    SYS             INTERACTIONEXECUTE             FUNCTION
    SYS             XOQ_VALIDATE                   PROCEDURE
    PUBLIC          ALL_AW_LOAD_DIMENSIONS         SYNONYM
    PUBLIC          ALL_AW_LOAD_DIM_FILTERS        SYNONYM
    PUBLIC          ALL_AW_LOAD_CUBE_FILTERS       SYNONYM
    PUBLIC          ALL_AW_LOAD_CUBE_MEASURES      SYNONYM
    PUBLIC          ALL_AW_LOAD_DIM_PARMS          SYNONYM
    PUBLIC          ALL_AW_LOAD_CUBE_DIMS          SYNONYM
    PUBLIC          ALL_AW_LOAD_CUBES              SYNONYM
    PUBLIC          ALL_AW_LOAD_CUBE_PARMS         SYNONYM
    PUBLIC          ALL_LOAD_CUBE_SEGWIDTH         SYNONYM
    PUBLIC          ALL_AW_CUBE_AGG_PLANS          SYNONYM
    PUBLIC          ALL_AW_CUBE_AGG_MEASURES       SYNONYM
    PUBLIC          ALL_AW_CUBE_AGG_LEVELS         SYNONYM
    PUBLIC          ALL_AW_DIM_ENABLED_VIEWS       SYNONYM
    PUBLIC          ALL_AW_CUBE_ENABLED_VIEWS      SYNONYM
    PUBLIC          ALL_AW_CUBE_ENABLED_HIERCOMBO  SYNONYM
    PUBLIC          DBMS_AWM                       SYNONYM
    SQL> alter public synonym ALL_AW_LOAD_DIMENSIONS compile;
    alter public synonym ALL_AW_LOAD_DIMENSIONS compile
    ERROR at line 1:
    ORA-00980: synonym translation is no longer validWhen I try compiling the synonyms, I get the above error. Could someone please help me out here as to what needs to be done to get these invalid synonyms fixed?
    Edited by: 877343 on Mar 5, 2012 2:13 AM

    MYCSMR3 > select TABLE_OWNER,TABLE_NAME,SYNONYM_NAME from dba_synonyms where SYNONYM_NAME like 'ALL_AW_%';
    TABLE_OWNER                                        TABLE_NAME                     SYNONYM_NAME
    OLAPSYS                                            ALL$AW_CUBE_AGG_LEVELS         ALL_AW_CUBE_AGG_LEVELS
    OLAPSYS                                            ALL$AW_CUBE_AGG_MEASURES       ALL_AW_CUBE_AGG_MEASURES
    OLAPSYS                                            ALL$AW_CUBE_AGG_PLANS          ALL_AW_CUBE_AGG_PLANS
    OLAPSYS                                            ALL$AW_CUBE_ENABLED_HIERCOMBO  ALL_AW_CUBE_ENABLED_HIERCOMBO
    OLAPSYS                                            ALL$AW_CUBE_ENABLED_VIEWS      ALL_AW_CUBE_ENABLED_VIEWS
    OLAPSYS                                            ALL$AW_DIM_ENABLED_VIEWS       ALL_AW_DIM_ENABLED_VIEWS
    OLAPSYS                                            ALL$AW_LOAD_CUBES              ALL_AW_LOAD_CUBES
    OLAPSYS                                            ALL$AW_LOAD_CUBE_DIMS          ALL_AW_LOAD_CUBE_DIMS
    OLAPSYS                                            ALL$AW_LOAD_CUBE_FILT          ALL_AW_LOAD_CUBE_FILTERS
    OLAPSYS                                            ALL$AW_LOAD_CUBE_MEAS          ALL_AW_LOAD_CUBE_MEASURES
    OLAPSYS                                            ALL$AW_LOAD_CUBE_PARM          ALL_AW_LOAD_CUBE_PARMS
    OLAPSYS                                            ALL$AW_LOAD_DIM                ALL_AW_LOAD_DIMENSIONS
    OLAPSYS                                            ALL$AW_LOAD_DIM_FILT           ALL_AW_LOAD_DIM_FILTERS
    OLAPSYS                                            ALL$AW_LOAD_DIM_PARM           ALL_AW_LOAD_DIM_PARMS
    OLAPSYS                                            DBMS_AWM                       DBMS_AWM
    OLAPSYS                                            ALL$AW_LOAD_CUBE_SEGWIDTH      ALL_LOAD_CUBE_SEGWIDTHWhen I checked the dba_registry, I found that couple of components are showing the status as REMOVED. Could that be a reason for this issue? And if yes, how do I get that component back to VALID state?
    SQL> select comp_id, comp_name, version, status from dba_registry;
    COMP_ID              COMP_NAME                                VERSION              STATUS
    OWB                  OWB                                      11.1.0.7.0           VALID
    APEX                 Oracle Application Express               3.0.1.00.12          VALID
    EM                   Oracle Enterprise Manager                11.1.0.7.0           VALID
    WK                   Oracle Ultra Search                      11.1.0.7.0           VALID
    SDO                  Spatial                                  11.1.0.7.0           VALID
    ORDIM                Oracle Multimedia                        11.1.0.7.0           VALID
    XDB                  Oracle XML Database                      11.1.0.7.0           VALID
    CONTEXT              Oracle Text                              11.1.0.7.0           VALID
    EXF                  Oracle Expression Filter                 11.1.0.7.0           VALID
    RUL                  Oracle Rules Manager                     11.1.0.7.0           VALID
    OWM                  Oracle Workspace Manager                 11.1.0.7.0           VALID
    CATALOG              Oracle Database Catalog Views            11.1.0.7.0           VALID
    CATPROC              Oracle Database Packages and Types       11.1.0.7.0           VALID
    JAVAVM               JServer JAVA Virtual Machine             11.1.0.7.0           VALID
    XML                  Oracle XDK                               11.1.0.7.0           VALID
    CATJAVA              Oracle Database Java Packages            11.1.0.7.0           VALID
    APS                  OLAP Analytic Workspace                  11.1.0.7.0           REMOVED
    XOQ                  Oracle OLAP API                          11.1.0.7.0           REMOVED
    RAC                  Oracle Real Application Clusters         11.1.0.7.0           VALID

  • PLS-00905: object SYS.DBMS_DATAPUMP is invalid

    环境如下：
    OS：AIX 6.1
    DB:11.2.0.2
    数据库被同事执行了如下操作：
    connect / as sysdba;
    SQL> startup upgrade;
    SQL> @catalog.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> @catproc.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> @utlrp.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> shutdown immediate;
    SQL> startup;
    在执行catalog.sql时发现大量错误就ctrl+C，强行中断了。现在数据库重新启动后发现如下问题：
    1、expdp进行备份报错
    UDE-06550: operation generated ORACLE error 6550
    ORA-06550: line 1, column 104:
    PLS-00905: object SYS.DBMS_DATAPUMP is invalid
    ORA-06550: line 1, column 100:
    PL/SQL: Statement ignored
    ORA-06550: line 1, column 206:
    PLS-00905: object SYS.DBMS_DATAPUMP is invalid
    ORA-06550: line 1, column 202:
    PL/SQL: Statement ignored
    alter package SYS.DBMS_DATAPUMP compile;
    报错
    2、DBA_REGISTERY视图失效
    SQL> select comp_name, version, status from dba_registry;
    ORA-04063: package body "SYS.DBMS_REGISTRY" has errors
    3、数据库可以的基本读写功能还正常
    可以正常启动、关闭，alert文件在关闭、启动过程无异常
    数据库可以正常的支撑业务系统，ERP系统
    请高手指点下解决办法。
    想重新执行catalog.sql 、catproc.sql 、utlrp.sql 一次脚本，会不会变得更糗呢。

    I'm truly grateful for your help, my Englist is poor.
    The system environment is listed as follows:
    OS：AIX 6.1
    DB:11.2.0.2
    My Oracle database has been performed those script:
    connect / as sysdba;
    SQL> startup upgrade;
    SQL> @catalog.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> @catproc.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> @utlrp.sql <--------------$ORACLE_HOME/rdbms/admin
    SQL> shutdown immediate;
    SQL> startup;
    When catalog.sql was going, lots of error printed, then dba press "CTRL+C".
    After restart,the database became abnoral.
    1、expdp command error
    UDE-06550: operation generated ORACLE error 6550
    ORA-06550: line 1, column 104:
    PLS-00905: object SYS.DBMS_DATAPUMP is invalid
    ORA-06550: line 1, column 100:
    PL/SQL: Statement ignored
    ORA-06550: line 1, column 206:
    PLS-00905: object SYS.DBMS_DATAPUMP is invalid
    ORA-06550: line 1, column 202:
    PL/SQL: Statement ignored
    alter package SYS.DBMS_DATAPUMP compile;
    this also return warnnig
    2、DBA_REGISTERY became invalid
    SQL> select comp_name, version, status from dba_registry;
    ORA-04063: package body "SYS.DBMS_REGISTRY" has errors
    3、the app is running normally，and Oracle database can be manipulated to read and write.

  • SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID'; = 39 rows .

    We just applied "SAP Bundle Patch 10.2.0.4.5 - 201010" in our development system.
    We completed all the post installation activities.
    In tail end - when we execute subjected command, 39 rows returned.
    Very First --- May we understand  What is the negative impact on Oracle system?
    Secondly -- Do we need to make these rows to "ZERO" is must ?
    Finally -  How to make them to "ZERO"
    2 lines expert advise...will enable us to move forward.
    Rgds
    ==========
    COMMAND
    ==========
    SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';
    OBJECT_NAME
    LOGMNR_KRVRDLUID3
    DBMS_SQLTCB_INTERNAL
    DBMS_LOGMNR_FFVTOLOGMNRT
    DBMS_LOGMNR_OCTOLOGMNRT
    DBMS_RULE_EXP_UTL
    DBMS_LOGSTDBY
    DBMS_AW_EXP
    DBMS_SNAP_INTERNAL
    DBMSOBJG_DP
    DBMS_REPCAT_EXP
    DBMS_STREAMS_TBS_INT_INVOK
    DBMS_FILE_GROUP_UTL
    DBMS_FILE_GROUP_UTL_INVOK
    DBMS_STREAMS_MT
    DBMS_LOGREP_EXP
    DBMS_LOGREP_IMP
    DBMS_STREAMS_RPC
    DBMS_STREAMS_DATAPUMP
    DBMS_STREAMS_DATAPUMP_UTIL
    DBMS_STREAMS_TBS_INT
    DBMS_STREAMS_TBS_INT_INVOK
    DBMS_STREAMS_TABLESPACE_ADM
    DBMS_FILE_GROUP_UTL
    DBMS_FILE_GROUP_UTL_INVOK
    DBMS_FILE_GROUP
    DBMS_FILE_GROUP_INTERNAL_INVOK
    DBMS_FILE_GROUP_EXP
    DBMS_FILE_GROUP_IMP_INTERNAL
    DBMS_REDEFINITION
    DBMS_CDC_DPUTIL
    LOGMNR_KRVRDREPDICT3
    DBMS_CDC_DPUTIL
    DBMS_CDC_EXPDP
    DBMS_CDC_EXPVDP
    DBMS_CDC_IMPDP
    DBMS_SCHEMA_COPY
    UTL_RECOMP
    DBMS_SQLTUNE_INTERNAL
    DBMS_CDC_DPUTIL
    39 rows selected.
    SQL>
    ==========

    Hi,
    there has been an issue with an earlier set of bugfixes or an older CPU patch.
    It did invalidate the catproc component.
    Check:   select comp_id,status, version from dba_registry;
    if CATPROC is invalid, shutdown and startup your DB.
    run
    @?/rdbms/admin/catproc.sql
    it can run between 10 and 25 minutes depending on horse powers.
    Check again:   select comp_id,status, version from dba_registry;
    CATPROC should now be valid.
    If yes run utlrp.sql again and your errors will be gone.
    If not, your issue is something else.
    Volker

Maybe you are looking for