Recipient Is Getting Batched but Sometimes One of the Batches Is Not Being Processed
(Doc ID 2465151.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Documaker - Version 12.6 and later
Information in this document applies to any platform.
On : 12.6 version, Enterprise Edition
Document not batching into correct batches
I ran a single transaction and it batched properly into ENV1 and ARCHIVE1. Everything successful (Tran ID 1845).
I ran the exact same transaction through a few seconds later and it successfully batched to ENV1 , but ARCHIVE1 failed (Tran ID 1846).
There was no load; just two single transactions (same form, same xml, etc). We can reproduce this consistently by simply pushing one transaction at a time ... eventually one of them will fail. It does not take a lot of attempts to get it to fail.
I attached TRNS, BCHS_RCPS, BCHS, RCPS and PUBS for each transaction. Also included log files (nothing much there), ERRS table (nothing but a timeout message), the XML i used to generate both transactions, and the FSISYS/FSIUSER.
ORA-12516, TNS:listener could not find available handler with matching protocol stack
The issue can be reproduced at will with the following steps:
1. Run a single transaction over and over.
The issue has the following business impact:
Due to this issue, transactions are not posting to the correct batch.
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