DSXchange: DataStage and IBM Websphere Data Integration Forum
View next topic
View previous topic
Add To Favorites
This topic is not resolved, but there is a WORKAROUND.
Author Message
rkashyap



Group memberships:
Premium Members

Joined: 02 Dec 2011
Posts: 498
Location: Richmond VA
Points: 4518

Post Posted: Wed Mar 01, 2017 9:34 am Reply with quote    Back to top    

DataStage® Release: 11x
Job Type: Parallel
OS: Unix
Additional info: IIS 11.5 fp1 on RHEL 7; XMETA DB2; LDAP authentication.
While performing SFDC sparse lookup, the position of the lookup column in the input link is entered in SOQL's WHERE clause (counting from zero) e.g. ''{3}'' for 4th column.

If any column is modified/manipulated in a transformer (prior to SFDC stage) then modified column(s) move up in internal output from transformer (though not in Designer canvas), so when it comes to column position 'what you see is Not what you get'! This makes developing code with SFDC sparse lookup quite challenging.

Further, an unrelated/passthru column change (during post production maintenance) in an upstream transformer will necessitate modification of SFDC sparse lookup's WHERE clause to map to new position of lookup column.

Please share your thoughts/experiences on working around this issue.
rkashyap



Group memberships:
Premium Members

Joined: 02 Dec 2011
Posts: 498
Location: Richmond VA
Points: 4518

Post Posted: Wed Mar 15, 2017 12:58 pm Reply with quote    Back to top    

Only workaround for this issue is to perform some operation on every column in the upstream transformer (e.g. append an empty string to a string column, add 0 to a numeric column) rather than mapping directly.

During version 8.5, this issue was addressed in JR47138, but it is reoccurring in DataStage 11.5.

I have raised a PMR for this issue.
Rate this response:  
Not yet rated
rkashyap



Group memberships:
Premium Members

Joined: 02 Dec 2011
Posts: 498
Location: Richmond VA
Points: 4518

Post Posted: Sat Apr 22, 2017 7:06 am Reply with quote    Back to top    

IBM has informed us ...
Quote:
We should prioritize the patch JR47138 implementation based on the work effort since its not a simple fix and might need some design changes so, it might be considered for the next release of IS.

We will workaround this issue by either:
- Avoiding upstream transformer from SFDC stage OR
- Performing some operation on every column in the upstream transformer (e.g. append an empty string to a string column, add 0 to a numeric column) rather than mapping directly.
Rate this response:  
Not yet rated
Display posts from previous:       

Add To Favorites
View next topic
View previous topic
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



Powered by phpBB © 2001, 2002 phpBB Group
Theme & Graphics by Daz :: Portal by Smartor
All times are GMT - 6 Hours