E1: OS: Troubleshooting a UNIX Enterprise Server (Doc ID 626295.1)

Last updated on JUNE 11, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Generic UNIX

*** check for relevance 10-SEP-2012 ***
*** check for relevance 08-SEP-2014 ***

Try to narrow down the definition of any problem that you may have, particularly when communicating the issue to Oracle Support. For example, stating: "The UBE failed" is not a good description of the issue. Instead, try to provide as much detail as possible, for example:
- UBE Rxxxxx status is "E"
- Unable to submit UBE Rxxxxxx to Server abc123
- Always try to provide logs with errors

When communicating an error message to a support engineer, be sure to include all parts of the error message and the logs from client and/or server. Parts of the message that may not seem important to you may actually hold the key as to why an error occurs. Also, distinguish between characters that might be misinterpreted (for example, the capital "O" and the number zero ("0")). You should collect logs and screen prints and attach to your service request.
As soon as you notice an error, examine the log files. Messages near the bottom of the log files will probably reveal the most important information about the cause of the error.

Before you restart EnterpriseOne service(s) on the server, either delete or move the jde_xxx.log and jdedebug_xxx.log files (where "xxx" is a process ID number of logs from the server). Do not rename the log files because it is easier to work with logs that use the standard naming convention ("jde_xxx.log" and "jdedebug_xxx.log"). If you need to save the log files until the problem is solved, then create a temporary directory and move the files there.

Clear the log directory on a regular basis to avoid filling the file system. If the file system gets filled, then the spec files will become corrupted.

Always keep a backup of the spec files handy in case the specs become corrupted. Spec files should be backed up regularly for easy recovery of spec installs. If spec files have to be replaced, all spec installs will be lost if backups are not kept.

Here is a quick way to find "smoking guns" due to server failure: In the system/bin32 directory:
grep -n "failed" *log* > problems.txt

The file "problems.txt" will contain a list of errors with the file and line number.

In UNIX CaSe Is ImPoRtAnT…. "jde.ini" is NOT the same file as "JDE.INI".
For a better understanding of the flow of the UNIX EnterpriseOne Server processes, review the section called: JD Edwards EnterpriseOne Architecture and Process Flow for UNIX and Linux in any of the JD Edwards EnterpriseOne Tools 8.9x Server and Workstation Administration Guides.

All of the following tasks assume that you are logged on to UNIX in an account that has administrative privileges.