Skip to main content
Skip table of contents

Known issues

Version 9.0.0.0

Key

Summary

Workaround

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-84977

For RAC environments, export of an Oracle VDB to a database with a new unique name is not supported.

Perform the export with the same unique name as of the VDB and then manually change the physical database’s unique name.

DLPX-84423

Export operation does not retain the read-only mode in the newly converted physical database after an in-place conversion of a read-only Oracle VDB or vPDB

None

DLPX-84598

sysadmin user cannot view actions initiated by different sysadmin user

None

DLPX-84655

A false warning message that listener registration was not successful is posted when enabling a VDB or a vCDB, users can ignore this message.

Ignore the warning message.

DLPX-84679

Unable to add Staging push PDB if Staging Environment has more than one repository.

From the Add dSource Wizard dSource Configuration screen for Staging Push.

  • Before selecting PDB as the Database Type, select CDB.

  • Select the correct Staging Environment and repository.

  • Select PDB for the Database Type.

  • Now CDB will be shown under Container Database

  • Fill in the remaining PDB details

DLPX-85076


Instance init file is not copied to $ORACLE_BASE_CONFIG/dbs during staging push dSource linking

Specify the pfile parameter in the startup command as

pfile='/<MOUNT_BASE>/<DATABASE_UNIQUE_NAME>
/script/<DATABASE_SID>/init<DATABASE_SID>.ora'

Version 8.0.0.0

Key

Summary

Workaround

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-84679

Unable to add Staging push PDB if Staging Environment has more than one repository.

From the Add dSource Wizard dSource Configuration screen for Staging Push.

  • Before selecting PDB as the Database Type, select CDB.

  • Select the correct Staging Environment and repository.

  • Select PDB for the Database Type.

  • Now CDB will be shown under Container Database

  • Fill in the remaining PDB details

DLPX-85076

Instance init file is not copied to $ORACLE_BASE_CONFIG/dbs during staging push dSource linking

Specify the pfile parameter to startup command as

pfile parameter=/<MOUNT_BASE>/<DATABASE_UNIQUE_NAME>
/script/<DATABASE_SID>/init<DATABASE_SID>.ora

Version 7.0.0.0

Upgrades from versions < 6.0.17.0 to any version between 6.0.17.0 and 7.0.0.0 on a replication target engine may fail due to the management services being down, which will require a support call. This applies to “Delay the Reboot” or “Apply Now” upgrades.

Key

Summary

Workaround

DLPX-84255

In a Single Engine Continuous Vault product, adding a new Sybase dSource to a locked group may result in the background environment monitoring process to stop working.

No workaround.

DLPX-84495

If upgrading from versions < 6.0.17.0 to any version between 6.0.17.0 and 7.0.0.0, a support call is needed.

Call support.

DLPX-84679

Unable to add Staging push PDB if Staging Environment has more than one repository

From the Add dSource Wizard dSource Configuration screen for Staging Push.

  • Before selecting PDB as the Database Type, select CDB.

  • Select the correct Staging Environment and repository.

  • Select PDB for the Database Type.

  • Now CDB will be shown under Container Database

  • Fill in the remaining PDB details

DLPX-85076

Instance init file is not copied to $ORACLE_BASE_CONFIG/dbs during staging push dSource linking

Specify the pfile parameter to startup command as

pfile parameter=/<MOUNT_BASE>/<DATABASE_UNIQUE_NAME>/script/<DATABASE_SID>/init<DATABASE_SID>.ora

Version 6.0.17.0

Key

Summary

Workaround

DLPX-66860

For SSO/SAML, ADFS requires explicit rule to transform emailAddress attribute into nameid.

Create an explicit rule in ADFS that transforms the {{emailAddress}} attribute into a {{nameid}}. The rule type must be "Transform an incoming claim". The incoming claim type must be "Email address" and the outgoing claim type "Name ID". The nameid format must be "Email address".

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-83622

In 6.0.15.0 and 6.0.16.0, Fluentd gems from plugins were installed in the base Fluentd. These left over gems can cause Fluentd to fail post-upgrade.

No workaround.

DLPX-83643

