NME Engine Tables

The tables are created automatically based on nme-model.xml configuration files. All the following tables are prefixed based on a prefix definition in the nme-config.xml: [prefix].

Name Pattern for Instance and Master Data Tables

These two types of tables store all the cleansed, matched, and merged data processed by the NME engine. The following pattern is used for General CDI project, but it can differ in other iWay MDS projects:

[prefix][entity_name][entity_type_suffix]

The entity name is based on nme-model.xml.
The suffix is derived from iWay MDS project transformations (it can differ among iWay MDS projects).
- _i stands for instance tables.
- _[Master_layer_name] stands for master tables of particular master domain view.

Examples:

a_party_i
a_party_Master

Top of page

Engine Technical Tables

The following table does not have any business related data. They are used by the NME engine itself to manage its processes.

Table

Description

[prefix]_INL_L

Temporary table for SQL queries, which uses a where condition including an IN statement. An IN list table keeps all long items (usually ID) which are used in joins instead of doing a full scan of a table.

[prefix]_INL_S

Same purpose as _INL_S, but it is used for string items (usually source_id).

[prefix]_ORIGIN

This table is used to store generated origin ID code (hash) and related origin.

[prefix]_TASKS

This table is used to store information about finished tasks (load, export, processDelta)

[prefix]_STATS

This table is used to store information about counts of process data divided into active and inactive (divided per system on instance layer).

[prefix]_TREG

This table is created only when the VLDB persistence/logical transaction is used. It keeps the information about ongoing, finished, and failed logical transactions. Based on this information, the NME engine is able to provide only the committed data when there is an already running transaction.

When all transactions including the garbage collecting process are finished, the table is empty.

[prefix]ENGINE_VARS

This table is used to store certain variables. It currently stores the last modified transactional ID only.

[prefix]EXPORT_REG

This table is used to manage incremental exports. It contains export name and the last exported transactional ID.

[prefix]ID_SEQ

This table (or sequence, depends on DB support) stores the maximum ID assigned by the NME engine.

[prefix]TASK_SEQ

This table (or sequence, depends on DB support) stores the maximum ID assigned by the NME engine (used only for tasks).

Table	Description
[prefix]_INL_L	Temporary table for SQL queries, which uses a where condition including an IN statement. An IN list table keeps all long items (usually ID) which are used in joins instead of doing a full scan of a table.
[prefix]_INL_S	Same purpose as _INL_S, but it is used for string items (usually source_id).
[prefix]_ORIGIN	This table is used to store generated origin ID code (hash) and related origin.
[prefix]_TASKS	This table is used to store information about finished tasks (load, export, processDelta)
[prefix]_STATS	This table is used to store information about counts of process data divided into active and inactive (divided per system on instance layer).
[prefix]_TREG	This table is created only when the VLDB persistence/logical transaction is used. It keeps the information about ongoing, finished, and failed logical transactions. Based on this information, the NME engine is able to provide only the committed data when there is an already running transaction. When all transactions including the garbage collecting process are finished, the table is empty.
[prefix]ENGINE_VARS	This table is used to store certain variables. It currently stores the last modified transactional ID only.
[prefix]EXPORT_REG	This table is used to manage incremental exports. It contains export name and the last exported transactional ID.
[prefix]ID_SEQ	This table (or sequence, depends on DB support) stores the maximum ID assigned by the NME engine.
[prefix]TASK_SEQ	This table (or sequence, depends on DB support) stores the maximum ID assigned by the NME engine (used only for tasks).

Top of page

Engine X-tables

These tables are created only when the VLDB persistence/logical transaction is used. In general, the x-tables are used during each data processing and store a list of IDs to remove from original non-x tables after the transaction is finished successfully. When the transaction is completed (including garbage collector process), these tables are empty.

[prefix]x_stats
[prefix]xengine_vars
[prefix]xexport_reg
[prefix]x[entity_name][entity_type_suffix]

Examples:

a_xparty_i
a_xparty_Master