My Oracle Support Banner

Ejournals Stop Flowing to CentralOffice When POS server is Restarted (Doc ID 1395953.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle Retail Point-of-Service - Version 13.0 and later
Oracle Retail Central Office - Version 13.0 and later
Information in this document applies to any platform.

Symptoms

When Oracle Retail Back Office (ORBO) is restarted while Oracle Retail Central Office (ORCO) & Oracle Retail Point of Service (ORPOS) are running,  e-journals stop flowing to ORCO from ORPOS and the following error observed on the ORPOS log.

ERROR :



Steps To Reproduce:

1. Start ORCO, ORBO and ORPOS
2. Login to ORPOS
3. Perform a sale transaction of Item 1234 tendered with Cash
4. Observe that corresponding tables TR_TRN & JL_ENR are updated with the transaction on BO and CO
5. Stop the Back Office instance
6. Start the Back Office instance
7. Perform a sale transaction of Item:4321 tendered with Cash

Ejournal records are not available in CO.

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
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.