topic Re: Unicode conversion - space allocation in Application Development and Automation Discussions

Unicode conversion - space allocation

Former Member — Wed, 14 Apr 2010 20:36:23 GMT

Hi All -

We are starting to look at converting our system to Unicode this summer, and I'm worried that we have enough space allocated on UNIX box to allow for successful conversion!

I have read the Unicode conversion guide for allocating additional space to tablespaces on the database, but does anyone have any words of caution / wisdsom for non-tablespace related space needs during a Unicode conversion? For example, I think I have all our /oracle/[sid]/sapdata directories accounted for - I am just trying to determine if I'm missing anything else.

Input is appreciated. Thanks!

Abby

Re: Unicode conversion - space allocation

nils_buerckel — Tue, 27 Apr 2010 08:26:37 GMT

Hi Abby,

additional Hardware requirements due to Unicode are described in SAP note 1139642.

There are no general rules for the additional hardware components needed for a Unicode conversion.

This highly depends on your planned scenario (One Server inplace / new Unicode server) and your downtime requirements. But even knowing the details no one will be able to give exact figures.

If you are lucky, you might find someone who did a similar scenario on comparable hardware.

However we highly recommend to plan for a Sandbox conversion (with a copy of your PRD system), which will be the best approach to find out reliable downtime figures and possible hardware bottlenecks.

Please also have a look at SAP note 857081.

Best regards,

Nils Buerckel

SAP AG

Re: Unicode conversion - space allocation

former_member214857 — Tue, 04 May 2010 12:31:57 GMT

Hi Abby

Actullly Unicode conversion increases database size in order of 60% of the initial size. It is an estimative for this grown.

For reference you can check note:

551344 - Unicode Conversion Documentation

Kind regards