/usr/sap/SID Folder 100 % Full

[Former Member]

Hello Gurus

In My SAP Server /usr/sap/SID Folder is 100 % Full ; and its giving me error in sm21

> File: /usr/sap/SID/DVEBMGS00/data/stat

I/O error in audit file /usr/sap/PBA/DVEBMGS00/log/audit_20070520, operation flush

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Failed to write to file, error 0028

> File: /usr/sap/SID/DVEBMGS00/data/stat

Can anybodu guide me the rectification ; in which way i am going to rectify this error

Thanks & Regards

Shishir

[Former Member · Accepted solution]

Hello guy!!!

Go to the Workload Monitor via transaction ST03N. In rares cases (such as space problems in the file system), it can become necessary to delete the statistics file of an SAP instance. To delete: Expert Mode >> Collector and Performance DB >> Statistics Records & File >> Delete File >> 'Instance Name' >> In Dialog step or application (It depends of configuration).

After this, go to transaction ST06 and you can verify if the filesystem it's ok.

Regards,

Alberto Condotta.

[Former Member · Accepted solution]

it was succesfully.

[former_member306260]

Dear all,

How can we review the history of Paging Area ? I had double-clicked to page area in ST02 but just see the lastest snapshot using of paging area.

Thanks.

[isaias_freitas]

Hello Pham,

Despite that this thread is very old, your question has no relation to the original question of this thread.

Please open a new thread.

Regards,

Isaías

[former_member306260]

Thanks Isaias

[Former Member]

Thanks

[andreas_herzog]

<b>any huge trace files under /usr/sap/SID/DVEBMGS00/work?</b> i recently had the problem that /usr/sap filled up to 100% (= 4 GB!) because all work proceses were at trace level 2 generated by a faulty kernel release...after patching, everything went fine

GreetZ, AH

[Former Member]

Hi,

What is your OS? Try to find core under /usr/sap/<SID>

Regards,

Arshad

[former_member204746]

Arshad, This is exactly what I replied, look a few posts back... I even provided a command to find and delete those core files...

[blair_towe2]

Shishir - In addition to the responses you have already received, you may also want to check for notes in the SAP Service Marketplace dealing with security audit logs (Tcodes SM19/SM20). The first entry in your SM21 listing seems to be from an audit log being written. If you haven't cleaned these up in a while, they can take up a significant amount of space. You may consider moving these to a separate volume. If this is your problem, you should talk to your auditors about how long you need to keep these logs online. Perhaps you can keep a year or two and archive the rest.

Regards,

Blair Towe

[Former Member]

You can go ahead and delete the core files generated in

/usr/sap/SID/DVEBMGS00/work.

This gets generated as you may have cancelled the WP with cancel with

core.

But to get free space on permanent basis delete the tranport files of

your hotpacks generated in /usr/sap/trans/EPS/in

Also check do you have any hotpack files .CAR files still lying in the

system. These files generally carry in MB's

Generally, the directories /usr/sap/<SID> and /usr/sap/trans are seperately

mounted filesystems. Thus, deleting any transport files in the EPS/in or

data or cofiles will not fix the problem you are having if this is the case.

If you run AL11 it will tell you where your DIR_DATA and DIR_SORTTMP files

get written, usually, /usr/sap/<SID>/DVEBMGS00/data. The filesystem is

usually mounted as /usr/sap. You may want to add space there, but as

suggested, check for core files on a regular basis. On UNIX, you can run -

find / -name core This will search every directory that sidadm has access

to for core files. You can run it as root to be thorough.

--Sreejesh

[former_member204746]

look for core files and delete them:

find /usr/sap -name core -exec rm {} \;

good luck.

[Former Member]

Hi Shishir,

Please check if there is any tracing active on this instance that is using up most of the space. Also, it looks like there is some type of audit files written as well. If you have set the printing to filesystem, even then this filesystem will be used.

The quickest method to clear the space in this filesystem is to go to SM50, go to menu Process -> trace -> reset -> either "All files" or "work process files".

and then investigate where the space is being used. If the you do need to increase the filesystem, add more disks to it.

Cheers,

Nisch

[Former Member]

Hi,

see whther the stat \usr\sap\sid\DVEMGS00\work\stat.DAT is taking huge size or not..if so delete it or move it to another partition and see

Regards

Umesh K

[Former Member]

Hi Shishir,

Please check the note 6833. May be this one would help you.

You have to set the automatic cleaning of statistics file beacuse those files are consuming the space in you usr/sap directory.

Thanks