---
slug: "oci-terraform-oci-9-0-0-breaking-change"
title: "Terraform OCI provider 9.0.0: breaking changes"
summary: "Release date for Terraform OCI provider 9.0.0: 2 Sep 2026. Removals or breaking changes listed in the release notes: 1."
cloud: "oci"
service: "Terraform OCI provider"
service_slug: "terraform-oci"
category: "iac_provider"
type: "breaking_change"
announced_date: "2026-09-02"
effective_date: "2026-09-02"
effective_precision: "day"
replacement: null
affected_versions: ["9.0.0"]
source_url: "https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0"
extra_source_urls: []
vendor_ref: "v9.0.0"
last_checked_at: "2026-11-12T09:55:31.026Z"
created_at: "2026-11-13T13:36:44.208Z"
updated_at: "2026-11-13T13:36:44.208Z"
url: "https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change"
short_url: "https://eolwatch.dev/i/i"
markdown_url: "https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change.md"
json_url: "https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change.json"
---

# Terraform OCI provider 9.0.0: breaking changes

Release date for Terraform OCI provider 9.0.0: 2 Sep 2026. Removals or breaking changes listed in the release notes: 1.

- Effective date: 2 Sep 2026
- Cloud: [OCI](https://eolwatch.dev/cloud/oci.md)
- Service: [Terraform OCI provider](https://eolwatch.dev/services/oci/terraform-oci.md)
- Type: Breaking change
- Category: [IaC provider](https://eolwatch.dev/categories/iac.md)
- Affected versions: 9.0.0
- Replacement: Not stated by vendor
- Announced: 2 Sep 2026
- Official source: [github.com](https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0)
- Last checked: 12 Nov 2026

## What breaks

Breaking changes listed in the release notes:

- Removed Terraform Support for distributed_database

## Who is affected

### Affected versions

- `9.0.0`

## What to do

1. Give the provider a version constraint in the `required_providers` block. HashiCorp recommends a version constraint for every provider a module depends on.
2. In a root module, also specify the maximum provider version, to avoid accidental upgrades to incompatible new versions. The `~>` operator is a shorthand that allows the rightmost component of a version to increment. Do not use `~>` or other maximum-version constraints in modules you intend to reuse across many configurations. Specify a minimum version there and let the root module manage the maximum version.
3. Commit the dependency lock file to version control with the configuration, so that Terraform always installs the same provider versions.
4. To adopt 9.0.0, change the version in the `required_providers` block and re-run `terraform init`. HashiCorp states that this upgrades the provider version in the lock file. Without a change, Terraform re-selects the version recorded in the lock file, even if a newer version has become available. With the `-upgrade` option, `terraform init` disregards the recorded selection and selects the newest available version matching the version constraint. The [release notes](https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0) list each removal or breaking change.
5. Review the changes Terraform made to the lock file in version control. If they are changes you made intentionally, send them through the usual code review process.

## Replacement

Not stated by vendor.

## Sources

- [Official source](https://github.com/oracle/terraform-provider-oci/releases/tag/v9.0.0) (github.com, Official)

Last checked against this source on 12 Nov 2026.

Page: https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change | JSON: https://eolwatch.dev/items/oci-terraform-oci-9-0-0-breaking-change.json

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published.