After engine upgrade or after a disable and enable of a vPDB, the NFS version in GUI/API may be incorrect (if it's a vPDB in a vCDB, it was mounted with NFSv3 and now the host supports NFSv4 mounts). This condition corrects itself on the next refresh operation.

Perform a vPDB refresh operation to update the NFS protocol version to 4.

DLPX-83575

The port in the connection string for a vPDB in a Linked CDB may be shown incorrectly when it is registered to a non-default listener.

Use the port in the connection string of the CDB to connect.

Version 6.0.16.0

Key

Summary

Workaround

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-82448

Python2 has been deprecated and is being removed from the platform. During this removal, there are still trace artifacts of legacy Python versions being found on the engine.

No workaround.

DLPX-81559

After upgrading an Oracle VDB from 12c to 19c, the VDB refresh fails with "Failed to mount database instance" due to ORA-01130 or ORA-00201 errors.

Update the VDB parameters (either directly or via a VDB Config Template). For more information, please see KBA6234

DLPX-82169

Provisioning a TDE-enabled vPDB to a CDB with a different patch level than the source CDB will fail.

Patch the dSource to match the target and provision again. If this is not an option, run datapatch on the vPDB, update the timeflow in MDS to a CONFIGURED state, restart the vPDB, and run SnapSync. This second option requires an engineering escalation.

Version 6.0.15.0

Key

Summary

Workaround

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-81610

If a tablespace is encrypted before an incremental snapshot is taken, provisioning from that snapshot can lead to the tablespace containing partially unencrypted data, which will not be accessible.

Take a snapshot with parameter "Force Full Backup" and provision a new vPDB/VDB with this snapshot.

Version 6.0.14.0

Key

Summary

Workaround

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-80489

TDE-enabled vPDB provisions failing with LOCAL_AUTOLOGIN configuration

Use a regular autologin wallet in the target CDB.

DLPX-80822

vPDB provision from a fully encrypted shared undo parent to local undo CDB results in a vPDB with new UNDO TS which is not encrypted

Encrypt the local undo space manually after provision, or with the Configure Clone hook point.

DLPX-81125

MSSQL Export fails when performed on a target with a Microsoft SQL Server instance running with the network service user

If you update the instance owner of the SQL server, you should refresh the environment to reflect the new user in the MDS.

DLPX-81128

Masking: Unable to create/edit a profile set from GUI

Profile set can be add/edited using API

Version 6.0.13.0

Key

Summary

Workaround

DLPX-38908

LogSync should automatically resolve faults for transient issues.

Manually resolve the faults generated when Oracle LogSync encounters transient issues.

DLPX-57078

Job cancel requests during provisioning are not processed until the end of the step.

Find and kill the Oracle pmon process for the instance that is being provisioned.

DLPX-64386

LogSync thread hangs when trying to remove temporary RMAN command file from source host toolkit directory.

Remove the rm alias for the Delphix OS user.

DLPX-76382

Force disable should succeed despite environmental problems.

No workaround.

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-78412

SCM/Talaria failure reason should be communicated in fault.

No workaround.

DLPX-78986

Prevent DSP connections for disabled cluster nodes.

No workaround.

DLPX-79212

While restoring full backups of file stream type database on open staging DB and taking snapshots, snapshots are consuming full space instead of referring to each snapshot.

No workaround.

DLPX-79355

V2P export throws an error when suspended and resumed at the Opening Database step.

Cancel the V2P export job and start the V2P export operation all over again.

DLPX-79502

SnapSync fails if more than 1000 tempfiles exist in the whole CDB.

No workaround.

DLPX-79596

DB files are getting deleted for staging DB if staging push dSource is forced disabled after performing a restore outside Delphix and then enabled again.

No workaround.

DLPX-79833

You can no longer select performance metric resolution for fluentd configurations.

No workaround.

DLPX-80385

Fluentd does not support deferred upgrades when upgrading to 6.0.13.0, and beyond, when starting from a prior release and using the Historic Splunk Insight solution.

Reboot after upgrade.

Version 6.0.12.0

Key

Summary

Workaround

DLPX-67604

Manually recovering a database after V2P from a snapshot of dSource fails with an error.

No workaround.

DLPX-69775

Updating Oracle credentials with an empty string throws an error when Simplified Connection Management is enabled.

Use the Delphix CLI to unset the user.

DLPX-75209

Network configuration is lost when changing EC2 instance type.

On Nitro-based instance types, use the virtual machine's virtual serial console and login to the sysadmin CLI, then add a DHCP address to the network interface.

DLPX-75878

The JDBC connection string for an Oracle vPDB does not get updated after a listener port change.

A second environment refresh will update the connection string for the vPDB.

DLPX-77231

When source discontinuity on the dSource is followed by resync on the livesource, one or more livesource workers may fail to start. This prevents livesource status from getting updated and the first snapshot from being taken after a resync.

No workaround.

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-78689

Oracle vPDB snapshot job fails after doing reset logs on a linked CDB.

Disable the vPDB and re-enable it to clear out the snapshot job errors.

DLPX-78700

Oracle vPDB source enable jobs for Oracle 21c are taking more than 15 minutes to complete. This issue is only seen during the first Oracle vPDB enable operation on Oracle 21c.

No workaround.

Version 6.0.11.0

Key

Summary

Workaround

DLPX-44544

A SnapSync of an Oracle standby dSource in Real-Time Apply mode sometimes calculates the snapshot's timestamp incorrectly. This can cause ORA-01194 or ORA-01152 errors when provisioning to a timestamp after the snapshot.

To provision from a snapshot of an Oracle standby dSource in Real-Time Apply mode, provision by SCN instead of timestamp.

DLPX-57971

The latest snapshot of a LiveSource may take a long time to show the SCN/timestamp range on its card in the GUI.

No workaround.

DLPX-72123

Detaching or deleting an Oracle dSource may fail on RAC environments due to the failure of deletion of RMAN backups on RAC and the operation needs to be retried with the force option.

If the detach or delete operation on an Oracle dSource fails, retry the command using the force option.

DLPX-75209

Network configuration is lost when changing EC2 instance type.

On Nitro-based instance types, use the virtual machine's virtual serial console and login to the sysadmin CLI, then add a DHCP address to the network interface.

DLPX-77664

Oracle SnapSync fails with "RMAN-06183: datafile or datafile copy  (file="" number="">> ) larger="" than="" maxsetsize"="" if="" a="" datafile="" resized="" in="" the="" middle="" of="">)>

