List Gap Table in Agile Product Lifecycle Management (PLM) System (Doc ID 2958487.1)

List Gap Table 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.3, 9.3.4, and 9.3.5 with limited support.

 

Note: Agile PLM version 9.3.3, 9.3.4, and 9.3.5 are in Sustaining Support.  Any issue rising from the execution of the script 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

The gap table (GAP_TABLE) was introduced in Agile PLM version 9.3.3 to address the issue with running out of sequence numbers generated by AGILEOBJECTIDSEQUENCE.  As the name implies, this table stores groups of gaps in tables that use this sequence.  The Agile application was modified to use this table to get unique values before using the AGILEOBJECTIDSEQUENCE.  Once the values are depleted in this table, the Agile application will resume using the AGILEOBJECTIDSEQUENCE sequence generator.  One or more transactions can concurrently use the gap table. 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.  Therefore, the script that resets the values in the gap table can be run as often as needed to optimize the availability of numbers.

 

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.