Migrating Data in MDM

Open Advanced Features > Migration.

Select Migration Load composite element and select the Overrides tab.

Open Advanced Features > Migration.

Select the Authored Master Records composite element.

Enable authored record migration by selecting Enable.

Enable Load Master ID, Duplicate Id, and Load Engine Columns.

Select the Master Layer for which the load plan is relevant. Only one can be selected.

To migrate overrides on all available entities, select All Entities.

Otherwise, select individual entities within the Entities section. Double-click the asterisk (*) to begin.

Under Advanced Features > Migration > Task Migration Load, select composite element.

To enable task migration, select Enable.

To also migrate drafts, select Migrate drafts. This adds drafts integration outputs to the plan and is not selected by default.

To override null or empty input values by task template defaults, select Use task defaults. Do not select this when migrating existing tasks, otherwise you lose all the task details.

Under Advanced Features > Migration > Manual Match Decision Load, select composite element.

Select Enable to enable match decision load.

To be able to overwrite eng_ columns, select Load Engine Columns.

Stop the current MDM server and back up the whole solution.

Ideally, copy the previous schema for the MDM storage and keep the old one as backup. You don’t need to copy data tables, for example, [prefix][entity]_I, [prefix][entity]_[master layer], and all [prefix][entity]_K_[matching repository name].

Delete the [prefix]_STATS table, otherwise the migration load does not start. Data statistics are filled in after the migration is finished.

Check that the following exist (prefix = I_ for Internal):

Upload the new configuration and start the new MDM server.

Perform the Migration Load.

Find out the value that is available from the databse sequence [prefix]_ID_SEQ.

-- Example of how to get the current value from an Oracle database
SELECT last_number FROM user_sequences WHERE sequence_name = 'A_ID_SEQ';

Find out the highest id or master_id assigned to any entity, divide it by 1000, and round it up.

If the database sequence is lower than the highest id used, increase the database sequence to have both values equal. Otherwise, continue to the next step.

-- Example of how to increase the sequence as required in an Oracle database
-- Note: Oracle does not let you change the value of a sequence. If you need to change its value, you should recreate the sequence. On the other hand, there is a workaround allowing you to change the value of a sequence without recreating it. For example, if the sequence value is 1000 and you want to set it to 1100, you could do the following:
-- Increase the sequence increment
ALTER SEQUENCE A_ID_SEQ INCREMENT BY +100;
-- Set the required value
SELECT A_ID_SEQ.NEXTVAL FROM dual;
-- Revert the sequence increment to 1
ALTER SEQUENCE A_ID_SEQ INCREMENT BY 1;
-- Check the result
SELECT last_number FROM user_sequences WHERE sequence_name = 'A_ID_SEQ';