Delphix Continuous Data Engine 2026.6.0.0 and later automatically detects Oracle Data Guard configurations and models each one as a Data Guard group. You choose which database role SnapSync continues from: primary, standby, or no preference. After a switchover or failover, the next SnapSync detaches the dSource and reattaches it to the member that now holds the chosen role, unless syncFrom is NO_PREFERENCE or the group is disabled. A dSource linked to a CDB is not moved.

For example, you can configure SnapSync to always run from the physical standby database, which offloads backup I/O from the production primary. After a planned or unplanned role change, Delphix follows the correct member on the next SnapSync.

You manage Data Guard groups through the Delphix Engine API and CLI only. The Continuous Data UI does not support Data Guard groups. Data Guard support in DCT (API and UI) will be available in the DCT 2026.6.0 release.

This feature is always on and changes the behavior of existing dSources on Data Guard databases. Upgrading does not create Data Guard groups. Delphix creates the group for an existing dSource the next time you refresh its environment, link another dSource in the same Data Guard configuration, or run refreshDgRoles. SnapSync does not create groups. Detection during an environment refresh requires the environment OS user to be a member of the OSDBA or OSBACKUPDBA group. When Delphix creates the group during an environment refresh, it sets syncFrom to the role of the database that's already linked. When it creates the group while linking a dSource or running refreshDgRoles, it sets syncFrom to the role of the database you link or run refreshDgRoles on. Delphix does not change syncFrom afterward. After a later switchover or failover, SnapSync moves the dSource to the member that holds that original role, which earlier versions did not do. See Create the Data Guard group for a dSource linked before the upgrade.

Setting syncFrom to NO_PREFERENCE or enabled to false takes effect immediately but does not last. A disabled group is re-enabled the next time Delphix detects the group during an environment refresh. Linking a dSource to a database that Delphix hasn't yet added to the group can also re-enable it; linking a database that's already in the group does not. If a member of the group is linked as a dSource, Delphix also replaces NO_PREFERENCE with the current role of a linked member the next time it detects the group during an environment refresh, when a dSource is linked, or when you run refreshDgRoles on a linked member while the group is enabled. For a CDB, only a linked PDB in that CDB counts as linked; a dSource linked to the CDB itself does not. For more information, see Configure and manage Oracle Data Guard groups.

Key concepts

Concept

Description

Data Guard group

Delphix object that represents one Oracle Data Guard configuration. Delphix names the group DATAGUARD_GROUP- followed by each member's db_unique_name, joined by hyphens. For example: DATAGUARD_GROUP-DBOMPR5F392E-DBOMST5F392E.

Member

Database in a Data Guard group. Each member has one of the following roles:

  • PRIMARY: the primary database.

  • STANDBY: a physical standby database.

  • INVALID: a logical, snapshot, or far-sync standby. These members are not eligible for SnapSync and Delphix never selects them.

Resolved and unresolved members

A member is resolved when its environment has been added to the Delphix Engine. A member is unresolved when Delphix knows it only by its db_unique_name because its environment has not been added to the Delphix Engine.

Sync-from role (syncFrom)

Group setting that controls which member SnapSync continues from: PRIMARY, STANDBY, or NO_PREFERENCE.

  • syncFrom is a preference, not a guarantee. If no member holds the chosen role, SnapSync continues from the current member. The job does not show a warning.

  • With NO_PREFERENCE, Delphix does not move the dSource, even after a role change. If a member of the group is linked as a dSource, Delphix replaces NO_PREFERENCE with the current role of a linked member the next time it detects the group during an environment refresh, when a dSource is linked, or when you run refreshDgRoles on a linked member while the group is enabled. For a CDB, only a linked PDB in that CDB counts as linked.

Enabled (enabled)

Group setting that turns Data Guard-aware SnapSync on or off. When a group is disabled, SnapSync behaves as if the group does not exist. A disabled group is re-enabled the next time Delphix detects the group during an environment refresh. Linking a dSource to a database that Delphix hasn't yet added to the group can also re-enable it; linking a database that's already in the group does not.

PDBs

A PDB is never a member of a Data Guard group. PDB dSources are associated with their CDB's group and follow the CDB.

When roles are re-read and when the dSource moves

Several operations re-read member roles, but only SnapSync moves the dSource to the member that holds the syncFrom role.

Operation

Re-reads all member roles?

Moves dSource to the syncFrom member?

SnapSync

Yes, when the group is enabled and syncFrom is PRIMARY or STANDBY

Yes, when the group is enabled and syncFrom is PRIMARY or STANDBY — detaches and reattaches to the member holding the syncFrom role. A dSource linked to a CDB is not moved.

