Symptom
Importing a package from a space with storage type "HANA Data Lake Files" to a space with storage type "Disk and In-Memory" within the same tenant fails.
Error message: "couldn’t import object [object_id]: we couldn't import your object because the storage type of space [target_space] mismatches."
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."”
Environment
- SAP Datasphere
Reproducing the Issue
- Log in to Datasphere and open Transport > Import.
- Select a package exported from a space that uses storage type "HANA Data Lake Files".
- In Import Options, choose Space Mapping and select a target space that uses storage type "Disk and In-Memory".
- Start the import. The process fails with a storage type mismatch error.
Cause
Product limitation. Importing (transport) objects between spaces that use different storage types is not supported.
Resolution
- Import packages only between spaces that use the same storage type (for example, "HANA Data Lake Files" to "HANA Data Lake Files", or "Disk and In-Memory" to "Disk and In-Memory").
- If the source and target spaces use different storage types, share or move the required objects as an alternative.
See Also
- SAP Help: Transporting Content Between Tenants
Keywords
transport, import, export, package, storage type mismatch, different storage types, hana data lake files, disk and in-memory, space mapping, couldn’t import object, datasphere transport, cross-space import, share objects, data builder share, same tenant , KBA , DS-ACN , Datasphere Content Network and Transport , Problem
SAP Knowledge Base Article - Public