ORPOS Client Performance Slows Down When Database is Offline (Doc ID 1920088.1)

Last updated on MARCH 29, 2017

Applies to:

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

Symptoms

Oracle Retail Point-Od-Service (ORPOS) client performance degrades when the database is down (offline mode).


Steps to Reproduce:

  1. Set up Store Conduit and Database (DB) on the same server.
  2. Start ORPOS Server and Client. Ensure that Offline DB is populated.
  3. Start ORPOS Client in Online mode.
  4. Scan a few SKU's.
  5. Take console of the store server and stop DB service from Services.msc.  Ensure that Store Conduit is running.
  6. Observe ORPOS Client. It will be in hang mode for a minute or so.
  7. ORPOS Client will come back and start working; however, every SKU scan will take around 25-30 seconds.
  8. Now stop Store Conduit on server.
  9. Observe ORPOS scanning speed. It is now improved to a great extent.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms