Service Change Announcements

Service Change: The required subnetId attribute from the Oracle Cloud Infrastructure's CreateRecoveryServiceSubnet API is deprecated.

The CreateRecoveryServiceSubnet API can instead use the optional Subnets attribute, which later changes to become a required attribute.

Date Announced: May 2023.

Date in Effect: May 2024.

Details: Prior to this service change, the subnetId attribute can be used to specify only a single subnet to be associated with a Recovery Service subnet. After this service change, the subnetId attribute is ignored and subnets will be required attribute. The subnets attribute can be used to specify multiple subnets to be associated with a Recovery Service subnet.

Does this impact me? If you have custom scripts or Terraform scripts that are referencing the CreateRecoveryServiceSubnet API and are explicitly using the subnetId attribute, you might want to modify the scripts to remove this attribute and use subnets instead.

What do I need to do? When using OCI SDKs and command line tools, you must choose to update your custom scripts to use the subnets attribute. After May 2024, the subnets attribute is a required field.

Service Change: On January 31, 2023, the agreement between Oracle and Cloudera expires. As a result, starting on January 31, Oracle Big Data Service will no longer support using the Cloudera Distribution including Apache Hadoop (CDH) to launch new clusters or add nodes or cores to existing clusters beyond a set limit. This change doesn’t impact ongoing support of existing Big Data Service CDH clusters.

This change is applicable only to Big Data Service CDH. This change does not impact customers who use on-premises Oracle Big Data Appliance (BDA) or Big Data Service with Oracle Distribution of Hadoop (ODH).

Date Announced: December 13, 2022

Date in Effect: January 31, 2023

Details: On January 31, 2023, the limit for Big Data Service CDH expansion of the number of compute cores (OCPUs) freezes. The number of compute cores in a customer’s tenancy on January 31 becomes the maximum number of cores allowed for that tenancy, and no further expansion will be allowed.

Does this impact me? This change is only applicable to Big Data Service with CDH. Big Data Service with Oracle Distribution of Hadoop (ODH) is not impacted in any way.

For example, on January 31, 2023 if a tenancy has 2 BDS CDH clusters with 15 nodes each with a total of 120 OCPUs, then after January 31, 2023 the maximum limit for OCPUs will be set to 120 and cannot be increased beyond 120 after that date. For support issues such as replacing failed nodes, new nodes may be added up to that limit. Users can also decrease the number of cores and increase back to the same limit (for example, 120).

Next steps: Oracle recommends planning and implementing any required Big Data Service CDH cluster expansions before January 31, 2023. For customers who want to avoid this expansion constraint after that date, we recommend migrating to Big Data Service ODH.

About Big Data Service with ODH: In 2022, Oracle released Big Data Service ODH, which we developed as a cloud native service for our big data customers. Oracle provides continuous investment and support for ODH, with no licensing requirements from Cloudera. ODH has key enterprise-focused features, including autoscaling, Kerberos, Active Directory integration, HDFS connector for Object Storage, and Bootstrap scripts. And it’s one of the most cost-efficient big data products in the market.

Big Data Service ODH has multiple versions with the latest and previous versions of Hadoop components for compatibility with newer and older application stacks. It’s also verified with WANdisco Data Migrator for easier migrations at scale and uses Oracle Cloud Lift services to work with Oracle engineers for migrations. For information about migrating to Big Data Service ODH, see the documentation.

Service Change: Oracle defined backup policies no longer include full volume backups.

Date Announced: November 3, 2020

Date in Effect: November 3, 2021

Details: Starting November 3, 2021, Oracle defined backup policies no longer include full volume backups. All volume backups generated from Oracle defined policies are now incremental backups. This change applies to existing volume backup policy assignments and new volume backup policy assignments. This change does not impact user defined policies, which remain unchanged.

Does this impact me? If you have assigned an Oracle defined policy to boot volumes or block volumes for scheduled backups, full backups are no longer generated after November 3, 2021.

What do I need to do? Incremental backups are functionally the same as full backups for data recovery purposes, for more information, see Volume Backup types. No action is needed for data recovery scenarios. Some compliance scenarios may require scheduled full backups. For these compliance scenarios, change the backup policy assignment to a user defined backup policy prior to November 1, 2021. You can create a new user defined policy from an existing backup policy, see Duplicating Existing Backup Policies.

