Any suggestion to how to get rid of the invalid objects.
=======================================
SQLWKS> select owner,object_name,object_type from dba_objects
2> where status = 'INVALID';
OWNER OBJECT_NAME
OBJECT_TYPE
------------------------------ ------------------------------
-------------
SYS ALL_ADMINCATLOG
VIEW
SYS ALL_ADMINOBJECTS
VIEW
SYS ALL_ADMINREGSNAPS
VIEW
SYS ALL_ADMINRESOLUTION
VIEW
SYS ALL_REPCATLOG
VIEW
SYS ALL_REPDDL
VIEW
SYS ALL_REPGENERATED
VIEW
SYS ALL_REPKEY_COLUMNS
VIEW
SYS ALL_REPOBJECT
VIEW
SYS ALL_REPPROP
VIEW
SYS DBMSOBJG
PACKAGE BODY
SYS DBMSOBJGWRAPPER
PACKAGE BODY
SYS DBMS_DEFERGEN_UTIL
PACKAGE BODY
SYS DBMS_OFFLINE_OG
PACKAGE BODY
SYS DBMS_OFFLINE_SNAPSHOT
PACKAGE BODY
SYS DBMS_RECTIFIER_DIFF
PACKAGE BODY
SYS DBMS_RECTIFIER_FRIENDS
PACKAGE BODY
SYS DBMS_REPCAT
PACKAGE BODY
SYS DBMS_REPCAT_AUTH
PACKAGE BODY
SYS DBMS_REPCAT_CONF
PACKAGE
SYS DBMS_REPCAT_CONF
PACKAGE BODY
SYS DBMS_REPCAT_MAS
PACKAGE BODY
SYS DBMS_REPCAT_SNA
PACKAGE BODY
SYS DBMS_REPCAT_SNA_UTL
PACKAGE BODY
SYS DBMS_REPCAT_UTL
PACKAGE BODY
SYS DBMS_REPCAT_UTL2
PACKAGE BODY
SYS DBMS_REPCAT_UTL3
PACKAGE BODY
SYS DBMS_UTILITY
PACKAGE BODY
SYSTEM ROSATTRIBS VIEW
SYSTEM ROSSTRUCTS VIEW
==========================================
Please reply directly to my e-mail .
Thanks ..
=========================
Pinchas Nisenson
Data Base Manager
University (of Calgary) Computing Services
E-mail: nise...@acs.ucalgary.ca
Phone: (403) 220-4447
Fax: (403) 282-9361
Try running catproc.sql. It is located in /ORACLE_HOME/rdbms/admin
directory. But before running this script, make sure that STANDARD.sql and
DBMSSTDX.sql first to avoid errrors.
Noly
Pinchas Nisenson <nise...@acs.ucalgary.ca> wrote in article
<61bo72$n...@ds2.acs.ucalgary.ca>...
This happen to me before with replication scripts.
I ran create scripts. Had errors. didn't compile. Re-ran creation scripts. Had
more errors.
Ran the remove scripts and then ran create scripts and everything
was fine.
> I just finished building a database. After checking for invalid
> objects I found dbms that DBMS_SNAPSHOT is invalid.
> Looked it up it said that dbmssnap.sql and prvtsnap.plb have to
> be run.
> I did so and got more errors. That I decided to rerun catalog.sql
> + catdbsyn.sql
> hoping to get rid of errors alas I got even more invalid objects.
I had exactly the same problem. It is a known bug, here is the solution:
Article-ID: <PrSol:2077468.6>
For-Problem: <Pr:1030033.6>
Subject: YOU HAVE HIT BUG 389795, SIMPLE WORKAROUND AVAILABLE
Circulation: ** PUBLIC **
Affected-Platforms: - Generic: not platform specific
Affected-Products: Oracle Server - Enterprise Edition V7
Solution Description:
=====================
You have encountered Bug 389795. You need to verify your resources and
recompile the package.
Solution Explanation:
=====================
This is bug 389795. The issue exists in version 7.2.X and 7.3.X.The bug is
currently being resolved.
Check the value of the shared_pool_size parameter.
Often having a shared_pool_size of 10M or lower can cause this.
Shared_pool_size should be 30M or higher in a replicated
environment. A simple workaround will solve the problem.
Please do the following:
svrmgr> CONNECT INTERNAL
svrmgr> ALTER PACKAGE DBMS_SNAPSHOT COMPILE BODY;
The you should rerun the above query again to check for INVALID objects.
All objects should be VALID prior to configuring the replicated
environment.
Hope it helped.
Brian
--
------------------------------------------------------------------------
Brian Rasmusson, Software engineer & analyst e-mail: bri...@belle.dk
Belle Systems A/S web : www.belle.dk
Network, Internet and communication specialists phone : +45 59442500
------------------------------------------------------------------------
try
execute dbms_utility.compile_schema('SYS')
Pinchas Nisenson <nise...@acs.ucalgary.ca> wrote in article
<61bo72$n...@ds2.acs.ucalgary.ca>...