hash file problem
Moderators: chulett, rschirm, roy
hash file problem
Hey I am using Hash File as Lkp. The problem is the hash file has the data ans the Transforemer is not able to read any records from hash file
When I keep the database lkp Transformer stage is taking data.
I dont understand whats happening.The thing is it ran fine when i usede hash file for the first time .But from second run onwards the transformer stage is not taking any records from hashfile
I am using DS 7.5 and plugin is DRS the jobs i am working is delivered jobs
quick reply will be helpful
When I keep the database lkp Transformer stage is taking data.
I dont understand whats happening.The thing is it ran fine when i usede hash file for the first time .But from second run onwards the transformer stage is not taking any records from hashfile
I am using DS 7.5 and plugin is DRS the jobs i am working is delivered jobs
quick reply will be helpful
Is the job running fine or are you getting any error messages? From what you say, it seems that your job is running fine but is not reading any inputs from the hashed file. Please elaborate so that we could help.
Did you change any metadata in the hashed file from the previous run. ?
Are you deleting and creating the hashed file everytime you run the job?
Did you change any metadata in the hashed file from the previous run. ?
Are you deleting and creating the hashed file everytime you run the job?
hash file problem
Thanks cris for replying.
The job is running fine when i keep db stage as lkp.But when i want to keep a hash file instead of db stage its not picking up records.
i copied the same metadata as of db stage
i donno whats happening
[quote="kris007"]Is the job running fine or are you getting any error messages? From what you say, it seems that your job is running fine but is not reading any inputs from the hashed file. Please elaborate so that we could help.
Did you change any metadata in the hashed file from the previous run. ?
Are you deleting and creating the hashed file everytime you run the job?[/quote]
The job is running fine when i keep db stage as lkp.But when i want to keep a hash file instead of db stage its not picking up records.
i copied the same metadata as of db stage
i donno whats happening
[quote="kris007"]Is the job running fine or are you getting any error messages? From what you say, it seems that your job is running fine but is not reading any inputs from the hashed file. Please elaborate so that we could help.
Did you change any metadata in the hashed file from the previous run. ?
Are you deleting and creating the hashed file everytime you run the job?[/quote]
check out a couple of things.
Make sure the hashed file names are the same on both the input and output (while building the hashed file and while reading it)
The keys are identical in both the cases.
you are triming the source keys and the hashed file keys for blank spaces.
Make sure the hashed file names are the same on both the input and output (while building the hashed file and while reading it)
The keys are identical in both the cases.
you are triming the source keys and the hashed file keys for blank spaces.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Thanks for all of the tips,
I have tried all those options. and still i am getting the same problem. I am not able to trace out what the problem is ? the thing i am confused is these are people soft delivered jobs.
should the SQl query effects the hash file
I got no clue
Help in this matter is appreciated
I have tried all those options. and still i am getting the same problem. I am not able to trace out what the problem is ? the thing i am confused is these are people soft delivered jobs.
should the SQl query effects the hash file
I got no clue
Help in this matter is appreciated
It is because there is not hit on the keys in the hashed file.
That usually happens when there are leading or trailing spaces in the record.
In the key derivation of the hashed file link, inside the transformer, make sure you are trimming it. I cannot think of any other reason why its behaving like this.
Give a new name to the hashed file, in the hashed file stage, in both the input and output.
That usually happens when there are leading or trailing spaces in the record.
In the key derivation of the hashed file link, inside the transformer, make sure you are trimming it. I cannot think of any other reason why its behaving like this.
Give a new name to the hashed file, in the hashed file stage, in both the input and output.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.