Environment refresh

Yes

No

refreshDgRoles API

Yes, when the group is enabled

No

LogSync

Reads only the currently connected database's role

No — raises WARNING fault "LogSync DG role mismatch detected (pending SnapSync)"

"Environment refresh" in this topic means the Refresh action in the UI, CLI, or API. Adding an environment and the lightweightDiscover API operation also detect Data Guard. Automatic host refreshes, such as those after an upgrade or when an environment is enabled, don't.

How Delphix detects a Data Guard configuration

Delphix detects Data Guard configurations in two ways.

When you add or refresh an environment

  • Delphix connects to each database by OS authentication and reads its Data Guard role and configuration from v$database and v$dataguard_config.

  • The environment OS user must belong to the OSDBA or OSBACKUPDBA group, which provides SYSDBA or SYSBACKUP access. If it does not, Delphix skips Data Guard detection for that database without raising an error. If Delphix has not yet checked the OS user's privileges for that Oracle home, it skips the database and the job shows a warning that SYSDBA or SYSBACKUP is required.

  • VDBs and auxiliary CDBs are excluded from detection. PDBs are not detected separately; they are covered through their CDB.

  • Members whose environments have not been added to the Delphix Engine are added as unresolved members.

  • Delphix parses the DG_CONFIG value of the LOG_ARCHIVE_CONFIG parameter.

  • Delphix connects to each peer database listed in DG_CONFIG. Peers whose environments haven't been added to the Delphix Engine, are disabled, or can't be reached are skipped.

  • Delphix creates a group only if at least two members, including the linked database, are reachable. Linking a dSource to a CDB alone does not create a group; a PDB in that CDB, or in another CDB in the same Data Guard configuration, must be linked.

Group lifecycle

  • Creation: Delphix creates Data Guard groups automatically when it detects a configuration.

  • Role updates: Delphix updates member roles at environment refresh, at dSource link, when you run refreshDgRoles (when the group is enabled), and at SnapSync (when the group is enabled and syncFrom is PRIMARY or STANDBY).

  • Automatic deletion: Delphix deletes a group when DG_CONFIG is removed or when the group drops below two members.

  • Deletion with a dSource: Delphix deletes a group when the dSource of any member is deleted, including a PDB dSource whose CDB is a member. It re-creates the group at the next environment refresh, dSource link, or refreshDgRoles.

  • Re-created groups: A group that Delphix re-creates after any deletion uses default settings, so you must reapply any changes you made to syncFrom, skipFullSync, description, or enabled.

  • Re-enabling: A disabled group is re-enabled the next time Delphix detects the group during an environment refresh. Linking a dSource to a database that Delphix hasn't yet added to the group can also re-enable it; linking a database that's already in the group does not.

Prerequisites

  • Each Oracle database must have a unique DB_UNIQUE_NAME across all environments added to the Delphix Engine. Do not add environments whose databases share a DB_UNIQUE_NAME.

  • The environment OS user must belong to the OSDBA or OSBACKUPDBA group for Data Guard detection to run on a database when you add or refresh an environment.

  • At least two eligible members must be reachable for a group to be created when you link a dSource.

  • API version 1.11.50 or later is required for dataguardInfo. API version 1.11.52 or later is required for dataguardGroupRef and the Data Guard group list endpoints.

Supported configurations and limitations

  • Single-instance, RAC, and CDB databases can be Data Guard group members. PDB dSources follow their CDB.

  • Only PRIMARY and physical standby members are eligible for SnapSync. Logical, snapshot, and far-sync standbys have the role INVALID and are never selected.

  • Data Guard groups are managed through the Delphix Engine API and CLI only. There is no Delphix Engine UI.

  • Data Guard support in DCT (API and UI) will be available in the DCT 2026.6.0 release.

  • dataguardInfo is returned only when you get a single source config. It is not returned by the source config list endpoint.

  • A dSource linked to a CDB is not moved by SnapSync. Non-multitenant and PDB dSources are moved. A PDB dSource moves to the PDB with the same name in the target CDB. If the target CDB has no PDB with that name, the dSource is not moved.

  • When SnapSync moves a PDB dSource to a CDB that is not yet linked, Delphix links that CDB automatically, so a new CDB dSource appears.

  • If a dSource link or refreshDgRoles fails with an error that a database "already belongs to a different DataGuard group" or "already belongs to an existing DataGuard group", check that every database has a unique DB_UNIQUE_NAME across all environments, and that the database is not still configured in another Data Guard configuration.

Last updated
Nov 19, 2026