Ansicht
Dokumentation
08880 - Upgrade decision making blues
BAL_S_LOG - Application Log: Log header data TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Upgrade decision making blues
Hi Rick,You have two opportunities to stop before you actually can get to the
620 version. The first is that you must upgrade to 46C before you can
go any higher. The second is that you must to do a codepage
conversion while at the 46C release level before you can upgrade to a
higher release. You can expect some fairly significant disk growth
there (I can only speak for our BW database, which grew 52% in this
step). When all that is done you are actually able to upgrade to a
higher release such as 620.
I would recommend at the minimum going to 46C and doing the codepage
conversion. The codepage conversion time is somewhat proportional to
big your database is so the longer you wait, the longer the
conversion (unless you are doing archiving).
I would give advice on the 620 upgrade but we only have BW at that
level so I could not guarantee that R/3 would behave the same way.
Our current database size is about 375 gig. We have been working
through some issues which I believe are more BW specific than what
you would encounter in an R/3 system.
Our current R/3 plan is to go to the 46C ASCII version by August and
avoid the additional support % for staying on 46B. We may choose to
go higher by next summer depending on what we learn between now and
then. Support package releases do wonders so I am confident that 620
will be a much more robust option by June.
By the way, our BW is still viable on the 740 LPAR that we have it in
(V5R1, 6 processors, 6 gig ram, 700 gig disk (soon to be 1.5 TB)),
but I think the end users would be much happier with it running on an
8XX. The point being that we are running 620 on a lower level of an
Iseries so I expect it will be even better on an 8XX.
Our 500 gig (and growing) 46B R/3 system is running fine on an 8XX
with 8XX application servers.
Pardon my rambling, I hope this helps,
Craig.
--- In DoNotReply@consolut.eu, "Rick Githens <rgithensZg...>"
<rgithensZg...> wrote:
> Greetings Saplings,
>
> Been a while. I was recently promoted to player / coach and all
that
> bitching I've been doing about getting the upgrade rolling is now
my
> decision to make (watch what you wish for and all that). We are
> currently at 4.0B (still), V5R1M0 and have been talking about the
> 4.6C Basis (4.6D frontend) for some time. Now, we are being asked
to
> seriously consider 6.20Basis, etc. Some say the 400 is not a "good"
> server in this environment (but I've been listening to scurrilous
> rumours about the 400 for years), stick to 4.6C. Some say go for it
> and save yourself an extra year on the upgrade train right now.
Some
> say (as always), dump the 400 AND go to 6.20 (just a click of the
> heels, don't you know?) I noticed a few people have the 6.20 Basis
> release up. Is anyone running it in Production? From what did you
> migrate? How much pain and suffering? How much extra juice? (disk,
> memory, cpu,, consulting).
>
> Thanks,
> Rick
Durban Tours - Südafrika Safari
Addresses (Business Address Services) PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 3718 Date: 20240520 Time: 160844 sap01-206 ( 4 ms )
