Hi,
I would like to know what type of errors I can encounter apart from reject records from business rules when loading data from staging to datawarehouse.
Thanx.
Error records in DataWarehouse
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Connectivity failures, including network, database server, authentication errors (e.g. wrong password) and more. These should be immediately fatal.
Violation of security and/or integrity constraints (most usually primary key uniqueness constraints), which should be prevented in your design.
Property or object does not exist - where "they" have changed the target table but that information has not propagated through to the ETL design team. These should be fatal, and cause recriminations between you and "them".
Scheduled or unscheduled database activity, such as backups and bulk loads, for which they have quiesced the database without informing ETL Operations group. Again, a management/communication failure which ought never to have happened. Classed as "bitter experience".
To name a few.
Violation of security and/or integrity constraints (most usually primary key uniqueness constraints), which should be prevented in your design.
Property or object does not exist - where "they" have changed the target table but that information has not propagated through to the ETL design team. These should be fatal, and cause recriminations between you and "them".
Scheduled or unscheduled database activity, such as backups and bulk loads, for which they have quiesced the database without informing ETL Operations group. Again, a management/communication failure which ought never to have happened. Classed as "bitter experience".
To name a few.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.