After our recent upgrades to Oracle 18.104.22.168, we noticed a few non-production databases that were filling up the DIAGNOSTIC_DEST. There were huge trace files in there which contained this type of information:
----- Cursor Obsoletion Dump sql_id=6aca4drrt76x3 -----
Parent cursor obsoleted 1 time(s).
It appears this is a known bug in 22.214.171.124. Oracle turned on some diagnostic info and forgot to turn it off. But you can turn it off in your environments with the following:
alter system set "_kks_obsolete_dump_threshold" = 0;
New Cloud Services Enable Organizations to Gain an End-to-End View of Applications From End-Users to the Underlying Infrastructure, Effectively Manage Diverse IT Environments and Drive DevOps Efforts….
Read what Finance Yahoo tell us about it
I’ve been working with MongoDB a bit and one of the things I like about it is how sharding helps the platform achieve high performance. MongoDB is not the only database platform that uses sharding, just one of the more mainstream ones. While I’ve been working with MongoDB and admiring sharding and the ability to handle JSON documents, I’ve also been troubled by a few other things.
I attended a session today at Oracle Open World 2015 by Markus Michalewicz which highlighted some new features we can look forward to for Oracle Grid Infrastructure 12.2, currently in beta. There were lots of new features, but a few stood out as major changes to the architecture.
Today at Oracle Open World 2015, I learned that Oracle12cR2 is now in beta. I attended a session from Oracle VP Andy Mendelsohn where he highlighted a few of the new features found in 12.2. This is not an exhaustive list, but contains some highlights from that session.
During the installation of Oracle Grid Infrastructure 126.96.36.199 you had the option to install the Grid Infrastructure Management Repository (GIMR) database MGMTDB. With 188.8.131.52, that option went away, and the MGMTDB database became mandatory. Given that it’s a database, the question of whether it should be monitored by Enterprise Manager was raised by a number of customers, and unfortunately a variety of different answers were forthcoming from different sources in Oracle.
I recently upgraded a critical production system from Oracle 184.108.40.206 to 220.127.116.11. This is also a 3-node Oracle RAC database. I ran into a few issues which needed resolution after the upgrade. Hopefully this helps out others in their upgrades.