SAP Knowledge Base Article - Public

3732629 - SAP Datasphere tenant is unavailable due to unexpected full disk

Symptom

  • SAP Datasphere tenant is unavailable; landing page shows: "An unexpected error has occurred."
  • HTTP Status: 500 error; Error Code: unexpectedError; Technical Message: HANA Database instance is starting, Code: 1891, SQL State: HY000.
  • Disk usage reached 100%, preventing the instance from operating.
  • Monitoring may show overall storage below total capacity while the effective DATA volume is full.

Environment

  • SAP Datasphere

Cause

  • Datasphere's HANA Cloud instance may experience a full disk/storage condition when running in a multi-volume setup where LOG and DATA are on separate volumes.
  • The multi-volume setup is usually enabled in large Storages.
  • Due to this architecture, the effective usable storage for DATA is lower than the total storage capcacity selected in the tenant configuration.
  • The LOG volume has a fixed provisioned size and is fully managed by HANA Cloud and cannot be used for customer data.
  • Continuous growth (for example, system/runtime data and audit logs) consumed the effective DATA volume until it reached full utilization.

Resolution

The effective usable and current usage for DATA is visible in the Disk Storage Usage card in SAP Datasphere's System Monitor, which reads the provisioned volume sizes directly from the HANA Cloud M_DISKS view. SAP recommends using this values as the reference for capacity planning. 

  1. Temporarily pause or reduce data-ingesting activities to prevent increasing the usage of storage.
  2. Increase Datasphere's storage to provide sufficient space. For example, upsize total storage so the effective DATA volume has free capacity.
    Otherwise it my trigger automatic lock for all spaces in tenant, as a prevention mechanism. See SAP Note 3718046 - Locked spaces in SAP Datasphere due to high tenant disk usage.
  3. Verify the tenant is up and running after the upsize. Check if the new storage size is reflected in System Monitor and Tenant Configuration.
  4. Plan capacity based on the effective DATA volume (not the total provisioned storage) and closely monitor data growth, including audit logs, system/runtime statistics, and metadata via System Monitor.

See Also

Keywords

datasphere tenant down, disk full, data volume full, multi-volume, data log separation, http 500, unexpectederror, code 1891, sql state hy000, cleanupauditlog, reclaim failed, snapshot page, storage upsize, monitoring discrepancy, space management , KBA , DS-SM , Space Management , Known Error

Product

SAP Datasphere all versions