My Oracle Support Banner

Updating an Offer Causes Table Locking and Screen Timeout (Doc ID 2367193.1)

Last updated on MARCH 07, 2019

Applies to:

Oracle Trade Management - Version 12.2.6 and later
Information in this document applies to any platform.

Symptoms

User A makes a modification to an offer and saves the changes. Then User B tries to update a different offer; when he saves, the screen takes a long time before returning a timeout.

This seems to be caused by a table lock; we found that the SQL that could not be completed by User B's session is the following:

UPDATE QP_PATTERN_PHASES
SET END_DATE_ACTIVE = :B1
WHERE PRICING_PHASE_ID = :B5
AND PATTERN_ID = :B4
AND ( (:B3 IS NULL) OR (END_DATE_ACTIVE IS NOT NULL AND END_DATE_ACTIVE < :B2 ) )

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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