Service Change: The PCI-NIC fault class for Compute bare metal instance health monitoring is deprecated.

Date Announced: June 21, 2022

Date in Effect: June 21, 2023

Details: The PCI-NIC fault class provides information about a hardware issue with your bare metal instances, specifically when a fault in the instance network interface card (NIC) has been detected. The PCI-NIC fault class will no longer be emitted.

Does this impact me? When support ends, you will no longer receive health monitoring notifications for the PCI-NIC fault class. Infrastructure health metrics will no longer be emitted for the PCI-NIC fault class.

What do I need to do? Migrate to the PCI fault class for similar functionality. For more information, see Compute Health Monitoring for Bare Metal Instances and Infrastructure Health Metrics.

Service Change: OCI Java SDK version 2 is being deprecated.

Date Announced: April 6, 2023

Date in Effect: June 30, 2023

Details: Oracle has recently released Oracle Cloud Infrastructure (OCI) Java SDK version 3. OCI Java SDK version 3 is a major SDK release, and we recommend that you upgrade to this latest version. We will continue to fully support OCI Java SDK version 2 until the end of June 2023. During this time, both OCI Java SDK versions 2 and 3 will receive regular updates to add support for new service APIs, critical bug fixes and security patches, and documentation modifications.

Does this impact me? After June 30, 2023, OCI Java SDK version 2 will no longer receive updates to add support for new regions, new services, or features in existing services, unless otherwise specified. For older versions of the OCI Java SDK version 2 that are less than 12 months old, upon request, OCI will backport critical bug fixes and security issues only.

What do I need to do? Upgrade to OCI Java SDK version 3.

Oracle Cloud Infrastructure's Autonomous Data Warehouse APIs were deprecated on Feb. 15, 2019.

Important! Support for these Autonomous Database for Analytics and Data Warehousing APIs will end on Jul. 1, 2020. Oracle recommends that you migrate your database workloads to the replacement APIs as soon as possible.

Service Change: The default value of the isMTLSConnectionRequired attribute will change from true to false on July 1, 2023 in the following APIs:

• CreateAutonomousDatabase
• GetAutonomousDatabase
• UpdateAutonomousDatabase

Date Announced: February 7, 2023.

Date in Effect: July 1, 2023.

Details: Prior to this service change, the isMTLSConnectionRequired attribute default value was true. This is applicable for Autonomous Database on shared Exadata infrastructure.

Does this impact me? If you have custom scripts or Terraform scripts that are referencing the CreateAutonomousDatabase, GetAutonomousDatabase, or UpdateAutonomousDatabase APIs, you might want to modify the scripts to account for the changed default value of this attribute. However, should you choose not to make any changes to your scripts, the API calls containing this attribute will continue to work except that the default value will switch from "true" to "false".

What do I need to do? When using OCI SDKs and command line tools, you might choose to update your custom scripts to explicitly set the isMTLSConnectionRequired attribute to "true".

Service Change: The following APIs have changes where the API or certain API fields are deprecated.

Date Announced: May 17, 2023.

Date in Effect: May 17, 2024.

Details: Prior to this service change, these APIs included the APIs or the API fields mentioned. After this service change, the mentioned APIs or APIs fields will be removed. This is applicable for Autonomous Database on shared Exadata infrastructure.

Support for these Autonomous Database API Fields will end on May 2, 2024. Oracle recommends that you migrate your scripts to discontinue the use of these Fields as soon as possible. Where provided, switch to use the replacement field or API.

Does this impact me?: If you have custom scripts or Terraform scripts that are referencing these APIs, or the mentioned fields, you should modify the scripts to account for these changes.

What do I need to do?: When using OCI SDKs and command line tools, you update your custom scripts to either remove use of the deprecated APIs or fields or use the replacements.

Service Change: The return values for certain APIs changes, where return the value of 409 Incorrect State in some cases, as appropriate, is changed to 409 Conflict.

Date Announced: October 2023.

Date in Effect: October 2024.

