This content has been marked as final. Show 2 replies
I too faced same issue during my initial days of Bi Apps! Even though we don't have duplicate records for those source tables, we are getting duplicte records while loading!! So, here I have 2 options: Either not to create unique indexes while loading or delete that record which is causing duplicate records while loading. Even Oracle told me to remove that record which is causing the duplication.
SO, at this moment, if you are building your system for demo purpose, then have your ETL run by removing Unique index.
INTEGRATION_ID is normally the ID column from the source system. I.e.: it MUST NOT be a non-unique column!
Check your source qualifier and / or SQL statement to make sure that you get unique rows into the dimension staging table!