List Database Sequences in Agile Product Lifecycle Management (PLM) System
(Doc ID 2957201.1)
Last updated on OCTOBER 12, 2023
Applies to:
Oracle Agile PLM Framework - Version 9.3.1.0 and laterInformation in this document applies to any platform.
Goal
List database sequence utilization in Agile PLM.
Scope
This document applies to the following products and versions:
· Oracle Agile PLM version 9.3.6
· Oracle Agile PLM version 9.3.1.x, 9.3.2, 9.3.3, 9.3.4, and 9.3.5 with limited support.
Note: Agile PLM version 9.3.1.x, 9.3.2, 9.3.3, 9.3.4, and 9.3.5 are in Sustaining Support. Any issue rising from the execution of the scripts attached to this Knowledge Management (KM) article cannot involve Oracle Development on these versions of the product. Sustaining Support policy details can be obtained at https://www.oracle.com/us/support/library/057419.pdf
Purpose
Sequence generators, which are database objects, provide unique integer values used by the Agile application. These are often used for applying a relationship between two objects on the system. This can be a primary key for a table or unique value for an item, such as a part number. Sequence numbers are incremented sequentially and are independent of any transaction. One or more transactions can concurrently increment the same sequence and neither one can obtain the value of the other transaction. This means sequence numbers acquired by each transaction may have gaps since some of the available values may have been used by other transactions, or by transactions being rolled back.
Note: The script attached to this KM article will not gather any sensitive business data. The information gathered by this script should come from a production system. It will gather only diagnostic information and it is completely safe to run on a production system while the system is in use.
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 |