Recommended Maximum Availability Architecture (MAA) Patches for Oracle Database In-Memory
(Doc ID 2045279.1)
Last updated on OCTOBER 07, 2022
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This note lists the Oracle Maximum Availability Architecture (MAA) team's recommended patches for Oracle Database In-Memory. This list of patches generally improve availability and reduction of human errors with the goal of minimizing impacts during failures.
These fixes are recommended for customers using Oracle Database In-Memory with the configuration details described in the list below. All the bugs listed below are unpublished.
|Bug||Bug Description||Configuration||Impacted releases||Bundle Patch Fix|
QUERY SUFFERS PERFORMANCE IMPACT DURING OUTAGE EVEN WITH INMEMORY DUPLICATE
This bug fixes an issue during re-population of IMCUs after an instance outage. There is a small window where a query issued from a live instance will not access the secondary copies of IMCUs and suffer performance issues. This fix will ensure that the available IMCU copies are accessed while the IMCUs are being redistributed.
|Exadata and Engineered Systems||
ADD FAST DATABASE NODE DEATH DETECTION SUPPORT ON EXADATA
Adds the capability on Exadata systems to detect a node outage very quickly by looking at the IB network status of a node instead of waiting for MISSCOUNT timeout.
SUM OF BYTES_NOT_POPULATED FOR ALL NODES NOT EQUAL TO DISKSIZE
If an IM segment is distributed among many Real Application Cluster (RAC) nodes, then BYTES - BYTES_NOT_POPULATED in gv$im_segments should be the total number of bytes per node populated, so the sum of this number across the nodes should be the total number of BYTES. In this case, in many cases it is actually more than the number of BYTES, which is actually incorrect.
IMC:CHANGING ONE IN-MEMORY ATTRIBUTE WILL MODIFY OTHERS WITH DEFAULT VALUES
This fix ensures the inheritance of each IM attribute should be independent and in memory segments should not be invalidated only if the priority is being changed. This means that an ALTER TABLE command that changes an INMEMORY attribute only changes the attribute specified and inherits the ones already set for the segment.
For more information on configuring Oracle Database In-Memory for high availability, see the MAA technical briefs, Oracle Database In-Memory, High Availability Best Practices.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!