We've had the same problem occasionally (and it seems to be worse now that we are on Oracle10.1 than it was on Oracle8 or 9) so we don't allow changes to heavily-used tables in our prodution database during the week anymore. We have the luxury of production down time on Saturday night and Sunday, so we wait with structure changes to our production database until the weekend, when we can shut down and reboot the instance if necessary to clear locks on PL\SQL objects.
Main Topics
Browse All Topics





by: pbocanegraPosted on 2006-03-29 at 07:56:50ID: 16322897
In the practice, the developers works on shared developer database, when the developer finish your work then, your scripts run in pre-production database.
The aplication pointer move to pre-production database, when the users certificate then migrate to production database.
For your problem describe , your resolution is the only way, I think so, for fixed this inconvenient.