Today a developer added a column to a very frequently used table in our production environment, which caused a number of packages to get invalid.
One package did not compile, our developer tool hung and after a while we got a time-out message. We couldn't come up with anything better (and we needed a solution quickly) than killing all processes in the database that were using the package (we got that info from dba_ddl_locks), and then recompile the package successfully. As our users weren't really amused, we'd like to come up with a better solution in the future, if there is one?
We already blocked access to our production environment for part of the developers, but still this could happen to others.
Does any of you know how to handle this kind of problems in a better way?
Start Free Trial
