How To Fix DTINF079 - Starting Table Cluster could not be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: DTINF - Information Retrieval Framework texts

• Message number: 079

• Message text: Starting Table Cluster could not be determined

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 DTINF079 - Starting Table Cluster could not be determined ?

  The SAP error message DTINF079 ("Starting Table Cluster could not be determined") typically occurs during data extraction processes, particularly when working with Data Transfer (DT) or Data Warehousing scenarios. This error indicates that the system is unable to identify the starting table for a cluster of tables that are supposed to be processed together.
  Causes:
  
  Missing or Incorrect Configuration: The configuration for the data source or the InfoObject may be incomplete or incorrect, leading to the inability to determine the starting table.
  Table Structure Changes: If there have been changes to the underlying database tables or structures (e.g., renaming, deleting, or altering tables), the system may not be able to find the expected starting table.
  Authorization Issues: Lack of proper authorizations to access the required tables can also lead to this error.
  Data Source Issues: The data source may not be properly defined or activated in the system.
  Transport Issues: If the transport of data sources or related objects was not successful, it could lead to inconsistencies.
  
  Solutions:
  
  Check Configuration: Review the configuration of the data source and ensure that all necessary settings are correctly defined. This includes checking the InfoPackage and the DataSource settings.
  Verify Table Structures: Ensure that the underlying database tables have not been altered in a way that would affect the data extraction process. If changes were made, update the data source accordingly.
  Authorization Check: Ensure that the user executing the data extraction has the necessary authorizations to access the required tables.
  Recreate Data Source: If the data source is corrupted or misconfigured, consider deleting and recreating it.
  Check for Transport Issues: If the issue arose after a transport, verify that all objects were transported correctly and that there are no inconsistencies.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like RSA1 (Data Warehousing Workbench) to check the data source configuration or SE11 (Data Dictionary) to inspect the table structures.
  Logs and Traces: Review the application logs (transaction SLG1) and short dumps (transaction ST22) for more detailed error messages that could provide additional context.
  SAP Community: Engaging with the SAP Community forums can also provide insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.