Records lost when reading a hashed file after upgrading DS
Posted: Tue Dec 11, 2012 9:01 am
Dear all,
We are testing the jobs after their migration from DataStage 7.5 to DataStage 8.7, and we are facing the following mismatch:
- there is one job that writes the records to the Hashed File - the same number of records is written by 7.5 and 8.7 versions of datastage.
- now the next job reads from that Hashed File, but DataStage 8.7 retrieves two records less than DataStage 7.5, from the exact same Hashed File, and with the same job design.
Does anyone have any idea how it is possible?
Is there a way to compare two hashed files to determine which 2 records get lost?
Additional info, if it might be important: we move from windows to unix server as well, and nls is enabled in the 8.7 version.
Thank you!
We are testing the jobs after their migration from DataStage 7.5 to DataStage 8.7, and we are facing the following mismatch:
- there is one job that writes the records to the Hashed File - the same number of records is written by 7.5 and 8.7 versions of datastage.
- now the next job reads from that Hashed File, but DataStage 8.7 retrieves two records less than DataStage 7.5, from the exact same Hashed File, and with the same job design.
Does anyone have any idea how it is possible?
Is there a way to compare two hashed files to determine which 2 records get lost?
Additional info, if it might be important: we move from windows to unix server as well, and nls is enabled in the 8.7 version.
Thank you!