E1:OUTBND SQL Deadlock conditions in F90710 and F90730 Tables When Processing High Volume of Real Time Events
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Customer is experiencing deadlock conditions in SQL for RTE table F90710 and F90730 when triggering high volume of events from E1. Customer has different RTE server and different set of F907* tables, but this issue is happening in production where they only have one active RTE server pointing to one F907* tables, which is not shared.
The F90710 table should not deadlock under heavy volume conditions.
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