My Oracle Support Banner

Sales and Return Transactions Not Persisting To The Back Office Database Due to SQL Error Code '72000' & '17002' (Doc ID 755054.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Retail Point-of-Service - Version 12.0.3.3 to 13.1.1 [Release 12.0 to 13.1]
Information in this document applies to any platform.
Oracle Retail Point-Of-Service - Version: 12.0.3.3 to 12.0.9


Symptoms

Sometimes return and sales transactions go missing from the Backoffice database when the database system goes offline.

Steps to Reproduce:

Scenario 1 :
1. Perform a sales transaction and link a new customer by creating new customer.
2. Perform a return using the same customer from step 1.
3. Get the SQL Queries from logs.
4. Now perform a sale and link a customer by reusing the customer created in step 1.
5. Get the Update query that was identified in step 3, and run one of the update queries (similar to the following) WITH AUTOCOMMIT set to FALSE

 UPDATE PA_CT SET ID_EM = '', LCL = null, STS_CT = 1 WHERE ID_CT = 'xxxxxxx' AND ID_PRTY = xxx
 Note:  Do NOT commit the above query.

6. Do multiple transactions using the same customer, keeping track of all transaction numbers.
7. Check the store server database and see if all the transactions made it to the database.  Some transactions will be missing.

 

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.