Step 3: Migration of SDB database using SDB Merge Tool - Intergraph Smart Reference Data Standard Database - Version 12.3 - Installation & Upgrade - Hexagon PPM

Standard Database for Intergraph Smart Reference Data Upgrade and Migration

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

SDB Merge Tool available in the SDB product installation location should be hosted in an application server using IIS by following the steps in Installing Standard Database.

After hosting the SDB Merge Tool successfully, you can access the web URL of the tool in a web browser to merge data from the SDB 12.3 delivered source database to the target (customer) database.

For example, url: http://<servername>/SDBMerge/Index.html.

Currently, both Microsoft Edge and Google Chrome browsers support SDB Merge Tool.

Log on to SDB Merge Tool

  1. Open the SDB Merge Tool URL in the preferred web browser.

  2. Select Source and Target Database details from available list of connections. The databases for use in SDB Merge Tool need to be configured by the Administrator using SDB Merge Tool Configurator Tool which is delivered as part of the SDBMergeTool. For more information on how to configure the database connections, refer to Configuring the database connection details using the SDB Merge Tool Configurator.

    • The Source Database is the SDB 12.3 delivered database. This can be created using the SDB Setup wizard, which is delivered with SDB installation.

    • The Target Database is the customer database, which is to be migrated from SDB 12.1/SDB 12.2 to SDB 12.3.

  3. Provide the SRD username and associated password for respective database connections.

    The SRD user must have the PUBLIC or SUPERUSER role to proceed.

  4. Choose the data to merge from the list:

    1. Select Standard Reference Data to merge SDB data to the target database.

    2. Select Smart Materials to merge SMAT data in SDB to the target database.

  5. Select SDB from the Product Group list.

  6. In the Language drop down, select a language to display the descriptions. For example, Language: English

  7. After clicking Login, users are provided with the following options:

    • Differences not shown in hierarchy: Select this option to go directly to the merging operations. In this mode, differences will not be shown in the hierarchical tree view.

    • Show differences in hierarchy: Select this option to show the differences in the hierarchical tree view. It may take several hours to generate this data the first time this mode is selected. If selected, this provides the following options:

      • Non-CMS Data

      • CMS Data

        Users can select both options or either option for comparison. Once comparison is completed, the following sub modes are enabled for comparison completed data.

      • Selective Merge of Data: You can manually merge the required data after the database comparison is completed.

      • Complete Merge of Data: All the data is merged from source database to target database without any manual effort.

        In case you choose to perform only the Non-CMS comparison first, you will have to choose one of the following during login:

      • Perform the comparison for CMS

      • Perform Selective / Complete merge of Non-CMS data. (Comparison completed).

The user is recommended to use the Show differences in hierarchy mode of migration to perform complete migration of SDB 12.1/SDB 12.2 database to SDB 12.3.

  • To Reload/Re-connect to the databases, users must sign out and refresh the browser URL.

  • After DB comparison is completed, the SDB Merge Tool displays the differences between two databases in the tree hierarchy. Also, data from the source and target databases can be seen side by side in the grid view as per the selected hierarchy node.

For more information on SRD-SDB Merge Tool, see Understanding SDB Merge Tool.

Order of Merge/Migration Process

It is recommended to follow the order below to perform a complete merge of data to the target database.

  1. Administration

  2. Document Management

  3. Attribute Management

  4. Table Management

    1. A special node to quickly merge all the Table Detail differences from source to target database.

  5. Geometric Management

  6. Commodity/Ident Management

    1. Special nodes to quickly merge all the Commodity code description and Commodity code layout description differences from source to target database.

    2. Objects under Commodity/Ident Management.

  7. Geometric Rules

  8. Specification

  9. Smart 3D Integration

    1. A special node to quickly merge all the Data Table Configuration Attribute differences from source to target database.

    2. Objects under Smart 3D Integration.

  10. CADWorx Integration

  11. PDMS Integration

  12. SPIso Integration

  13. CMS

    1. Special node to quickly merge all the CMS Class properties and layout differences from source to target database.

    2. Objects under CMS.

For more information on merging of data from each node, see Data Merging Modes in SDB Merge Tool.

  • You must identify, validate, and delete all the invalid idents from the target database after the merging/upgrade process has been completed.

  • You need to validate and delete Target Only records at all the levels.

  • After the migration is completed successfully, log on to the Smart Reference Data > Specification Management and build idents for all the specs.

If you are using SDB 2018 or 2018R1, you can migrate to latest SDB by following the steps given below:

  1. Install SDB 12.1 and migrate your database to SDB 12.1 using the SDB Migration process (steps 1 - 3).

  2. Migrate database from 12.1 to 12.3 using the SDB Migration process (steps 1 - 3) as mentioned above.

Migration Process Flow Chart

SDBMigration flow chart

SDBMigration flow chart legend

  • Users can exit/logout from the SDB Merge tool at any point of time and continue the migration process again after logging in.

  • Recomparison of data nodes may take time depending on the available data under the selected node. It is at the user’s discretion to plan when to re-compare hierarchy.

  • It is not recommended to use multiple instances of the merge tool at the same time if connecting to same source and target databases.

If you are using SDB 2018 or 2018R1, you can migrate to latest SDB by following the steps given below:

  1. Install SDB 12.1 and migrate your database to SDB 12.1 using the SDB Migration process (steps 1 - 3).

  2. Migrate database from 12.1 to 12.3 using the SDB Migration process (steps 1 - 3) as mentioned above.

Special Instructions

Post merge data changes on Target database

  • If you see any discrepancies in commodity geometric relations between the source and target databases, then you must review, evaluate and merge corresponding geometric rules first and then build the geometric relations for the newly merged rule on the target database.

  • You must delete invalid idents from the database after complete merge of SDB 12.3 data into the target SDB DB to avoid export job related issues.

Smart 3D Interface

  • You need to delete target only item mappings from SDB_ITEM_MAPPING & SDB_METRIC_MAPPING to sync with SDB 12.3.

  • In case of complete merge of SDB 12.3 data into SDB 12.1/ SDB 12.2, users need to validate and delete all the Target only records at all levels to sync the database with SDB 12.3.

    For example, S3D Short codes, Link table details, and Data Table mappings.

CADWorx Interface

  • In case of complete merge of SDB 12.3 data into SDB 12.1/ SDB 12.2, users need to validate and delete all the target only records at all levels to sync the database with SDB 12.3.

Logout from SDB Merge Tool

Once the merge activity is complete, users need to select the option to log out of the SDB Merge Tool.

  1. Click on the right header section corner having vertical ellipsis symbol 1 and then click Log Out.

If the user closes the browser without logging out from SDB Merge tool, the database sessions will be released after some time.