Fusion Core HR: Transactions Are Stuck Due to Diamond Special Character (Failed to Load Value at Index 6) (Doc ID 2699917.1)

Last updated on AUGUST 14, 2022

Applies to:

Symptoms

Whenever users are trying to terminate a stuck/pending transactions an application error is thrown in User Interface.

To terminate transactions the below steps are used:

1.  Navigator menu
2.  Tools
3.  Transaction Console → Transaction Summary
4.  Search pending transaction → Open transaction
5.  Actions → Terminate process

When the above action is performed an error is throw in the User Interface with the following message:

The same error message is thrown as well when users initiate new transactions for employees with data issue caused by wrong encoding type. 

In this scenario, the error is thrown at the review step, and once with that, a transaction with draft status is created in TXN HEADER tables, which is similar to transaction saving action. These transactions cannot be found in transaction console entry due this error. 

Changes

Starting with release 20B new changes have been done to tables used to store transaction details.

These changes were done over the tables structure and their column types used to store the data cache of each transaction.

Because of this, the transactions cache is parsed by SQL statements, and whenever are found any special/unknown character, the transactions are getting stuck.

Cause

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