MDM records inactive in Ataccama but active in source system - How do I re-activate those in Ataccama?

Here are the solution notes from the support ticket (in case others have the same question in the future): 
 

“I’d like to share that: This is most likely due to the source_timestamp field. The MDM system only updates rows if the source_timestamp in the input is equal to or newer than the stored timestamp.

For deleted records in a Full Load operation, the timestamp of the load operation itself is used since there are no corresponding rows in the input.

In your case, the old records are restored in the input, but their source_timestamp values are in the past because they haven't been modified since then. The MDM system compares these timestamps to the stored timestamps (from the time of the erroneous operation) and determines that it has newer data, thus ignoring the records in the input.

Possible Solutions:

1. Update Records in the Source: Modify the records in the source system to have a newer source_timestamp. This will ensure the MDM recognizes the updated information.

2. Nullify source_timestamp Column: Set the source_timestamp column to null in the load operation. This will force the MDM to use the operation timestamp, which will be newer.

Important Note: The second approach (nullifying source_timestamp) might have drawbacks if the source data is delivered through mixed modes (e.g., online during the day and batch overnight). In such cases, the MDM might not recognize fresher data from online updates and could potentially overwrite it with batch data.

Please be noted that it is strongly recommended to backup your database before running any queries.”