Modes for Logon to the Merge Tool - Intergraph Smart Reference Data Standard Database - Version 12.1 - Installation & Upgrade - Hexagon PPM

Standard Database for Intergraph Smart Reference Data Merge Tool Help

Language
English
Product
Intergraph Smart Reference Data Standard Database
Search by Category
Installation & Upgrade
Standard Database for Smart Reference Data Version
12.1

The users can log on to the SDB Merge Tool by two modes:

  • Differences not shown in hierarchy

  • Show differences in hierarchy

    • Non-CMS Data

    • CMS Data

The sub modes, Selective Merge of Data and Complete Merge of Data, are enabled only after the completion of DB comparison between the source and target databases.

Differences not shown in hierarchy

When the user logs in using this mode, the object hierarchy does not have the functionality to filter the tree nodes based on the data filter options.

This mode is recommended if the user wants to merge a record/dataset from source to target database. This mode is not recommended for performing complete migration of SDB database to SDB 12.1.

In Differences not shown in hierarchy mode, the color coding will be assigned to the hierarchy nodes as follows:

  • All the Identical nodes and records are shown in black color whereas records with differences are shown in orange color.

  • If a node exists only in source database, it is highlighted in blue color and (S) tag is appended at the end of the record.

  • If a node exists only in the target database, it is highlighted in blue color and (T) tag is appended at the end of the record.

Show differences in hierarchy

When user logs into Show differences in hierarchy mode for the first time, data comparison between source and target databases must be done. You can choose to perform the comparison of CMS data and Non-CMS data separately or together based on user requirement. Select the respective option and click Next to start the comparison process.

The comparison process might take several hours depending on the data available in both source and target databases.

User can cancel the comparison process at any stage by clicking the Cancel on the progress form.

User can identify whether the data comparison between source and target databases is completed from the Comparison Status label beside the Show differences in hierarchy mode.

  • Status Not Started indicates that the comparison of data between source and target databases is not yet started. And the data will be compared if the user clicks Next.

  • Status Completed indicates that the comparison of data between source and target databases is completed and user can use this option to start the merging operation.

After the completion of database comparison for CMS data and/or Non-CMS data, following sub modes are now enabled under Show differences in hierarchy mode for user selection for the compared data:

  • Selective Merge of Data

  • Complete Merge of Data

In the Differences shown in hierarchy mode, the color coding is assigned to the hierarchy nodes as follows:

  • Nodes that has same data and the child nodes hierarchy along with the data are displayed in black color.

  • If a node and its data exist only in the source database, it is shown in blue color and (S) tag is added at the end of the node. If the entire hierarchy is source only, the parent nodes until the leaf node level displays in blue color.

  • If a node and its data exist only in the target database, it is shown in blue color and (T) tag is added at the end of the node. If the entire hierarchy is target only, the parent nodes until the leaf node level displays in blue color.

  • If there is any difference in a node, or in the data defined, or any of the child nodes and its data, then the node displays in orange color.

  • If a node is skipped for comparison as the time taken to retrieve data from database exceeded Timeout for DB Comparison, in the tree hierarchy it is displayed in red color. These nodes are also reported in the log file. You can click on the node to view and merge data.

If a node is skipped during comparison, it is also skipped during the complete merge. You can manually navigate to such node, view and merge the data. You can compare to update the tree hierarchy.

In the Object hierarchy, tree nodes are filtered based on the hierarchy filter options. User can filter Identical, Different, Source only and Target only hierarchy nodes by selecting and clearing the check boxes available on the hierarchy.

  • Identical – Refers to the nodes that have same data and the child nodes hierarchy along with the data.

  • Different – Refers to the nodes that have different data, or its child nodes hierarchy along with its data.

  • Source only – Refers to the nodes and its data that exists only in source database.

  • Target only – Refers to the nodes and its data that exists only in target database.

