Invalid Objects in DMSYS after EBS Database Upgrade (Doc ID 731454.1)

Last updated on FEBRUARY 02, 2017

Applies to:

Oracle Data Mining - Version 10.2.0.1 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
Checked for relevance on 15-Jan-2013.


Symptoms

Querying the dba_registry show Data Mining being invalid:

SQL> select COMP_ID,SCHEMA,COMP_NAME COMPONENT,VERSION,STATUS from dba_registry where schema = 'DMSYS';


COMP_ID  SCHEMA    COMPONENT                      VERSION                      STATUS
=======================================================================================
ODM      DMSYS     Oracle Data Mining          10.2.0.3.0                      INVALID



The following query returns :

SQL> select object_name,object_type,owner from all_objects where status<>'VALID' and owner='DMSYS';


OWNER       OBJECT_NAME                   OBJECT_TYPE
--------    -------------------------     ------------------------------ 
DMSYS          OLAP_API_SESSION_INIT      PACKAGE BODY
DMSYS          DBMS_XSOQ                  PACKAGE BODY
DMSYS          DBMS_XSOQ_UTIL             PACKAGE BODY
DMSYS          APS_VALIDATE               PROCEDURE
DMSYS          XOQ_VALIDATE               PROCEDURE


Changes

The database has been upgraded/migrated from Oracle 9i to 10g Release 2 (10.2.0.3).
Data Mining and Olap options have been installed following the Interoperability <Note 362203.1> : Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0) (Section 1 - Chapter 19 : install ORACLE DATA MINING and OLAP)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms