How to refresh a lookup in every job iteration
Moderators: chulett, rschirm, roy
How to refresh a lookup in every job iteration
Hello all, please excuse me if this is a newbie question, I am actually new to DataStage development.
Is it possible to refresh a lookup to reflect inserts done to the lookup table within the same job?
My job writes records to a table X, It is capable of insert new records, insert new versions and update old versions of existing records. The lookup to identify existing records and new versions is done to the same table X. The problem arises because the input data may have several versions of the same record inside.
This question was probably asked before here, please point me out the right keywords to include in a search for similar situations.
Thank you
Yonny Serrano
Is it possible to refresh a lookup to reflect inserts done to the lookup table within the same job?
My job writes records to a table X, It is capable of insert new records, insert new versions and update old versions of existing records. The lookup to identify existing records and new versions is done to the same table X. The problem arises because the input data may have several versions of the same record inside.
This question was probably asked before here, please point me out the right keywords to include in a search for similar situations.
Thank you
Yonny Serrano
You couldn't have missed much... check again.
However, the 'expense' is well worth it. Not only are you helping support the site that helps support you, but from what I'm told there's more goodies on the way for Premium Members. Not only that, but you'd get full access to all of the Wurlod Goodness available here!
However, the 'expense' is well worth it. Not only are you helping support the site that helps support you, but from what I'm told there's more goodies on the way for Premium Members. Not only that, but you'd get full access to all of the Wurlod Goodness available here!
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
The hashed file approach is bog standard DataStage Server stuff. Replace your two ODBC lookup stages with hashed file stages (and build something to do the initial population, if needed) and you'll be fine. As noted, make sure the hashed lookup is either not cached (my personal preference) or set to 'Locked for updates'.
As to the SHARAD123 suggestion, right now it is fairly incomprehensible. I too would be curious as to what the actual suggestion would be, once clarified.
As to the SHARAD123 suggestion, right now it is fairly incomprehensible. I too would be curious as to what the actual suggestion would be, once clarified.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: