Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# procedure_lock

The `procedure_lock` table holds the locks that are used to control access to procedures.

## Structure

The `procedure_lock` table has the following structure:

    TABLE procedure_lock (
    	node_id		INTEGER			NOT NULL,
    	proc_id		INTEGER			NOT NULL,
    	lock_state	SMALLINT		NOT NULL,
    	lock_owner	VARCHAR(24),
    	lock_date	TIMESTAMP		NOT NULL,
    	lock_reason	SMALLINT		NOT NULL)

Column | Description
`node_id` | ID of the node that this procedure is defined on, as defined in the nodes table.
`proc_id` | ID of this procedure, as defined in the proc_index table.
`lock_state` | Flag that defines the procedure state: either unlocked (`0`) or locked (`1`).
`lock_owner` | Name of the user who has the procedure definition locked (if `lock_state = 1`), as defined in the user_names table.
`lock_date` | Date and time when the procedure lock was created.
`lock_reason` | Defines why the procedure is locked:
| • | `0` not locked.
| • | `1` locked by the TIBCO iProcess Modeler.
| • | `2` locked by `SWDIR``\bin\swutil IMPORT`.

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s)
`pk_procedure_lock` | `proc_id node_id`

## Foreign Keys

None.

## Indexes

None.

## Table Activity

The `procedure_lock` table contains one row for each procedure on the system that is currently being edited.

Rows are added, updated and deleted in the following situations.

A row is... | When...
added | a procedure is opened (for example, in the iProcess Modeler).
updated | Never.
deleted | a procedure is closed (for example, in the iProcess Modeler).

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO iProcess® Engine