How To Fix DT104 - Physical pool/cluster & not active

DT104 - Overview

• Message type: E = Error

• Message class: DT - Table activation (incl. indexes)

• Message number: 104

• Message text: Physical pool/cluster & not active

What causes this issue?

Pooled and cluster tables must be assigned to a physical table pool or
table cluster. The physical pool or cluster for the pooled or cluster
table which you are processing is not active. The table therefore
cannot activated.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check whether a physical pool or cluster has already been assigned to
the table. If this is the case, you need only activate it. You obtain
the maintenance screen of a pool or cluster by selecting <LS>Utilities
-> Pool/Cluster -> Change pool/cluster</> in the initial screen of the
ABAP Dictionary.
Otherwise you must assign a valid pool or cluster to the table. The
existing physical pool or cluster can be selected with the R/3
Repository Information System. If necessary, create a new pool or
cluster with <LS>Utilities -> Pool/Cluster -> Create pool/cluster</> in
the initial screen of the ABAP Dictionary.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DT104 - Physical pool/cluster & not active ?

  The SAP error message DT104, which indicates that a physical pool or cluster is not active, typically relates to issues with the database or the underlying storage system that SAP is trying to access. This error can occur in various contexts, such as when working with database tables, data storage, or when trying to access certain data structures.
  Causes:
  
  Database Connection Issues: The database server may be down or unreachable, leading to the physical pool or cluster being inactive.
  Configuration Errors: Incorrect configuration settings in the SAP system or the database can prevent access to the required data structures.
  Resource Limitations: Insufficient resources (like memory or disk space) on the database server can cause it to become unresponsive or inactive.
  Corrupted Data Structures: If the physical pool or cluster has become corrupted, it may not be accessible.
  Maintenance Activities: Ongoing maintenance or backup activities on the database can temporarily render certain pools or clusters inactive.
  
  Solutions:
  
  Check Database