The Database In-Memory team has been busy attending conferences in the last couple of months letting you know what's new with Database In-Memory. These conferences have included Open World, the East Coast Oracle Users Conference (ECO), the Bulgarian Oracle User Group (BGOUG) conference, the German Oracle User Group (DOAG) conference, the All India Oracle Users Group (AIOUG) conference SANGAM16 and we would like to thank everyone for attending our sessions and stopping by to ask questions.
One of the questions that continues to get asked is about Patch Set Updates (PSUs). We're still finding that people are installing PSUs (see MOS Note 854428.1), or even Critical Patch Updates
(CPUs), and expecting to get fixes for Database In-Memory. We've blogged about this in the past here
, but I think it's worth repeating.
Database In-Memory became available in the first Oracle Database 12c Release 1 patch set (220.127.116.11) back in July 2014. Since then we've made numerous enhancements and fixes to the product, but the only way to get all of these changes is to install what is now known as a Database Proactive Bundle Patch (see MOS Note 1937782.1). Many people are then concerned that Database Proactive Bundle Patches are only for engineered systems, and others are concerned that they don't include all of the fixes in PSUs and/or CPUs. As MOS Note 1937782.1 explains, each bundle patch includes all database PSU fixes along with additional proactive fixes. Some of these additional proactive fixes include all of the fixes to Database In-Memory.
The bottom line is please apply the latest Database Proactive Bundle Patch when using Database In-Memory. After all, there's no sense in re-inventing the wheel and discovering problems that have already been fixed, or not getting to take advantage of the enhancements that have been made.