There are a variety of reasons for duplicating (i.e. copying) an MDM repository:
• Backup. Duplicate an MDM repository as a backup, allowing you to discard subsequent changes and revert to the point of duplication.
TIP ►► If you duplicate an MDM repository to the same DBMS machine as the original, the repository is not secure against hardware failure, only against user corruption. If your objective is to back up the MDM repository, it is safer to duplicate a repository to a separate DBMS machine.
• Training. Use the duplicate for training purposes or experimentation by designers and other MDM repository maintenance personnel.
• Testing. Use the duplicate for testing purposes, to try out new ideas without affecting or endangering the active, online repository.
• Repartitioning. You can create the duplicate with a different number of partitions than the original.
• DBMS server transfer. You can create the duplicate under the control of a different DBMS Server than the original, to move the MDM repository from one DBMS Server to another as part of the duplication.
• DBMS brand transfer. You can create the duplicate under the control of a different DBMS brand than the original, to move the MDM repository from one DBMS brand to another as part of the duplication.
You can use the Duplicate command to duplicate an existing MDM repository, including masked subsets, and schema-only duplicates that contain no records (see “Setting ” on page 110 for more information).
NOTE ►► You can duplicate a mounted MDM repository that is either loaded or unloaded.
NOTE ►► If you duplicate an MDM repository while it is loaded, it will be locked from being modified during the operation; therefore, duplication should be scheduled with other user activities in mind.
TIP ►► Before duplicating an MDM repository, you should run the Verify > Check command, then run Verify > Repair, and then run Verify
> Check again, to make sure the repository does not contain errors.
MDM Console Reference Guide 153 TIP ►► The structure of an MDM repository cannot be modified while it is loaded. To minimize disruption to MDM client users while the repository is unloaded for modification: (1) duplicate the repository while the original remains loaded; (2) mount and load the duplicate on a different port; (3) make modifications to the duplicate; (4) unload both repositories; and (5) load the duplicate on the same port the original repository was using.
TIP ►► When you duplicate a repository from one DBMS instance to another, MDS tries to instruct the two DBMS instances to perform a whole-table copy. A whole-table copy is very efficient because the target DBMS instance directly contacts the source DBMS instance and pulls the entire table from it. In order for a whole-table copy to work, however, the source and target DBMS instances must be "known" to each other. For example, when duplicating from one Oracle instance to another, the name of the source instance must be in the
tsanames.ora file used by the target Oracle instance. If a whole-table copy cannot be performed, MDS falls back to row-by-row duplication which can result in much slower duplication times.
NOTE ►► Duplicating a slave repository creates a new slave repository that shares the same master as the original slave.
NOTE ►► Duplicating a master repository creates a normal repository.
When you duplicate an MDM repository, MDM automatically generates a report file, which you can view when the process is complete (See
“Reports” on page 211 for more information on reports and how to view them at a later time.)
To duplicate an MDM repository:
1. In the Console Hierarchy tree, right-click on the MDM repository you want to duplicate and choose Duplicate Repository from the context menu, or select the tree node and choose Repositories > Duplicate from the main menu.
TIP ►► If the top-right pane is currently displaying the list of MDM repositories, you can also right-click on the repository in the grid and choose Duplicate from the context menu.
DATA INTEGRITY ►► MDM marks the repository as read-only for the duration of the duplication process, which does not prevent other users from accessing the repository, but does prevent them from modifying its contents and possibly destroying the integrity of the duplicate.
154 MDM Console Reference Guide 2. MDM opens a dialog asking whether you want to perform a Verify >
Check operation. Click Yes to verify the repository or click No to proceed with the Duplicate operation without verifying the repository.
NOTE ►► If the check detects any inconsistencies in the repository, MDM allows you to cancel the duplicate operation and first perform a Verify > Repair. Click Yes to duplicate the repository without repairing the errors, or click No to cancel the duplicate operation so that you can repair the repository.
3. MDM opens the Duplicate MDM Repository dialog shown in Figure 41.
Figure 41. Duplicate MDM Repository dialog (1 of 2)
4. Select the DBMS Server for the duplicated MDM repository from the drop-down list.
TIP ►► To reference a SQL Server named instance, append a backslash (\) and the instance name after the machine name above.
TIP ►► To use Windows authentication, leave the Login empty (requires the SQL Server Allow Windows Authentication Mode parameter in the Master Data Server Settings file (mds.ini) to be set to True).
TIP ►► To remove an entry from the drop-down list of DBMS Servers, make it visible in the closed drop-down control and press Del.
TIP ►► The drop-down list of DBMS Servers includes only those servers that you have previously added to the list and will usually include for selection all the servers to which you might want to connect.
If the desired server is not in the list, click the “…” (browse) button to open the Select DBMS Server dialog, and select from the list of DBMS Servers known to MDM. If the desired DBMS Server is not in this list either, then click the Add button in the Select DBMS Server dialog to open the Add DBMS Server dialog, and select from the list of servers (or type in a new name in the text entry control at the top of the dialog), and choose the DBMS type from the drop-down list.
MDM Console Reference Guide 155 5. Enter the appropriate DBMS login (which must have system
administrator privileges) and password for the selected DBMS Server and click Next.
6. If the Master Data Server is password-protected, MDM opens the Connect to Master Data Server dialog shown in Figure 42 and prompts you to enter your Master Data Server password. Type the password and click OK.
Figure 42. Connect to Master Data Server dialog
NOTE ►► If you have already entered the Master Data Server password during your current MDM Console session, you will not be reprompted. However, if you unmount and then remount the Master Data Server during the current session, you will be required to reenter the password.
7. MDM disables the DBMS Server, Login, and Password fields and enables the Repository Name field, as shown in Figure 43.
Figure 43. Duplicate MDM Repository dialog (2 of 2)
TIP ►► You can click the Options button to open the Repository Options dialog to: (1) change the number of partitions given to the new MDM repository from the default currently set for the Default Partitions DBMS setting; and/or (2) create a subset or schema-only repository (see “Setting ” on page 110 for more information on repository options).
8. Enter the name for the new MDM repository.
9. Click Finish to duplicate the repository.
10. If the duplicate repository name already exists, MDM prompts you to confirm that you really want to overwrite the existing repository. Click Yes to overwrite the repository.
156 MDM Console Reference Guide 11. While the repository is being duplicated, MDM reports the progress in
the Status field for the repository in the Repositories pane. If the repository is unloaded, MDM also changes the repository status icon (shown at left) to two blue dots.
12. When the duplicate process is complete, MDM displays a message dialog indicating whether or not the duplicate was successful, as shown in Figure 44.
Figure 44. Repository Duplicate Complete dialog
NOTE ►► The duplicate MDM repository is not mounted automatically on the Master Data Server after it is created. See
“Mounting and Unmounting an MDM Repository” on page 45 for more information about mounting MDM repositories.
13. To view the report, click Yes. MDM opens the Report Detail dialog to view the XML report.
NOTE ►► You can view any of the reports previously generated by MDM by selecting the Reports table under the Admin node in the Console Hierarchy. See “Reports” on page 211 for more information.
MDM Console Reference Guide 157