One of the following three workarounds can be applied:

1. Re-issue SnapSync.

2. Reduce the frequency of datafile resizes, or

3. Ensure datafile resize operations are not being performed while the SnapSync operation is in progress.

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

DLPX-77869

Unable to drop and recreate descending order (or any other functional) index as part of Oracle Connector masking/reidentification/tokenization jobs.

Oracle interprets descending order as functional indexes. There is no workaround. This is a known limitation of Drop Indexes for Oracle connectors that will be resolved in a future release.

DLPX-78015

V2P export with absolute data files is failing with an internal error.

No workaround.

DLPX-78263

A SnapSync of an Oracle standby dSource in Real-Time Apply mode sometimes fails with "exception.oracle.snl.linkedsource.current_scn.invalid" if the rate of change in the database is low.

Force a log switch on all primary instances/nodes and then try another SnapSync.

Version 6.0.10.0

Key

Summary

Workaround

DLPX-77467

Loading the setup app dashboard (as sysadmin) renders a server error popup with instruction to contact Delphix Support. This message can be ignored. However, it is known that this error impairs the ability to configure web proxy, PhoneHome, and SMTP servers via the GUI.

These settings can still be configured via the CLI. This issue will be fixed in the next version release.

DLPX-64082

Oracle provisioning scripts have hard-coded timeouts.

Retry the provisioning operation to see if it succeeds. Otherwise, contact Delphix Support.

DLPX-72369

RAC migration for VDB with a deleted parent may fail with error "Cannot update RAC instances if virtual source 'xxx' has a deleted parent." 

No workaround.

DLPX-74896

Race condition during refresh may result in incorrect MDS entry for parent snapshot.

No workaround.

DLPX-75148

DSP throughput tests do not work when from-version is < 6.0.6.0 and target-version is >= 6.0.6.0.

No workaround, however, the user will need to upgrade the source version.

DLPX-75215

Switching AWS instance types can leave the Delphix engine with no network configuration.

On Nitro-based instance types, use the virtual machine's virtual serial console and login to the sysadmin CLI, then add a DHCP address to the network interface.

DLPX-75995

On Windows 2019 Server, with KB4598230 cumulative update, adding or refreshing an environment fails when PowerShell transcription is enabled.

