2444632 - Error DA300 "No active nametab exists" occurs during table activation in transaction SE11

 

 

During the activation of a table with status "New" in transaction SE11, error occurs as below:

 

대량의 데이타의 꺠짐으로 인해 테이블을 삭제하고 동일한 이름으로 테이블 생성시 아래와 같이 에러가 발생할경우가 있습니다.

 

DA300 No active nametab exists for <Table_Name>
DA432 Termination due to inconsistencies
DT066 Table <Table_Name> (Statements could not be generated)

Environment

• SAP NetWeaver all versions.
• S/4HANA all versions.

Reproducing the Issue

• Start transaction SE11.
• Open a table with display option.
• Activate the table with the magic wand icon.

Other possible case when the error occurs in "ABAP Dictionary Activation" phase during transport.

 

Cause

The database object exists on the database level, but the runtime object of the table does not exist.

Resolution

Depending on whether the table on database level contains records or not (Or whether the records within the table are needed or not), the solution can be different:

 

Condition 1: The database table contains no records.

Solution 1: Delete the table on database level using database tools, then activate the table in transaction SE11.

 

Condition 2: The database table contains records, but the records within the table can be deleted.

Solution 2: Delete the table on database level using database tools, then activate the table in transaction SE11.

 

Condition 3: The database table contains records, and the records within the table are needed.

Solution 3: Rename the database table to another one using database tools firstly. Activate the table in transaction SE11, then delete the newly-created empty table on database level. Rename the table back to original table name again.

 

It may happen that the error still persists even after deleting the database table. The reason might be that the primary index <tab_name>-0 is still existing on the database level. It should have been deleted together with the deletion of table <tab_name>. But it could happen that it was not created based on the original table <tab_name>, but on a QCM8 table QCM8<tab_name>. For example, if the used database's type is oracle, it is possible to check using the SQL command as below:

select index_name, table_name from dba_indexes where index_name = '<tab_name>^0';

If the result shows that the value of field table_name is QCM8<tab_name>, delete both table QCM8<tab_name> and the index <tab_name>^0 based on it. Such problems generally occurs if table conversion terminated with error before, so that the temporary table QCM8<tab_name> and the primary index <tab_name>-0 based on it remained. For details information about table conversion, refer to KBA 2428810 - Frequently asked questions about table conversion. After deleting table QCM8<tab_name> and the index <tab_name>^0, perform one of the solutions above again.

No matter which solution was implemented, it is necessary to perform consistency check afterwards to make sure no inconsistency with the runtime object or database object.

For  details about consistency check, refer to KBA 2180238 - DDIC Inconsistency Check.

 

참고 url : 2444632 - Error DA300 "No active nametab exists" occurs during table activation in transaction SE11 - SAP for Me

https://me.sap.com/notes/0002444632