IM Relationship Resolution Information Center, Version 4.2

Adding tables to the entity database

You may need to add a new database table when adding a new data source.

About this task:

Adding tables to the entity database does not allow resolution on the new data, it is just a place to store data.

It is recommended that you should use a test database when verifying new configurations before applying those new configurations to your production environment.

It is recommended to use existing tables and fields to classify new data if at all possible.

Adding a new table will accommodate expected data that is not yet configured in the system. You should create the new database table to be consistent with your current data model.

Be sure to include the required relevant fields:
  • ENTITY_ID
  • DSRC_ACCT_ID
  • HIST_STAT - required if using sequential history tracking.
  • SYS_CREATE_DT
  • SYS_DELETE_DT
  • SYS_LSTUPD_DT
  • SYS_LSTUPD_US
Procedure:
  1. Create the new table in the entity database.
  2. Create the data mapping for the new table.
  3. Add new database tables to the dictionary.
  4. Define the data mappings for the new table.
  5. Determine the appropriate DQM rules to apply to the new segment and configure those rules through the console.
  6. Verify the new configuration by running known test data through a pipeline and checking the resultant log files.
    1. Verify the test runs without errors.
    2. Check for UMF Exceptions in console.
    3. Check log files nodename.Sql.Err.log and nodename.err for errors.
    4. Verify test results match the expected results.
    5. Check the UMF_LOG table to ensure all records load properly.


Feedback

Last updated: 2009