Show differences in hierarchy is the preferred mode for complete migration of SDB 2018 R1/2020 database to SDB 12.1.

  • Multiple merge tool sessions that are connecting to the same source and target database are not recommended to use.

  • If multiple users log into the same source and target databases using the SDB Merge tool and one user logs out from a session, all the other active sessions also get logged out automatically.

Clear Comparison Results

After the completion of data comparison, CLEAR COMPARISON RESULTS option is enabled that allows the users to clear all the comparison results between source and target databases.

This functionality enables the users to either:

  • Restart the comparison process again (or)

  • Cleanup the comparison results after the migration is completed.

Clear comparison results process is irreversible. User must re compare the two databases to use Show differences in hierarchy.

Selective Merge of Data

If the user selects the sub mode Selective Merge of Data and clicks Next, the Merge Tool User Interface displays the differences in the hierarchy. By selecting this mode, user can merge specific set of data selectively from source to target database.

For example, if user wants to merge only few commodity codes only from source to target database, they can use this mode.

Complete Merge of Data

If the user selects Complete Merge of Data and clicks Next, the complete merge process is initiated and all the Source Only and Difference records will get merged into target database from source database.

The complete merge of data is an irreversible process and may take up to several hours depending upon the data available in the source and target databases.

User can identify if the merging process between source and target databases is completed from the Complete Merge Status label located beside the Show differences in hierarchy mode.

  • The status Not Started indicates that the complete merging of data between source and target databases is not completed.

    If the merging process is stopped by the user at any point of time and resumed later by logging in to the same mode again then the complete merge status is shown as Not started. User can resume the merging process by clicking Next, the process continues from the point where it was stopped.

  • The status Completed indicates that the merging of data between source and target databases is completed. Now, the sub modes under the mode Differences shown in hierarchy are disabled and by default the sub mode Selective Merge of Data is selected.

    If the user clicks Next, the Merge Tool User Interface is displayed.

After completion of merge process the message, "Complete Merge of data from the source database to target database is completed" is displayed. User can click View Log File to view the Complete Merge log file.

Complete Merge log file

  • The complete merge log files are generated in HTML file format at the SDB Merge tool location in logs folder. The generated logs have the same hierarchical structure as the nodes in the merge tool. User can click on each parent node and child nodes to navigate and view the changes made during the complete merge process in a tabular format.

  • For the newly added data, the records display in a tabular format under each node in the log file.

  • For difference records, the old and new records are shown side by side similar to the Excel report format, and the difference cells are highlighted in orange color.

  • Errors if any, are displayed in the log file with the error description. Users can review the reported errors and can resolve them in the target database.

The Merge Tool log displays after the Complete Merge of Data as below:

Right Mouse Click (RMC) menu options on Tree Hierarchy

Show differences in hierarchy mode is provided with the following RMC menu options on the hierarchy nodes:

Mark Reviewed/Unmark Reviewed

Using this option, user can mark or unmark any node on the tree hierarchy as reviewed. This enables to identify the nodes under which the user has already completed the merge process.

If the user has marked a hierarchy node as Reviewed, user can hide that node from tree view by clicking Hide Reviewed which is available at the top of the tree hierarchy. Also, user can see all the hidden reviewed nodes by clicking Show Reviewed which is available on top of tree hierarchy.

Unmark reviewed for all child nodes

Using this option, the user can unmark a specific node and all the child records under that node.

Re-compare Hierarchy

Whenever user merges data under a specific node, the comparison status of that node will be indicated as Node Category Not up to Date with the symbol . After all the merge activities are completed under a node, user can re-compare the node by selecting Re-compare Hierarchy option from RMC menu options.

This option will compare all the data under all child nodes present under the selected tree hierarchy node and applies the color coding to the tree nodes again according to the data differences between source and target databases.

  • Re-comparison of hierarchy nodes may take some time based on the data available under the selected node.

  • Users may face errors while re comparing the data, if any duplicate records exist under the selected node in the target database. Users can proceed with the re comparison of the data under a node after clearing the duplicate records.