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 in Glpubr Module (Doc ID 1602141.1)

Last updated on MAY 19, 2022

Applies to:

Symptoms

GLPPOS Posting program gets stuck on glpubr.concurrency() after the database has been upgraded to RDBMS 11.2.0.4 or 12.1.0.1 or 12.1.0.2.
Journal Posting runs slowly and appears to hang in >> glpubr.

• Example of GLPPOS log:

General Ledger: Version : 11.5.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
GLPPOS module: Posting
+---------------------------------------------------------------------------+
>> glpubr() 19-AUG-2015 15:58:58
<< glpubr() 19-AUG-2015 16:42:38

• Example of GLPPOSS log:

General Ledger: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
GLPPOSS module: Posting: Single Ledger
+---------------------------------------------------------------------------
>> glpubr.concurrency() 03-JUN-2016 16:25:20
<< glpubr.concurrency() 03-JUN-2016 16:25:20
SHRD0147: Finished processing rows
SHRD0180: glpubr() - Performing action >> update_gl_balances...
PERF0005: Oracle error detected in glpubr() - ORA-01652: unable to extend temp segment by 128 in tablespace TEMP
<x glpubr() 03-JUN-2016 16:32:01
>> gluerr() 03-JUN-2016 16:32:01

The PERF0005 message error can be also as below:
PERF0005: Oracle error detected in glpubr() - ORA-01652: unable to extend temp segment by 16 in tablespace TEMP
or PERF0005: Oracle error detected in glpubr() - ORA-1652: unable to extend temp segment by 256 in tablespace TEMP
Also, PERF0005 message error may not be present in the logs, but can observe performance for glpubr() process.

Changes

Database upgraded to 11.2.0.4 or 12.1.0.1 or 12.1.0.2.

Cause

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