We’ve been working on 6.1.2 for a few months now, but we didn’t do a regular migration, but instead have slowly been building new in it. So far, I think it’s a great improvement over 5.8, but I suppose I haven’t gotten too far into the weeds yet. The GUI does take a bit to get used to, but it’s growing on me. I love the SMAT DB and the Database tools so far.
We’ve been on 6.1.2 in production for about a month. Overall I think it’s good, but we’ve had a couple processes that seem to crash every few days. We’re waiting for a 6.1.2.4 patch for RHEL from R&D.
Now that we are talking about it, we are on 6.1.2 in production as well. The only issues we encountered are 1) the SmatDB resend function which does not work if the search query includes a NOT condition, and 2) we had one drastic memory leak that stopped all our processes, we think it was due to a table lookup to a database table that executed in a translate. It was not a simple SQL query, and just from two incidents over the last two years, it seems like (1) there may be a memory leak when invoking SQL queries from inside a translator, and (2) the error handling in a translator when executing a SQL Query may not be catching/handling all scenarios.
I’ve passed this on to R&D as well. I encourage everyone to please submit feedback and suggestions by creating tickets using Infor Xtreme. We can then work to improve and update the tools based on your feedback.
-- Max Drown (Infor)
Author
Replies
Viewing 3 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.
.
