on 09-09-2014 3:09 PM
Dear expert,
I have just applied SPS12 on our Solution Manager system. In result, the database has grown,
a lot of alerts for low space in the sapdata filesystems were triggered, our solaris admins had to
increase them. As it is quite cumbersome for them to extend filesystems (they say, actions on the
storage are also required!), they have asked to plan how much space would be required quite a
long time in advance (like now for the next year!!).
I have tried to explain them how complicated it is to plan, and I am really wondering if such a
planning is possible at all... Probably each SPS lets the database grow by a different amount of
GB, also it depends on which kind of system is it applied - a BW system has just a couple of
components, an ERP system has quite a lot of components!
Maybe there is a note (I recall something like a central note) for an SPS. Could you please
advise if such notes contain the DB free space requirements ? I found
but it contains just the components for NetWeaver and absolutely no word about DB free space
requirements.
So, I am kindly asking for some advice on that topic or to share some experience with me.
I can share on my side, that SUM requested me to increase PSAP7302 by 4 GB and I think that
several data files, which are set on AUTOEXTEND grew a little bit as well...
Thank you!
Hello Symon
As far as I know there is not estimate given in any SAP note for the SP updates. The SUM guide speaks about the database space requirements but that is basically for an EHP update or a release upgrade which is in the range of 50 GB to 200 GB. If you are doing an SP update using SUM or using the traditional SPAM/SAINT then you extend the tablespace or have 20% free space and yes you need to monitor them.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Reagan,
Yeah, I know that, but we have the systems just since a few months... And moreover, the system on which this problem first occurred, is our Solution Manager, on which I did its first SPS since its initial installation. I checked, and historically nothing grew for months, till I did the SPS.
So I took your suggestion for those 20% free, requested 45% more (to be safe) and that's it. I will give you the points for the correct answer, but would be very thankful, if someone would be able to add a statement, made of SAP, how much DB space an SPS requires...
P.S.: What really screwed me up, was SGEN, which then made the DB grow further...
Thanks a lot !!
Hello Symon
At present I don't see an SAP note suggesting the free space in the database to be considered for an SP update apart from the one mentioned in the SUM guide. If I come across such a recommendation, I will make sure to update that here as I have made a note of this thread.
And yes thanks for the points even though it was just a helpful one.
Regards
RB
Hi Symon,
It is difficult to estimate by how much DB will grow during a patch application.
We normally ensure that tablespace have atleast 15 - 20 % free space before any patching activities begin.
Also ensure that filesystems have 15 - 20% free space to allow expansion.
Regards,
Deepak Kori
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.