Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.
Customer is performing an upgrade from ERP 8.0 to EnterpriseOne 9.0 application release level. By default, many of the large transactional table conversions are run on the Enterprise Server. The issue is, the F43199 conversion job, TC Workbench R8943199AA is set to run locally on the Deployment Server by default.
This table for the customer has a large amount of data causing the job to run for a very long time...approx 62 hours just by itself.
Because the job attempts to process so much data, customer had a problem with the local OEE database running out of UNDO space. It also caused issues related to expired security token.
1 - Does this job have to run locally (i.e. is it set to run locally for a reason)?
2 - Can it be changed to run on the Enterprise Server instead of running it locally?
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