About the Database
The master index database stores information about the entities being indexed, such as people
or businesses. The database stores records from local systems in their original form
and also stores a record for each object that is considered to be
the single best record (SBR).
The structure of the database tables that store object information is dependent on
the information specified in the object.xml file created by the wizard. Oracle Java CAPS
Master Index generates a script to create the tables and fields in the
database based on the information in object.xml. If you update object.xml, regenerating the
application updates the database scripts accordingly. This allows you to define the database as
you define the object structure.
While most of the structures created in the database are based on information
in object.xml, some of the tables, such as sbyn_seq_table and sbyn_common_detail, are standard for
all implementations. The database includes tables that store information about the objects defined
for the master index application as well as tables that store common maintenance
information, transactional information, and external system information. The database includes the tables listed in
Table 1.
Table 1 Master Index Database Tables
|
|
|---|
|
Stores information for the parent objects associated with local system records. This
database table is named by the parent object name. For example, a table
storing company objects is named sbyn_company; a table storing person objects is named
sbyn_person. Only one table stores parent object information for system records. |
|
Stores information for the
parent objects associated with single best records. This database table is named by
the parent object name followed by “SBR”. For example, a table storing company
objects is named sbyn_companysbr; a table storing person objects is named sbyn_personsbr. Only
one table stores parent object information for SBRs. |
|
Stores information for child objects associated
with local system records. These database tables are named by their object name.
For example, a table storing address objects is named sbyn_address; a table storing comment
objects is named sbyn_comment. One database table is created for each child object
defined in the object structure. |
|
Stores information for child objects associated with a single
best record. These database tables are named by their object name followed by
“SBR”. For example, a table storing address objects is named sbyn_addresssbr; a table storing
comment objects is named sbyn_commentsbr. One SBR database table is created for each
child object defined in the object structure. |
|
Lists the applications with which each item
in stc_common_header is associated. Currently the only item in this table is eView. |
|
Stores
information about records that were automatically matched by the master index application. |
|
Stores audit
information about each time object information is accessed from the MIDM.
Note - If audit logging
is enabled, this table can grow very large and might require periodic archiving.
|
|
Contains all
of the processing codes associated with the items listed in sbyn_common_header. |
SBYN_COMMON_HEADER |
Contains a
list of the different types of processing codes used by the master index
application. These types are also associated with the drop-down lists you can specify
for the MIDM. |
|
Stores the local ID and system pairs, along with their
associated EUID. |
|
Stores information about all merge and unmerge transactions processed from either external systems or
the MIDM. |
|
Stores information about fields that are locked for updates in an SBR. |
|
Stores a
list of potential duplicate records and flags potential duplicate pairs that have been
resolved. |
|
Stores the sequential codes that are used in other tables in the database,
such as EUIDs, transaction numbers, and so on. |
|
Stores information about the system
objects in the database, including the local ID and system, create date and
user, status, and so on. |
|
Stores a list of systems in your organization, along
with defining information. |
|
Stores transaction information about an SBR, such as the create or update
date, status, and so on. |
|
Stores a history of changes to each record stored
in the database. |
|
Like the sbyn_common_detail table, this table stores processing codes and drop-down
list values. This table contains additional validation information that allows you to validate
information in a dependent field (for example, to validate cities against the entered
postal code). |
|
