Forum Replies Created
-
AuthorReplies
-
What was your source value?
Hey Rob, my strategy has always been to try and keep the db sizes under 100 mb. If we are already taking a downtime for something else (emr upgrade, server reboot, etc.) and other conditions are ideal (edb is being maintained and rdb is empty and I don’t have to save off files and replay them) then I will reinit everything that I can. If I get into a situation where the db size has gotten much larger than 100 mb and there is concern that it is negatively impacting performance, then I might opt to take a brief downtime for a site outside of a already scheduled downtime. The hcidbinit gives you a lot of options though. I’ve been in situations where I was planning to do a hcidbinit -ACf but there were less than ideal conditions with either the edb (unaddressed errors) or rdb (a system unexpectedly down and messages queued up) and I chose to only reinit one of the two and came back around and did the other when conditions were more ideal.
August 28, 2019 at 9:47 am in reply to: Xlate – STRING Action Function code location and other questions #111921Jim, check out $HCIROOT/tclprocs/xltpfuncstr.tcl.
I believe I have isolated what triggers the issue.
Unfortunately Infor is refusing to look at the issue any more unless I reintroduce the issue into our production environment with logging verbosity turned all the way up.
Max, we are using a very similar setup to the one in your diagram.
September 5, 2017 at 6:47 pm in reply to: Outbound Retries, Interval, sendfail UPOC, Await Replies #81840Bumping this thread. I too am struggling to trigger a SENDFAIL. Anyone have any ideas?
We are seeing the random cycling in our new 6.1.2.0 (AIX7.1) test environment. It has happened to 7 smatdb files in the last 3 days. Seeing other weird behavior that seems to be related to this too. One of the smatdb files randomly cycled on Tuesday. The new file had messages in it for Wednesday and no messages for today(Thursday) even though the thread statistics showed it should have 22 messages. The file timestamp showed last activity from Wednesday. I turned up the engine logging and bounced the process and voila, all of today’s messages wrote to the smatdb with the correct time saved timestamp from when the messages actually passed through the thread.
-
AuthorReplies