My Oracle Support Banner

RPAS FC: Issues with commitAsap. commitAsap Does Not Work Correctly When There are Lock's on meta.db (Doc ID 2524784.1)

Last updated on JANUARY 24, 2021

Applies to:

Oracle Retail Predictive Application Server - Version 14.1 and later
Information in this document applies to any platform.


If a lock exists on a meta database such as hmaint.db, when a user initiates a Commit via Fusion Client, the commitAsap attempts to lock the hmaint.db and once it fails, the commit will stay in the 'In Progress' status forever.   The rpasWorkbookServer does not continue to try to commit the workbook. 
Also, Fusion Client Commits are not respecting the Commit Time as registered by configCommitAsap -deadline. The rpasWorkbookServer continues to run even after the Commit Time has been reached. 

Below errors can be noticed from the commitAsap logs:

<E 2019Mar29 15:54:16.078> Cannot obtain a write lock on database '<RPAS_Domain>/data/hmaint.db.lck', 41.

<E 2019Mar29 15:54:16.078> Another process has the database locked.
<E 2019Mar29 15:54:16.078>
<E 2019Mar29 15:54:16.078>
<E 2019Mar29 15:54:16.078> Locker::logAllLocks()
<E 2019Mar29 15:54:16.078>
<E 2019Mar29 15:54:16.078> 0.010650 '<RPAS_Domain>/data/measdata'
<E 2019Mar29 15:54:16.078> 0.128714 '<RPAS_Domain>/data/meta'
<E 2019Mar29 15:54:16.078> 0.010150 '<RPAS_Domain>/data/meta'
<E 2019Mar29 15:54:16.078> 0.143638 '<RPAS_Domain>/data/wbdata'
<E 2019Mar29 15:54:16.078> 0.135862 '<RPAS_Domain>/users/<userName>/t00024/t00024'




To view full details, 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 a vibrant support community of peers and Oracle experts.