SAP Knowledge Base Article - Public

3635247 - Local table configured with storage type "Disk" is consuming excessive memory in SAP Datasphere

Symptom

Local table in SAP Datasphere is configured with storage type "Disk". However, when checking on the Monitoring page, it is observed that the table is consuming significantly more memory than disk. 

Environment

SAP Datasphere

Reproducing the Issue

  1. Go to the Data Builder
  2. Select the Local Table 
  3. On General tab it is possible to confirm that the Storage Type is set to "Disk"
  4. Go to Space Management and click on "Monitor"
  5. On Monitoring page, search for the table name under the "Table Details" section
  6. Observe that the table shows high memory consumption, even though it is configured to use Disk Storage.

Cause

This behavior is caused by an inconsistency between the database and the metadata. The metadata configuration, which defines the storage as 'Disk', may not accurately reflect the current state of the table in the database. In this case, performing a re-deploy of the table can force a re-synchronization between both, restoring the expected behavior.

Resolution

  1. Check if the table is in "Deployed" status in the Data Builder. If it is not deployed, deploy it first and check again the Monitoring page 
  2. If the table is already deployed, change the Storage Type from Disk to In-Memory 
  3. Deploy the table
  4. Change the storage type back to Disk
  5. Deploy the table again 

Keywords

local table, storage type, memory consumption, disk , KBA , DS-MD-TAB , Tables , Problem

Product

SAP Datasphere all versions