The user has to turn off the transcription if the staging is on Windows 2019 Server with recent updates.

DLPX-77231

When source discontinuity on the dSource is followed by resync on the Oracle LiveSource, one or more LiveSources workers may fail to start. This prevents the LiveSource status from getting updated and the first snapshot from being taken after a resync.

No workaround.

DLPX-77849

Excessive number of connections to SQL Server Instance observed by Delphix Environment User. This causes infra issues and leads to LSASS.exe to crash and host to reboot

Rather than using a Windows domain user for authentication switch the dSource to use a database user. It seems SQL Server may be able to handle the massive number of connections that Delphix is establishing for each dSource better than Windows LSASS.EXE.

Version 6.0.9.0

Key

Summary

Workaround

DLPX-72186

CDB logfile retention works incorrectly if a PDB has multiple timeflows pointing to the same CDB timeflow.

No workaround.

DLPX-74749

Oracle ENVIRONMENT_REFRESH_AND_DISCOVER job may fail with "The object OraclePDBConfig does not exist on the system".

Manually run an environment refresh after the ENVIRONMENT_REFRESH_AND_DISCOVER job fails.

DLPX-75517

Provisioning an Oracle vPDB to a vCDB fails with "ORA-00959: tablespace 'TEMP' does not exist" if there is no temporary tablespace named TEMP within the production PDB$SEED database.

One of the following two workarounds can be applied:

  1. Re-attempt the vPDB provision to a linked CDB. The provision should succeed.

  2. Manually create (or rename) the  TEMP tablespace in the production PDB$SEED database, take a new snapshot of the vPDB, and provision from that snapshot to the vCDB.

DLPX-75737

Retention saves unnecessary logs if the bookmark falls exactly on a snapshot end SCN or snapshot end timestamp.

No workaround.

DLPX-75995

On Windows 2019 Server, with KB4598230 cumulative update, adding or refreshing an environment fails when PowerShell transcription is enabled.

The user has to turn off the transcription if the staging is on Windows 2019 Server with recent updates.

DLPX-76388

Entering key pairs directly into hook environment variables (a new feature in 6.0.9.0) results in an internal error.

Use password variables instead, or use a password vault. See Passing Credentials Securely to Hook Operations

Version 6.0.8.0

Key

Summary

Workaround

DLPX-64307

Environment refresh should ignore cluster discovery for VDBs

The following workaround should resolve the issue without Delphix support intervention.

For RAC databases

1. Add the instances to the clusterware configuration, ensuring you add all instances configured via Delphix. For example:

CODE
srvctl add instance -db <Database Name> -instance <Instance Name> -node <Node Name>

2. Refresh the environment. At this point, Delphix will add the instances back to the Delphix configuration, and you should be able to perform actions such as stop, start, disable, enable, etc.

From here, we recommend removing the clusterware configuration.

3. Stop the VDB via the Delphix GUI or CLI.

4. Remove the instances from clusterware

CODE
srvctl remove instance -db <Database Name> -instance <Instance Name>

5. Remove the database from clusterware

CODE
srvctl remove database -db <Database Name>

6. Refresh the environment.

7. Start the VDB via the Delphix GUI or CLI.

For RACOne databases

1. Stop the instance.

CODE
sqlplus "/as sysdba" shutdown immediate

2. Ensure the RACOne configuration has the "instance prefix" configuration set.

CODE
[oracle@mwtestx1 ~]$ srvctl config database -d <vdb name> | grep "Instance name prefix" Instance name prefix: VDB

3. If this is not set, then set it using

CODE
srvctl modify database -db <vdb name> -instance <instance prefix>

4. Set the pfile location to allow clusterware to start the instance

CODE
srvctl modify database -db <vdb name> -spfile <path to pfile>

The pfile is located in

CODE
<Delphix Mount base>/<VDB Name>/datafile/spfile.ora

5. Start the instance using clusterware

CODE
srvctl start database -d vdb

When querying the status of the database, it should now show a running instance. As an example:

CODE
[oracle@mwtestx1 ~]$  srvctl status database -d VDB Instance VDB_1 is running on node mwtestx1 Online relocation: INACTIVE

6. Refresh the environment. At this point, Delphix will add the instances back to the Delphix configuration, and you should be able to perform actions such as stop, start, disable, enable, etc.

