Troubleshooting
Log Files
BDT stores its logs in the file
BDT_HOME/log/bdt.log
.The default log level is DEBUG for the log file and INFO for the console. These log properties can be changed in the
BDT_HOME/conf/log4j.properties
file.
Note
BDT_home
points to your installation directory.
Error and Description
Error / Exception | Description |
---|---|
NAE_IP.1 contains invalid IP addresses in the IngrianNAE.properties | CADP JCE is not configured properly, and the parameter NAE_IP.1 is blank. Refer to CADP JCE documentation for details. |
Failed to obtain JDBC Connection; nested exception is java.sql.SQLException: Cannot create PoolableConnectionFactory (Access denied for user 'userName'@'xx.xx.xx.xx'). | This exception occurs if: • Database user's password is empty. • Database user's password is incorrect. |
Driver class not found: | Copy the required database driver to BDT_HOME/lib path. |
PreparedStatementCallback; SQL [Insert into MYTESTDB.CUSTOMERYD27 values(?,?)]: Duplicate entry '3' for key 'customeryd27.PRIMARY'; nested exception is java.sql.BatchUpdateException: Duplicate entry '3' for key 'customeryd27.PRIMARY'. | This error occurs when a table contains primary key, createDestinationTable is set to true and destination table already exists.So, the same value for a primary key can not be written. |
Loading class 'com.mysql.jdbc.Driver': This is deprecated. The new driver class is com.mysql.cj.jdbc.Driver . The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary. | Change the driver class from com.mysql.jdbc.Driver to com.mysql.cj.jdbc.Driver in the BDT policy. |
Could not create the destination table: Make sure the source table exists. | If the source table exists, ensure table name is configured correctly in the BDT policy file. |
Record parsing failed: The value of columnCount in the BDT policy file and parsed records does not match. | Ensure that all the records in the input file have the same column count as mentioned in the columnCount field of the BDT policy file. |
Invalid or missing algorithm: The encryption algorithm used in config@type is not supported when symmetric key cache is disabled. | Refer to supported encryption algorithms for details. |
Limitations
- If a source table contains spaces in its column name, then that source table cannot be transformed.