Last updated on MAY 04, 2017
Applies to:Oracle General Ledger - Version 18.104.22.168 to 22.214.171.124 [Release 11.5.10]
Information in this document applies to any platform.
GLPPOS - Posting program
Database (DB) upgraded from 126.96.36.199 to 188.8.131.52 (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 184.108.40.206.0 or 220.127.116.11 or 18.104.22.168 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 22.214.171.124 (12c) and installed <Patch 18485835>.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms