on 04-16-2010 9:27 AM
Hi,
We are facing space crunch in our E:\ where the /usr/sap had been installed.
I am telling our scenario.
We have installed Windows 2003 server X(64) in our Server machine.
It's a Development Portal.
The E:\usr\sap is currently occupying 22.4 GB of space.
The free space in E:\ is: 3.29 GB.
Currently, the SAP NetWeaver Version installed Version : SAP NetWeaver 7.0 EHP1 SP5.
I need to upgrade it to SAP NetWeaver 7.0 EHP1 SP6.
Please tell me what to do?
There are two files in the SDM location which takes more than 1 GB space.
They are 1> E:\usr\sap\DJ1\JC61\SDM\program\pack\packedOrigin_com.adobe.jar
and 2> E:\usr\sap\DJ1\JC61\SDM\program\pack\packedOrigin_sap.com.jar
Could they moved before patching the server to SP6?
Regards
Kaushik Banerjee
Edited by: Kaushik Banerjee on Apr 16, 2010 1:59 PM
Hi,
You should increase the space of drive E:. 25 GB is much too small for a SAP usr\sap file system tree.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
We have taken backup of E:\usr\sap and then restored it back.
The E:\ drive was increased to 80 GB.
Regards
Kaushik Banerjee
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess by now you must have solved the problem if not then
extend you file system/disk partition which will solve you space complexity issue..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Check SAPnote # 16513 and go for the cleanup if possible.Check this note and make your acition plan accordingly.
Next check if you can increase space for this drive. the space you are having will be less.
Best Regards
Niraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For UNIX, we follow below steps.
Steps to be followed to maintain /usr/sap/PRD Filesystem u2013 Do it once a week
u2022 Reset trace files from SM51
u2022 Delete stats file from ST03N
u2022 Remove dev_*.old files from work directory
Command u2013 ls u2013lrt dev*.old
u2022 Remove core file from work directory
Command u2013 du u2013sk *|sort u2013nr|head -10 (It will list top 10 files including core)
u2022 Remove files with name (TRACE and TRACE*) from the location where it exists (generally work/log). These files get generated when user trace is active in the system. We can remove it if the user trace or any other trace is switched off. (We can check its status in ST01 and ST05)
u2022 Remove *.conv & *.read files from work directory. These files are generated due to lsmwu2019s and no longer required in the system.
u2022 Check the global directory and identify different logs that can be removed from the system.
u2022 (Deletion of old spool jobs, workflow logs or job logs)
u2022 Execute the report RSBDCREO from SE38. It removes the log of Batch Input Sessions (SM35).
u2022 Note - Above report is executed from job SAP_REORG_BATCHINPUT. Perform this action once in a month.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.