You are on page 1of 3

Reorg tables and indexes in Oracle EBS Applications � Best Practices

Usually in OLTP environment like EBS Applications, tables are often get fragmented
due to multiple DML activities that happens.Fragmented tables cause queries on
those tables to slow down. It is very important to de-fragment this table and to
reclaim the fragmented space from these objects.
For EBS we have also seen that usually gathered statistics, indexing and proper
SQL tuning is plenty to improve and maintain acceptable performance but sometime it
is required to reorg the table.

One primary cause of fragmentation is that when you run delete command on the
tables it delete the rows but doesn�t frees up the memory and also do not changes
the high water mark.

We have also seen that this requirement for doing reorg is more required in
Demantra applications and since Demantra is both OLTP and data warehouse the
applications we must tune accordingly so that query run time can be optimum.
Although this article focus on the EBS/Demantra application tables but it is true
for all oracle databases.


As DML activity happens in the database, it is possible for there to be
discontinuous chunks, or fragments of unused space within the tablespace and
fragmentation within the table rows.

When you insert or update row in table

As rows are added to tables, the table expands into unused space within the space.
It will naturally fragment as discontiguous data blocks are fetched to receive new
rows. Updating table records may also cause row chaining if the updated row can�t
fit into same data block.

When you delete rows from table

At deletion, a table may coalesce extents, releasing unused space back into the
tablespace. A lot of deletes leaves high-water mark behind at a high value. It will
cause slower full-table-scan performance since Oracle must read to the high water


Fragmentation can make a database run inefficiently.

a) Negative Performance impact � SQL statements that performs full-scan and large
index range scans may run more slowly in a fragmented table. When rows are not
stored contiguously, or if rows are split onto more than one block, performance
decreases because these rows require additional block accesses.

b) Wasted Disk Space � It means you have space in your disk which your database can
not use.

The main goal of table reorganization is to reduce IO when accessing the big
database tables.

1. Reorders the table data according to the primary key index.

2. Column reordering to push columns that have no data, nulls, to the end of the
table row
The column reordering can be very useful for tables that have 300+ columns many of
the columns are null. When the null columns are pushed to the end of the row, the
read operation becomes streamlined thus increasing performance.

We usually follow below process for counter table fragmentation. We have also
mentioned some good scripts related to data fragmentation at that end of this


First you need to check exact difference in table actual size (dba_segments) and
stats size (dba_tables). The difference between these value will report actual
fragmentation to us. This means we need to have updated stats in the dba_tables for
the tables.
To understand how we collect latest statistics in EBS, please see this earlier
article Gather Statistics in R12 (and 11i)


Execute Script 1 provided below to find the fragmented tables
It is important that you execute step 1 for gathering statistics first before you
run this script or else result will be inaccurate.
This script will show you tables which are more fragmented. You can identify tables
which are frequently used in your problematic long running queries and target those
for reorg process.
Please note that it is not always a good idea to reorganize a partitioned table.
Partitioning of data is considered an efficient data organization mechanism which
boosts query performance.


We have multiple options to reorganize fragmented tables:

METHOD 1. Alter table move (to another tablespace, or same tablespace) and rebuild
METHOD 2. Export and import the table
METHOD 3. Shrink command . (applicable for tables which are tablespace with auto
segment space management)

Method 1 is most popular and is described below:

METHOD 1. Alter table move

A) Check Table size and Fragmentation in table

It is good idea to check and record what is the current size and fragmentation in
table using script 1 provided below

B) Collect indexes details

Execute below command to find the indexes details
select index_name,status from dba_indexes where table_name like '&table_name';

C) Move table in to same or new tablespace

For moving into same tablespace execute below:
alter table <table_name> move;
For moving into another tablespace, first find Current size of you table from
dba_segments and check if any other tablespace has free space available
alter table <table_name> enable row movement;
alter table <table_name> move tablespace <new_tablespace_name>;
After that move back the table to original tablespace
alter table table_name move tablespace old_tablespace_name;

D) Rebuild all indexes

We need to rebuild all the indexes as move command will make all the index
unusable. Run the alter index command one by one for each index.
select status,index_name from dba_indexes where table_name = '&table_name';
alter index <INDEX_NAME> rebuild online;
select status,index_name from dba_indexes where table_name = '&table_name';

E) Gather table stats

For EBS application�s datbase we use FND_STATS package
exec fnd_stats.gather_table_stats('&owner_name','&table_name');
For normal oracle database, we use DBMS_STATS
exec dbms_stats.gather_table_stats('&owner_name','&table_name');

F) Check Table size and Fragmentation in table

Now again check table size using script 1.
In our case we were able to reduce the table size from 4 GB to 0.15 GB as the table
was highly fragmented.
It is also good idea to see if there are any new invalid objects in database and
run utlrp.sql to compile objects.