Review EBS product's new releases & features, troubleshooting tips & tricks, best practices, upcoming webcasts

Posting Performance Issues Reported After Database Upgrade

Adriana Bacila
Senior Principal Technical Support Engineer

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, 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: 

Posting Logfile

Did you upgrade to RDBMS 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 Program Stuck on Glpubr.Concurrency (Doc ID 1602141.1)

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.