Database sizing for the E-Business Suite can be a tricky business. Doing sizing estimates for major upgrades, like moving from Apps 11i to 12 can be even tricker, given the degree of data model changes involved.
Our Applications Performance Group has released an informative white paper with sample data from one of their internal benchmark environments, which they upgraded from Release 11i (11.5.10.CU2) to Release 12. Interesting findings: they tested two upgrade scenarios, one with three years of historical data, and the other with twelve years of data. The large Apps database with 12 years of data went from 6.6 TB to 7.2 TB, an increase of ~8%.
This white paper covers contains:
- Tablespace and schema sizing information
- Information on required post upgrade concurrent jobs
- Upgrade timing
- Some best practices to manage the upgrade of Release 12
- Oracle Applications Release 12 Upgrade Sizing and Best Practices (Metalink Note 399362.1)
Naturally, these results won't map directly to your own upgrade, since your transactional mix (and level of master-detail complexity) will be unique to your own organization. However, this paper is useful in that it shows the general ballpark.
If you have data on your upgrade tests, by the way, we'd be delighted to hear from you. Feel free to post a comment to this story or drop me a private email. I'll be sure to pass on your comments to our Apps Performance team for you.
Related
Comments (7)
Thanks for the data on your upgrade, Fadi. I appreciate your taking the time to share this information with our readers.Regards,Steven
Posted by Steven Chan | March 28, 2007 7:53 AM
Posted on March 28, 2007 07:53
please ignore my previous post i managed to get the correct size for, before upgrad the database was 262GB (without the application tire) and after the upgrade it become 273GB (this without the application tire).
with the application tire it was 311GB before the upgrade and after the upgrade it become 343GB
i hope that was helpful
fadi
fadi
Posted by Fadi Hasweh | March 28, 2007 8:51 AM
Posted on March 28, 2007 08:51
thank you steven, i appreciate the time you spent on post to this great blog
fadi
Posted by Fadi Hasweh | March 28, 2007 11:46 AM
Posted on March 28, 2007 11:46
Hello Fadi,
application tier size is 311GB ?!
Probably, you can purge logs and CP outputs.
Regards,
Viacheslav
Posted by Viacheslav | March 30, 2007 1:36 AM
Posted on March 30, 2007 01:36
Can you tell me what was the Uniform Extent Size for the Tablespaces ?
Posted by Fernando | December 3, 2008 9:57 AM
Posted on December 3, 2008 09:57
Fernando,
I'll pass on your question to our Applications Performance Group. If they're able to extract this information from their testbed notes, I'll post their reply here.
Regards,
Steven
Posted by Steven Chan | December 3, 2008 1:41 PM
Posted on December 3, 2008 13:41
Hi, Fernando,
Our Applications Performance Group managed to dig up details. Here's what they said:
We tested with 1m, 4m and auto all with good performance (started with 128k which was too small and did affect negatively some large jobs).
We finally settled with auto and it is the most space efficient.
Regards,
Steven
Posted by Steven Chan | December 4, 2008 3:21 PM
Posted on December 4, 2008 15:21