Details: Prior to this service change, certain API calls fail with 409 Incorrect State error code. After this service change, in certain cases as appropriate, the API calls will fail with error code 409 Conflict.

Before this change, many APIs return 409 Incorrect State when the Autonomous Database is Stopped or is Unavailable. For these states, according to the API guidelines the correct return is 409 Conflict. For other Autonomous Database states, such as Starting, Stopping, and Provisioning, the current return of 409 Incorrect State is correct and this will not change after this update.

The 409 Incorrect State return should be used to indicate that retries are OK and that the resource will eventually reach the correct state, and the return 409 Conflict indicates that the resource will not reach the correct state on its own and that retries should not be performed. This service change changes the error code value in these APIs for the cases where 409 Conflict is representative of the known Autonomous Database state.

This service change applies to the following APIs:

• UpdateAutonomousDatabase
• DeleteAutonomousDatabase
• ChangeDisasterRecoveryConfiguration
• RotateAutonomousDatabaseEncryptionKey
• StartAutonomousDatabase
• RestartAutonomousDatabase
• ShrinkAutonomousDatabase
• StopAutonomousDatabase
• ConfigureAutonomousDatabaseVaultKey
• AutonomousDatabaseManualRefresh
• FailOverAutonomousDatabase
• SwitchoverAutonomousDatabase
• ChangeAutonomousDatabaseCompartment
• RegisterAutonomousDatabaseDataSafe
• DeregisterAutonomousDatabaseDataSafe
• EnableAutonomousDatabaseOperationsInsights
• DisableAutonomousDatabaseOperationsInsights

Does this impact me?: If you have custom scripts or Terraform scripts that are handling the 409 Incorrect State return from these APIs, you might want to modify the scripts to handle the 409 Conflict return, as appropriate.

What do I need to do?: When using OCI SDKs and command line tools, you might choose to update your custom scripts.

Service Change: The isShared parameter from the Oracle Cloud Infrastructure's ListAutonomousDatabaseCharacterSets is deprecated.

Date Announced: October 2023.

Date in Effect: October 2024.

Details: Prior to this service change, the optional isShared parameter can be used. This change introduces the optional isDedicated parameter, and the isShared parameter will be removed after October 2024.

Does this impact me?: If you have custom scripts or Terraform scripts that are referencing the ListAutonomousDatabaseCharacterSets API using the isShared parameter with the value TRUE, modify the scripts to replace this parameter with the isDedicated parameter with the value FALSE, and if you are referencing the ListAutonomousDatabaseCharacterSets API using the isShared parameter with the value FALSE, modify the scripts to replace this parameter with the isDedicated attribute with the value TRUE.

What do I need to do?: When using OCI SDKs and command line tools, update your custom scripts to replace the isShared parameter with the isDedicated parameter.

Oracle Cloud Infrastructure's Exadata DB system APIs were deprecated on November 15, 2020.

Important!: No new systems can be provisioned with the old DB system resource model/APIs after May 15th, 2021. Support for the old DB system resource model/APIs on existing systems will end on November 15th, 2021. Oracle recommends that you migrate your Exadata Database Service on Dedicated Infrastructure instances to the new resource model APIs as soon as possible. Converting to the new resource model does not involve any system downtime.

Service Change: The optional dbWorkload attribute from the Oracle Cloud Infrastructure's CreateDatabase API is deprecated.

Date Announced: November 2022.

Date in Effect: November 2023.

Details: Prior to this service change, the dbWorkload attribute can be used to choose between either the OLTP (Online Transaction Processing) or the Data Warehouse (Analytic) workload, and is used internally to determine memory settings based on the database workload. After this service change, the dbWorkload attribute is treated as a "no-op" (no operation), which means that while API calls containing the deprecated attribute will not fail, the passed value will be ignored and the system will instead use a default value internally. This is applicable for Exadata Database Service on Dedicated Infrastructure, Exadata Database Service on Cloud@Customer, and Base Database Service.

Does this impact me? If you have custom scripts or Terraform scripts that are referencing the CreateDatabase API and are explicitly using the dbWorkload attribute, you might want to modify the scripts to remove this attribute. However, should you choose not to make any changes to your scripts, the API calls containing this attribute will continue to work except that the value passed for the dbWorkload attribute will not be considered.

