- Below error is coming up during the Upgrade in SPAM/ SAINT.
Phase CHECK_REQUIREMENTS: Explanation of Errors
Inactive runtime objects exist for the following ABAP Dictionary
objects. This represents a system inconsistency and can cause errors
when importing the Support Package Queue. The import is only continued
if no inactive runtime objects exist.
Proceed as follows:
- Open a new mode
- Start transaction SE11
- Enter the relevant object and activate it
- If it is not possible to activate it using transaction SE11, contact
SAP Support using component BC-DWB-DIC-AC
- Repeat the import phase. If no further inconsistencies are found, the
import is continued
Phase CHECK_REQUIREMENTS: inactive runtime objects
Object Type Object Name
- Check SE11:
Table /ASU/XXX_CONTNV does not exist in the
Upon checking the consistency of table in SE11 after moving ahead from above message:
Technical log for mass activation
See log DDIC20200908194734:ACT
TABL /ASU/XXX_CONTNVwas not activated
End of activation of worklist
- Click See log
Database Log: DDIC20200908192751:ACT
INDEX IN "ED9#POOLI"
LONG IN "ED9#POOLD COMPRESS YES"
SQL0107N The name "ED9#POOLD COMPRESS YES" is too long. The maximum
length is "18". SQLSTATE=42622
DDL time(___1): ........21 milliseconds
The SQL statement was not executed
Table /ASU/XXX_CONTNV (Error adjusting the database)
Table /ASU/XXX_CONTNV was not activated
Software Update Manager -ABAP
Database -DB6, DB2
R3load, DB6, DB2, deferred table creation, compression, PAT05, SQL error -107, SPAM, Support Packages, SQL0107, SQL0107N, SQL0010N , KBA , BC-UPG-OCS , Online Corr. Support (Tools:Supp.-Pack., Addon Install/Upgr) , BC-DWB-DIC-AC , ABAP Dictionary Activation and Conversion , BC-DB-DB6-SYS , Database Interface/DBMS , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.