Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.
Moderators: chulett , rschirm , roy
cosec
Premium Member
Posts: 230 Joined: Tue May 08, 2007 8:10 pm
Post
by cosec » Tue May 31, 2011 11:43 pm
Please advice if there is any special handling that needs to be done for character fields using a lookup after migration for v8.1
Last edited by
cosec on Wed Mar 27, 2013 9:28 pm, edited 1 time in total.
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Wed Jun 01, 2011 6:15 am
Special? No. Since this is a direct DB lookup, I'd say double-check your SQL and column metadata, ensure they match. Are you using custom SQL?
-craig
"You can never have too many knives" -- Logan Nine Fingers
cosec
Premium Member
Posts: 230 Joined: Tue May 08, 2007 8:10 pm
Post
by cosec » Wed Jun 01, 2011 8:13 pm
I have checked and the column meta deta is exactly the same. Yes, I am using a custom SQL.
Last edited by
cosec on Wed Mar 27, 2013 9:29 pm, edited 1 time in total.
chulett
Charter Member
Posts: 43085 Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO
Post
by chulett » Wed Jun 01, 2011 8:35 pm
You might want to check with support. Sometimes they plug holes and fix things that people didn't know were broken and relied upon. And sometimes they break things.
-craig
"You can never have too many knives" -- Logan Nine Fingers
cosec
Premium Member
Posts: 230 Joined: Tue May 08, 2007 8:10 pm
Post
by cosec » Wed Jun 08, 2011 5:57 am
Thanks. We are currently checking with IBM on this issue.
Last edited by
cosec on Wed Mar 27, 2013 9:37 pm, edited 2 times in total.
ray.wurlod
Participant
Posts: 54607 Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:
Post
by ray.wurlod » Wed Jun 08, 2011 4:30 pm
Always use trimmed VarChar on both inputs. Char is always untrimmed, so you need to have them identically padded.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.