Troubleshooting
This section describes the issues you may run into and how to resolve them. If you face an issue that is not listed here, contact Thales Customer Support.
| Error/Issue | Possible Cause and Fix |
|---|---|
| Resource doesn't exist on Key Manager. | Make sure the resources associated to the job (such as job configuration, data sources, and protection policy) exist on Key Manager. |
| Client is unable to fetch latest policy even after synchronizing time between client and server. | To get the latest updates, the heartbeat interval must be longer than the delay between the client and server. |
| Failed to update BDT job status on CipherTrust Manager. | BDT failed to update the job status on CipherTrust Manager. Check liveness probe of the container. If it returns HTTP code 503, BDT can't process more jobs. In such scenarios, restart the container. |
| JDBC driver jar does not exist at location. | JDBC driver JAR is missing from the specified location. Ensure the JAR file exists in the specified location with the exact file name when a job is being processed. |
| Invalid value provided in database certificate value. | The provided database CA certificate is malformed. Make sure the database CA certificate is a valid certificate in .PEM format. |
| Failed to download the driver. | The required JDBC driver for database connection could not be downloaded. Ensure to specify correct JDBC driver download URL. |
| Could not parse JDBC driver download URL. | Unable parse JDBC driver download URL due to following reasons: — Empty or null key value pair in JDBC driver URL. —Invalid key-value pair. Ensure to provide correct JDBC driver download URL. See Using JDBC Driver URLs. |
| The job could not be stopped successfully. | Unable to stop the job, as it may have already completed or stopped. |
| Job configuration does not exists. | The job configuration associated with the job is deleted from CipherTrust Manager. Ensure job configuration exists on the CipherTrust Manager. |
| Primary key column not found. Can't perform in-place update. | Occurs when the Primary Key column is not available in the source/destination table in case of in-place update. |
| 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. | 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>); |
