2026.1 version release (January 2026)
New features
-
License Report
Introducing the full release of an administrative central report to monitor source sizing usage summaries and historical trends across the entire Delphix platform, including Continuous Data, Continuous Compliance, and Elastic Data. Users will notice that a much wider set of data types is now supported in the full release.
-
Note: Delphix Telemetry configuration is required to enable this report.
-
-
Delphix MCP Server (Preview)
Introducing a preview release of the MCP Server, which enables users to query information about their Delphix Platform via DCT APIs. This is a READ-only implementation and does not leverage our embedded Delphix AI Services. For additional information, see the MCP Server GitHub repository.
-
Perforce App Switcher
Introducing a navigation tool that allows users to move between and discover different Perforce software offerings.
-
Documentation Help updates
Perforce Search has been renamed to Documentation Help, providing better clarity on its functionality. In addition, this feature will be enabled by default. It can be disabled within the AI Settings page.
-
AES-256 GCM encryption support
Sensitive data stored within DCT, such as engine, vault, and connector passwords, is now encrypted using AES-256 in GCM mode.
-
Continuous Data Parity
All available Oracle UI and API features in Continuous Data are now fully supported in Data Control Tower. The list below outlines the remaining set of Oracle features and other improvements migrated as part of the 2026.1 release.
-
CDB management
The ability to manage CDBs is now available in DCT. This includes the attachment and detachment of CDBs, CDB policy management, and the viewing of CDB status information.
-
Target Environment search
Users can now search from a list of available targets during VDB provisioning.
-
Snapshot SCN & date ranges
In the timeline view, users can now view the SCN & date range for each snapshot if it's available.
-
Custom Environment Variables support for hooks
Define custom environment variables for their dataset hooks and manage them directly from the Hooks tab within the detail view of their VDBs and dSources. Select from two credential types for these variables: either standard password credentials or enterprise password vault credentials. Support for these custom variables is fully integrated into the Add/Edit Hook dialog in the UI, enabling seamless creation and updates.
-
-
New and improved APIs and CLIs
New endpoints and commands have been introduced or heavily modified. Complete documentation can be found within the API references page or in the DCT Toolkit's Command references page.
-
APIs for TDE OKV multiple OKV_HOME per target host support
Multiple OKV clients per host are now supported. Different databases running on the same host can use either the same or different OKV clients to connect to one or more OKV servers, and work with the same or different wallets. This replaces the previous OKV implementation, which allowed only a single OKV client per host. Under the old model, all databases on a host were required to share one OKV client and connect to the same OKV server using a single wallet. Visit the API references for 2026.1.
-
Fixed issues
| Issue ID | Description |
| APIGW-14634 | Fixed an issue where the dSource Timeline > Snapshot > Provision VDB action would bring the user to a Source Selection screen rather than the Target Environment screen. |
| APIGW-14637 | Fixed an issue where VDB Refreshes from Bookmarks using the UI will fail with the following error messages: 'No elements in sequence' and 'Variable [$snapshotID] of required type [NonEmptyString!] was not provided'. |
| APIGW-15215 | Fixed an issue where running a virtualization Policy’s Apply job on a replicated VDB never completes. |
| APIGW-15293 | Fixed an issue where a Policy Apply job failed with an internal error due to sharing a name with another DCT-managed policy. |
Known issues
| Issue ID | Description |
| APIGW-13509 | An error occurs when deleting engine-owned policies from DCT, despite a successful deletion. You can ignore the warning as a fix is being worked on. |
| APIGW-13599 | No warning or alert occurs when a data admin login fails for registered Continuous Compliance Engines. |
| APIGW-13711 | Policy Create or Update APIs do not validate CRON expressions. |
| APIGW-14229 | Operations do not show Actions started by engine-side policy workers. |
| APIGW-14517 | Frequent DCT APIs made against the Continuous Data and Compliance Engines cause high CPU and responsiveness issues. |
| APIGW-14545 | Replication profiles are not properly deleted from DCT. |
Deprecation/end-of-life notice
-
PostgreSQL 12.x and 13.x external databases no longer supported
Starting with DCT version 2026.1, PostgreSQL 12.x and 13.x external databases are no longer supported. If an external database is used, you must upgrade it to a supported version before upgrading to DCT 2026.1. In 18 months, in December of 2027, PostgreSQL 12.x and 13.x external databases will be end-of-life in DCT, meaning no versions will support their use.