Open topic with navigation

TIBCO iProcess® Engine 11.9.1

# pack_nmemo

The `pack_nmemo` table stores memo data associated with memo fields in the pack_data table after upgrading to iProcess Engine 11.6.

Since iProcess Engine version 11.6, all the new memo data associated with the memo fields is stored in the ``BLOB`` data type in the `pack_nmemo` table.

You can migrate case memo data in the pack_memo table to the `pack_nmemo` table when upgrading to iProcess Engine 11.6 or migrate them by using the `swutil` `MIGRATEMEMOS` command after the upgrades.

When a work item is sent out to a queue, memo data is copied from the nmemo table to the pack_nmemo table. The client uses the memo data in the pack_nmemo table to fill out the form correctly. When the form is kept any changed memo data is updated in the pack_nmemo table. When a work item is released memo data is moved from the pack_nmemo table to the nmemo table.

## Structure

The `pack_nmemo` table is structured as follows:

    TABLE pack_nmemo (
    	reqid		number(20)		NOT NULL,
    	node_id		number(5)			NOT NULL,
    	proc_id		number(5)			NOT NULL,
    	casenum		number(20)		NOT NULL,
    	memo_id		number(4)			NOT NULL,
    	memo_index	number(10)			NOT NULL,
    	memo_size	number(10)			NOT NULL,
    	memo_data	blob		NOT NULL,
    	array_idx	number(6)			NOT NULL)

Column | Description
`reqid` | ID of the work item that this memo belongs to, as defined in the staffo table.
`node_id` | ID of the node that this memo is associated with, as defined in the nodes table.
`proc_id` | Number of the procedure that this memo belongs to, as defined in the proc_index table.
`casenum` | Case number that this memo belongs to, as defined in the case_information table.
`memo_id` | Unique (for this case) ID of this memo.
`memo_index` | Index number into the set of rows that make up this memo. This value is always `1`.
`memo_size` | Size (in bytes) of the memo data for this row.
`memo_data` | Memo data.
`array_idx` | Either:
| • | The array element index number of the memo.
| • | `-1`, if the memo is not an array memo field.

## Primary Key

The following primary key is defined for this table.

Key Name | Column(s) | Index Tablespace
`pk_pack_nmemo` | `reqid node_id casenum memo_id memo_index array_idx` | HUGEINDEXSPACE

## Foreign Keys

None.

## Indexes

None.

## Storage

The following STORAGE values are defined for this table.

Value | Definition
Initial | HUGETABLESIZE
Percentage Increase | HUGETABLEPCTINCREASE
Tablespace | HUGETABLESPACE

## Table Activity

The `pack_nmemo` table contains one row for every assigned memo field that contains data (for example, that has a value other than `SW_NA`) in every outstanding step on the system.

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

A row is... | When...
added | Either:
| • | a step containing memo data is sent out.
| • | a memo field is assigned a value on a keep or release.
updated | An assigned memo field has its data changed on a keep or release.
deleted | any of the following occur:
| • | a release instruction for a work item containing memo data is processed by the background process.
| • | a work item containing memo data is withdrawn.
| • | a case containing memo data is purged.

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