4.6C to ECC 6.0 upgrade - disk requirements

[Former Member]

Hello,

I am curious about actual disk space growth in the R3<SID>DATA library when upgrading from 4.6C EBCDIC to ECC 6.0 Non-unicode ASCII. The sizing center suggests allocating a 60% increase for EBCDIC => ASCII and an additional 30-40% for 4.6C => ECC 6.0. Is that true in actual practice? Can anyone post their before and after upgrade sizes for your R3 data library? Does it really grow over 100%? This is becoming a very expensive upgrade for us. Of course, we'll archive beforehand but still, when you look at our dev, test and production systems we are needing a lot of additional disk drives here. What is the real world experience? Thanks!

[Former Member · Accepted solution]

Hello Dave,

Unfortunately the data from the sizing center looks right.

The database is in fact converted to Unicode (except cluster and pool tables) during EBCDIC => ASCII conversion. So the growth would not be significant when you perform ASCII => Unicode conversion later on, unlike other database platform.

To enhance the software functionality, many tables are added, and many tables are extended with more fields during ECC upgrade... more space is needed.

Best regards,

Victor

[Former Member]

Hi Dave,

I had one 4.6C ASCII => ECC 6.0 ASCII upgrade as follows:

Db-Size: 1458 GB 4.6C

1675 GB ECC 6.0

=> +14,8%

I would guess, that the percentage will be higher for smaller systems, because of the totally 90000+ objects in the DB ...

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Thanks Victor, that's what I was afraid of. Anyone else like to weigh in? Let's see some numbers! I'm dying to see some real before and afters. If you went all the way to Unicode, that's OK, too. Who's doubled the size of their R/3 data library on the iSeries just to upgrade to the latest version?