Consequences of modifying the Recovery Appliance (Doc ID 2172842.1)

Last updated on OCTOBER 27, 2019

Applies to:

Purpose

The Recovery Appliance is built on top of the Exadata Database Machine, but unlike the Exadata Database Servers, the Recovery Appliance Compute Nodes may not be customized in any way, with the only exceptions documented in the Recovery Appliance Owners Guide.

This Bulletin aims to reinforce what types of modifications are supported and not supported. This bulletin provides examples of the adverse consequences of some unsupported customizations out in the field.

Scope

One of the key benefits of the Recovery Appliance is that every customer who has purchased a Recovery Appliance is running the exact same system. Customers benefit from the fact that while they may have only one or two appliances, the same engineered software and hardware stack is running on many other customer systems around the world. However, a common misconception is that the Recovery Appliance may be customized in the same ways that are permitted with an Exadata Database Machine. Many such customizations have broken this engineered appliance so that patching or upgrades do not complete successfully. These types of problems have led to appliances needing to be re-imaged, resulting in the loss of all backups on the re-imaged appliance.

Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.