The below error comes up when exporting/importing a System Landscape Transformation (SLT) system, in system migration ( using SWPM):
(EXP) ERROR: DbslExeRead failed
rc = 103, table “/1CADMC/XXXXXXXX”
(SQL error 942)
ORA-00942: table or view does not exist
INFO: disconnected from DB
During the replication process, SAP LT Replication server creates various objects in the source, target, and in the system where SLT is installed. These objects include ABAP dictionary objects that are created in the system where SLT is installed. However, the ABAP dictionary objects that are created in the SLT system are table definitions that have no corresponding physical table in the system database. Exporting these ABAP Dictionary tables without corresponding physical tables results in errors.
SLT namespaces have the prefix /1CADMC/* or /1LT/*. Table definitions that have this prefix and that have no corresponding physical table in the database of the system where SLT is installed will potentially cause errors during the export.
SAP ideally recommend below three situtation to avoid the situation.
1) Create the Corresponding Physical Tables Automatically
The system can create corresponding physical tables in the database of the system where SLT is installed for the table definitions.
In order to do this, you must set the below parameter for the table DMC_RT_PARAMS:
PARAM_NAME = ‘REPL_CRE_LCL_TAB_ON_DB’
PARAM_VALUE = ‘X’
2) Create the Corresponding Physical Tables Manually
Create corresponding physical tables in the SLT system database for the table definitions that are created in the SLT system.
In order to do this, use transaction SE14 to process individual tables. For mass processing, you can use the function module DD_DATABASE_UTILITY. Other options for mass processing include generating batch input sessions a recording.
3) Exclude the Table Definitions that have no Corresponding Physical Table
In the system in which SLT is installed, view the table definitions that have this prefix (/1CADMC/ or /1LT/) and that have no corresponding physical table. In transaction ST04, navigate to Diagnostics -> Missing Tables and Indexes -> Objects missing in the database -> Tables.
To exclude these tables from the export/import , remove these entries for the relevant .tsk and .str files, and run the export/import again for the failed packages in your system.
Please note the ign modification only applies for /1LT/* or /1CADMC/* tables. Any other error from other tables must first be analyzed.
If you still faces the issue then you can raise an OSS with SAP under component (BC-INS-MIG).
Recommended SAP Note: 2380824