My Oracle Support Banner

Get ORA-14403/ORA-14766 when SPM update "invalidates" the "SKIP LOCKED" cursor during Accounting Program request (Doc ID 1559600.1)

Last updated on AUGUST 02, 2024

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.2.0.3 [Release 11.1 to 11.2]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After Database upgrade to 11g, Accounting program (xla_accounting_pkg) for Receivables
is failing with "ORA-14403: cursor invalidation detected after getting DML partition lock":

Accounting Program concurrent request log:

Subledger Accounting: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

XLAACCUP module: Accounting Program
+---------------------------------------------------------------------------+

Current system time is 28-DEC-2012 03:01:25

+---------------------------------------------------------------------------+

**Starts**28-DEC-2012 03:01:25
ORACLE error 14403 in FDPSTP

Cause: FDPSTP failed due to ORA-14403: cursor invalidation detected after getting DML partition lock
ORA-06512: at "APPS.XLA_ACCOUNTING_PKG", line 6479
ORA-06512: at "APPS.XLA_ACCOUNTING_PKG", line 2660
ORA-06512: at line 1


Trace file .../trace/EBSP_ora_56996.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
===
*** 2012-10-23 21:37:36.254
----- Error Stack Dump -----
ORA-14403: cursor invalidation detected after getting DML partition lock
----- Current SQL Statement for this session (sql_id=0mj3gtmkckw7f) -----
     SELECT /*+ leading(tab,evt) use_nl(evt) */
===
FOR UPDATE OF evt.event_id skip locked
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
 object      line  object
 handle    number  name
0x34ca2eac0      6479  package body APPS.XLA_ACCOUNTING_PKG
0x34ca2eac0      2660  package body APPS.XLA_ACCOUNTING_PKG
0x349d12dd0         1  anonymous block
----- Call Stack Trace -----
===
kdugetpart()+1008    call     ksesecl0()          
qerfuFetch()+4398    call     kdugetpart()        
kpofrws()+328        call     qerfuFetch()

 

Some Accounting Program concurrent requests, spawned from Create Accounting for Receivables,
terminate with error (ORA-14403) while others complete normally.

Database 11.2 Bug 12571991, which did not actually resolve the root cause of the ORA-14403 problem,
changed only the ORA-14403 error to ORA-14766 so the error can be caught in PLSQL.

Now, with database patch 12571991, the Accounting program request log shows:

An internal error occurred.  Please inform your system administrator or support representative that:
An internal error has occurred in the program xla_accounting_pkg.unit_processor.  
ORA-14766: Unable to obtain a stable metadata snapshot.

 

Changes

 

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.