ACTIVITY_LOCK table

ACTIVITY_LOCK table

The activity lock count contention point can affect the performance of certain large-scale workflows. To avoid this issue, the information in the LOCK_COUNT column of the ACTIVITY table is broken into multiple rows of the ACTIVITY_LOCK table. The ACTIVITY_LOCK¹ table tracks the completion of an activity. The server and thread identifiers control which row must be incremented; only one thread attempts to update a row in this new table at any time.
Column Name Description Data type

PROCESS_ID^* Unique ID of a process. Primary key. References PROCESS (ID). Numeric

ACTIVITY_ID^* Unique ID of an activity. Primary key. References ACTIVITY (ID). Numeric

SERVER^* String identifier of the server that makes the update (cell/node/server). Primary key. Character (255)

THREAD_ID^* Identifier of the thread (within the server) making the update. Primary key. Numeric

LOCK_COUNT Updated value, an integer counter to track when workflows are complete; it might be positive, negative, or zero. Numeric

^* Indicates the column is required and not null.
¹ Indicates the table is added in release 5.0.
Parent topic: Workflow tables

Column Name	Description	Data type
PROCESS_ID^*	Unique ID of a process. Primary key. References PROCESS (ID).	Numeric
ACTIVITY_ID^*	Unique ID of an activity. Primary key. References ACTIVITY (ID).	Numeric
SERVER^*	String identifier of the server that makes the update (cell/node/server). Primary key.	Character (255)
THREAD_ID^*	Identifier of the thread (within the server) making the update. Primary key.	Numeric
LOCK_COUNT	Updated value, an integer counter to track when workflows are complete; it might be positive, negative, or zero.	Numeric