Enabling Real-Time Analytics With Database In-Memory

Oracle Database In-Memory Bundle Patch 10 Released

Maria Colgan
Master Product Manager

The latest Bundle Patch for Database In-Memory has been released. The Bundle Patch is 21188742 or Bundle Patch 10 for Engineered Systems and DB In-Memory (July2015)). This Bundle Patch improves the performance of mixed workload environments (OLTP & DW workloads), as well as enhancing the performance of analytic queries with aggregation. More information on the latest Bundle Patch can be found in the MOS note 21188742.8 or in the Mos note: Bundle Patches for
Engineered Systems and DB In-Memory (Doc ID 1937782.1).

Remember that Bundle Patches are cumulative, which means that
Bundle Patch 10 includes all fixes from Bundle Patches 1 through 9 in
addition to new content. It also includes the most recently released
Patch Set Update (PSU) (JULY 2015 GI PSU and DB PSU), which also includes the most recently released
Critical Patch Update (CPU) as of the time that the Bundle Patch is
created. This has caused quite a bit of concern so I wanted to point out two MOS notes that provide more details:

  • Exadata Patching Overview and Patch Testing Guidelines (Doc ID 1261380.1)
  • Exadata Database Machine and Exadata Storage Server Supported Versions (Doc ID 888828.1).

Don't let the "Exadata" in the name of the Bundle Patch scare you off. Bundle Patches are supported for Exadata and non-Exadata systems and on RAC and non-RAC databases as well.

When it comes to patching your system, it's important to remember that an installation can only use one
of the CPU, PSU or Bundle Patch patching methods. This is documented in
MOS note: Oracle Database - Overview of Database Patch Delivery Methods
(Doc ID 1962125.1).

For In-Memory customers we recommend that you always run with the latest Bundle Patch!

 Good luck and happy patching!

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.Captcha