How To Fix DB10059 - Job with XDB ID &1 has status 'COMPLETED', but its end time is not set

DB10059 - Overview

• Message type: E = Error

• Message class: DB10 - Database Monitor: messages

• Message number: 059

• Message text: Job with XDB ID &1 has status 'COMPLETED', but its end time is not set

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 DB10059 - Job with XDB ID &1 has status 'COMPLETED', but its end time is not set ?

  The SAP error message DB10059 indicates that a job with a specific XDB ID has completed, but its end time has not been set. This can occur in various scenarios, often related to database jobs or background processing in SAP systems. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Database Issues: There may be issues with the database that prevent it from updating the job status correctly.
  Job Termination: The job may have terminated unexpectedly or encountered an error that prevented it from properly updating its status.
  System Resource Constraints: Resource constraints (like memory or CPU) could lead to incomplete job processing.
  
  Configuration Issues: There might be misconfigurations in the job scheduling or database settings.
  Locking Issues: If the job was waiting for a lock on a resource, it might not have been able to complete properly.
  
  Solutions:
  
  Check Job Logs: Review the job logs for any errors or warnings that