Vinay Elite    Posts: 640 Joined: 12/9/2011 Location: Planet Earth  User Profile | This issue which was fixed last year has raised its ugly head again in OT-2020. This time the problem is worse than last time. Earlier this problem occurred only after OT restart. Now it can occur anytime. It can happen after couple of analysis runs or after running database repair tool also. Last time the problem went away if we recompiled the OmniLanguage Stop used in the Trade Plan. Now recompiling doesn't fix the problem. So if you are using any OmniLanguage Stop in a Trade Plan and change the parameters from the default values, then the analysis results may change anytime. It appears that this issue has something to do with the changed compiling method introduced in OT-2020. Till this bug is fixed, the only way to avoid it is to use the default parameter values. I have not checked whether this issue affects the System block also. [Edited by Vinay on 11/25/2019 7:14 AM] | |
