Error in hashed file
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 614
- Joined: Fri Feb 06, 2004 3:59 pm
Error in hashed file
Hi All,
When i validated the job it was fine but when i started running the job
it is failing due to following reason,
IDEXECCOMP2..Hashed_File_1.DSLink11: ds_uvput() - Write failed for record id 'CHECKPOINT SYSTEMS GMBH
KNAB
G
NTER'
could some one please decipher above error and how to fix it...
the job does comparision of two files current file is in hashed file and newfile is in sequential file stage..
Thanks to all,
When i validated the job it was fine but when i started running the job
it is failing due to following reason,
IDEXECCOMP2..Hashed_File_1.DSLink11: ds_uvput() - Write failed for record id 'CHECKPOINT SYSTEMS GMBH
KNAB
G
NTER'
could some one please decipher above error and how to fix it...
the job does comparision of two files current file is in hashed file and newfile is in sequential file stage..
Thanks to all,
Re: Error in hashed file
Hey kollurianu,
You had a similar problem before, and it seemed it was addressed in the following post -
viewtopic.php?t=98882&highlight=dsuvput+write+failed
gateleys
You had a similar problem before, and it seemed it was addressed in the following post -
viewtopic.php?t=98882&highlight=dsuvput+write+failed
gateleys
-
- Premium Member
- Posts: 614
- Joined: Fri Feb 06, 2004 3:59 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The "line feeds" lead me to suspect that, somehow, you have (illegal) "mark characters" (value mark, field mark, etc.) in the key. Check whether this is the case.
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.
-
- Premium Member
- Posts: 614
- Joined: Fri Feb 06, 2004 3:59 pm
Use Translate in Before routine (ExecSH)
kollurianu wrote:Hi All,
Thanks Ray for ur reponse but how to find out illegal mark characters in the fields....
Any ideas...
Thank you
Hi
You can use this in the before routine (ExecSH)
tr -d '\0' < /home/mukherav/ESA_050.txt > /home/mukherav/ESA_test1.txt
This would delete all the illegal mark characters. But you need to know what illegal characters you are getting.
Avishek Mukherjee
Data Integration Architect
Chicago, IL, USA.
Data Integration Architect
Chicago, IL, USA.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The easiest way to determine whether there are any, but not what they are, is to apply Oconv(TheString, "MCP"), which converts any non-printing characters to period ("."). Perhaps capture this into a sequential file while you are investigating.
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.
-
- Premium Member
- Posts: 614
- Joined: Fri Feb 06, 2004 3:59 pm
Thanks alot for all the responses , Ray and Mukerjee ,
But i have one more question , i found that there some foreign characters
in some foreign address fields and name fields , so is hashed file giving
problem becos of those foreign characters which are printable ,
if not , then i can ignore it try to use MCP , which take off unprintable characters....
any ideas...
Thanks alot...
But i have one more question , i found that there some foreign characters
in some foreign address fields and name fields , so is hashed file giving
problem becos of those foreign characters which are printable ,
if not , then i can ignore it try to use MCP , which take off unprintable characters....
any ideas...
Thanks alot...
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can try to use "MCP" conversion, but there is a risk that you'll lose uniqueness. Better would be to find out what the non-printing characters are, and convert these to explicit printable characters. Something like
Code: Select all
Convert(Char(254):Char(253):Char(252):Char(251):Char(27):Char(9), "~}|{!@", InLink.TheString)
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.