SM37: Error reading job log JOBLGX* (Message no. BT167)

Error reading job log JOBLGX12345
Message no. BT167

Diagnosis

The background processing system was unable to read the job log named in the message.

This message suggests that there is a problem with the TEMSE storage system of the SAP system. The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.

This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:

  • Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
  • A CRON (or equivalent scheduler) job has deleted the TEMSE file.
  • The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
  • The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.

In normal operation, a job log is deleted from the TEMSE only when the background job to which it belongs is deleted.

System Response

Action terminated abnormally.

Procedure

To analyze this problem, start by checking the SAP system log for relevant error messages. Possible candidates include messages from the background processing system or the TEMSE storage system, as well as messages pertaining to database problems.

With the TEMSE management facility, you can check for problems in the TEMSE database, where job logs are kept. The List all objects function may be the best place to start looking for the lost log file. If the log was stored in the file system (not in the database), then the TEMSE management record for the log may still exist and may indicate what happened to the log data.

You May Also Like

Leave a Reply?