From here, we recommend removing the clusterware configuration.

7. Stop the VDB via the Delphix GUI or CLI.

8. Remove the database from clusterware

CODE
srvctl remove database -db <Database Name>

9. Remove the database from clusterware

CODE
srvctl remove database -db <Database Name>

10. Refresh the environment.
11. Start the VDB via the Delphix GUI or CLI.

DLPX-72186

CDB logfile retention works incorrectly if a PDB has multiple timeflows pointing to the same CDB timeflow

No workaround.

DLPX-73409

Duplicate listener entry gets generated in MDS if Oracle listener is manually started with non-uppercase name

Follow these steps:

  1. Restart the listener without a name parameter so it displays in uppercase.

  2. Update VDBs to use uppercase LISTENER.

  3. Refresh the environment. lowercase listener will be removed and LISTENER updated appropriately.

DLPX-74749

Oracle ENVIRONMENT_REFRESH_AND_DISCOVER job may fail with "The object OraclePDBConfig does not exist on the system"

Manually run an environment refresh after the ENVIRONMENT_REFRESH_AND_DISCOVER job fails.

DLPX-74860

Provisioning a 2nd generation VDB from a dSource with imported RO transportable tablespaces fails with ORA-19654

No workaround.

DLPX-74882

Masking's SFTP client no longer compatible with SolarWinds and Goanyware SFTP servers

No workaround.

DLPX-75517

Provisioning an Oracle vPDB to a vCDB fails with " ORA-00959: tablespace 'TEMP' does not exist " if there is no temporary tablespace named TEMP within the production PDB$SEED database

One of the following two workarounds can be applied:

  1. Re-attempt the vPDB provision to a linked CDB. The provision should succeed.

  2. Manually create (or rename) the  TEMP tablespace in the production PDB$SEED database, take a new snapshot of the vPDB and provision from that snapshot to the vCDB.

Version 6.0.7.0

Key

Summary

Workaround

DLPX-74457

Cluster discovery for Oracle RAC partially fails on Solaris 10

Switch the default login shell for the Delphix OS user from /bin/sh to /bin/bash.


DLPX-74749

Oracle ENVIRONMENT_REFRESH_AND_DISCOVER job may fail with "The object OraclePDBConfig does not exist on the system"

Manually run an environment refresh from the Delphix UI if the ENVIRONMENT_REFRESH_AND_DISCOVER job fails with the mentioned error.

DLPX-76718

Time required to display the point-in-time pop-over on timelines for Self-Service Templates with replicated objects can degrade linearly with each replication.

No workaround but reducing replication frequency can reduce the impact.

Version 6.0.6.0

Key

Summary

Workaround

DLPX-73224

When provisioning from a non-multitenant source to a virtual pluggable database (vPDB), the post-plug hook script (dx-post-plug-hook.sh) should exit with the vPDB either closed or open unrestricted. If the vPDB is left open with restricted access subsequent Snapshots of the vPDB will fail with "oracle.ucp.UniversalConnectionPoolException"   and "  java.sql.SQLException: ORA-01035 ORACLE only available to users with RESTRICTED SESSION privilege" .

To prevent the issue: Ensure that the vPDB is either closed/mounted or open unrestricted when exiting from dx-post-plug-hook.sh.

After it has happened: close and reopen the vPDB.

DLPX-72749

Provisioning a TDE-enabled vPDB with system encrypted tablespaces fails with the error "ORA-28374: typed master key not found". 

No workaround, contact Delphix Support (TBD)

DLPX-72655

Provisioning an Oracle TDE-enabled vPDB fails intermittently if the dSource is encrypted after linking

Enabling TDE on an existing non-encrypted dSource is not supported. Detach, rename the Delphix dSource name and re-attach it as a new TDE-enabled dSource before re-attempting the provisioning operation.

DLPX-73224

When provisioning from a non-multitenant source to a virtual pluggable database (vPDB), the post-plug hook script (dx-post-plug-hook.sh) should exit with the vPDB either closed or open unrestricted. If the vPDB is left open with restricted access subsequent Snapshots of the vPDB will fail with "oracle.ucp.UniversalConnectionPoolException"  and " java.sql.SQLException: ORA-01035 ORACLE only available to users with RESTRICTED SESSION privilege"

