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.

Retail Price Management (MOSC)

Truncating bulk conflict tables

Jun 25, 2014 3:00AM edited Jul 3, 2014 5:00AM in Retail Price Management (MOSC) 1 commentAnswered

if rpm bulk conflict tables are truncated on a daily basis to improve performance of conflict check..what is the impact??

I can see there is batch clears data from these tables on daily basis but deletes data...it does not clears the space.

Instead if these tables are truncated defragmentation will be in control.

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