DB Sizing Examples for Release 12 Upgrades
By Steven Chan (Oracle Development) on Mar 27, 2007
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.