Home Our Concept Services Other Products Shopping Cart Payment Options FAQ Privacy About Us Contact Us
You are here: Home > Whitepapers > The danger of invalid database objects

The Danger of Invalid Database Objects


This document shows the risks when operating a database with invalid objects. This document is written for members of application support operations managers. The operations managers should understand the risk associated when operating databases with invalid objects and he should solve the dispute between application support and DBA's who both argument that this is not "his" but "the others" problem.

An invalid database object (Synonym, Package, Procedure, View,..) could indicate a problem, but it might be also harmless. Nevertheless operating a database with "harmless" invalid objects makes the detection of a new invalid object indicating a serious problem impossible or much more difficult. Combined with missing controls in other areas severe malfunction might not be detected. In case of problems the troubleshooting process might require more time because investigators might also research all invalid objects.

Effort for an initial cleaning (getting rid of invalid objects) of all databases pays off, as all involved persons get awareness about risks and importance so that new systems and changes will not introduce new invalid objects. Thus you will increase the maturity level of your IT.


  • Operations Manager
  • Testing Manager
  • Environment Manager
  • Application Support Staff
  • System-DBA, Application-DBA, Development-DBA
  • Quality Assurance Manager

Download this Free Whitepaper as PDF-File

The Danger of Invalid Database ObjectsPDF-Icon

Bookmark this page with: | reddit reddit | delicious delicious | digg digg | furl furl | google google | yahoo yahoo | Technorati search Technorati search
Copyright © 2005-2008 Mercury Consulting Limited.