Fixed length issue
Moderators: chulett, rschirm, roy
Fixed length issue
Hi Guru's,
I am not sure how thsi fixed lenght works.....
I am facing a problem -
I have 4 fields where i have to do a lookup for a particular field against oracle Db. all the 4 fields have varchar 10 nullable "Y" .
Not sure why this is happening. If i just take one field into the transformer neglecting the rest 3 fields the job works fine but when i include the rest of the fields in the transformer and then to lookup stage the jobs fails. Can anyone tell me how to fix this issue.
appreciate your concern
I am not sure how thsi fixed lenght works.....
I am facing a problem -
I have 4 fields where i have to do a lookup for a particular field against oracle Db. all the 4 fields have varchar 10 nullable "Y" .
Not sure why this is happening. If i just take one field into the transformer neglecting the rest 3 fields the job works fine but when i include the rest of the fields in the transformer and then to lookup stage the jobs fails. Can anyone tell me how to fix this issue.
appreciate your concern
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
thanks for the reply.
Let me expain -
I have 4 fields and a,b,c,d
i have to do a lookup for "a" on oracle db.
so the job desing is
sequentialfile - transformer- lookup-dataset
so when i add all the four fields in transformer the lookup fails..but when i just pull field "a" the lookup works fine. Not sure why it is so.
all the source fields are varchar and nullable "Y"
Let me expain -
I have 4 fields and a,b,c,d
i have to do a lookup for "a" on oracle db.
so the job desing is
sequentialfile - transformer- lookup-dataset
so when i add all the four fields in transformer the lookup fails..but when i just pull field "a" the lookup works fine. Not sure why it is so.
all the source fields are varchar and nullable "Y"
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Not the attitude of someone who really wants to receive help...
Considering you haven't specified anything that is actually fixed width, why do you think it is a fixed width issue?
Since you haven't specified your problem particularly well, you should appreciate Sainath's attempts to get the full picture.
Considering you haven't specified anything that is actually fixed width, why do you think it is a fixed width issue?
Since you haven't specified your problem particularly well, you should appreciate Sainath's attempts to get the full picture.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Hi,
i'm totally aggred with Ray's point.
Are you able to read the fixed width data from sequentail file?
I mean to say, just right click on the sequential file where you mentioned the fixed width file and see whether you are able to see the data or not.
If you are having some issues while reading data itself, means you have not configured your fixed width file properly.
Please let us know so that some one can help you out from this.
Thanks
Ashish.
i'm totally aggred with Ray's point.
Are you able to read the fixed width data from sequentail file?
I mean to say, just right click on the sequential file where you mentioned the fixed width file and see whether you are able to see the data or not.
If you are having some issues while reading data itself, means you have not configured your fixed width file properly.
Please let us know so that some one can help you out from this.
Thanks
Ashish.
Thanks in Adv.
Ashish
Ashish
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Yes, make sure that they have identical data type and are padded with identical characters.pandujoy wrote:is there a way to just make both (source and lookup) fixed widht
Is your Shift key broken? You aren't e.e.cummings, so please don't try to be.
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.