proc_defn

The proc_defn table holds procedure definitions.

Structure

The proc_defn table has the following structure:

TABLE proc_defn (
	node_id		number(5) 		NOT NULL,
	proc_id		number(5) 		NOT NULL,
	pd_version	number(5)			NOT NULL,
	pd_type		number(1)			NOT NULL,
	pd_index	number(10)			NOT NULL,
	pd_size		number(10)			NOT NULL,
	pd_directory	varchar2(25)		NOT NULL,
	pd_file		varchar2(25)		NOT NULL,
	pd_data		blob			NOT NULL)

Column

Description

node_id

ID of the node that this procedure definition is defined on, as defined in the nodes table.

proc_id

ID of the procedure that this procedure definition relates to, as defined in the proc_index table.

pd_version

ID of the procedure instance that this row relates to, as defined in the proc_instance table.

pd_type

Type of procedure definition data stored in this row. Either:

• 0 pro data (textual procedure definition)

• 1 lst data (binary procedure definition)

• 2 nod data (not used)

• 3 gwd data (iProcess Modeler layout information)

• 4 nod data (not used)

• 5 VBA project data (VBA project files)

pd_index

Index number into the set of rows that make up this procedure definition.

If the procedure definition is longer than 30,000 bytes, multiple rows (in 30,000 byte chunks) are used to store the data. Each segment of the procedure definition data is uniquely identified by its pd_index value.

Note:

•

If you have upgraded your system from one of the following versions , existing procedure definitions are divided into 2000 byte chunks :

—

(UNIX Oracle) any Version i9.n-o iProcess Engine, or from a pre-Version 9.0-o(0.15) Process Engine.

—

(Windows Oracle) any Version 9.0-o Process Engine.

•

However, if a procedure definition is modified, the new instance is added using 30,000 byte chunks.

pd_size

Size (in bytes) of the procedure definition data for the current row. This is 30,000 bytes (or 2000—see above) for all but the last row of the procedure definition.

pd_directory

If pd_type is 5, contains the sub-directory path (relative to SWDIR\projects) where any VBA project files related to this procedure definition are stored. Filenames are stored in pd_file.

If pd_type is 0 to 4, this field contains a hyphen.

pd_file

If pd_type is 5, contains the filename of a VBA project file related to this procedure definition (if there is one). The file is physically stored in the location defined by pd_directory.

If pd_type is 0 to 4, this field contains a hyphen.

pd_data

Raw data for this (portion of the) procedure definition.

Primary Key

The following primary key is defined for this table.

Key Name	Column(s)	Index Tablespace
`pk_proc_defn`	`proc_id pd_index pd_type node_id pd_version pd_directory pd_file`	LARGEINDEXSPACE

Foreign Keys

The following foreign key is defined for this table.

Key Name	Column(s)	Referenced in Table...
`fk_proc_defn`1	`node_id proc_id pd_version`	proc_instance

Indexes

The following index is defined for this table.

Index Name	Column(s) Indexed	Tablespace
`idx_proc_defn_fk`	`proc_id node_id pd_version`	LARGEINDEXSPACE
`idx_proc_defn`	`proc_id pd_version pd_type node_id`	LARGEINDEXSPACE

Storage

The following STORAGE values are defined for this table.

Value	Definition
Initial	LARGETABLESIZE
Percentage Increase	LARGETABLEPCTINCREASE
Tablespace	LARGETABLESPACE

Table Activity

The proc_defn table contains one or more rows for each instance of each procedure definition on the system.

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

A row is...	When...
added	a procedure is saved in the iProcess Modeler (thus creating a new instance), or imported.
updated	never.
deleted	a procedure is deleted.

Did you find this helpful?

Yes No