New Whitepaper: Database Partitioning for the E-Business Suite

Some readers complain that we don't have sufficient documentation to cover all possible scenarios and topics of interest.  This is a valid observation.  As your E-Business Suite deployments grow in complexity and scope, keeping ahead of your questions and new requirements is a constant challenge.

In my position as the editor of this blog, something I do only in my so-called free time, my situation is the odd inverse of yours, namely:  the rate at which we release new Metalink Notes far-outstrips my capacity to read and announce them to the world.  Here's a much-belated announcement about a database partitioning whitepaper produced by our Applications Performance Group.

What Is Database Partitioning?

Partitioning allows a single database table and its associated indexes to be broken into smaller components depending on the table and choice of index partitioning methods.  Several E-Business Suite modules take advantage of database partitioning right out of the box, and custom partitioning is also fully supported.  I've covered database partitioning concepts for Apps environments in more depth in this older article.

Database Partitioning Methods:

Best Practices for Partitioning Apps Databases

As I've noted before, we have a group in our Applications Development division that's dedicated to optimizing the E-Business Suite's performance.  As a member of this Applications Performance group, Mohsin Sameen has worked extensively with some of our enterprise-class customers -- including many of the largest companies in the world -- on fine-tuning the performance of of their high-volume Apps environments.

Mohsin has distilled these experiences into an extensive and in-depth paper on database partitioning:
Mohsin's excellent whitepaper covers topics such as:
  • Overview of database partitioning concepts
  • Table partitioning strategies involving range, list, hash, composite, and multi-column partitions
  • Index partitioning methods, including global and local partitioned indexes
  • Step-by-step decision framework for using partitions
  • Partition maintenance operations
  • Partitioning case study
The knee-jerk reaction answer to a performance problem is often to throw more hardware at it.  If you have a large E-Business Suite environment where the growth rate of your historical transactional data is starting to affect performance, I'd strongly recommend reading this whitepaper.  It's entirely possible that you could use it to squeeze some additional performance out of your existing environment without the added expense of new hardware.

Related Articles


Partitioning is a great performance option but creates some unique testing challenges every time you patch as you have to validate that everything is working as designed. That's hard enough in a system without partitioning.

Our biggest challenge is getting DBAs to walk (apply the latest technology and CPU patches) - most of them want to start off with multi-tier RAC without tech/FP patches and then say the Apps are not "working" correctly. :-(

Just a rant. I'll stop now. :-)

Good stuff and glad to finally see some E-Business supported methods from Oracle.


Posted by John Stouffer on May 28, 2008 at 11:25 PM PDT #

Hi, Michael,Interesting suggestion.  I've passed this along to the Applications Performance group for their comments.  I'll post an update here on their response.Regards,Steven

Posted by Steven Chan on June 11, 2008 at 03:35 AM PDT #

Hi Steven,

It would be great if the EBS Performance Team considered integrating database partitioning on FND_CONCURRENT_REQUESTS. Having a limitation of 50k rows is so 1980s, and many large corporations push more than 50k requests every day. This does not afford much time to resolve issues (requests ending with a status of 'ERROR'.

Thanks -Michael

Posted by Michael Taylor on June 11, 2008 at 05:33 AM PDT #

Agreed on the FND_CONCURRENT_REQUESTS! This is a big headache for us as we push a lot of batch jobs through a day and it gets really slow, really quick.

Also from what I understand Oracle charges a lot for database partitioning in the enterprise edition, correct? This is CPU based and if you have a large DB footprint (which we do) it can get expensive very quickly.

Thanks - Drew

Posted by Drew Poggemann on September 05, 2008 at 01:16 AM PDT #

Hi, Drew,

I believe that our Apps Performance team is working on the FND_CONCURRENT_REQUESTS issue now. I don't have any more details that I can share, but I'll post any news as soon as it becomes available.

>Also from what I understand Oracle charges a lot
>for database partitioning in the enterprise edition,

I'm in EBS Development, and I'm afraid that I don't have a lot of visibility into Database licencing costs or policies. This is something you might want to ask your Oracle account manager. He or she can provide you with specifics around the latest licencing terms.


Posted by Steven Chan on September 05, 2008 at 06:38 AM PDT #

Hi Steven,

Do we have any script or procedure to find out what are all the tables/indexes that are eligible for partitioning?

Please suggest.


Posted by Krishna on September 15, 2011 at 05:05 PM PDT #

Hi, Krishna,

I'm not aware of any EBS-specific scripts for this. You might wish to check the generic DB partitioning documentation to see if they have something along these lines.


Posted by Steven Chan on September 16, 2011 at 07:15 AM PDT #

Download link not working.

Posted by guest on February 03, 2014 at 02:22 AM PST #

Please advise exactly which link you are having problems with.



Posted by Robert Farrington on February 03, 2014 at 04:42 AM PST #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016