We use Informatica to load data from SAP BW to Teradata staging layer and could see a job not dropping the ET table (some records exist with error code 6705) during Mload operation (upsert) and succeeds. During the next run of the job, it fails in its first phase of Mload as it couldn't create the ET table which already exists.
How to identify the source records (for which we don't have access to) that have violated and landed into ET table? (The source data is landed into Informatica server through the flat file, data is kept in pipe in Informatica which is deleted once the job is completed)
If Teradata has database_link like Oracle, we could have accessed the source data of SAP BW right from Teradata and could have troubleshooted the issue. Can you explain why Teradata implicitly doesn't support db link (I guess). I have gone through the following link and couldn't find a implicit db_link support (for external source systems like SAP, oracle,...) rather than through external tools.
One option is to find all the distinct values on the column which is recorded in ET table of Teradata from the source SAP BW system and identify the records missing in source which may be a tedious task or
use a flat file in Informatica rather than pipe so that we could read the file.
Are there any provision to find the missing records right from Teradata?