If meta data mismatches in a server job what we have to do?
And what error we will get in the director?(Fatal error or warning).
Thanks
Metadata mismatches
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Answer that yourself by experimentation.
Some metadata matches are insignificant, some are very significant (especially when, for example, one side is a numeric data type and the other side is a non-numeric data type).
Prevention is always better than cure. Make sure that your metadata never mismatches by applying rigorous metadata management practices. Always import/save table definitions and effect all changes in the Repository, not in job designs.
Some metadata matches are insignificant, some are very significant (especially when, for example, one side is a numeric data type and the other side is a non-numeric data type).
Prevention is always better than cure. Make sure that your metadata never mismatches by applying rigorous metadata management practices. Always import/save table definitions and effect all changes in the Repository, not in job designs.
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.
Re: Metadata mismatches
Metadata mismatches while writing into the table can b severe.Metadata mismatches can happen due to inordered columns or datatypes.
The best way to avoid this is to directly import it from manager.
The best way to avoid this is to directly import it from manager.