Question Re: /usr/sap/SID is getting full for JAVA stack in Technology Q&A

/usr/sap/SID is getting full for JAVA stack

former_member201054 — Tue, 16 Jul 2013 17:17:06 GMT

Hi ,

/usr/sap/SID is getting full for a Java stack system. Can you anybody guide for the files to be deleted under the mentioned path without any harm.

Please guide.

Thanks in advance

Re: /usr/sap/SID is getting full for JAVA stack

Former Member — Tue, 16 Jul 2013 17:26:14 GMT

Hi Daniel basis,

You need to check the std_serverX.out file size in work directory.

When your java is running , then server node uses this file continuously and store the output information of the activity executed on JVM.

So to delete the above file , you need to stop the corresponding node and remove the file from the directory and again start the server node which will create a new std_serverX.out file.

Please check and confirm us.

With Regards

Ashutosh Chaturvedi

Re: /usr/sap/SID is getting full for JAVA stack

Former Member — Tue, 16 Jul 2013 18:08:03 GMT

Hi Daniel,

Kindly go to /usr/sap/SID and then execute ls -ltr and see which directory is occupying more space .

Mostly you can find the space occupied in JC** instance.

The most occupied space will be with the server nodes . So go to path

/usr/sap/SID/JC**/j2ee/cluster/server0/log . Generally these logs will be archived / zipped when they reach maximum limit and will be placed in /usr/sap/SID/JC**/j2ee/cluster/server0/log/archive/

Delete all the files except the files that are on the current day in the directory /usr/sap/SID/JC**/j2ee/cluster/server0/log/archive . Remaining files need not to be maintained so delete them which will fetch you more space .

For further info please find the below link.

http://dc582.4shared.com/doc/omec1btx/preview.html

Re: /usr/sap/SID is getting full for JAVA stack

Manas_Vincit — Tue, 16 Jul 2013 18:10:57 GMT

Hi Daniel,

Check below threads , you will get idea which files need to be delete .

http://scn.sap.com/thread/1511850

http://scn.sap.com/thread/2026284

and Note 1589548 - J2EE engine trace files fills up at a rapid pace

Thanks

Manas Behra

Re: /usr/sap/SID is getting full for JAVA stack

pavan_anjimeti — Tue, 16 Jul 2013 18:28:00 GMT

Hi Daniel,

Can you check is there any huge number of *jrfc.trc files in /usr/sap/<SID>/JC00/j2ee/cluster/server0 ?

If you have any backend system JCO rfc issues, trace files will be growing extremely. please fix those issues first.

Usually in java stack the node trace files will be automatically archive/zipped when they reach to max. size and moved to /usr/sap/<SID>/JC00/j2ee/cluster/server0/log/archive.

These node trace files need not be maintained except recent date, we can delete the old date archive log/application trace files.

Regards,

Pavan

Re: /usr/sap/SID is getting full for JAVA stack

Reagan — Tue, 16 Jul 2013 19:31:22 GMT

Hello

You need to look into the server0 directories present in the /usr/sap/SID file system.

Additionally provide the size of the file system and the number of server nodes and the heap configuration.

Also what is this Java system used for ?

Regards

Re: /usr/sap/SID is getting full for JAVA stack

sapguru-2 — Tue, 16 Jul 2013 21:44:58 GMT

Check if you have the following parameter in Configtool, this will create a huge Mempry Dump file everytime your Java Stacks gets an error.

-XX:+HeapDumpOnOutOfMemoryError

Re: /usr/sap/SID is getting full for JAVA stack

Former Member — Wed, 17 Jul 2013 03:16:51 GMT

Hi Daniel,

Please check the retention period which you have decided for keeping old log files.

If required you can delete old log files and memory dump files which will be created whenever

either Java system go down or there is some critical problem.

This will provide you some space in the filesystem.

Thanks and Regards,

Kunal Gahlot

Re: /usr/sap/SID is getting full for JAVA stack

divyanshu_srivastava3 — Wed, 17 Jul 2013 03:28:50 GMT

Hi Daniel,

Here is what you should do:

1. Use du - command to check size of your instance directory and its folders. This will give a better idea where to check for large file.

2. Goto /usr/sap/SID/.../serverX/ and check for dumps eg, heap or java core. If there are any move them to some other file system for analysis or delete them.

3. In the same directory check for goto log - archive and apply the same method of move or delete.

4. Reduce the trace level, n the size of future files will also be small

5. In your work directory, you can check for core dumps. If there then do the same.

6. In work, you can remove files with extension .00x or .0x for eg. std_server0.out.001

7. Have a look in data directory of you instance.

Add few more gigs to the same file system.

Regards,

Divyanshu