2025.6 version release (November 2025)

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'. This issue can be worked around by refreshing using another source, such as a snapshot or a timestamp, or triggering the refresh from a bookmark using the API or CLI. This issue will be resolved in the 2026.1 release.

New features

  • Full Continuous Data Feature Parity for Oracle

    The DCT UI, API, and CLI can now be used to manage the test data management practices of your Oracle data types. This includes the environment creation, dSource linking, snapshot ingestion, and VDB provisions. We encourage Delphix administrators to install DCT and migrate their day-to-day Oracle management to DCT.

  • DCT unlimited engine connections

    The engine connectivity limits have been removed from all Data Control Tower tiers. Starting with 2025.6, you can connect any number of Delphix engines to your DCT instance. This grants full data management and reporting capabilities by simply installing and connecting your engines. As a reminder, DCT Core is available to all Delphix customers.

  • Perforce Intelligence Search

    Find accurate answers from within the DCT UI using natural-language search and generative AI across our official documentation and knowledge base content. This AI co-pilot feature must be enabled manually, and it communicates with a hosted Perforce AI service from the user’s browser.

  • ServiceNow Spoke – Enable Catalog user

    Introduced a new catalog item called Enable Catalog User that enables a self-service workflow for users to manage their access to the Delphix ServiceNow Catalog. Administrators or IT teams no longer need to manage individual user access! Check out the Ecosystem documentation for more information about ServiceNow and our other DevOps Integrations.

  • Dedicated storage and APIs for Oracle Staging Push CDBs

    Oracle Staging Push CDBs now have dedicated handling in DCT. Staging Push CDBs are stored separately from standard dSources and exposed through new Staging Push APIs, so you can list and manage them with operations such as enable, disable, and delete. This change prevents Staging Push CDBs from appearing as regular dSources in the UI and removes incorrect options, such as snapshot actions, for these objects.

  • Data management enhancements for Oracle Staging Push CDBs

    CDB and StagingCDB detail pages now include a Data management tab with snapsync, logsync, and no-logging tiles, along with updated dialogs for modifying these settings, providing a clearer and more accurate management experience. In addition, the detail page now includes a shared Source tab with Source database and Source environment tiles, each with edit dialogs. A conditional Custom environment variables tile is also available, using the updated shared component to support vCDB updates.

    • A range of new operations are now available in the Actions menu for vCDBs, Linked CDBs, and Staging CDBs (Enable/Disable, Start/Stop, Attach/Detach, etc.).

  • Incremental V2P APIs for Oracle

    DCT now provides Oracle APIs for incremental V2P from VDB and vPDB sources on physical file system or ASM. These APIs make sure a new physical database created via V2P can be kept in sync with a stand-in production VDB or vPDB by incrementally applying changes based on snapshot, timestamp, bookmark, or location, which is valuable for ransomware recovery and disaster recovery scenarios.

    • This approach significantly reduces cutover time compared to traditional full V2P operations and supports Oracle 12.1.0.1.0 and later. With this release, the functionality is available via API only and does not support RAC sources, physical database sources, PDB exports to non-CDB targets, or exports to multiple ASM disk groups.

  • New and improved APIs and CLIs

    The following endpoints and commands have been introduced or heavily modified. Complete documentation can be found within the Swagger API or the DCT Toolkit’s.

    • /connectors/{connectorId}/properties: Minor updates.

    • /job-orchestrators/*: APIs introduced to assist group Compliance engines (nodes) together. Part of the Centralized DCT Compliance (Preview) initiative.

    • /masking-file-downloads/* and /reporting/{executionID}/*: APIs introduced to generate saveable PDF reports. Part of the Compliance Reports for Database Sources (Preview).

    • /toolkits/schema_definitions: New capability to grab a Data Connector’s schema.

    • /vdbs/{vdbID}/export_cleanup (Oracle Only) and /vdbs/{vdbID}/export_finalize: New APIs to support the Oracle and SQL Server incremental Virtual to Physical (V2P) capabilities.

  • Snapshot administration

    For the Provision, Snapshot Timeline Provision, and Refresh of a VDB, there will be an additional check that will identify whether the selected snapshot can be provisioned or not. If the snapshot cannot be provisioned, DCT will not allow you to proceed with the flow.

  • License Report (Preview)

    An administrative central report to monitor source sizing usage summaries and historical trends across the entire Delphix platform, including Continuous Data, Continuous Compliance, Hyperscale Compliance, and their associated add-on modules. Users will notice that a much wider set of data types are now supported in this version release.

  • PaaS Data Automation (Preview)

    Continuing our larger multi-cloud TDM initiative, DCT now offers native orchestration capabilities (ie, no virtualization) for AWS RDS Oracle, AWS RDS PostgreSQL, and Azure SQL Server MI. This solution is critical to help data administrators safely move sensitive data to de-sensitized downstream environments.

  • Centralized DCT Compliance (Preview)

    This release introduces a preview of Compliance on DCT, which rearchitects the continuous compliance experience by making DCT the source of truth for compliance artifacts. This major set of enhancements enables centralized management, maintains referential integrity across data sources by managing the deployment of global algorithms, and delivers all the platform benefits of DCT. This is a feature-flagged release, so please reach out to your account team to get access and share feedback.

  • Compliance Reports for Database Sources (Preview)

    Data Control Tower now aggregates table-wise statistics and rule-set assignments with error reports from database compliance jobs run on the Continuous Compliance Engine and presents them with an improved user experience. This enhancement goes beyond the on-engine view by providing more detailed insights and longer retention, with a default persistence of one year. DCT also introduces on-demand PDF generation for these reports, making it easier to share and archive critical compliance information.

    If you encounter issues or have feedback about a feature preview, contact your Delphix Account Team. Your input during the preview stage helps guide future development and general availability. Please note, Delphix Support does not support feature flag capabilities.

Fixed issues

Issue ID Description
APIGW-11450 Fixed an issue where tags on policies like Refresh, Restore, Snapshot, etc. were not persisting across a restart of DCT.
APIGW-13885 Fixed the permission model for dSources and VDB policies.
APIGW-13929 Fixed a bookmark issue when engines registered in DCT have empty name(s) in Self-Service bookmarks.
APIGW-14204 The self-service-data-operator role now contains permissions to start, stop, enable and disable VDB Groups.
APIGW-14505 Fixed an issue where Login via SAML/SSO or LDAP no longer erases login_groups tag/Access Group mapping when group attribute mapping is not enabled.

Known issues

Issue ID Description
APIGW-13509 An error occurs when deleting engine-owned policies from DCT, despite succeeding in the deletion.
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 need enforced validation of CRON expressions.
APIGW-14229 Operations do not show Actions started by engine-side policy workers.
APIGW-14517 DCT is running APIs against Continuous Data and Compliance Engines too frequently, which causes high CPU and responsiveness issues.
APIGW-14545 Replication profiles are not properly deleting from DCT.
APIGW-14634 Policy Apply jobs fail with an internal error.
APIGW-14637 Virtualization-policy Apply job on incorrect targets never complete.
APIGW-15215 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'. This issue can be worked around by refreshing using another source, such as a snapshot or a timestamp, or triggering the refresh from a bookmark using the API or CLI. This issue will be resolved in the 2026.1 release.

Deprecated and end-of-life notices

PostgreSQL 12.x and 13.x external database deprecation

  • For Kubernetes and OpenShift deployments, external databases running PostgreSQL 12.x or PostgreSQL 13.x remain supported in DCT 2025.6 but are now deprecated. Support for these versions will be removed in DCT 2026.1, which is the end of support release for PostgreSQL 12.x and 13.x external databases.

    • Customers using PostgreSQL 12.x or 13.x for the external DCT database must upgrade to a supported PostgreSQL version (14.x or 15.x) before upgrading to DCT 2026.1.

    • Appliance (OVA) deployments are not affected and ship with PostgreSQL 14.x. Data Control Tower also provides PostgreSQL 14.x by default, so environments using the default database or a supported external PostgreSQL version are not impacted.