'ORA-12899 - SQLState: 72000' Causes Continuous Retrying of Transaction Persistence, Resulting in Loss of the Next Set of Transactions (Doc ID 1519656.1)

Last updated on MARCH 20, 2023

Applies to:

Symptoms

When attempting to insert a record with a longer response than accepted into "TR_LTM_CHK_TND"."ID_AJD_CHK", the following error occurs and the application does not handle the exception.  This causes loss of transaction data for subsequent transactions.

"ERROR 2012-12-04 19:57:42,093 51418562 (RMI TCP Connection(11460)-10.192.68.1:com.extendyourstore.domain.arts.JdbcSaveTenderLineItems):

[com.extendyourstore.domain.arts.JdbcSaveTenderLineItems.insertCheckTenderLineItem(JdbcSaveTenderLineItems.java:1857)]

Class: com.extendyourstore.foundation.manager.data.DataException(Revision $Revision: /main/10 $) @12460173: SQLState: 72000

Error generated from Oracle: user requested cancel of current operationSource Exception: java.sql.SQLException: ORA-12899: value too large for column "POS_OWNER"."TR_LTM_CHK_TND"."ID_AJD_CHK" (actual: 22, maximum: 20)

Transaction Name:

Error code: [15] [An error occurred while executing the command]

Error code (extended): [12899]

Description: [SQLState: 72000

Error generated from Oracle: user requested cancel of current operationSource Exception: java.sql.SQLException: ORA-12899: value too large for column "POS_OWNER"."TR_LTM_CHK_TND"."ID_AJD_CHK" (actual: 22, maximum: 20)"

Steps to Reproduce:

1. Introduce a transaction with a response for the check approval longer than 20 characters.
2. POS does not move the transaction to the QueueException folder, nor is it retried for persistence.

The transaction is just lost (as well as the subsequent transactions) in the FileQueue.

Changes

Cause

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