Oracle Data Guard Patching Scenarios
Scenario 1: The primary and standby databases are RAC databases.
Table 14-2 describes the steps to apply an Oracle Grid Infrastructure PSU or an Oracle Database PSU, when the primary and standby databases are RAC databases:Table 14-2 Oracle Data Guard Patching (RAC - RAC)
Primary and Standby Database Configuration | How to Patch? |
---|---|
The primary and the standby RAC databases are running from the same cluster. |
|
The primary and the standby RAC databases are running from different clusters. |
|
Two primary RAC databases, P1 and P2, are running from two different clusters, C1 and C2, respectively. Their standby RAC databases, S1 and S2, are running from C2 and C1, respectively. |
Note: You can patch the clusters in any order, that is, C1 first and then C2, or C2 first and then C1. |
Table 14-3 describes the steps to apply an Oracle Grid Infrastructure PSU or an Oracle Database PSU, when the primary database is a RAC database, and the standby database is a single-instance database that is managed by a CRS target or a SIHA (Single Instance High Availability) target.
Table 14-3 Oracle Data Guard Patching (RAC - SIDB)
Primary and Standby Database Configuration | How to Patch? |
---|---|
The primary RAC database and the standby single-instance database are running from the same cluster. |
|
The primary RAC database and the standby single-instance database are running from different clusters. |
|
Two primary RAC databases, P1 and P2, are running from two different clusters, C1 and C2, respectively. Their standby single-instance databases, S1 and S2, are running from C2 and C1, respectively. |
Note: You can patch the clusters in any order, that is, C1 first and then C2, or C2 first and then C1. |
Scenario 3: The primary and standby databases are single-instance databases that are managed by CRS or SIHA targets.
Table 14-4 describes the steps to apply an Oracle Grid Infrastructure PSU or an Oracle Database PSU, when the primary and standby databases are single-instance databases that are managed by CRS or SIHA targets.Note:
When patching Single Instance High Availability (SIHA)12.1.0.2 Oracle Database through Enterprise Manager 13.4 and Perl 5.38 Update, the database needs to be patched at least to version 12.1.0.2.191015, with the October 2019 or later GI PSU patch applied on the target.Table 14-4 Oracle Data Guard Patching (SIDB - SIDB)
Primary and Standby Database Configuration | How to Patch? |
---|---|
The primary and the standby single-instance databases are running from the same cluster. |
|
The primary and the standby single-instance databases are running from different clusters. |
|
Two primary single-instance databases, P1 and P2, are running from two different clusters, C1 and C2, respectively. Their standby single-instance databases, S1 and S2, are running from C2 and C1, respectively. |
Note: You can patch the clusters in any order, that is, C1 first and then C2, or C2 first and then C1. |
Follow these steps to apply an Oracle Grid Infrastructure PSU or an Oracle Database PSU on this configuration:
- Search for the required Oracle Grid Infrastructure PSU, or the Oracle Database PSU, then create a patch plan by selecting the first cluster target (C1).
- Specify the required deployment options.
- Analyze and deploy the plan.
- Search for the required Oracle Grid Infrastructure PSU, or the Oracle Database PSU, then create another patch plan by selecting the second cluster target (C2).
- Specify the required deployment options.
- Analyze and deploy the plan.
Note:
You can patch the clusters in any order, that is, C1 first and then C2, or C2 first and then C1.