Bulk Load Database with Data - Intergraph Smart 3D - Reference Data

Intergraph Smart 3D Reference Data

Language
English
Product
Intergraph Smart 3D
Subproduct
Reference Data
Search by Category
Reference Data
Smart 3D Version
11 (2016)

  • You should back up all Excel workbooks before modifying them and bulk loading. All of the workbooks are delivered with read-only properties.

  • Perform this procedure on a workstation computer with the Bulkload utility and Server Connectivity component installed. Log on with a user name that has database ownership privileges. For more information about necessary components, see the Intergraph Smart 3D Installation Guide available from the Help > Printable Guides command in the software.

  • The bulkload process consumes one Smart 3D license seat.

  • You should close all Excel workbooks before starting the bulkload. Do not open Excel during the bulkload.

  • When you use the Bulkload utility to create a new marine catalog, the Excel workbooks for the Hangers and Supports task must appear last in the list. If they are not placed at the end of the input files list, errors will be generated in the log file.

  • It is not recommended that you create a new catalog database when bulkloading the reference data. The catalog database created when bulkloading is not associated with any site database.

  1. Click Start > All Programs > Intergraph Smart 3D > Database Tools > Bulkload Reference Data.

  2. In the Excel files box, specify the Excel workbooks to load by clicking Add.

    • The default location for reference data workbooks is [Product Folder]\CatalogData\BulkLoad\DataFiles.

    • You can select more than one workbook to bulk load. Hold CTRL, and click each workbook in the Open dialog box.

    • Select the workbooks that contain the parts and cross sections in the Excel files box. You specify the codelist workbooks in the Excel codelist files box.

  3. In the Excel codelist files box, click the browse button to specify the codelist workbooks.

    You must specify a workbook in this box if you are adding a new codelist or modifying an existing codelist. In all other cases, you are not required to populate this box.

  4. Under Bulkload mode, select a mode for the bulkloading process.

    Mode

    Description

    Bulk load to a new catalog

    Creates a new catalog database.

    Append to existing catalog

    Adds new classes only to an existing database.

    Add, modify, or delete records in existing catalog

    Reads flags in Excel workbook to add, modify, or delete data.

    Delete and replace

    Deletes all records in the catalog database and replaces with data in Excel workbooks. New part classes are appended to the catalog.

    If you are re-creating part classes or parts, you must include the R-ClassNodeDescribes sheets in the workbooks in order to establish relationships among the hierarchical nodes in the reference data.

  5. If you want to store geometry for each unique part defined by the Solid Edge model, select Create flavors.

    • Do not select Create flavors when you are creating symbols.

    • The Create flavors option can increase the time needed for the bulkload process. If you are loading Solid Edge flavors, you must have Solid Edge installed on the bulkload computer.

  6. If you are working in a test catalog or a training environment, you can clear the Update Object Type Hierarchy and Catalog Views check box to reduce bulkloading time. However, if you are in a production environment, leave this option selected.

  7. Under Catalog information, select either MSSQL or ORACLE in the Database Type box. This box is active only if you are creating a new database set.

    • If you selected MSSQL, select the name of a server in the Database server name box. This location is where the catalog database and schema are stored (or will be stored, if you are creating a new database set).

    • If you selected ORACLE, select the name of the Oracle net service for the catalog database connection in the Oracle Service box. The service must exist before you choose it in this box. ORACLE is only available if you are creating a new plant database set.

  8. In the Database name box, select the name of the catalog database that you want to update with new reference data.

    • To create a new database, select <New Database>, and type a name for the new database.

    • If you select a site or model database in the Database name box, the utility displays a notification message.

  9. If you are modifying an existing catalog, select the Catalog Schema database name in the Schema database name box.

  10. If you are creating a new catalog, click the browse button beside the Template file to be used to create schema box to specify the template file for the catalog schema.

    • For MSSQL, use the apprepos.dat file to create the catalog schema. This file is located in [Product Folder]\DatabaseTemplates on the computer where the reference data was installed.

    • For ORACLE, use the apprepos.dmp file to create the catalog schema. This file is located in [Product Folder]\DatabaseTemplates on the computer where the reference data was installed.

  11. In the Log file box, click the browse button to specify the name and location of the log file.

    • The default location for the log file is [Product Folder]\CatalogData\BulkLoad\DataFiles, but you can change this location.

    • You must have write privileges to the folder in which you are saving the log file.

    • The log file name must not contain any special characters. However, you can use the back slash when specifying a UNC path to a log file.

    • You must use the file extension .log for the log file.

  12. If you are bulk loading to a new catalog, click the browse button under Symbol and custom program file location and select a SharedContent folder on the server.

    • This box is populated automatically if you are using the Append, Add/Modify/Delete, or Delete and Replace modes. You should not modify the location unless you are sure that you want to change the symbol path for the catalog.

    • To allow all workstations to access the symbols, specify a UNC path to a shared folder on a remote computer, such as the server. The server setup installs the contents of the SharedContent folder under [Product Folder]\CatalogData, so if the computer name is smith, you can type \\smith\SharedContent. At a minimum, users need read access to this share. They need change access in order to modify the symbols.

  13. Click Load. You can see messages in the status bar of the Bulkload utility while it is running.

    If you interrupt the bulkloading process, you might see a Switch To/Retry message. Click Switch To to return to the bulkloading process.

  14. Open the log file to check for any errors or warnings in the bulkloading process. You can quickly scan the Error Analysis section at the end of the log file to check for errors.

  15. Click Close.

  • You can modify the Excel workbooks and bulk load again to correct errors.

  • Create a new log file for each bulkload operation, instead of overwriting the existing one. Check the log file for errors after each bulkload operation.

  • It is recommended that a Project Management backup be done after each bulkload step. If an error occurs, it is easy to restore and correct the problem.

See Also

Bulkload Utility