Fixed issues

2025.2.1 fixes

  • APIGW-11938: Fixed an issue causing slow performance in the compliance service upgrade process.

  • APIGW-11904: The VDB provision flow has been fixed to function correctly with the CORE license, which was experiencing issues prior to this bug fix.

  • APIGW-11855: Fixed an issue related to the AppData dSource disable operation, which was failing in the previous DCT-2025.2.0 release.

2025.2.0 fixes

  • APIGW-11490: Fixed an issue where the ReplicationRelationshipJob status would always be pending if the namespace or replication spec notification is missed.

  • APIGW-11681: Fixed an issue where Delete Engine jobs would get stuck in a pending state when some internal notifications are missed.

2025.1.2 fixes

  • APIGW-11362: Fixed an issue where if a user is using PostgreSQL v12.x, an internal service (e.g., virtualization-app) fails to start. Recommendation is to upgrade PostgreSQL 12 to a newer version, as PostgreSQL 12 has reached its End of Life (EOL).

2025.1.1 fixes

  • APIGW-11388: In the DCT upgrade scenario from version < 15.0.0 to a version >= 24.0.0, bookmarks listing fails due to an internal data error.

  • APIGW-11367: To allow DCT deployment using docker-compose a deployment configuration file docker-compose.yaml is packaged with delphix-dct-2025.1.1.tar.gz.

21.0.0 fixes

  • APIGW-9536: Reduced memory requirement to collect rule sets from connected compliance engines.

20.0.0 fixes

  • APIGW-8504: Resolved an issue where masking job execution sometimes failed due to concurrent updates.

18.0.0 fixes

  • APIGW-8771: Fixed a memory leak, where the virtualization-app was restarting frequently. The reason for the memory leak was a background bookmark migration job for timestamp if the number of bookmarks are more than 100.

17.0.0 fixes

  • APIGW-8156: Fixed a timeout issue when creating a bookmark for a large VDB group.

  • APIGW-8057, APIGW-8113, APIGW-8114, APIGW-8142: This issue was introduced in 8.0.0 and fixed in this version, which means arbitrary code execution can be performed by any user permitted to log into the DCT application, even without admin permissions.

16.0.1 fixes

  • APIGW-8144: Fixed an issue that masking jobs of a registered engine are not shown in DCT.

16.0.0 fixes

  • APIGW-7480: Fixed the UI on the Infrastructure Connections screen such that long environment names will wrap around instead of spilling unto the next column.

14.0.0 fixes

  • APIGW-7090: Fixed an issue where the username was not displayed in the top navigation bar, if logging in using anything other than username/password.

13.0.0 fixes

  • APIGW-4971: Fixed a problem when VDB_GROUP_REFRESH job's update time did not get updated on receiving job updates for the underlying VDB_REFRESH jobs.

  • APIGW-6705: Fixed an installation problem when masking database migration runs out of memory for large tables.

12.0.0 fixes

  • APIGW-6240, APIGW-6241: Fixed a memory exhaustion issue that caused frequent HTTP 500 errors.

  • APIGW-5052: Fixed an issue when viewing the Summary screen after provisioning a vDB in DCT where the dSource summary name was showing the vDB name.

  • APIGW-5511: Added the ability to unregister engines in the UI.

  • APIGW-5585: Fixed an issue where users were unable to logout following SSO token expiration.

10.0.1 fixes

  • APIGW-5406: Fixed an issue where the VDBGroup update API gives an internal error if vdb_ids are the same as ones already present in VDBGroup.

  • APIGW-5419: Fixed an issue where the VDBGroup delete API gives a 404 error if underlying VDBs are already deleted or not present.

  • APIGW-5418, APIGW-5517: Fixed an issue where VDB provisioning via DCT GUI fails with, “There was an error trying to process your request.”

  • APIGW-5570: Fixed an issue preventing the link of a Postgres database as a dSource.

  • APIGW-5571: Fixed an issue where the Provision VDB -> dSource Listing would not show more than 25 items.

  • APIGW-5574: Hyperscale datasets tables-or-files list and search APIs now return all instead of filtering by dataset.

  • APIGW-5578: Fixed an issue where Pagination was not working for some of the pages in a testing environment.

10.0.0 fixes

  • APIGW-3931: Fixed an error found when loading the LDAP config page in the UI, if the LDAP config domains have empty values.

  • APIGW-3961: Fixed the issue where the Environment link to the dSource detail view is broken.

  • APIGW-4270: Cleaned up pending jobs left by deleted engines.

  • APIGW-5056: Addressed VDB provisioning failures where there were a lot of concurrent requests.

9.0.0 fixes

  • APIGW-3772: Replicated VDBs/dSources are now identified in the Provisioning wizard.

  • APIGW-3931: Fixed a null pointer exception during LDAP configuration without a domain.

  • APIGW-3979: Fixed an issue where the Import VDB Configuration templates dialog was showing the engine ID in error messages. It is now changed to show engine names.

  • APIGW-3983: Fixed an issue where a new masking job could not be started from DCT when the previous job was cancelled on the masking engine.

  • APIGW-4009: Fixed an issue where the first and last name will be cleared if incorrect names were entered for SSO.

  • APIGW-4010: Fixed an issue in the UI where first and last name attributes cannot be reset.

8.0.1 fixes

  • APIGW-4324: Fixed an issue where users who upgraded to DCT 8.0.0 were not able to interact with the UI or connect to the GraphQL service container.

  • APIGW-4317: Fixed an issue where an error would occur when searching for a VDB in the relative refresh UI.

8.0.0 fixes

  • APIGW-3764: Removed THE requirement on setting credentials if a masking job execution happens on the origin engine.

  • APIGW-3771: Allows the policy name to be empty when provisioning a VDB.

  • APIGW-3783: Allows for an existing ImagePullSecret to be provided to to pull docker images.

  • APIGW-3985: Fixed the  "VDB Container is part of a container" error while refreshing from bookmark directly on the VDB > Bookmark tab. 

  • APIGW-3990: Fixed the broken view for a bookmark that has multiple VDBs on the Data > Bookmark tab.

7.0.1 fixes

  • APIGW-3592, APIGW-3594: Previously, a non-admin user that was granted access to a VDB, but not its environment, would get an error accessing the VDB overview. A fix has been implemented to show that the access error is with the environment and not the VDB.

  • APIGW-3775: Fixed an issue where refreshing from the bookmark wizard was not showing compatible bookmarks.

  • APIGW-3831: Fixed a certificates import failure if the truststore is on OpenShift.

6.0.1 fixes

  • APIGW-3460: Fixed a request timeout issue.

  • APIGW-3395: Fixed an issue where the refresh wizard did not update snapshots when selecting different datasets. 

6.0.0 fixes

  • APIGW-3223: Fixed an issue where DCT failed to get info from detached dSources.

5.0.3 fixes

  • APIGW-3344: Fixed an issue causing provision failure from RAC dSource to non-RAC target.

5.0.2 fixes

  • APIGW-2979: VDB refresh will no longer fail if the refresh target name is not unique.

  • APIGW-2981: Fixed an issue where all the Compliance jobs and source jobs on the engine will be deleted when a Compliance engine is unregistered.

5.0.1 fixes

  • APIGW-2463: The default docker-compose.yaml file is now provided with log size and rotation configured for all containers.

  • APIGW-2735: Fixed an issue where DCT migration failed with, "could not create unique index environments_host_pkey".

  • APIGW-2828: Helm chart now allows cronjob resource limits to be set via the values.yaml.

3.0.0 fixes

  • APIGW-1785: Fixed an issue where Nginx sometimes failed to start after a server restart.