Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

Thales Logo

All

  • All
back

Release Notes

search

Please Note:

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. From this release onward, the unescapeInput attribute has been removed, however, it does not impact the existing functionality. Please refer to CSV properties section.

Resolved Issues

ReferenceDescription
CADP-21329If input data contains delimiter, qualifier, or backslash ("\") characters and is transformed to CSV format using an FPE algorithm. In such a scenario, a backslash character gets prepend to all the delimiters, qualifiers, and backslash("\") characters.
CADP-22684No validation happens for the tokenTemplate and tokenGroup parameters. BDT throws a null pointer exception when these parameters are not provided.

Known Issues

ReferenceDescription
CADP-24175A 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 name
FROM sys.key_constraints
WHERE 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 <constraint name> is obtained as the output of 1st query.

3. Alter table to create a new primary column of integer type.
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-13218Following error message appears continuously on console while performing transformation on empty table in DB2:
ERROR [threadPoolTaskExecutor-3] - Exception: null
Note: The user needs to abort manually using Ctrl+C option.
CADP-14217If 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.
alter table <table_name> modify <column_name> generated BY DEFAULT as identity
DB2:

Alter table to drop identity property from column.
alter table <table_name> alter column <column_name> drop identity
Alter table to add identity property of type BY DEFAULT.
alter table <table_name> alter column <column_name> set generated BY DEFAULT as identity
CADP-20695After 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.

On this page