In 2026 the Database Tools service introduced a new data plane called Database Tools Runtime supported by all the standard OCI interfaces such as the OCI CLI, SDK, and Terraform provider. This is an introduction to the new data plane with some examples of executing statements against databases in the cloud.
The Database Tools MCP server supports role-based access control for tools which allows for users or groups to be granted access to only specific MCP tools. In this example we will look at one way to configure tools with IDCS application roles and what the end-user might see once configured.
You can use a Database Tools identity in Oracle Cloud Infrastructure (OCI) to give Oracle Databases access to OCI resources through something called a "resource principal". There are a few configuration requirements and the use case is interesting in general, so let's check it out!
With Oracle's Java Database Connectivity (JDBC) driver starting with 23ai it is now possible to provide the configuration of a connection to Oracle Database using the opaque identifier of a Database Tools connection.
In the past few posts I looked at using the Oracle Cloud Infrastructure (OCI) services related to creating database connections in the cloud. Here I want to show how you can build on that by creating secrets in a vault using the OCI provider.
In this post we will look at setting up a Database Tools connection resource in Oracle Cloud Infrastructure (OCI) using the OCI Terraform provider. Database Tools connections in OCI are first-class resources just like other cloud primitives such as virtual cloud networks (VCN), compute instances, or databases.
TL/DR: To use OCI Database Tools (DBTools) Connections to connect to ADB with a public IP and access control list (ACL), DBTools requires the use of a DBTools Private Endpoint (PE).
TL/DR: if you are an Oracle Cloud Infrastructure (OCI) customer running Oracle Database or MySQL in OCI, use Database Tools (DBTools) private endpoints and connections to simplify database access in the cloud.