Additional requirements for Source environments when Oracle Database Vault is enabled

When Oracle Database Vault (DV) is enabled on the source database, certain operations are restricted even for users with SYSDBA privileges. Specifically, the SYSDBA user cannot disable system triggers or modify the recovery destination during database recovery operations without explicit permissions.

To ensure proper functionality during dSource operations, such as linking or snapshotting, the necessary privileges must be granted to the SYSDBA user in advance.

Sample Pre-Sync Hook Scripts

Below is an example of pre-sync hook script designed for use with a multitenant Oracle Database that has Database Vault enabled:

# Pre-Sync Hook (example)

sqlplus "<database_vault_owner_username>/<password>" <<EOF
ALTER SESSION SET CONTAINER = CDB$ROOT;

SPOOL /work/dv_patch_\${DELPHIX_DATABASE_UNIQUE_NAME}.log
SHOW USER

GRANT DV_PATCH_ADMIN TO SYS CONTAINER=ALL;
SPOOL OFF

EXIT
EOF

Sample Post-Sync Hook Scripts

Below is an example of post-sync hook script designed for use with a multitenant Oracle Database that has Database Vault enabled:

# Post-Sync Hook (example)

sqlplus "<database_vault_owner_username>/<password>" <<EOF
ALTER SESSION SET CONTAINER = CDB$ROOT;

SPOOL /work/dv_patch_\${DELPHIX_DATABASE_UNIQUE_NAME}.log
SHOW USER

REVOKE DV_PATCH_ADMIN TO SYS CONTAINER=ALL;

SPOOL OFF
EXIT
EOF