This content has been marked as final. Show 5 replies
In my cases this happens when i regenerate a particular scenario multiple times. Time by time it gets slow to regenerate but 1 hour is too much. Normally it gets resolve if i drop and recreate the interface. Can you export the interface/models to any other system and try to generate scenario once again ?
No Bhabani , the issue is not just regenerate ,its about generate scenario and not just an hr , one or two scenario takes more than 12 hrs too . We have tried to duplicate or create a new interface completely from scratch too but nothing has helped . Thanks for your suggestion.
what's 10.1.6? if you mean 126.96.36.199
I suggest you enable TRACE:32 for your studio to see what really go ahead under the cover.
also you should try to create a separate clean repository, try the case.
I suppose there is no way to say what's the reason, just try every possibility we can think, filter them.
I agree with Tina.
We had an instance with a different version of ODI where the customized profiles in Security Manager caused delays in opening the mappings. By tracking our Oracle connections to the Master and Work repositories we did find that millions of SQLs were being fired against them causing the ODI Designer to slow down.
A similar situation in your case maybe slowing scenario generation.
Please check if any of the interfaces are part of a different folder. I had a similar issue and it was resolved by checking the references for each interface that are part of the scenario.
Hope this helps.