Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Demantra Solutions - EBS (MOSC)

Is Sales Data Table Reorganization sensitive to the number of records (rows) in the table?

Mar 14, 2013 11:58AM edited Mar 14, 2013 10:14PM in Demantra Solutions - EBS (MOSC) 3 commentsAnswered

In a recent implementation we have about 80 million records on sales data.

Over the planning cycle we have seen that performance decreases as more users input information into demantra.

We have ran several times the sales data reorganization table following [ID 1085012.1]

This is my understanding of the sales_data reorganization process:

i. Check for fragmentation (out of order ratio)

ii. Rebuild the data table and while rebuilding, reordering the columns so that columns with no data will be at the end of the table.

iii. Then import the data back based on the primary key

iv. Confirm that table fragmentation (out of order ratio) has decreased

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month