Duplicate records loaded into Request table
Duplicate records are loading into the RIODS.Request table from the ClearQuest data source in our UAT environment.
The ETL delivery node specifies DBID and Datasource_ID as the composite key for the delivery into RIODS.REQUEST but this is not enforceing uniqueness. The UAT ETL was imported as a package created in the SIT environment. The ETL does not load duplicates in the SIT environment. Are there any other load criteria besides the key values that I have to consider in my delivery? Could the data -- or internal tracking -- be corrupted by deleting all data in Request before re-running the ETL? Can someone help me out! Thanks. |
One answer
Duplicate records are loading into the RIODS.Request table from the ClearQuest data source in our UAT environment. Are both environments using the same xdc file? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.