Register Login

File system /usr/sap/<SID> Full

Updated Sep 27, 2023

USR-SAP-SID is Getting Full

The file system within the R/3 file structure is nearing its capacity. Before proceeding with any deletions, it's important to first assess the available disk space to determine if it's insufficient to accommodate the existing files. Additionally, identify any files within the file system that are no longer needed

Remove Old Spool and Log Files

These files are not necessary for R/3 to function and should be deleted regularly. You can execute the following 3 reports in SE38 to free up some space in the system. These files are for all instances and are located in the global directory:


Report: RSPO1043

Job Description: This job is for a Spool data (Temse) consistency check. The report can delete inconsistencies in the background, and it only deletes inconsistencies if it has found them in repeated runs.

  • Report: RSBTCDEL2
  • Job Description: This job deletes old background jobs from the system.

Delete Old Audit Logs

Go to transaction code SM18 to execute the process.

Delete the Old Core File

The old core file is generated when the previous system is terminated and can be deleted at any time. You can find the work directory at /usr/sap//DVEBMGSxx/work.

Delete the Old Archiving Files

When old data is archived, files are written to the global directory. The naming convention typically follows Rxxmmddn (xx = application, mm = month, dd = day, n = number), for example, RMM12280. If this data is no longer required for productive operation and if the files are saved on tape, you can delete them from the disk. Find the global directory at /sapmnt//global.

Delete the Old ABAP/4 Trace Files

The trace files ATnnnn are in the data directory. The maximum space available for all files is defined by the parameter abap/atrasizequota (in kbytes, default = 10,000 kbytes). You can use Transaction SE30 to delete the files. Find the data directory at /usr/sap//DVEBMGSxx/data.

Delete the Pagefile and Rollfile

The files PAGFILnn and ROLLFLnn are located in the data directory. Do not delete them while the system is online. You can delete the roll and page files when the R/3 System is offline. They are automatically recreated during the R/3 System startup and grow as necessary up to the allowed maximum. Therefore, deleting them makes hardly any sense. The maximum size of the roll file is given by: (rdisp/ROLL_MAXFS – rdisp/ROLL_SHM) * 8 kBytes. A similar formula applies to the paging file. You can move the files to a different file system by defining other values for R/3 parameters DIR_ROLL and DIR_PAGING.

Delete the Old Output Requests

Output requests are stored on the data directory as files SP*. Under normal circumstances, they are deleted automatically when the output is completed. Find the data directory at /usr/sap//DVEBMGSxx/data.

Delete the Old Sort and Extract Files

Temporary files are created by the ABAP commands Sort and Extract. The temporary files for Sort are named S++++ (on NT, .dat is used as an extension; on Unix, there is normally no extension). For the Extract, E++++++. These files are automatically deleted after these commands have been successfully executed. However, if a termination occurs, it can happen that these files remain. Old files can be deleted. The locations of these files can be set using profile parameters DIR_SORT or DIR_EXTRACT. The exact file names are stored in the profile parameters FN_SORT or FN_EXTRACT.

Delete Old Java Archive Logs

Go to the directory below. Find X months old logs in zip files and delete them all. These logs are AS Java log files, and they are written to five files, each with a maximum size of 10 MB. When the fifth file is completed, the new logs start overwriting the old log files. If you enable the archiving process, the set of five files is converted into a ZIP file and stored as an archive on the file system.

Send Work Process to Nowhere

Sometimes, the work process crashes and causes the file system to overflow. The files under the work directory suddenly become very large. First, try to reset the trace file from t-code SM50. If the trace file cannot be reset because someone may be using the file at the moment, you need to send the work process file to nowhere. For example, if dev_w0 is overflowing, you need to send dev_w0 to null. Execute the following command. Please note that the trace file is going nowhere, and you cannot find logs after that.

cat /etc/null > dev_w0

Reset Trace File

Reset the trace file from transaction code SM50 or SMGW.

Delete Old Developer Trace File

Under the work directory, find files that are named as .OLD. These files are automatically named.OLD after the system restart. Please consult with your colleagues before proceeding with the file deletion.