Requirements for Free Disk Space 

You have to make sure that there is enough free disk space for the archives that you download on SAP Service Marketplace at service.sap.com.

Patching SAP Kernel and IGS

During SAP kernel or IGS patch, JSPM extracts the archives to a temporary directory under the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/tmp directory. If the total size of the archives is X MB, there must be about 3 times X MB free disk space. When the patch is completed, the temporary directory is deleted.

If you have a heterogeneous cluster, this procedure is repeated for each separate kernel. When each kernel patch is completed, the temporary directory is deleted.

Patching SDM

During SDM patch, JSPM extracts the SDMkit.jar to a temporary directory under the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/tmp directory. Since this archive contains other archives, its extracted size is almost the same, about 10 MB. When the SDM patch is completed, the temporary directory is deleted.

Patching J2EE Components

The deployment of the SCA files from the global EPS inbox directory is handled by SDM. If the total size of an SCA is X MB, at least 2 times X MB must be free under the /usr/sap/<SID>/<Central instance name>SDM/root directory. In addition, during the deployment X MB must be free temporarily under the /usr/sap/<SID>/<Central instance name>/SDM/program/temp directory. Therefore, a total of 3 times X MB must be free under the /usr/sap/<SID>/<Central instance name>/SDM directory.

In addition, depending on the J2EE components, some J2EE Engine containers require additional free disk space. There must be at least enough free disk space to extract all software deployment archives inside the SCAs.

Additional

JSPM requires about 20 MB free disk space under the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM directory for log and data files.