Re: Recompiling invalid objects in PL/SQL

#> If you don't monitor how do you catch problems caused by application

#> changes? This is just basic DBA 101 here Frank.

# No it's not - it's the TUSC/BCHR school of DBA here - monitor for # monitoring sake.

Sorry it's still 101 stuff Frank.

Have a set of things that you want to alert on when they go outside of operational norms.

# Objects do not go invalid during normal operations, period.
# They could become invalid as a result of code changes
# (application update/upgrade, database update/upgrade, etc).

Sure it's a fine idea to make sure that after implementing changes that things are ok. That's just good standard 101 SOP.

Some shops operate more loosely than others. Not all changes in every shop go through a rigorous QA process and a clean implementation procedure.

And of course it wouldn't be possible for any one of a large team of DBA's to make a mistake or slip up somewhere would it?

So you put something in place to catch these things and then double check why they happened.  

But checking that is part of the test and implementation plan. Received on Wed Dec 07 2005 - 12:54:40 CST