SAP Knowledge Base Article - Public

3732503 - [RCA PROVIDED] March 25 2026 - SAP Datasphere in US10 region facing a disruption service

Symptom

  • Spaces are not available (service call has failed).
  • HTTP 500 error when accessing spaces.
  • [PoolAcquireError] Failed to acquire connection from pool using pool user REPODUMMY, requestUser is TENANTUSER_the id.
  • Original error message indicates: Database instance resize in progress, Code: 1894, SQL State: HY000.
  • HTTP Status: 500 error
  • Error Code: Technical Message: HANA Database instance resize in progress, Code: 1894, SQL State: HY000
  • Spaces are not available (service call has failed)

Environment

  • SAP Datasphere

Reproducing the Issue

  1. Open Space Management;
  2. Observe that the UI returns "Spaces are not available (service call has failed)" or an HTTP 500 error; backend logs may show a PoolAcquireError and/or "Database instance resize in progress" (Code 1894, SQL State HY000).

Cause

Regression

Resolution

RCA provided:

Impact Description:
The system was not accessible. The issue has been successfully resolved.
 
Incident Description:

On 25 March 2026, a subset of SAP customers may have been affected by a customer experience issue that degraded the performance of their SAP Datasphere tenants. Following the deployment of a new product version, users experienced slowdowns in repository and catalog operations. The performance degradation persisted for several hours and impacted overall service responsiveness, ultimately requiring a system upsize.

Incident Resolution:

Investigating teams identified that elevated request response times caused by database overload were affecting service availability and accordingly SAP initiated an upsizing of the backing database to handle the additional load. After further troubleshooting, technical teams restarted the database to apply the new capacity. These actions restored the affected services' functionality, and sanity tests confirmed that the system was once again performing as expected.

Root Cause Analysis:

Root cause investigations confirmed that the incident occurred as a result of a new product release that performed upgrade actions and functionality verification, which increased demand on the backing database beyond its available capacity. Experts identified the following findings:

  • The new release executed upgrade steps and verification tasks that significantly increased database activity.
  • The elevated database load led to longer request response times for repository and catalog-related operations.
  • The existing database capacity could not absorb the additional load, which affected service responsiveness.
  • Upsizing the database and restarting it were necessary to restore normal performance levels.
Preventive Measures:
  • Improvements made to the product to reduce load created on the backing database when new software is released - Completed
  • Better management of resources on the backing database to avoid overload - In progress

Update on: March 25, 2026:

Related failed requests and runtime is back to normal, so no outages in US10 are expected.
Information regarding RCA will still be updated in this document.

Keywords

datasphere, spaces are not available, service call has failed, http 500, poolacquireerror, failed to acquire connection from pool, database instance resize in progress, code 1894, sql state hy000, tenant unavailable, connection pool, space management, resize in progress, hy000, 1894 , KBA , DS-SM , Space Management , Known Error

Product

SAP Datasphere all versions