Class CreateCrossRegionDisasterRecoveryDetails


  • @Generated(value="OracleSDKGenerator",
               comments="API Version: 20160918")
    public final class CreateCrossRegionDisasterRecoveryDetails
    extends CreateAutonomousDatabaseBase
    The following are the details necessary to create a disaster recovery (DR) association for an existing Autonomous Database with a standby in a remote region.

    IMPORTANT For creating a standby databases in a cross-region DR association: - To create the standby database in a remote region, use the API endpoint in the region where the standby is located. For example, if the primary database is in the IAD region and the standby is 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. - To create the request in the standby database, the sourceId value must be the OCID of the primary database. The following parameters are required for the cross-region standby database and must contain the same values as the source Autonomous Database: - remoteDisasterRecoveryType The following parameters are optional for the cross-region standby database. If included in the request, these parameters must contain the same values as the source Autonomous Database: - dbName - dbVersion - ecpuCount - dataStorageSizeInTB - customerContacts - scheduledOperations - isAutoScalingForStorageEnabled - definedTags - freeformTags - licenseModel - whitelistedIps - isMtlsConnectionRequired
    Note: Objects should always be created or deserialized using the CreateCrossRegionDisasterRecoveryDetails.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 CreateCrossRegionDisasterRecoveryDetails.Builder, which maintain a set of all explicitly set fields called CreateCrossRegionDisasterRecoveryDetails.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).