I have a simple job where range look up is occuring based on two equality operator and one range(range cols are from reference link).The reference link is made entire partition and sorted on the look up keys.
In datastage 8.5 the job ran fine but in datastage 11.3 the job is failing with the below reasons
1. Updatable lookup requires sorted keys($APT_NO_SORT_INSERTATION=True)
2. Non initialized APT_LOCATOR($APT_NO_SORT_INSERTATION=False)
Is there anything needs to be changed to run range lookup in datastage 11.3?
Issue in range lookup
Moderators: chulett, rschirm, roy
Is the sort also on the range lookup columns? If not, that could explain the error message.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 152
- Joined: Mon Mar 07, 2011 6:16 am
Did you partition before or after the sort? And is the "from" column in the range lookup also part of the sort?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 152
- Joined: Mon Mar 07, 2011 6:16 am
Try running the job with a 1-node configuration file to force things to be sequential and see if the error message remains the same.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 152
- Joined: Mon Mar 07, 2011 6:16 am
Yes, I have also tried that option.I put a sort stage in the ref link and run this sort stage sequential only, else are running in parallel This time the job is running fine. From my understandings it seems that anything running on multi node just before the lookup stage in reference link cause the job failure.It's applicable for reference link only
Also job is running fine while removing the in line sort from the reference link and keeping $APT_NO_SORT_INSERTION=False
Also job is running fine while removing the in line sort from the reference link and keeping $APT_NO_SORT_INSERTION=False
Soumya