Oracle Database Discussions

Lets assume that you are preparing for a big project migration, lots of test have been done but you are nearly 100 percent sure there will be some major performance problems.

So when that migration time comes catching that problematic query is easy but until the tuning ends you need to stop that sql or plsql coming in order to go on servicing for the other applications.

Undeploying what changed is the quickest answer but during that caotic environment it is very hard to find that related deployment since the project is huge.

When you want to stop execution of an sql you may stop it parsing first, so revoking some grant or invalidating maybe other easy solutions. But what if you can not do this, it maybe a central package and this would mean lots of applications' downtime.

Another workaround - but not an exact solution - is resource manager, you may configure a specific resource consumption threshold. But some execution will be in place and what if that problematic query is being called lots of times, it will have again a great impact.

So I hope the need is clear enough and any comments will be welcomed, thank you very much.

Best regards.
Tonguc