Transactions Performed During the Offline Mode are not Saved to Database if Transaction Sequence Roll Over Happens During the Offline Mode
(Doc ID 2583533.1)
Last updated on MAY 28, 2021
Applies to:Oracle Retail Point-of-Service - Version 14.1.3 and later
Information in this document applies to any platform.
On Oracle Retail Point of Service (ORPOS), once the transaction maximum sequence number (Ex: 9999) is reached, transaction sequence number roll over happens. When there are a number of transactions performed in the offline mode while the transaction sequence number is nearing the maximum transaction number with some of the transactions having the transaction sequence number after the roll over (Ex: 0001,0002 etc), few transactions fail to be persisted in the database with unique constraint error.
Steps to recreate:
1. Perform a simple transaction make sure transaction number is 9951 (i.e nearing the maximum transaction sequence number 9999)
2. Stop the store server so that client will be offline
3. Perform 60 sale transactions, so the last transaction number is 0011
4. Stop POS client.
5. Start Store server, wait till it creates offline DB.
6. Start POS client.
7. As soon as the POS Client is up, login and perform a sale transaction
8. check transaction number (done in step 7) it could be like 9962 This depends upon how fast client, server can consume queued transactions.
9. perform few more transactions (getting saved as 9969, 9973, 9977,9980, 9986 etc..)
10. Notice that <Server>\pos\bin\QueueException folder has few transactions performed in Step 7 and Step 9 failed with the below Exception
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