Retail Point-of-Service Solutions (MOSC)

MOSC Banner

Registers consuming large Derby file is causing slowness at registers

edited Jan 11, 2017 3:31PM in Retail Point-of-Service Solutions (MOSC) 4 commentsAnswered ✓

Steps to reproduce

1.  Generate Derby (EXPORTDB.zip) at the BackOffice server level  (BackOffice server is located at the main store); Generation starts at 10PM (cron set in the ServiceContext.xml).

2.  Registers to start (11:15PM) to consume EXPORT DB (over the network) to each register at the store (12 registers are located in this remote store).  This store is not located at the main store.

3.  Register Derby consumption does not complete before store opens at 6AM.

4.  Registers at the remote store is running slow (logging into ORPOS, item scanning, credit auth.).

Note:  Derby (EXPORTDB.zip) offlinedb contains LOGIN, ITEM, PRICING, PROMO information from various ORPOS tables.  We are purging data out of these tables on a daily or weekly basis.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center