To prevent the issue: Ensure that the vPDB is either closed/mounted or open unrestricted when exiting from dx-post-plug-hook.sh.

After it has happened: close and reopen the vPDB.

DLPX-73357

Rewinding an Oracle TDE-enabled vPDB to the snapshot before vPDB migration may fail with exception.oracle.tde.export.keys.failed if all of the steps of the keystore merge procedure are not followed correctly

Verify that the CDB is restarted after merging the keys of the old target CDB into the new target CDB and re-attempt the rewind operation.

If the rewind still fails, provision a new vPDB from the required snapshot instead of the rewind operation.

DLPX-72181

The "Restore Self-Service data container from the bookmark of sibling data container" operation may fail in an Oracle TDE environment with exception.oracle.tde.export.keys.failed if the keystore merge procedure is not followed correctly. In this case, the warning "Refresh operation on the TDE-configured container <target container> from the Timeflow of another container <sibling container> requires merging of the TDE keystores." will be displayed in the Delphix UI events log

Verify that the procedure for merging the sibling keystores is followed correctly and re-attempt the self-service operation.

DLPX-73742

Provisioning an Oracle TDE-enabled vPDB may fail with the error "ORA-28367: wallet does not exist" if the TDE wallet for the target linked CDB is stored on ASM storage

Storing the TDE wallet on ASM storage is currently unsupported. Modify sqlnet.ora to point to the keystore location outside of the ASM diskgroup and re-attempt the provisioning operation.

DLPX-73788

Provisioning or enabling an Oracle TDE-enabled vPDB fails when $ORACLE_BASE is used in sqlnet.ora

Any environment variable referenced in sqlnet.ora must always be set in the environment for the Delphix OS user. Ensure that the environment variable $ORACLE_BASE is set in the shell initialization file for the Delphix OS user and re-attempt the operation.

DLPX-73789

If WALLET_ROOT initialization parameter is configured on a TDE-enabled dSource PDB, provisioning may fail since the auxiliary CDB instance uses dSource keystore location.

If the provision fails, there are 2 workarounds:

  1. Provide permissions to the Delphix OS user to create files in the location identified by WALLET_ROOT directory of the source keystore on the target host.

  2. Modify the dSource database to not use WALLET_ROOT to identify the TDE keystore.

Version 6.0.2.0

Key

Summary

Workaround

DLPX-69638

Masking job created on engine 6.0.1.1 or prior is failing after the upgrade to version 6.0.2.0 or later

Masking jobs created in 6.0.1.x using a Hana JDBC driver will need to be updated to grant the following permission {"java.io.FilePermission" "/", "read"} in 6.0.2.0. All drivers created in and after 6.0.2.0 will be granted this permission by default.

Version 6.0.0.0

Key

Summary

Workaround

DLPX-60397

If a mapping algorithm is included in multiple jobs, only one job should be run at a time. If multiple jobs are run at the same time, then the mapping algorithm might contain multiple mappings to the same value or the jobs might deadlock.

Only run one job at a time.

DLPX-60947

Self-Service template with replica VDB is not updated with new Timeflow on incremental replication update

The latest replica VDB data can still be accessed by doing a Self-Service container Refresh, rather than a point-in-time restore from the template.

DLPX-61079

Certificate import validation may incorrectly reject a root CA certificate

Support must manually import the certificate into the truststore.

DLPX-61405

Masking operation should wait for zfs delete queue to drain

Replication may send more data than expected if masking involves dropping large DBF files.

DLPX-64493

V5 API /roles endpoint missing certain items

View and set these privileges through the GUI

DLPX-66155

Failed DSP engine test leads to multiple blocked client.jar processes on target hosts.

Restarting a Delphix Engine during a network throughput test is not recommended as it may lead to a system hang.

DLPX-66860

ADFS does not like NameIDPolicy sent by SSO app

Create an explicit rule in ADFS that transforms the {{emailAddress}} attribute into a {{nameid}}. The rule type must be "Transform an incoming claim". The incoming claim type must be "Email address" and the outgoing claim type "Name ID". The nameid format must be "Email address".

DLPX-66973

Date format is changed after importing the environment

Either (a) use the GUI import feature and then review the imported date formats for correctness or (b) use EngineSync to export/import jobs, which will not alter the date format.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.