How To Fix FB059 - Job & restarted

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 059

• Message text: Job & restarted

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FB059 - Job & restarted ?

  The SAP error message FB059 typically indicates that a job has been restarted due to an issue encountered during its execution. This error can occur in various contexts, often related to financial transactions or batch jobs in the SAP system.
  Cause:
  
  Job Failure: The job may have encountered an error during processing, such as a data inconsistency, missing data, or a system error.
  Resource Issues: Insufficient system resources (like memory or processing power) can lead to job failures.
  Configuration Issues: Incorrect configuration settings in the job or related processes can cause the job to fail.
  Database Locking: If the job tries to access a locked database record, it may fail and trigger a restart.
  Timeouts: Long-running jobs may hit timeout limits set in the system.
  
  Solution:
  
  Check Job Logs: Review the job logs to identify the specific error that caused the job to fail. This can provide insights into what went wrong.
  Analyze Error Messages: Look for any additional error messages that may accompany FB059. These can help pinpoint the issue.
  Resource Monitoring: Ensure that the system has adequate resources (CPU, memory, etc.) to handle the job.
  Configuration Review: Verify the job configuration settings to ensure they are correct and appropriate for the task.
  Database Locks: Check for any database locks that may be affecting the job. You can use transaction codes like SM12 to view and manage locks.
  Retry the Job: If the issue seems transient, you may simply retry the job after addressing any identified issues.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches.
  Contact Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SM37 (Job Monitoring) to check the status of jobs and view logs.
  System Monitoring: Use transaction codes like ST22 (Dump Analysis) and SM21 (System Log) to check for system errors or dumps that may relate to the job failure.
  Performance Tuning: If resource issues are common, consider performance tuning of the SAP system to improve job execution times.
  
  By following these steps, you should be able to diagnose and resolve the underlying issues causing the FB059 error in your SAP environment.