Overview

The Hyperscale UI is Controlled Availability, meaning that Delphix highly encourages interested customers to reach out to Delphix Product and Engineering for a guided onboarding. Please contact your account team if interested. 

To disambiguate execution flow nuances between Compliance Engines, Hyperscale Orchestrators, and DCT, refer to the following definitions:Hyperscale job execution
From the 2026.3 release, standard OTF jobs designed for Compliance Engines can be executed as Hyperscale jobs after enabling Hyperscale and configuring the required Hyperscale-specific parameters.

DCT has the ability to connect to one or more Hyperscale Compliance Orchestrators with one-to-mapping with Job Orchestrator, to serve as a complimentary user interface. The current Compliance Engine/Hyperscale Orchestrator/DCT workflow is as follows:

  1. Build the foundational objects (rule sets, connectors, inventories, OTF job etc.) within the Compliance Engine.

  2. Register the Hyperscale orchestrator under a Job Orchestrator. Ensure that the required mount points are already configured on the Hyperscale instance.

  3. Enable and execute the standard Compliance Engine jobs as Hyperscale, which requires the configuration of certain Hyperscale-specific attributes. You will have the option to further refine the job details such as defining table-specific masking parameters.

  4. DCT will recognize this job execution and present the execution details under the specific Hyperscale Orchestrator's Details page.

Prerequisites

  • Hyperscale Orchestrator version 2026.3.0 or later.

  • A staging area (mount point) configured in the Hyperscale Orchestrator before registering it in DCT.

  • All Compliance Engines added to the Hyperscale Orchestrator must be configured with access to the staging area.

Limitations

  • Only the Oracle connector is supported for Hyperscale execution in this 2026.4 release.

  • Hyperscale support bundle downloads are not available from the DCT UI.

  • Objects created during Hyperscale job execution are not cleaned up automatically after the job completes. These objects are retained for diagnosability purposes.

  • The sql_loader option cannot be configured through the DCT UI either at the table level or at the job level. The sql_loader option passes parameters to the Oracle Client to control how data is loaded into the target database.

Related topics

Implementation introduction

Managing Hyperscale jobs iņ DCT

Last updated
Oct 14, 2026