Releasing version 87.0.0

Releasing version 87.0.0

CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to this project will be documented in this file.
 
 The format is based on Keep a [Changelog](http://keepachangelog.com/).
 
+## 87.0.0 - 2024-04-30
+### Added
+- Support for enabling unified auditing for DBHome in the Database service
+- Support for listing minor Grid Infrastructure (GI) versions available for custom GI software image creation in the Database service
+- Support for network security groups in the Recovery Cloud service 
+- Support for lineage metadata import in the Data Catalog service
+- Support for workspace properties in workspace create and update operations in the Data Integration service
+- Support for monitoring ExaCC databases in the Database Management service
+- Support for validations on target and policy before the masking process in the Data Safe service
+
+### Breaking Changes
+- The type of property `Enabled` was changed from string to `EnabledEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `Accepted` was changed from string to `AcceptedEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `Fixed` was changed from string to `FixedEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `Reproduced` was changed from string to `ReproducedEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `AutoPurge` was changed from string to `AutoPurgeEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `Adaptive` was changed from string to `AdaptiveEnum` in the models `SqlPlanBaseline` and `SqlPlanBaselineSummary` in the Database Management service
+- The type of property `AllSqlStatementsFetched` was changed from string to `AllSqlStatementsFetchedEnum` in the model `SqlTuningSet` in the Database Management service
+
 ## 86.0.0 - 2024-04-23
 ### Added
 - Support for the Cluster Placement Groups service

Common/Src/Version.cs

@@ -7,7 +7,7 @@ namespace Oci.Common
 {
     public class Version
     {
-        public static string MAJOR = "86";
+        public static string MAJOR = "87";
         public static string MINOR = "0";
         public static string PATCH = "0";
         public static string TAG = "";

Database/DatabaseClient.cs

@@ -13909,7 +13909,7 @@ public async Task<ListFlexComponentsResponse> ListFlexComponents(ListFlexCompone
         }
 
         /// <summary>
-        /// Gets a list of supported GI versions for the Exadata Cloud@Customer VM cluster.
+        /// Gets a list of supported GI versions.
         /// </summary>
         /// <param name="request">The request object containing the details to send. Required.</param>
         /// <param name="retryConfiguration">The retry configuration that will be used by to send this request. Optional.</param>
@@ -18657,7 +18657,7 @@ public async Task<UpdateExternalPluggableDatabaseResponse> UpdateExternalPluggab
         }
 
         /// <summary>
-        /// If no database is associated with the key store, edit the key store.
+        /// Edit the key store.
         /// 
         /// </summary>
         /// <param name="request">The request object containing the details to send. Required.</param>

Database/models/AutonomousContainerDatabase.cs

@@ -471,19 +471,19 @@ public enum ComputeModelEnum {
         public System.Nullable<System.DateTime> TimeOfLastBackup { get; set; }
 
         /// <value>
-        /// The value above which an Autonomous Database will be split across multiple nodes. This value defaults to 16 when the \"CPU per VM\" value on the Autonomous VM Cluster is greater than 16. Otherwise, it defaults to the \"CPU per VM\" value.
+        /// The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
         /// </value>
         [JsonProperty(PropertyName = "dbSplitThreshold")]
         public System.Nullable<int> DbSplitThreshold { get; set; }
 
         /// <value>
-        /// The percentage of CPUs to reserve for a single node Autonomous Database, in increments of 25.
+        /// The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
         /// </value>
         [JsonProperty(PropertyName = "vmFailoverReservation")]
         public System.Nullable<int> VmFailoverReservation { get; set; }
                 ///
         /// <value>
-        /// This option determines whether to open an Autonomous Database across the maximum number of nodes or the least number of nodes. The default will be for the minimum number of VMs.
+        /// Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
         /// </value>
         ///
         public enum DistributionAffinityEnum {
@@ -497,7 +497,7 @@ public enum DistributionAffinityEnum {
         };
 
         /// <value>
-        /// This option determines whether to open an Autonomous Database across the maximum number of nodes or the least number of nodes. The default will be for the minimum number of VMs.
+        /// Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
         /// </value>
         [JsonProperty(PropertyName = "distributionAffinity")]
         [JsonConverter(typeof(Oci.Common.Utils.ResponseEnumConverter))]

Database/models/AutonomousContainerDatabaseSummary.cs

@@ -474,19 +474,19 @@ public enum ComputeModelEnum {
         public System.Nullable<System.DateTime> TimeOfLastBackup { get; set; }
 
         /// <value>
-        /// The value above which an Autonomous Database will be split across multiple nodes. This value defaults to 16 when the \"CPU per VM\" value on the Autonomous VM Cluster is greater than 16. Otherwise, it defaults to the \"CPU per VM\" value.
+        /// The CPU value beyond which an Autonomous Database will be opened across multiple nodes. The default value of this attribute is 16 for OCPUs and 64 for ECPUs.
         /// </value>
         [JsonProperty(PropertyName = "dbSplitThreshold")]
         public System.Nullable<int> DbSplitThreshold { get; set; }
 
         /// <value>
-        /// The percentage of CPUs to reserve for a single node Autonomous Database, in increments of 25.
+        /// The percentage of CPUs reserved across nodes to support node failover. Allowed values are 0%, 25%, and 50%, with 50% being the default option.
         /// </value>
         [JsonProperty(PropertyName = "vmFailoverReservation")]
         public System.Nullable<int> VmFailoverReservation { get; set; }
                 ///
         /// <value>
-        /// This option determines whether to open an Autonomous Database across the maximum number of nodes or the least number of nodes. The default will be for the minimum number of VMs.
+        /// Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
         /// </value>
         ///
         public enum DistributionAffinityEnum {
@@ -500,7 +500,7 @@ public enum DistributionAffinityEnum {
         };
 
         /// <value>
-        /// This option determines whether to open an Autonomous Database across the maximum number of nodes or the least number of nodes. The default will be for the minimum number of VMs.
+        /// Determines whether an Autonomous Database must be opened across the maximum number of nodes or the least number of nodes. By default, Minimum nodes is selected.
         /// </value>
         [JsonProperty(PropertyName = "distributionAffinity")]
         [JsonConverter(typeof(Oci.Common.Utils.ResponseEnumConverter))]

Database/models/AutonomousDatabase.cs

@@ -551,7 +551,7 @@ public enum DbWorkloadEnum {
         public System.Nullable<DbWorkloadEnum> DbWorkload { get; set; }
 
         /// <value>
-        /// This project introduces Autonomous Database for Developers (ADB-Dev), a free tier on dedicated infrastructure, and Cloud@Customer for database development purposes. ADB-Dev enables ExaDB customers to experiment with ADB for free and incentivizes enterprises to use ADB for new development projects.Note that ADB-Dev have 4 CPU and 20GB of memory. For ADB-Dev , memory and CPU cannot be scaled
+        /// Autonomous Database for Developers are free Autonomous Databases that developers can use to build and test new applications.With Autonomous these database instancess instances, you can try new Autonomous Database features for free and apply them to ongoing or new development projects. Developer database comes with limited resources and is, therefore, not suitable for large-scale testing and production deployments. When you need more compute or storage resources, you can transition to a paid database licensing by cloning your developer database into a regular Autonomous Database. See [Autonomous Database documentation](https://docs.oracle.com/en/cloud/paas/autonomous-database/dedicated/eddjo/index.html) for more details.        
         /// 
         /// </value>
         [JsonProperty(PropertyName = "isDevTier")]
@@ -974,7 +974,8 @@ public enum RoleEnum {
         public System.Nullable<System.DateTime> TimeLocalDataGuardEnabled { get; set; }
                 ///
         /// <value>
-        /// The Autonomous Data Guard region type of the Autonomous Database. For Autonomous Database Serverless, Autonomous Data Guard associations have designated primary and standby regions, and these region types do not change when the database changes roles. The standby regions in Autonomous Data Guard associations can be the same region designated as the primary region, or they can be remote regions. Certain database administrative operations may be available only in the primary region of the Autonomous Data Guard association, and cannot be performed when the database using the primary role is operating in a remote Autonomous Data Guard standby region.
+        /// **Deprecated.** The Autonomous Data Guard region type of the Autonomous Database. For Autonomous Database Serverless, Autonomous Data Guard associations have designated primary and standby regions, and these region types do not change when the database changes roles. The standby regions in Autonomous Data Guard associations can be the same region designated as the primary region, or they can be remote regions. Certain database administrative operations may be available only in the primary region of the Autonomous Data Guard association, and cannot be performed when the database using the primary role is operating in a remote Autonomous Data Guard standby region.
+        /// 
         /// </value>
         ///
         public enum DataguardRegionTypeEnum {
@@ -988,7 +989,8 @@ public enum DataguardRegionTypeEnum {
         };
 
         /// <value>
-        /// The Autonomous Data Guard region type of the Autonomous Database. For Autonomous Database Serverless, Autonomous Data Guard associations have designated primary and standby regions, and these region types do not change when the database changes roles. The standby regions in Autonomous Data Guard associations can be the same region designated as the primary region, or they can be remote regions. Certain database administrative operations may be available only in the primary region of the Autonomous Data Guard association, and cannot be performed when the database using the primary role is operating in a remote Autonomous Data Guard standby region.
+        /// **Deprecated.** The Autonomous Data Guard region type of the Autonomous Database. For Autonomous Database Serverless, Autonomous Data Guard associations have designated primary and standby regions, and these region types do not change when the database changes roles. The standby regions in Autonomous Data Guard associations can be the same region designated as the primary region, or they can be remote regions. Certain database administrative operations may be available only in the primary region of the Autonomous Data Guard association, and cannot be performed when the database using the primary role is operating in a remote Autonomous Data Guard standby region.
+        /// 
         /// </value>
         [JsonProperty(PropertyName = "dataguardRegionType")]
         [JsonConverter(typeof(Oci.Common.Utils.ResponseEnumConverter))]
@@ -1150,7 +1152,8 @@ public enum DatabaseEditionEnum {
         public System.Nullable<DisasterRecoveryConfiguration.DisasterRecoveryTypeEnum> LocalDisasterRecoveryType { get; set; }
                 ///
         /// <value>
-        /// The disaster recovery (DR) region type of the Autonomous Database. For Autonomous Database Serverless instances, DR associations have designated primary and standby regions. These region types do not change when the database changes roles. The standby region in DR associations can be the same region as the primary region, or they can be in a remote regions. Some database administration operations may be available only in the primary region of the DR association, and cannot be performed when the database using the primary role is operating in a remote region.
+        /// **Deprecated.** The disaster recovery (DR) region type of the Autonomous Database. For Autonomous Database Serverless instances, DR associations have designated primary and standby regions. These region types do not change when the database changes roles. The standby region in DR associations can be the same region as the primary region, or they can be in a remote regions. Some database administration operations may be available only in the primary region of the DR association, and cannot be performed when the database using the primary role is operating in a remote region.
+        /// 
         /// </value>
         ///
         public enum DisasterRecoveryRegionTypeEnum {
@@ -1164,7 +1167,8 @@ public enum DisasterRecoveryRegionTypeEnum {
         };
 
         /// <value>
-        /// The disaster recovery (DR) region type of the Autonomous Database. For Autonomous Database Serverless instances, DR associations have designated primary and standby regions. These region types do not change when the database changes roles. The standby region in DR associations can be the same region as the primary region, or they can be in a remote regions. Some database administration operations may be available only in the primary region of the DR association, and cannot be performed when the database using the primary role is operating in a remote region.
+        /// **Deprecated.** The disaster recovery (DR) region type of the Autonomous Database. For Autonomous Database Serverless instances, DR associations have designated primary and standby regions. These region types do not change when the database changes roles. The standby region in DR associations can be the same region as the primary region, or they can be in a remote regions. Some database administration operations may be available only in the primary region of the DR association, and cannot be performed when the database using the primary role is operating in a remote region.
+        /// 
         /// </value>
         [JsonProperty(PropertyName = "disasterRecoveryRegionType")]
         [JsonConverter(typeof(Oci.Common.Utils.ResponseEnumConverter))]