issue in reconciliation

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
esivaprasad
Participant
Posts: 135
Joined: Tue Dec 09, 2008 10:35 am

issue in reconciliation

Post by esivaprasad »

Hi ,

Datastage version=8.1.0.0
We have reconciliations job.
1 source file - extracting data using ECC stage .
2 source file - other team drop the file in datastage server.
we have many reconciliation jobs.
one of reconciliation job had issue.
record value is same in both sources , but still reconciliation not happening.

i applied trim , then tried with TrimLeadingTrailing and then tried with
TrimLeadingTrailing(Convert(Char(10):Char(13):Char(9),' '.
But still recocilation logic not working .

When i see record value is same in both sources.
Please help me
Siva
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Unfortunately, there's really not enough information for anyone here to provide cogent help. Never mind I had to look up what the "ECC stage" might be, seems to be related to sourcing from SAP via a 'pack', yes?

Regardless, either your sources (which are not posted here) aren't quite as 'same' as you think they are or your reconciliation logic (which is not posted here) isn't working. Making a wild assumption that it is the same logic the other working reconciliation jobs are using then I'm go with file data being 'not the same'.

Details, please.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

When you say the records are the same, we're assuming that you mean visibly the same. But what about non-printing characters? Have you checked for these, for example using a hex editor?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply