Step 3: Migration of SDB database using SDB Merge Tool - Intergraph Smart Reference Data Standard Database - Help

Standard Database for Intergraph Smart Reference Data Upgrade and Migration

Language
English
Product
Intergraph Smart Reference Data Standard Database
Search by Category
Help
Standard Database for Smart Reference Data Version
2020 (12.0)

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

After hosting the SDB Merge tool successfully, users can access the web URL of the tool in a web browser to merge data from the SDB 2020 OOTB Source database to the Target (customer) database.

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

Currently the Microsoft Edge and Google Chrome browsers are supported for using merge tool.

Log on to SDB Merge Tool

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

  2. Enter the Source and Target database details along with the M_SYS schema password.

    • Source Database will be SDB 2020 OOTB Database: This can be created using the SDB Setup wizard, which is delivered with SDB installation.

    • Target Database will be the customer’s database, which is to be migrated from SDB 2018/2018R1 to SDB 2020.

  3. Click Connect and select SDB from the Product Group drop down.

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

  5. 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 up to several hours to generate this data the first time this mode is selected.

The user is recommended to use the Show differences in hierarchy mode of migration to perform complete migration of SDB 2018/2018R1 database to SDB 2020.

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

  • After DB comparison is completed, the 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. SPIso Integration

  12. 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 into the Smart Reference Data software, go to Specification Management, and build idents for all the specs.

Migration Process Flow Chart

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

  • Re-comparison of data nodes my 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.

Special Instructions

Pre-merge data changes on Target database (For SDB 2018 Target Database)

Since SDB 2020 has been updated with many data changes, a few manual steps need to be performed by users to merge some of these changes from the source to target database. Below is the list of changes that need to be done prior to merging respective data from source to Target to make your data in sync with SDB 2020.

Geometric/Part Data

  • For migrating to New Olets Design users need to re-name existing Standard Geometrics as legacy (Old) and merge the new design Geometric Tables. Below is the list of Impacted Geometrics.

Existing Table Name in Target Database

Re-Name To

P_BBPT_DSTD_MSS_SP97

P_BBPT_DSTD_MSS_SP97_OLD

P_BWEL_COG_MSS_SP97

P_BWEL_COG_MSS_SP97_OLD

P_BWEL_DSTD_MSS_SP97

P_BWEL_DSTD_MSS_SP97_OLD

P_BWEL_WGHT_BE

P_BWEL_WGHT_BE_OLD

P_OEBL_DSTD_MFG_BE

P_OEBL_DSTD_MFG_BE_OLD

P_OEPT_DSTD_MFG_BE

P_OEPT_DSTD_MFG_BE_OLD

  • Users need to delete the attribute, P_BOLT_DIA, from the Table Types listed below:

    • P_BI_NUT_HEIGHT_MM

    • P_BI_NUT_HEIGHT_MM_GS

    • P_BI_WASHER_THK_MM

  • The object parameters for a few olet and socket weld flange commodity codes have been updated as per changes done as part of SDB 2018R1. Users need to evaluate and merge these changes as per their requirements.

  • Users need to delete Target only records from the following Filter Geometrics:

    • 1CS1S0A_11

    • 1FE0A01_11

    • 6SK1S01_13

    • 9SK0S01_13

  • SP3D short code has been updated for Commodity Part "LC" and "SC" of Group "VC". Users need to delete existing Smart 3D short codes for Commodity Part "LC" and "SC" of Group "VC" before merging the data from SDB 2020 to SDB 2018 to get the update value.

CMS

For migrating to SDB with export functionality to both Smart Instrumentation and Smart Electrical, users must delete the following CMS class:

To be deleted

INSTRUMENTATION_CABLE_SPEL

The following CMS class should be merged after the above step:

To be merged

INSTRUMENTATIONCABLES

Smart 3D Interface

Users must use the updated Smart 3D interface configurations instead of the existing obsolete configurations to export cables data for both Smart Electrical and Smart Instrumentation.

Configuration

Obsolete

Updated

Transfer Job

SDB_EXP_SPEL

SDB_EXP_SPEL_SPI

Transfer Type

SDB_SPEL_PLC_CABLE

SDB_SPEL_SPI_PLC_CBL

Item Mapping

SDB_SPEL_ITM_MAP_CBL

SDB_SPEL_SPI_MAP_CBL

Template

SDB_SPEL_TPL_CABLE

SDB_SPEL_SPI_TPL_CBL

Data table Configuration

SDB_SPEL_SHT_CFG_CBL

SDB_SPEL_SPI_SFG_CBL

Post merge, data changes on Target database (For SDB 2018 Target Database)

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

  2. Users must delete invalid idents from the database after complete merge of SDB 2020 data into the target SDB 2018 DB to avoid export job related issues.

Smart 3D Interface

  1. Users need to delete target only item mappings from SDB_ITEM_MAPPING & SDB_METRIC_MAPPING to make it sync with SDB 2020.

  2. In case of complete merge of SDB 2020 data into SDB 2018/2018 R1, users need to validate and delete all the Target only records at all levels to make the database in sync with SDB2020.

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

CADWorx Interface

  • In case of complete merge of SDB 2020 data into SDB 2018/2018 R1, users need to validate and delete all the target only records at all levels to make the database in sync with SDB 2020.

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 .

  2. 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.