What do I need to do? When using OCI SDKs and command line tools, you might choose to update your custom scripts to exclude the dbWorkload attribute. After November 2023, if you pass a value to the dbWorkload attribute, it will be ignored.

Service Change: Oracle Cloud Infrastructure's Database Migration APIs of version 20200720 were deprecated on October 6, 2021.

Date Announced: October 6, 2021

Date in Effect: October 5, 2022

Details: Starting October 5, 2022, Database Migration APIs of version 20200720 is deprecated.

• Any resource created with the deprecated version is automatically converted to the latest resource model (version 20210929). (Before this date, any created with the deprecated version remains accessible on its basePath of /20200720.)
• OCI Console users are automatically migrated to the latest resource model (version 20210929).
• OCI SDKs and command line tools that were released before October 6, 2021, are limited to the features of the deprecated resource model (version 20200720).
• Database Migration Service Agent Kits that were downloaded before October 6, 2021, are limited to the features of the deprecated resource model (version 20200720).

Does this impact me? Yes, if you have an older client or agent kit.

What do I need to do?

• OCI SDKs and command line tools: To take advantage of newer features available in the latest resource model, you must update your client to any version released after October 6, 2021.
• Database Migration Service Agent Kits: If your kit was downloaded before October 6, 2021, you must reinstall it.

List of unsupported and replacement APIs

Service Change: Oracle Cloud Infrastructure's DevOps APIs (two APIs) of version 20210630 were deprecated on March 29, 2022.

Date Announced: March 29, 2022

Date in Effect: March 29, 2023

Details: Starting March 29, 2022, two DevOps APIs of version 20210630 were deprecated. From March 29, 2023, onwards the deprecated APIs will be unavailable.

Service Change: The Event Hub service is deprecated.

Date Announced: April 29, 2022

Date in Effect: May 31, 2023

Details: Effective May 31, 2023, the Oracle Event Hub service will reach end of life (EOL). Prior to the EOL date, we recommend that you migrate your data streams from Event Hub to Oracle Cloud Infrastructure Streaming.

Does this impact me? If you use Event Hub service to create Kafka Clusters and/or Event Hub topics, you will no longer be able to after May 31, 2023. Previously created clusters will continue to operate in your tenancy without changes.

What do I need to do? All Event Hub customers can now use Streaming to move data using its tight integrations with Oracle Cloud Infrastructure (OCI), Database, GoldenGate, and Integration Cloud. The service uses a Kafka Connect harness to provide out-of-the-box integrations for hundreds of third-party products across categories such as DevOps, databases, big data, and SaaS applications.

Service Change: A maximum of 100 file systems may be attached to any particular snapshot policy.

Date Announced: August 5, 2023

Date in Effect: August 7, 2023

Details: Starting August 7, 2023, a new service limit will be introduced to limit the total number of file systems attached to a snapshot policy. This change will allow up to 100 file systems to be attached per snapshot policy per tenant per availability domain.

Does this impact me? If you're planning to attach more than 100 file systems to any particular snapshot policy, then you won't be able to do so after August 7, 2023. Any existing tenants who have more than 100 file systems attached per snapshot policy before August 7, 2023 will be given an exception. No exceptions will be given after August 7, 2023.

What do I need to do? If you need to attach more than 100 file systems to a snapshot policy, then create a second snapshot policy or use any other existing snapshot policy. You can create 100 snapshot policy per tenant per availability domain. You can still generate policy-based snapshots for file systems, but you might have to use more than one snapshot policy.

Service Change: The COMPUTE_INSTANCE member type in DrProtectionGroupMemberType is getting deprecated and will no longer be supported.

Date Announced: October 31, 2023

Date in Effect: October 31, 2024.

Migrate to one of the new instance types before the effective deprecation date.

Does this impact me? If you use the COMPUTE_INSTANCE member type in your DR configuration, this change affects you. Make sure that you migrate to one of the new instance types before the effective deprecation date.

What do I need to do? To migrate from an existing COMPUTE_INSTANCE to one of the new instance types, follow these instructions.

Service Change: Fn Project CLI version 0.5.x (and earlier) will no longer be supported.

Date Announced: June 29, 2021

Date in Effect: August 1, 2021

Details: Starting August 1, 2021, Fn Project CLI version 0.5.x (and earlier) will no longer work with OCI Functions.

Does this impact me? If you are currently using Fn Project CLI version 0.5.x (or earlier), you will need to upgrade to Fn Project CLI version 0.6.x (or later).

What do I need to do? Upgrade to Fn Project CLI version 0.6.x (or later), by following the instructions in Upgrading the Fn Project CLI.

Service Change: From December 15, 2021, the Fn Project FDK (Function Development Kit) build-time and runtime base images, with the exception of the FDK for Python 3.7, are built on top of the Oracle Linux 8 slim distribution. The Alpine/Debian FDK base images are deprecated.

Date Announced: November 15, 2021

Date in Effect: December 15, 2021

Details: Starting December 15, 2021, most of the Fn Project FDK (Function Development Kit) build-time and runtime base images for the different supported languages are built on top of the Oracle Linux 8 slim distribution (instead of the Alpine and Debian Linux distributions). New functions you deploy will use these Oracle Linux 8 FDK base images. The only exceptions are the FDK build-time and runtime base images for Python 3.7, which continue to be built on top of the Debian Linux distribution.

The Alpine/Debian Linux distributions and the Oracle Linux 8 slim distribution have different package managers. After the transition to the Oracle Linux 8 FDK base images, the temporary Dockerfile created by OCI Functions when deploying new functions contains Oracle Linux 8 package manager commands.

Does this impact me?

For existing functions already deployed to OCI Functions:

• If OCI Functions uses the settings in a function's func.yaml file to create a temporary Dockerfile containing the instructions from which to build the function's Docker image, the function will build and deploy without errors. The temporary Dockerfile includes the correct Oracle Linux 8 package manager commands.
• If you have created a custom Dockerfile for a function (for example, by modifying the Dockerfile that OCI Functions creates, and setting runtime: docker in the function's func.yaml file), the function might now build and deploy with errors such as missing apt-get .... The errors occur if the custom Dockerfile includes Alpine/Debian package manager commands.

What do I need to do? If you have created custom Dockerfiles that contain Alpine/Debian package manager commands, replace those commands with Oracle Linux 8 package manager commands.

If you cannot immediately start using the Oracle Linux 8 FDK base images because you have functions that still require the Alpine or Debian Linux distributions, there is a temporary workaround. Until December 15, 2022, the Alpine/Debian FDK base images remain available but with modified image tags. You can update custom Dockerfiles to use the deprecated Alpine/Debian FDK base images instead of the Oracle Linux 8 base images by explicitly specifying the modified image tags. See My functions still require the Alpine and Debian Linux distributions. Is there a temporary workaround?.

Service Change: The Oracle Cloud Infrastructure Identity and Access Management Audit Events APIs and some reports templates for the Reports APIs, which you can use with IAM identity domains, will be deprecated.

Date Announced: May 15, 2023

Date in Effect: May 15, 2024

Details: Starting May 15, 2024, the IAM APIs for AuditEvents and certain reports templates in the Reports APIs no longer work with IAM.

Does this impact me? If you're currently using IAM APIs for AuditEvents, and the APIs for Reports which are based on AuditEvents, you will need to use the OCI Audit service APIs instead.

What do I need to do? You can now use OCI Audit APIs.

Service Change: Effective July 15, 2022, the CreateFleet API will require the custom log OCID in the inventoryLog property.

Date Announced: April 15, 2022

Date in Effect: July 15, 2022

Details: As of March 30, 2022, JMS uses the Oracle Cloud Infrastructure Logging service to store inventory and operation logs. Inventory logs are custom logs that store the Java Runtime inventory and usage related information reported from the hosts by the Management Agent. With this change, the CreateFleet API includes an additional property, inventoryLog, to specify the custom log to use.

What do I need to do? Existing fleets must be migrated using the UpdateFleet API by July 15, 2022. After July 15, 2022 the inventoryLog property of CreateFleet API will be a required parameter. See the CreateFleet and UpdateFleet operations for details. Agents need to be on 220302.1455 or later.

Starting October 26, 2022, the Detect Language APIs of version 20221001 were deprecated. From October 10, 2023, onwards the deprecated APIs will be unavailable.

Starting October 26, 2022, the BatchDetect Language APIs have a new supported API version of 20221001. With the introduction of API version 20221001, the following classes have been removed and replaced with the common class, com.oracle.bmc.ailanguage.model.TextDocument.

Service Change: The DB System backup retention period has been reduced from 10,000 to 365 days.

Date Announced: September 2020

Date in Effect: October 2020

Details:The DB System backup retention period has been reduced from 10,000 to 365 days.

Does this impact me? No.

What do I need to do? Nothing.

The Oracle Cloud Infrastructure's Network Load Balancer ListNetworkLoadBalancerProtocol API is deprecated as of January 12, 2022. Support for ListNetworkLoadBalancerProtocol ends on March 1, 2023. See ListenerDetails for the current list of supported protocol values.

Service Change: Terraform 0.11 is being deprecated.

Date Announced: August 23, 2021

Date in Effect: September 1, 2021

Details: Oracle Resource Manager removes support for Terraform 0.11 on September 1, 2021.

How does this change affect my service?

When support of Terraform 0.11 is removed, your service is affected in the following ways:

• Resource Manager does not allow creation of new stacks with Terraform 0.11.
• Oracle does not address support tickets for stacks that use Terraform 0.11. Customers are asked to upgrade their stacks to a supported version.

Are there any required actions I need to take?

If you have no need to manage the already provisioned infrastructure using Resource Manager, then no action is required.

To continue managing the provisioned infrastructure using Resource Manager, upgrade your 0.11 stacks to 0.12 or later. For instructions on upgrading stacks, see Upgrading a Stack to a Later Terraform Version.

Service Change: Oracle Cloud Infrastructure's Service Mesh APIs of version 20210930 were deprecated on December 14, 2022.

Date Announced: December 14, 2022

Date in Effect: December 15, 2023

Details: Starting December 14, 2022, Service Mesh APIs of version 20210930 was deprecated. From December 15, 2023, onwards the deprecated APIs will be unavailable.

• Update/Delete/Get/List Operations on any resources created by deprecated APIs will be supported by the new APIs (version 20220615).
• OCI SDKs and command line tools that were released before December 14, 2022, are limited to the features of the deprecated resource model (version 20210930).

List of unsupported and replacement APIs

Service Change: oci_identity_swift_passwords data source and oci_identity_swift_password resource are deprecated.

Date Announced: June 14, 2018

Date in Effect: June 7, 2023

Details: OCI Terraform Provider no longer supports the oci_identity_swift_passwords data source and oci_identity_swift_password resource.

Does this impact me? Yes, if you haven't yet migrated to the resources oci_identity_auth_token and oci_identity_auth_tokens.

Are there any required actions I need to take? Import the deprecated oci_identity_swift_password resource into oci_identity_auth_token. For the credential ID, use the swift password ID. Example:

terraform import oci_identity_auth_token.resource_identifier "users/ocid1.user.oc1..exampleid/authTokens/ocid1.credential.oc1.exampleid"

Service Change: Oracle Cloud Infrastructure Vision’s document analysis APIs were deprecated January 30, 2023. The document analysis functionality is now offered through the Oracle Cloud Infrastructure Document Understanding service.

Date Announced: January 30, 2023

Date in Effect: January 31, 2024

Details:

The following APIs were deprecated January 10, 2023:

• AnalyzeDocument
• CreateDocumentJob
• GetDocumentJob
• CancelDocumentJob

Any output data stored in an Object Storage bucket that resulted from previous Document Jobs will remain accessible after Document API deprecation. From January 31, 2024 onwards, the deprecated APIs will be unavailable in the Oracle Cloud Infrastructure Vision service.

Does this impact me? This change impacts customers using the document analysis functionality in the Oracle Cloud Infrastructure Vision service.

What do I need to do? Customers using the document analysis functionality in the Oracle Cloud Infrastructure Vision service should instead use the document analysis functionality offered through the Oracle Cloud Infrastructure Document Understanding service.