Release Notes
Product Description
CipherTrust Batch Data Transformation (BDT) is a command line utility that is used to transform (encrypt/tokenize) data in files and databases. It is a policy-based tool and can efficiently transform bulk data, and can also be used for rekey operations.
Release Description
This release includes bug fixes and security activities.
Advisory Note
Support for initial encryption is available up to DPG version 1.2.0.
Resolved Issues
| Reference | Description |
|---|---|
| CADP-16680 | BDT throws the following error while configuring dataProtectionConfig using the password that contains double quotes (") or backslash (\) characters:Failed post request to Data Protection Service. Received response - null |
| CADP-18948 | If the source table contains null value in the column to be transformed and trimSpaces is enabled, transformation fails with NullPointerException. |
| CADP-20693 | Unable to perform the rollback operation. |
Known Issues
| Reference | Description |
|---|---|
| CADP-24350 | Transformation on multiple tables fail when thread count is 1. |
| CADP-28055 | Encrypting or decrypting Arabic characters using FPE results in errors. |
| CADP-19398 | Unable to read the unprocessed record file when inPlaceUpdate is set to true, as the data is written without column headers. |
| CADP-24175 | A deadlock error occurs during an in-place transformation in the Microsoft SQL Server database when the table has a primary key with a varchar datatype. Workaround: Using a primary key of a varchar datatype can slow down comparisons compared to integer datatypes, potentially leading to a deadlock. Therefore, it is recommended to modify the table to have a primary key of integer datatype. After the transformation is over, these changes can be reverted. 1. Identify the primary key constraint name. SELECT nameFROM sys.key_constraintsWHERE type = 'PK'AND parent_object_id = OBJECT_ID('table_name');2. Drop composite primary key constraint from the table. ALTER TABLE table_name DROP CONSTRAINT <constraint_name>;The Alter table <table_name> add <new_primary_column> int primary key identity(1,1)4. Run the transformation. It will run successfully. 5. Delete the new primary key created in step 3. — Identify its constraint name using the query mentioned in step 1. — Drop the constraint using query mentioned in step 2. 6. Alter the table to add the composite primary key constraint back. ALTER TABLE <table_name> ADD CONSTRAINT <constraint_name> PRIMARY KEY (<column_name1>, <column_name2>); |
| CADP-13218 | Following error message appears continuously on console while performing transformation on empty table in DB2:Note: The user needs to abort manually using Ctrl+C option. |
| CADP-14217 | If the destination table contains identity column of type ALWAYS, transformation fails. This is a limitation from Oracle and DB2 databases that you cannot insert explicit value in identity column of type ALWAYS. Following are the workarounds to perform transformation: Oracle: Alter table and modify identity column type ALWAYS to BY DEFAULT. DB2: Alter table to drop identity property from column. Alter table to add identity property of type BY DEFAULT.
|
| CADP-20695 | After configuring the policy file for two tables and setting srcColumnAction to remove, if the transformation fails for any of these tables, the source column will not be removed. |
Compatibility Information
BDT is compatible with CipherTrust Manager 2.11.1 LTS and higher.