Service Change Announcements
This section includes details about Oracle Cloud Infrastructure breaking changes such as deprecated features, deprecated APIs, and service behavior changes.
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.
Oracle Cloud Infrastructure's Autonomous Data Warehouse APIs were deprecated on Feb. 15, 2019.
Important! Support for these Autonomous Data Warehouse APIs will end on Jul. 1, 2020. Oracle recommends that you migrate your database workloads to the replacement APIs as soon as possible.
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 Cloud Service instances to the new resource model APIs as soon as possible. Converting to the new resource model does not involve any system downtime.
|Unsupported API||Replacement APIs|
|LaunchDbSystem (deprecated for Exadata systems only)||CreateCloudExadataInfrastructure and CreateCloudVmCluster|
|ListDbSystems (deprecated for Exadata systems only)||ListCloudExadataInfrastructures and ListCloudVmClusters|
|GetDbSystem (deprecated for Exadata systems only)||GetCloudExadataInfrastructure and GetCloudVmCluster|
|ChangeDbSystemCompartment (deprecated for Exadata systems only)||ChangeCloudExadataInfrastructureCompartment and ChangeCloudVmClusterCompartment|
|UpdateDbSystem (deprecated for Exadata systems only)||UpdateCloudExadataInfrastructure and UpdateCloudVmCluster|
|GetExadataIormConfig (deprecated for Exadata systems only)||GetCloudVmClusterIormConfig|
|UpdateExadataIormConfig (Exadata systems only)||UpdateCloudVmClusterIormConfig|
|TerminateDbSystem (deprecated for Exadata systems only)||DeleteCloudExadataInfrastructure and DeleteCloudVmCluster|
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
Console users are automatically migrated to the latest resource model (version
- OCI SDKs and command line tools that were released before October 6, 2021, are limited to the features of the deprecated resource model (version
- Database Migration Service Agent Kits that were downloaded before October 6, 2021, are limited to the features of the deprecated resource model (version
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: 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 Oracle 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 Oracle Functions when deploying new functions contains Oracle Linux 8 package manager commands.
Does this impact me?
For existing functions already deployed to Oracle Functions:
- If Oracle 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 Oracle
Functions creates, and setting
runtime: dockerin 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?.
Network Load Balancer
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.
This change does not affect any Resource Manager stacks created with Terraform 0.12, 0.13, 0.14, or 1.0.
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 Stacks from 0.11.x to 0.12.x.