Topology change not propagated to interface

Question

Hi all,
Had a requirement that called for a topology change (adding a physical schema to existing data server and updating the logical schema to point to this new physical schema). In the end, this change is meant to eliminate the use of LKM. This affects, say 10 interfaces, which are being executed through a package scenario. Now when I regenerate the scenario after making the topology change and re-execute, I see the interfaces still using the LKM. BUT if I go and open the interfaces, make a minor change (e.g. move a datastore around), save and close them back, regenerate the package scenario and execute it, I can see the changes are there and it's not using the LKM. This is obviously tedious if we have to do it for hundreds of interfaces. Given this, is there anyway to propagate the topology change from the back end to all the interfaces? Maybe an update or something on the repository tables? It's bizarre since when I query the interfaces in the SNP_POP table, I see that I_TRT_KLM column is NULL which presumably means it's not using an LKM so I'm not sure why from the front end, we have to open and close the interfaces to see the change come through.
Any ideas why?
Thanks

Answer 1

Hi,
I believe what each Interface needs is to have the sourceset "recomputed". This is what happens when you open the Interface, click on the mapping tab, then over to the flow tab - which is why, after you save, it works. You should be able to write a Groovy script or Java code using the ODI SDK to handle this in a batch.
Take a look at the InteractiveInterfaceHelperWithActions class. There is a method to check for dirty sourcesets and another to compute the sourcesets.
http://docs.oracle.com/cd/E28280_01/apirefs.1111/e17060/index.html?overview-summary.html
Regards,
Michael Rainey