11i Posting Performance On Gluddl Process After Database Upgrade to 22.214.171.124 (12c) - Patch 18485835 Applied
(Doc ID 2057233.1)
Last updated on JULY 18, 2019
Applies to:Oracle General Ledger - Version 126.96.36.199 to 188.8.131.52 [Release 11.5.10]
Information in this document applies to any platform.
GLPPOS - Posting program
Database (DB) upgraded from 184.108.40.206 to 220.127.116.11 (12c), Posting concurrent shown performance problems afterwards, run time changing from about 30 seconds to 50-80 minutes.
According to <Note 1602141.1> 'GLPPOS After DB Upgrade to 18.104.22.168.0 or 22.214.171.124 or 126.96.36.199 Posting Program Has Poor Performance Stuck on Glpubr.Concurrency', database <Patch 18485835> has been applied. Posting run time improved to 3-5 minutes, still improper considering the volume of data posted.
From Posting log file it is obvious that gluddl() process takes longer.
The issue can be reproduced at will with the following steps:
1. GL responsibility
2. Run Posting: Single Ledger Program
Upgrades DB to 188.8.131.52 (12c) and installed <Patch 18485835>.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document