Class CreateCrossRegionAutonomousDatabaseDataGuardDetails


  • @Generated(value="OracleSDKGenerator",
               comments="API Version: 20160918")
    public final class CreateCrossRegionAutonomousDatabaseDataGuardDetails
    extends CreateAutonomousDatabaseBase
    Details to create an Autonomous Data Guard association for an existing Autonomous Database where the standby is in a different (remote) region from the source primary database.

    IMPORTANT Note the following for creating standby databases in cross-region Autonomous Data Guard associations:

    • To create your standby database in a region different from the region of the primary, use the API endpoint of the region in which the standby will be located. For example, if the primary database is in the IAD region, and you want to create the standby in the PHX region, make the API call using the PHX endpoint (https://database.us-phoenix-1.oraclecloud.com). See API Endpoints for the list of Database Service API endpoints. - In the request to create the standby database, the sourceId value should be the OCID of the primary database. The following parameters are optional for the cross-region standby database. If included in the request, these parameters contain the same values as the source Autonomous Database: - customerContacts - scheduledOperations - isAutoScalingForStorageEnabled - definedTags - freeformTags - licenseModel - whitelistedIps - isMtlsConnectionRequired - dbName - adminPassword - cpuCoreCount - dataStorageSizeInTB - dbVersion
      Note: Objects should always be created or deserialized using the CreateCrossRegionAutonomousDatabaseDataGuardDetails.Builder. This model distinguishes fields that are null because they are unset from fields that are explicitly set to null. This is done in the setter methods of the CreateCrossRegionAutonomousDatabaseDataGuardDetails.Builder, which maintain a set of all explicitly set fields called CreateCrossRegionAutonomousDatabaseDataGuardDetails.Builder.__explicitlySet__. The hashCode() and equals(Object) methods are implemented to take the explicitly set fields into account. The constructor, on the other hand, does not take the explicitly set fields into account (since the constructor cannot distinguish explicit null from unset null).