Do you have any question about this error?
Message type: E = Error
Message class: DT - Table activation (incl. indexes)
Message number: 629
Message text: Inconsistency in nametab (type transparent) and DD sources (type pool)
An inconsistency was found between the table type entered in the
runtime object for the table and the table type entered in the ABAP
Dictionary maintenance.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Try to eliminate this inconsistency by entering the required table type
in the ABAP Dictionary maintenance and then reactivating the table. The
runtime object is then rewritten.
Error message extract from SAP system. Copyright SAP SE.
DT629
- Inconsistency in nametab (type transparent) and DD sources (type pool) ?The SAP error message DT629 indicates an inconsistency between the name table (nametab) of a transparent table and the data dictionary (DD) sources of a type pool. This error typically arises when there are discrepancies in the definitions of the database table and the associated data dictionary objects.
Cause:
- Inconsistent Definitions: The most common cause of this error is that the structure of the transparent table has been modified (e.g., fields added, removed, or changed) without properly updating the associated data dictionary objects.
- Transport Issues: If changes were transported from one system to another (e.g., from development to production), and the transport did not include all necessary objects, inconsistencies can occur.
- Manual Changes: Manual changes made directly in the database or through other means that are not reflected in the data dictionary can lead to this error.
- Version Mismatch: If there are different versions of the data dictionary objects in different environments, this can also lead to inconsistencies.
Solution:
- Check the Definitions: Verify the definitions of the transparent table and the type pool in the data dictionary (transaction SE11). Ensure that they are consistent and that all fields are correctly defined.
- Activate Objects: If you have made changes to the table or type pool, ensure that you activate both the table and the type pool. This can often resolve inconsistencies.
- Rebuild the Name Table: You can use transaction SE14 (Database Utility) to check and repair the database table. This may involve rebuilding the name table.
- Transport Consistency: Ensure that all necessary objects were included in the transport request. If not, transport the missing objects.
- Check for Manual Changes: If there were any manual changes made to the database, revert those changes or update the data dictionary accordingly.
- Use SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.
Get instant SAP help. Start your 7-day free trial now.
DT628
Error in writing the technical settings
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DT627
Inactive nametab header could not be written
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DT630
Active nametab could not be written
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
DT631
Update requirements for pool/cluster -> transparent table
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.