Thanks for the question, Ramkumar.
Asked: December 12, 2016 - 7:46 pm UTC
Last updated: December 13, 2016 - 3:52 am UTC
Version: 11g
Viewed 1000+ times
You Asked
Hello Tom,
This is my First POST.
I experienced a performance issue with one of the package and in order to debug/troubleshoot the package, I cloned the original package and without changing any content of the cloned package; I ran a test for a single transaction with the cloned package. Surprisingly, the cloned package completed the process in less than a second, whereas the original package was running for 3 minutes. I am wondering, how would a same package with different names will work differently.
I performed all of this activities in same schema and in same connection/session. your input will greatly help me.
Note: I work for healthcare and will not be able to provide any screenshots or content of the code. If you need any additional details, let me know the specifics so that I can grab those information for you.
and Connor said...
It is very unlikely to be package, more likely to be an SQL within the package. It may well be the case than the new package has resulted in a fresh parse of the SQL's within it - which could have picked up new optimizer plans.
Is this answer out of date? If it is, please let us know via a Comment