Will Setting RPM_FUTURE_RETAIL_SEQ from ORDER to NOORDER, to Avoid Massive Blocking on RPM_FUTURE_RETAIL_GTT Table, Impact RPM Functionality? (Doc ID 2564240.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.

Goal

RPM frequently experiences massive blocking on RPM_FUTURE_RETAIL_GTT table which should not be the case. It looks like the wait event is on the sequence RPM_FUTURE_RETAIL_SEQ.

As per the Database (RAC) SR 3-20324122651, it has been recommended to set the RPM_FUTURE_RETAIL_SEQ from ORDER to NOORDER. Will this impact RPM functionality?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Will Setting RPM_FUTURE_RETAIL_SEQ from ORDER to NOORDER, to Avoid Massive Blocking on RPM_FUTURE_RETAIL_GTT Table, Impact RPM Functionality? (Doc ID 2564240.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!