My Oracle Support Banner

11i Posting Performance On Gluddl Process After Database Upgrade to 12.1.0.1 (12c) - Patch 18485835 Applied (Doc ID 2057233.1)

Last updated on DECEMBER 04, 2018

Applies to:

Oracle General Ledger - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10]
Information in this document applies to any platform.
GLPPOS - Posting program

Symptoms

Database (DB) upgraded from 11.2.0.3 to 12.1.0.1 (12c), Posting concurrent shown performance problems afterwards, run time changing from about 30 seconds to 50-80 minutes.

According to <> 'GLPPOS After DB Upgrade to 11.2.0.4.0 or 12.1.0.1 or 12.1.0.2 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.


STEPS
The issue can be reproduced at will with the following steps:
1. GL responsibility
2. Run Posting: Single Ledger Program

Changes

 Upgrades DB to 12.1.0.1 (12c) and installed <Patch 18485835>.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.