HI,
I have source is unicodedata but lookup table has nonunicodedata while doing lookup it's rejecting. pls tell me how i can do lookup in this case
Thanks in advance
regards,
Bollineni.
comparision between unicodedata and normaldata
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 111
- Joined: Thu Jun 01, 2006 5:12 am
- Location: Detroit
comparision between unicodedata and normaldata
kOTI,
1586-738-7785
1586-738-7785
-
- Premium Member
- Posts: 7
- Joined: Thu Nov 17, 2005 12:00 pm
Re: comparision between unicodedata and normaldata
Bollineni,bollinenik wrote:HI,
I have source is unicodedata but lookup table has nonunicodedata while doing lookup it's rejecting. pls tell me how i can do lookup in this case
Thanks in advance
regards,
Bollineni.
Couple of ways,
1. Change the lookup field format to unicode (nvarchar, nchar etc. ) if possible, OR,
2. Get the source and lookups into Hashs and perform further transformations from there on. Once the data is inside datastage it becomes internal to datastage.
Srinivas
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Basically you have to get the metadata to match. One is using string, the other is using ustring in the record schema. You could try changing the data type in the table definition so that it matches, which may work if you're using ASCII data.
Note that Srinivas's advice about using hashed files is not correct for parallel jobs. But you could use a Lookup File Set.
Note that Srinivas's advice about using hashed files is not correct for parallel jobs. But you could use a Lookup File Set.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 111
- Joined: Thu Jun 01, 2006 5:12 am
- Location: Detroit
Thanks rayray.wurlod wrote:Basically you have to get the metadata to match. One is using string, the other is using ustring in the record schema. You could try changing the data type in the table definition so that it matches ...
yes i am converting the datatype of lookup table from nonunicodedata to unicodedata by using of string to ustring function but it's not matching i think it's not converting. And i tried with changing of datatype also it means lookup table is oracle with number datatype i am converting it to char and source is flatfile with nchar to char b.coz it's unicodedata....pls tell me is theer any function to convert nonunicodedata to unicodedata or any other way
pls help me
Disable the RPC. IF you convert ustring_from_string() from the input stream, it should do lookup. At a worst case, write into a intermediate sequential file after the conversion. It will be useful for the verification as well.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'