Duplicate SYS Objects after 11g Upgrade

Duplicate SYS Objects after 11g Upgrade

The Problem

After an 11g upgrade you see the following presented to you:
===================================================
Number of Duplicate Objects Owned by SYS and SYSTEM
===================================================
Counting duplicate objects ....
COUNT(1)
----------
4
=========================================
Duplicate Objects Owned by SYS and SYSTEM 
=========================================
Querying duplicate objects ....
OBJECT_NAME                      OBJECT_TYPE
-------------------------------  -------------------
AQ$_SCHEDULES                    TABLE
AQ$_SCHEDULES_PRIMARY            INDEX
DBMS_REPCAT_AUTH                 PACKAGE
DBMS_REPCAT_AUTH                 PACKAGE BODY

DOC>
DOC>########################################################
DOC>
DOC>If any objects found please follow below article.
DOC> Note 1030426.6 How to Clean Up Duplicate Objects Owned by SYS and SYSTEM schema
DOC> Read the Exceptions carefully before taking actions.
DOC>
DOC>########################################################

The Cause

Certain replication scripts correctly create objects with the same names in the SYS and SYSTEM schema accounts. Listed below are the  objects user by replication that should be created in both accounts. Do not drop these objects from the SYSTEM account if you are using replication. The following objects are duplicates that will show up (and  should not be removed) when running this script in 8.1.x and higher. Without replication installed:

INDEX            AQ$_SCHEDULES_PRIMARY
TABLE            AQ$_SCHEDULES

If replication is installed by running catrep.sql:

INDEX            AQ$_SCHEDULES_PRIMARY
PACKAGE          DBMS_REPCAT_AUTH
PACKAGE BODY     DBMS_REPCAT_AUTH
TABLE            AQ$_SCHEDULES

When the database is upgraded to 11g using the DBUA, the following duplicate objects are also created

OBJECT_NAME                OBJECT_TYPE
-------------------------- -------------
Help                       TABLE
Help_Topic_Seq             INDEX

The Solution

In my opinion it’s safest to leave all  of the items there, even if you aren’t using replication. You could drop the  objects but it would be safer to remove them correctly with an appropriate  script for the removal of the replication options.

Like it, share it...

Category: 11g