E1: 47: EDI Inbound Purchase Order Change (R47131) Slow Performance Due To Excessive I/O
(Doc ID 2464945.1)
Last updated on MAY 26, 2021
Applies to:JD Edwards EnterpriseOne EDI - Version 9.1 and later
Information in this document applies to any platform.
EDI Inbound Purchase Order Change (R47131)
When EDI Inbound Purchase Order Change (R47131) job is run on the scheduler, it is taking longer than expected to run. Last week it was taking 10-15 minutes to run. Yesterday it was taking more than 30 minutes to run. Performance is twice as slow.
The customer believes the slow performance is due to excessive numbers of SQL SELECTS (I/Os) on the Preference Master File (F40070) table and the Table Sharing - Table Group Detail (F95311) table.
The issue was reproduced at will with the following steps:
- A version of EDI Inbound Purchase Order Change (R47131) is scheduled to run every 30 minutes throughout the day
- After the job is started, a user turns Debug Logging ON during Job Execution Detail
- After a minute, the user turns Debug Logging ON during Job Execution Detail
- The user retrieves the debug logs and is able to determine the number of SELECTS as follows:
- There were 9705 SELECT statements processed against the Preference Master File (F40070)
- There were 5073 SELECT statements processed against the Table Sharing - Table Group Detail File (F95311).
- When the user checked Work with Submitted Jobs the job took 44 minutes (Start: 12:12:00 End:12:56:12)
This batch is scheduled to run every 30 minutes but when it takes more than 30 minutes to run, it delays the start of the next batch.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document