what is the best way to avoid performance issues in Journal edit process (GL_JEDIT)? we are currentl
My users had complained this recently and they are on 9.1 PT 8.53, I have seen that the JRNL Line table is being scanned for skewed data for at least 4-5 SQLs (there may be more as per the trace I have extracted, but they all converse to the same root cause), which is causing the problem. I know adding hints would increase the performance, but that will make the program customized. I want to know if there are any best practices that can be followed to overcome the performance issues with the journal edit process. I dont think archiving