Last updated on JANUARY 14, 2016
Applies to:Oracle Retail Invoice Matching - Version 14.1 and later
Information in this document applies to any platform.
The Automatch batch fails to complete processing of invoices in RMTCH and URMTCH statuses. The automatch batch job runs for several hours and users have to terminate it. Upon analyzing the issue, it appears that the batch is stuck at the following delete statement:
It looks like the DELETE statement was blocked by another session from the same batch job, doing UPDATE against the same table without committing the change. The AWR report confirms that SQL statements were found waiting for row lock waits. The above delete statement is trying to delete a record from the IM_DOC_HEAD_LOCK table, but the record is already updated/deleted by another session ID without commit. Hence, the session becomes idle as it continues to wait for Row Lock Waits.
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