I found this nice blog entry today:
When performing database upgrades, adequate testing is important to understand the impacts, both positive and negative, the database upgrade has on the application. I have been preparing to upgrade databases from the 188.8.131.52 version to 184.108.40.206. One weekend, myself and another DBA spent some time upgrading about half of our production databases to the new target version. First thing on Monday morning I got a call from a Developer who had a query that was now running slowly. Why did we upgrade just half of the dev databases? For this specific reason.
I was playing around with the Result Cache the other day…I know…this isn’t a new feature and has been available for awhile. Unfortunately, it can take a while to get to things I guess.
In my simple test, I had a query that exhibited this behaviour:
Of course you already noticed document “Strategies for Scalable, Smarter Monitoring using Oracle Enterprise Manager Cloud Control 12c”, for those of you that didn’t you might want to check it out Strategies for Scalable, Smarter Monitoring using Oracle Enterprise Manager Cloud Control 12c