/usr/sap/SID is Getting Full, What Do i Do?

The file system with the R/3 file tree is getting full. Which files can be deleted? Before you go through with the steps, please verify that the disk size, is it too small to hold the files and define the unnecessary files inside the file systems.

Delete the old spool and log files.

These are not necessary for R/3 to function and should be deleted regularly. Execute these 3 reports in SE38 to free up some space in the system. These files are for all instances and located in the global directory, /sapmnt/<SID>/global (UNIX / Linux) , \\<sapglobalhost>\sapmnt\<SID>\sys\global (Windows).

• Job Name: SAP_SPOOL_CONSISTENCY_CHECK

Report: RSPO1043

Job Description: Job is for 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.

• Job Name: SAP_REORG_JOBS_NEW

Report: RSBTCDEL2

Job Description: This jobs deletes old background jobs from the system.

• Job Name: SAP_REORG_BATCHINPUT_NEW

Report: RSBDC_REORG

Job Description: This job deletes old batch input sessions and logs.

Delete old audit logs

Go to transaction code SM18 to execute the process.

Delete the old core file.

Old core file is a file that generated when the previous system is terminated. This core file can be deleted at any time. You can find the work directory at/usr/sap/<SID>/DVEBMGSxx/work

Delete the old archiving files.

When old data is archived, files are written to the global directory. The naming convention usually is Rxxmmddn (xx = application, mm = month, dd = day, n = number), for example, RMM12280. If these data are 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/<SID>/global (UNIX / Linux) , \\<sapglobalhost>\sapmnt\<SID>\sys\global (Windows).

Delete the old ABAP/4 trace files.

The trace files AT<instance number>nnnn are in the data directory. The maximum space available for all files is defined by the parameter abap/atrasizequota (in kbytes, default = 10000 kbyte). You can use Transaction SE30 to delete the files. Find the data directory at /usr/sap/<SID>/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. If the R/3 System is offline (but only then!!!), you can delete the roll and page files. They are automatically created again 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 appplies 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/<SID>/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++++++<Extension> (on NT .dat is used as extension, on Unix there is normally no extension) for the Extract, E++++++<Extension>. 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 parameter 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 below directory. Find X months old log in zip files and delete them all. These logs are AS Java log files. These Logs are written to five files, each file 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.

1. Go to the archive directory.

/usr/sap/SID/DVEBMGSxx/j2ee/cluster/server0/log/archive

2. List out old/zip type files.

find . -name *.zip -mtime +90 -exec ls -lrt {}\;

find . -type f -name "*.zip" -exec ls -lrt {} \;

3. To delete, just change the ls -lrt to rm -rf

find . -name *.zip -mtime +90 -exec rm -rf {}\;

find . -type f -name "*.zip" -exec rm -rf {} \;

Send Work Process to Nowhere

Sometimes, the work process crashes and cause the file system overflow. The files under work directory suddenly become very large. First, you try to reset the trace file from transaction code SM50 (i assume the trace file cannot be reset because someone maybe using the file at the moment). So, in order to avoid the file system overflow, you need to send the work process file into nowhere. Let say, the dev_w0 is overflow. So, in order to avoid the dev_w0 file large and larger. You need to send the dev_w0 to null. Execute below command. Please be noted that the trace file is going to nowhere and you cannot find logs after that.

# cat /etc/null > dev_w0

Reset Trace File

Reset the trace file from transaction code SM50, SMGW.

Delete Old Developer Trace File

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