Translate this Page

 

APPLICATION PARTIONING on Oracle E-Business Suite 11i

Not only the database needs to be partitioning to separate the data, we can also partitioning the applications. Why we need partitioning the applications? There are some reason if we talking about this topic, i.e.:

1. Load Balancing

  • EBS with Dataguard

We can separate the inquiry and transaction process. For inquiry can select from Standby Database and for transaction can do DML in Production Database. 

  •  EBS with RAC

We can bind some module to Instance A and others module to Instance B. So in this configuration there are 2 Load Balancer, from database side and application side.

2. Information Lifecycle Management

I’m pretty sure this concept will be trend. Data growing fast and getting bigger every year, but actually user only need to access some data not the whole data. It makes the performance database getting slow. To solve this problem and keep the performance database stable, we need to separate the data into some categorize, i.e. Active Data and Inactive Data. The Active Data contains the latest data that frequently access by users. And Inactive Data contains the old data that rarely or could be never access.

In this topic I will focus on the second reason. And implement it in Oracle E-Business Suite (EBS) 11i. Why only Oracle EBS 11i, because I only test on that version only.

Currently beside Oracle ILM, there are some hardware vendor provide the technology for archiving that integrated with Oracle E-Business Suite, such as IBM Optim and HP ILM. But for some company budget, using that ILM software would be overhead cost. Compliance is another issue that has become an IT challenge across all industries. Corporate governance and regulations such as Sarbanes-Oxley, HIPPA and Basel II require the organizations to retain the information for longer periods of time.

For that reason, so I try to research what the ILM software do when archiving the data. The ILM software that I mention above can purging the Inactive data from Production Database with high level storage to ILM Database with lower level storage.

Using the ILM method has some benefits:

  1. User still can access both Active Data and Inactive Data from single Oracle EBS Applications.
  2. Move the Inactive Data into low level storage, mean it will be cost down the budget instead to increase the high level storage for Production database.
  3. Improve the performance of production database, because the database will scan only the Active Data.
  4. Meet the requirement of corporate governance and regulation to retain the information for longer periods of time.

 The ILM Process.

 TheILMProcess2

 

Step 1:  Current condition (2009), we have 5-years old data in Production database. All the data store in High level storage. If do not maintain it, the data will grow year-by-year and we need to add new disk into the storage. If the enclosure of the storage already full than we should buy new enclosure and off course it not cheap. So we plan to keep 3 years recently data in the production server and move 2 years old to the ILM database.

Step 2:  In the archiving process, 2 years old data (Inactive Data) copy into lower level storage, configure the Oracle EBS, and the users still can read the inactive data but they don’t know, they actually using the different database.

Step 3:  After process archiving is done then we continue to purging the Inactive data in Production server. For process purging, it’s better to use the standard purging that provide by Oracle EBS. To reclaim the space of production database after purge, then we need to reorganize the Production Database.

In another session, I will explain the How-To Application Partitioning on Oracle EBS 11i. Wait n see….

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

   
© 2012 LevICORP's webnote Suffusion theme by Sayontan Sinha