GL_CONCURRENCY_CONTROL
GL_CONCURRENCY_CONTROL is used internally by Oracle General Ledger programs to prevent deadlock situations from arising.
Details
-
Schema: FUSION
-
Object owner: GL
-
Object type: TABLE
-
Tablespace: APPS_TS_TX_DATA
Primary Key
Name | Columns |
---|---|
GL_CONCURRENCY_CONTROL_PK |
CONCURRENCY_CLASS, CONCURRENCY_ENTITY_NAME, CONCURRENCY_ENTITY_ID |
Columns
Name | Datatype | Length | Precision | Not-null | Comments |
---|---|---|---|---|---|
CONCURRENCY_CLASS | VARCHAR2 | 30 | Yes | Oracle internal use only. | |
CONCURRENCY_ENTITY_NAME | VARCHAR2 | 30 | Yes | Entity for which action is being performed | |
CONCURRENCY_ENTITY_ID | VARCHAR2 | 240 | Yes | The internal ID of the entity for which the action is being performed | |
LAST_UPDATE_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the last update of the row. | ||
LAST_UPDATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who last updated the row. | |
CREATION_DATE | TIMESTAMP | Yes | Who column: indicates the date and time of the creation of the row. | ||
CREATED_BY | VARCHAR2 | 64 | Yes | Who column: indicates the user who created the row. | |
LAST_UPDATE_LOGIN | VARCHAR2 | 32 | Who column: indicates the session login associated to the user who last updated the row. | ||
OBJECT_VERSION_NUMBER | NUMBER | 9 | Yes | Used to implement optimistic locking. This number is incremented every time that the row is updated. The number is compared at the start and end of a transaction to detect whether another session has updated the row since it was queried. |
Indexes
Index | Uniqueness | Tablespace | Columns |
---|---|---|---|
GL_CONCURRENCY_CONTROL_U1 | Unique | Default | CONCURRENCY_CLASS, CONCURRENCY_ENTITY_NAME, CONCURRENCY_ENTITY_ID |