How To Fix SMMSS_SQLJOBS109 - DB13 job cleanup call is cancelled by user

SMMSS_SQLJOBS109 - Overview

• Message type: E = Error

• Message class: SMMSS_SQLJOBS - Message class for SMSS_SQLJOBS

• Message number: 109

• Message text: DB13 job cleanup call is cancelled by user

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 SMMSS_SQLJOBS109 - DB13 job cleanup call is cancelled by user ?

  The SAP error message SMMSS_SQLJOBS109 indicates that a job cleanup process in the DB13 transaction (which is used for managing database backups and other database-related jobs) has been canceled by the user. This can happen for various reasons, and understanding the cause and potential solutions can help you address the issue effectively.
  Cause
  
  User Intervention: The most straightforward cause is that a user manually canceled the job cleanup process while it was running.
  Timeouts: If the job takes too long to complete, it may be canceled due to a timeout setting or user action.
  System Performance: If the system is under heavy load, users might cancel jobs that are taking longer than expected.
  Misconfiguration: There could be configuration issues in the job scheduling or database settings that lead to unexpected behavior.
  
  Solution
  
  Check Job Status: Go to transaction DB13 and check the status of the job. If it was canceled, you may need to restart the job