Last updated on MAY 01, 2017
Applies to:Oracle Transportation Management - Version 5.5.04.07 to 6.4.2 [Release 5.5 to 6.4]
Information in this document applies to any platform.
The OBJECT_LOCK table is used on OTM instances with more than one application server to help prevent two or more application servers from taking actions on the same business object, Order Base, Order Release, Location, Shipment or other business objects within OTM. As these objects are being accessed, locks are written to the table to prevent another application server from taking actions on the same object.
When a lock is needed we first look in the OBJECT_LOCK table to see if a record exists and if so is it currently locked by another application server. If a record exists and is own by another application server the process will need to wait in the mediator until the existing lock is released. If there is a record and it is not owned by another application server the record will be updated with the application server making the request. New records will be created as needed.
Since locks are written for all of the business objects being used in OTM this table can grow large very quickly, especially in higher volume clients. In OTM versions 5.5.04.07 and above you have the ability to schedule a clean up of the older OBJECT_LOCK records.
The goal of this document is explain how to check to see if Object Lock Cleanup has been scheduled to run on your OTM instance. This note will also explain how to schedule the process the process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms