Oracle Database Management - Part 1 - Object Management

This is the first in a series of articles on Oracle Database Management that will cover some of the things a DBA should be looking at on a regular basis.

Object Management - Invalid Objects

-->

A well run Database should not have any invalid objects. It is important that no invalid objects exist in the database so that when either a database or application patch / deployment occurs, it is easier to determine whether there are any problems with a deployment leaving objects (views, synonyms, stored procedures / triggers) in an invalid state, when there are no invalid objects to begin with.

The list of invalid objects by schema should be reviewed. If the schema is an Oracle provided schema like SYS, SYSTEM, etc., the reason for the invalid object should be determined and resolved. The best way to do this is by searching Oracle Support (formerly Metalink) for a solution and then carrying it out. If the schema is an application schema, the list of invalid objects should be passed to the development / deployment team to be resolved. 

OEM generates an alert (evaluated every 24 hours) for invalid objects that is available on the Database Target Home page:

Oracle Enterprise Manager - Invalid Object Alerts