If you deploy and run a transformation (either BDT or CDT), Data Exchange records these actions in the internal tracking database UnisysDExchTrackingDB.
Data Exchange cannot revert changes to a transformation target. If you wish to rerun a BDT or CDT then you need to ensure any previously added data in the transformation target (that may cause transformation errors) is removed prior to the rerun.
If you start (not resume) a BDT then all the previously recorded tracking records will be removed and new records will be created. This means that the next time you start a CDT, if the transformation source Enterprise Database Server you will be prompted for the Audit file to start processing from. If the transformation source is RDMS or SQL Server then the date and time recorded during the last run BDT will be used as the starting date and time (if the Lock option was used).
If you do not run a BDT before running a CDT then you must manually clear the CDT tracking database records of your transformation source prior to rerunning CDT.
A number of stored procedures have been added to UnisysDExchTrackingDB to assist clearing the tracking database.
Warning
Do not run the stored procedures unless you want to rerun a BDT or CDT. Else, it may lead to data inconsistency.
Be careful when running the stored procedure ClearAllXXX as it applies to all your source data stores.
The stored procedures to assist in clearing the tracking database are: [dbo].[ClearAllCDT], [dbo].[ClearAllCDTandBDT], [dbo].[RemoveCDTRecordsForSourceId], [dbo].[RemoveCDTRecordsForSourceDataStoreLIKE].
[dbo].[ClearAllCDT]
Description: Clears all CDT tracking records existing in the tracking database.
Parameters: None
Impact to next BDT: None
Impact to next CDT:
Transformation source type Enterprise Database Server:
The next start of CDT will ask for the audit file to start processing from.
Transformation source type RDMS or SQL:
If a BDT had been previously run, the date and time of that last BDT run will be used to start processing CDT from.
If BDT had not been previously performed then the next start of CDT will ask for the date and time to start processing from.
[dbo].[ClearAllCDTandBDT]
Description: Clears all CDT and BDT records existing in the tracking database.
Parameters: None
Impact to next BDT: None
Impact to next CDT:
Transformation source type Enterprise Database Server:
The next start of CDT will ask for the audit file to start processing from.
Transformation source type RDMS or SQL:
The next start of CDT will ask for the date and time to start processing from.
[dbo].[RemoveCDTRecordsForSourceId]
Description: Clears all CDT and BDT records existing in the tracking database for the given source GUID.
Parameters: The GUID of the concerned transformation source. You can find the GUID for your transformation source by examining the contents of the [dbo].[DataStoreMap] table.
Impact to next BDT: None
Impact to next CDT:
Transformation source type Enterprise Database Server:
The next start of CDT will ask for the audit file to start processing from for the selected transformation source(s).
Transformation source type RDMS or SQL:
If a BDT had been previously run, the date and time of that last BDT run will be used to start processing CDT from for the selected transformation source.
If BDT had not been previously performed then the next start of CDT will ask for the date and time to start processing from for the selected transformation source.
[dbo].[RemoveCDTRecordsForSourceDataStoreLIKE]
Description: Clears all CDT records existing in the tracking database for a transformation source with a name LIKE (uses the SQL LIKE operator).
Parameters: The GUID of the concerned transformation source. You can find the GUID for your transformation by examining the contents of the [dbo].[DataStoreMap] table.
Impact to next BDT: None
Impact to next CDT:
Transformation source type Enterprise Database Server:
The next start of CDT will ask for the audit file to start processing from for the selected transformation source(s).
Transformation source type RDMS or SQL:
If a BDT had been previously run, the date and time of that last BDT run will be used to start processing CDT from for the selected transformation source(s).
If BDT had not been previously performed then the next start of CDT will ask for the date and time to start processing from for the selected transformation source(s).
[dbo].[ClearAllBDT]
Description: Clears all BDT tracking records existing in the tracking database.
Parameters: None
Impact to next BDT: None
Impact to next CDT: None
[dbo].[RemoveBDTRecordsForSourceId]
Description: Clears all BDT records existing in the tracking database for the given transformation source GUID.
Parameters: The GUID of the concerned transformation source. You can find the GUID for your transformation by examining the contents of the [dbo].[DataStoreMap] table.
Impact to next BDT: None
Impact to next CDT: None
[dbo].[ShowAllBDTinformation]
Description: Displays all BDT records.
Parameters: None
Impact to next BDT: None
Impact to next CDT: None
[dbo].[ShowAllBDTinformationForSourceId]
Description: Displays all BDT records for the given transformation source GUID.
Parameters: The GUID of the concerned transformation source. You can find the GUID for your transformation source by examining the contents of the [dbo].[DataStoreMap] table.
Impact to next BDT: None
Impact to next CDT: None
[dbo].[ShowAllCDTinformation]
Description: Displays all CDT records.
Parameters: None
Impact to next BDT: None
Impact to next CDT: None
[dbo].[ShowAllCDTinformationForSourceId]
Description: Displays all CDT records for the given transformation source GUID.
Parameters: The GUID of the concerned transformation source. You can find the GUID for your transformation source by examining the contents of the [dbo].[DataStoreMap] table.
Impact to next BDT: None
Impact to next CDT: None