Behavior of Exadata Fleet Update Service While Patching a Database in an Oracle Data Guard Environment
Learn about what terms are used with Exadata Fleet Update.
To patch databases in an Oracle Data Guard Configuration, apply a software update to the standby database before applying a software update to the primary database.
Peer databases (primary and standby) cannot be included in the same Exadata Fleet Update Collection.
The patches must be Data Guard first installable. It is imperative to specify the exact same patches in the primary and standby maintenance cycles.
For more information, see:
- Use Oracle Data Guard with Exadata Database Service on Cloud@Customer
- Use Oracle Data Guard with Exadata Cloud Infrastructure
Procedure
- Create an Exadata Fleet Update Collection of standby databases, if such a Collection does not already exist.
Create a separate Exadata Fleet Update Collection of primary databases, if such a Collection does not already exist.
In the case of cross-region Oracle Data Guard configuration, the Exadata Fleet Update Collections will exist in different regions.
For more information, see Create a Collection.
- Create a Maintenance Cycle for the Exadata Fleet Update Collection of standby
databases, specifying the desired goal version or database software image, and
complete Exadata Fleet Update Stage Action.
For more information, see:
- Create a Maintenance Cycle for the Exadata Fleet Update Collection of primary databases, specifying the identical goal version or database software image, and complete Exadata Fleet Update Stage Action.
For more information, see:
- Schedule Apply Exadata Fleet Apply Action for the Exadata Fleet Update Collection of standby databases.
- Upon the successful completion of Exadata Fleet Update Apply action for the Exadata Fleet Update Collection of standby databases, schedule Exadata Fleet Update Apply Action for the Exadata Fleet Update Collection of primary databases.
Parent topic: Exadata Fleet Update Overview