How To Fix HH063 - Freespace of specified dbspace has reached a critical size

HH063 - Overview

• Message type: E = Error

• Message class: HH - (Long) text for check tool 'infcfgcheck'

• Message number: 063

• Message text: Freespace of specified dbspace has reached a critical size

What causes this issue?

The freespace of the specified dbspace has reached a critical size.
The point at which dbspace freespace is regarded as critical and which
error severity category is chosen, depends on the following case
classifications:

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

CAUTION: If the critical dbspace names contains the first fragment
of a table which has fields of the type 'byte' or 'text',
then the fill level displayed is misleading:
These dbspaces always have a gross fill level of (almost)
100%. See Note 83117 if you are using the feature
'table fragmenting'.
Uncritical cases:
-----------------
o Freespace is 500M or more
o Dbspace is called 'rootdbs' and freespace is 20M or more
o Dbspace is not called 'rootdbs', the maximum next extent
size can fit into the freespace, and freespace is
5% or more of the total dbspace size
Warning cases:
--------------
o Dbspace is called 'rootdbs' and freespace is less than
20M, but at least 10M or more
o Dbspace is not called 'rootdbs':
o The maximum next extent size cannot fit into the
freespace, but half of the maximum next extent size
can fit into the freespace
o Half of the maximum next extent size cannot fit into
the freespace, but freespace is 250M or more
o The maximum next extent size can fit into the freespace
and freespace is less than 5%, but at least 2.5% or more
of the total dbspace size
o The maximum next extent size can fit into the freespace,
freespace is less than 2.5% of the total dbspace size,
but at least 250M or more
Error cases:
-------------
o Dbspace is called 'rootdbs' and freespace is less than
10M
o Dbspace is not called 'rootdbs':
o Half of the maximum next extent size cannot fit into the
freespace, and freespace is less than 250M
o Freespace is less than 2.5% of the total dbspace size,
and less than 250M

How to fix this error?

A dbspace can be extended using the (normal) SAP administration tool
SAPDBA (heading 'Dbspace') or with ONSPACES.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HH063 - Freespace of specified dbspace has reached a critical size ?

  The SAP error message HH063 indicates that the free space in a specified database space (dbspace) has reached a critical level. This can lead to performance issues or even prevent the database from accepting new data if the free space is exhausted. Here’s a breakdown of the cause, potential solutions, and related information for this error:
  
  Cause:
  
  Insufficient Free Space: The primary cause of this error is that the database space has been filled to a critical level, meaning there is not enough free space available for new data.
  High Data Volume: An increase in data volume due to transactions, logs, or other database activities can lead to rapid consumption of available space.
  Inefficient Data Management: Poor data management practices, such as not archiving old data or not purging unnecessary data, can contribute to the rapid filling of dbspace.
  
  Configuration Issues: Incorrect configuration of the database or the application can lead to inefficient use of