How To Fix DT979 - Index &-&: Check for database & not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: DT - Table activation (incl. indexes)

• Message number: 979

• Message text: Index &-&: Check for database & not possible

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 DT979 - Index &-&: Check for database & not possible ?

  The SAP error message DT979, which states "Index &-&: Check for database & not possible," typically indicates an issue with the database index in the SAP system. This error can arise due to various reasons, including inconsistencies in the database, issues with the index itself, or problems with the underlying database management system.
  Causes:
  
  Corrupted Index: The index may be corrupted or not properly maintained.
  Database Issues: There may be issues with the database itself, such as corruption or misconfiguration.
  Missing or Inaccessible Data: The data that the index is supposed to reference may be missing or inaccessible.
  Transport Issues: If the index was recently transported from another system, there may have been issues during the transport process.
  Database Locking: The database might be locked or in a state that prevents the index from being checked.
  
  Solutions:
  
  
  Rebuild the Index: 
  
  Use transaction codes like SE14 (Database Utility) to rebuild the index. This can help resolve issues related to corrupted indexes.
  You can also use the DB02 transaction to analyze the database and check for any inconsistencies.
  
  
  
  Check Database Consistency:
  
  Run consistency checks on the database using tools provided by your database management system (DBMS).
  For example, if you are using Oracle, you might use the DBMS_REDEFINITION package to check for inconsistencies.
  
  
  
  Check for Locks:
  
  Use transaction SM12 to check for any locks that might be preventing access to the database or index.
  If there are locks, you may need to release them.
  
  
  
  Transport Issues:
  
  If the issue arose after a transport, check the transport logs for any errors or warnings.
  You may need to re-transport the objects or manually adjust the indexes.
  
  
  
  Database Administration:
  
  Consult with your database administrator to ensure that the database is functioning correctly and that there are no underlying issues that need to be addressed.
  
  
  
  SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that can resolve the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE14, DB02, and SM12 for database management and monitoring.
  Database Documentation: Refer to the documentation for your specific database (e.g., Oracle, SQL Server, HANA) for additional troubleshooting steps and best practices.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be necessary to escalate the issue to SAP support for further assistance.