E1: UBE: Common UBE Execution and Runtime Issues
(Doc ID 1502985.1)
Last updated on APRIL 09, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version SP24 and later
JD Edwards EnterpriseOne Sales Order Management - Version 9.1 and later
Information in this document applies to any platform.
UBE execution or runtime issues are any issues that cause a batch application to not process or fail while processing on the server. This includes everything that happens AFTER the job record is added to the Job Master Table F986110. You can find more information about the job execution flow in <Document 1502974.1>.
If an issue is found while submitting the UBE to the server and a job record is not getting added to F986110, then this is considered to be a submission issue. The submission process and common issues are covered in <Document 1498831.1> and <Document 1502927.1> respectively.
This document provides solutions to common UBE execution and runtime issues.
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
|Issue 1: UBEs Remain in 'W' Status Indefinitely|
|Issue 2: UBEs Remains in 'S' Status Indefinitely|
|Issue 3: UBEs Remain in 'P' Status Indefinitely|
|Issue 4: UBEs End in 'E' (Error) Status|
|Issue 5: UBEs Fail to Submit or End in Error if EnterpriseOne is Unable to Save Files to PrintQueue or Temporary Folder|
|Issue 6: Backup on Server Locking EnterpriseOne Files|
|Issue 7: Corrupt Spec Files|
|Issue 8: Unable to Run Different Versions of the Same UBE Report Simultaneously|
|Issue 9: Unable to Create Large Report Output|
|Issue 10: On EnterpriseOne 8.12 and later, METADATA Kernel Might Run Out of Memory|
|Issue 11: UBE fails on the server with error "Unable to retrieve BLC Specs for function XXXXXX"|
|Issue 12: UBEs Remain In 'W' Status For Up To Five Minutes Before Launching|
|Issue 13: UBEs end in Error Status intermittently because of runtime cache corruption|
|Unix and Linux|
|Issue 1: Lack of Server Resources|
|Issue 1: EDRSQL Services not Properly Configured or not Started on Server|
|Issue 2: Permission Issues on the AS/400 Proxy User|
|Issue 3: Corrupt EnterpriseOne SQL Package on Server|
|Issue 4: The Maximum Number of Members Reached in System Library File B733XSYS/PRINTQUEUE|
|Issue 5: UBE Ends with Error "Problem opening temporary file with password"|
|Issue 6: UBE Fails with Error "OS400DT011 - FindSQLIndex:Failed to search for column"|
|Issue 7: Other AS/400 Issues|
|Other Less Common Issues|
|Issues Specific to EnterpriseOne 8.9 and above|
|Issues Specific to OneWorld Xe and ERP8|