How To Fix AD935 - In the DB Utility select Restart log -> Restart for this table

SAP Error Message - Details

• Message type: E = Error

• Message class: AD - Data Dictionary application messages

• Message number: 935

• Message text: In the DB Utility select Restart log -> Restart for this table

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 AD935 - In the DB Utility select Restart log -> Restart for this table ?

  The SAP error message AD935 typically indicates an issue related to database utilities, specifically when there is a need to restart the log for a particular table. This error can occur during database operations such as data archiving, table maintenance, or when performing certain database utilities.
  Cause:
  The error AD935 can be caused by several factors, including:
  
  Database Locking Issues: The table may be locked by another process, preventing the current operation from proceeding.
  Corrupted Log Entries: There may be corrupted log entries that need to be cleared or restarted.
  Inconsistent Database State: The database may be in an inconsistent state due to previous operations that did not complete successfully.
  Insufficient Permissions: The user executing the operation may not have the necessary permissions to perform the restart.
  
  Solution:
  To resolve the AD935 error, you can follow these steps:
  
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the table. If there are locks, you may need to wait for them to be released or manually unlock them if appropriate.
  
  
  Restart the Log:
  
  Go to the Database Utility (transaction code DB02 or DBACOCKPIT).
  Select the option to restart the log for the specific table that is causing the issue.
  Follow the prompts to complete the restart process.
  
  
  
  Check Database Consistency: Use transaction codes like DB02 or DBACOCKPIT to check the consistency of the database. If inconsistencies are found, you may need to run repair utilities or consult with your database administrator.
  
  
  Review Permissions: Ensure that the user executing the operation has the necessary permissions to perform the restart. You may need to consult with your SAP Basis team to verify user roles and permissions.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  Database Backup: If the issue persists, consider taking a backup of the database before performing any further operations, especially if you are planning to run repair utilities.
  
  
  Related Information:
  
  SAP Notes: Always check for relevant SAP Notes that may provide additional context or solutions for the AD935 error.
  Database Documentation: Review the documentation for your specific database (e.g., Oracle, SQL Server, HANA) for any known issues or maintenance procedures related to log management.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying these solutions, it may be necessary to involve your SAP Basis team or contact SAP support for further assistance.