Symptom
- When creating a data product, a specific local table does not appear in the list of available artifacts, while other local tables appear as expected.
- Integration/Replication Monitor shows a failure with activity MERGE_FILES for the affected local table.
- Error observed: "SQL error 2048: column store error ... executor: plan operation failed; Could not connect to remote source".
Environment
- SAP Datasphere
Reproducing the Issue
- Open the data product creation dialog.
- Attempt to add a local table as an artifact.
- Observe that the intended local table is missing from the artifact list while other local tables are available.
Cause
- A column in the affected local table used the data type TINYINT, which caused the integration/replication to fail. Because the table integration was failing, the local table did not surface as an artifact in the data product creation.
Resolution
The INYINT column type is planned to be supported on wave 2026.13. For wile, apply the below solution:
- Review the schema of the affected local table and identify columns defined with the TINYINT data type.
- Change the TINYINT column(s) to INT (or a supported equivalent) in the local table definition.
- Rerun the replication/integration for the local table to ensure a successful load.
- Open the data product creation dialog again and verify that the local table now appears as an artifact.
- If issues persist, check the Integration/Replication Monitor to confirm there are no remaining errors (for example, MERGE_FILES failures or connectivity errors) and resolve them accordingly.
See Also
Keywords
datasphere, data product, artifact not showing, local table missing, replication monitor, integration monitor, merge_files, sql error 2048, column store error, could not connect to remote source, tinyint, data type change, table schema, artifact list, data marketplace , KBA , DS-DM , SAP Datasphere Data Marketplace , Problem
Product
SAP Datasphere all versions
SAP Knowledge Base Article - Public