My Oracle Support Banner

After Upgrading to 11g, 21 Java Classs Are Invalid In The DMSYS Schema (Doc ID 821623.1)

Last updated on NOVEMBER 05, 2019

Applies to:

Oracle Data Mining - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.
Reviewed 12-Jul-2012.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material.  Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

After upgrading the RDBMS from 10.1 or 10.2 to RDBMS version 11g, the following objects are listed as INVALID. Recompilation (either individually or by using utlrp.sql script) does not resolve the issue.

List of INVALID objects:

Changes

An upgrade of the RDBMS has been performed from 10.1 or 10.2 to 11g.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.