Posting Performance Issues Reported After 188.8.131.52 Database Upgrade
By Adriana-Oracle on Jul 01, 2014
Posting is the main General Ledger process that updates the account balances for detail and summary accounts. As the program is submitted multiple times almost every day and the volume of data processed by this concurrent request is sometimes huge, getting a good performance for each run is crucial for having up-to-date balances available for reporting purposes at any moment.
After upgrading RDBMS to 184.108.40.206, Posting performance issues were reported due to a new optimizer feature introduced for Database. Posting uses a bad execution plan and might get severe performance issues or simply hang at glpubr.concurrency procedure:
Did you upgrade to RDBMS 220.127.116.11 recently? Do you plan to upgrade?
Ensure proper application usage for your users through a proactive patching plan!
This recently updated document provides all the needed details to help avoid a known issue:
GLPPOS Poor Performance after DB Upgrade to 18.104.22.168.0: Program Stuck on Glpubr.Concurrency (Doc ID 1602141.1)