My Oracle Support Banner

R12: GLOCPP Period - Close Periods Has Poor Performance And Takes a Long Time in glusbe (Doc ID 805887.1)

Last updated on JULY 13, 2018

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
GLOCPP - Periods - Close Period
XLAPEXRPT - Subledger Period Close Exceptions Report
XLAREPSEQ - Create Reporting Sequence number

Symptoms

When closing a period in General Ledger (GL), the concurrent request executes for a long time often 7-10 hours. The period does eventually open successfully and no errors are encountered.
The expected time for the concurrent request execution is minutes.


The log file for GLOCPP module: Periods - Close Period shows that a long time is taken in glusbe:

>> glusbe() 02-AUG-2015 17:20:17

<< glusbe() 03-AUG-2015 00:51:46
SHRD0147: Finished processing rows

Changes

Upgrade to release 12 or a new install of release 12.

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
 Still Have Questions?
References

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