Common Error Messages - Intergraph Smart Instrumentation - Help

Intergraph Smart Instrumentation Help

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Help
Smart Instrumentation Version
13.1

This table describes some of the most common error messages which appear in both the Import Report and the log file after an import process takes place. Also included in this table are possible causes and suggested solutions for each case.

Empty Component Number of Tag Number

Reason: The loop identifier segment of the imported tag is empty.

Solution: Modify the source data. Modify the import naming conventions.

Empty Loop Number of Loop Number

Reason: The loop identifier segment of the imported loop is empty.

Solution: Modify the source data. Modify the import naming conventions.

Illegal Instrument Type of Tag Number

Reason: The instrument type you want to import does not exist in the target domain (see Note 1 below).

Solutions:

  • Modify the source data.

  • Import instrument type data into the COMPONENT_FUNCTION_TYPE table first.

  • Clear the Validate tag and loop segments check box (see Note 3 below).

Illegal Equipment Name of Tag Number

Reason: The imported tag equipment name does not exist in the target domain (see Note 1 below).

Solutions:

  • Modify the source data.

  • Import data into the EQUIPMENT table first (see Note 3 below).

Illegal Equipment Name of Loop Number

Reason: The imported loop equipment name does not exist in the target domain (see Note 1 below).

Solutions:

  • Modify the source data.

  • Import data into the EQUIPMENT table first (see Note 3 below).

Illegal Loop Function of Loop Number

Reason: The imported loop function segment value does not exist in the target domain.

Solutions:

  • Modify the source data.

  • Import loop function data into the LOOP_PROC table first (see Note 3 below).

Illegal Measured Variable of Loop Number

Reason: The imported loop measured variable segment value does not exist in the target domain.

Solutions:

  • Modify the source data.

  • Import loop function data into the LOOP_PROC table first (see Note 3 below).

Illegal <Unit> Number in Tag Number

Reason: The imported <unit> number is different from the target <unit> number (see Notes 1, 2 below).

Solutions:

  • When importing more than one plant hierarchy item, make sure that you have specified the data import level and selected Apply on the Import Level tab of the Link Properties dialog.

  • Modify the source data.

  • Modify the import naming conventions.

Illegal <Unit> Name in Tag Number

Reason: The imported <unit> name is different than the target <unit> name (see Notes 1, 2 below).

Solutions:

  • When importing more than one plant hierarchy item, make sure that you have specified the data import level and selected Apply on the Import Level tab of the Link Properties dialog.

  • Modify the source data.

  • Modify the import naming conventions.

Illegal Area Number in Tag Number

Reason: The imported area number is different than the target area number (see Notes 1, 2 below).

Solution:

  • When importing more than one plant hierarchy item, make sure that you have specified the data import level and selected Apply on the Import Level tab of the Link Properties dialog.

  • Modify the source data.

  • Modify the import naming conventions.

Illegal Plant Number in Tag Number

Reason: The imported plant number is different than the target plant number (see Notes 1, 2 below).

Solution:

  • When importing more than one plant, make sure that you have specified the data import level and selected Apply on the Import Level tab of the Link Properties dialog.

  • Modify the source data.

  • Modify the import naming conventions.

The Process Function is not found

Reasons:

  • The imported process function name is different than the target (note that this variable is case sensitive and that this value is usually capitalized).

  • The process function name in the COMPONENT or COMPONENT_FUNCTION_TYPE table is different than the process function name value in the PROCESS_FUNCTION table (see Note 1 below).

Solution: Modify the import source and define correct mapping codes for instrument process function assignment. For details, see Process Function Mapping Codes for Instrument Index Import

The Instrument Type is not found

Reason: In the COMPONENT table, the CMPNT_FUNC_TYPE_ID column value contains an invalid reference to the COMPONENT_FUNCTION_TYPE table.

Solution: Modify the link settings or the source data, or clear the Validate tag and loop segments check box.

The Instrument Type does not match the Tag Number

Reason: In the COMPONENT table, the instrument type value in the COMPONENT_NAME column (tag number) is different than the value in the CMPNT_FUNC_TYPE_ID column.

Solution: Modify the link settings or the source data, or clear the Validate tag and loop segments check box.

The Instrument Type does not match the Process Function

Reason: The process function of the tag number does not comply with the process function type, for example, Flow, Temperature, and so forth.

Solution: Modify the link settings or the source data, or clear the Validate tag and loop segments check box.

User has selected to reject row on data mismatch

Reason: The Import Utility rejected a mismatched source row (see Note 4 below).

Solution: Modify the link properties on the Import Mode tab of the Link Properties dialog.

User has selected to disallow overwrite

Reason: The Import Utility has rejected a source row that is identical to an existing target row (see Note 4 below).

Solution: Modify the link properties on the Import Mode tab of the Link Properties dialog.

User has selected to disallow insertion

Reason: The Import Utility rejected a source new row (for example, the Import Utility is only updating the target data) (see Note 5 below).

Solution: Modify the link properties on the Import Mode tab of the Link Properties dialog.

Unique value not found

Reason: The imported table primary key value does not match the primary key value in the table from which it is derived (see Note 6 below).

Solution: Make sure the table that provides the value for the primary key is selected for import.

This is not a numeric value

Reason: An attempt has been made to import a non- numeric field to a numeric field.

Solution: Make sure you selected the appropriate links in the Link Explorer.

Invalid data

Reason: Inappropriate symbols were used in one or more imported fields. An incorrect comparison criteria was applied in the current import process (see Note 7 below).

Solution: Select the Use reserved symbols with import on the General tab of the Link Properties dialog. Make sure you have correct comparison criteria settings. See Target Table Definition for more information about this option.

Data is empty

Reason: The Import Utility has imported a Zero-ID row (see Note 8 below).

Solution: This message does not indicate an error.

  1. This message is specific for the case in which you select the Validate tag and loop segments check box on the Tag/Loop tab of the Link Properties dialog. See Set the Tag/Loop Parameters for more information.

  2. By default, the target <unit> is the one you selected when you started the current import session. If you selected during the import setup process to import data into additional <units>, the target <unit> would be any of these <units> which data will be imported into during the import process. See Importing Data into Multiple Plant Hierarchy Items or Projects for further information about importing data into additional target <units>.

  3. As a rule of thumb, always import data into reference tables before importing data into the tables they refer to. When importing data using the Module (multiple tables) import method, make sure that all appropriate reference tables have been selected for import. The corresponding message in the table varies according to the relevant reference table.

  4. This message is typical for the case in which you select the Insert option on the Import Mode tab of the Link Properties dialog.

  5. This message is typical for the case in which you select the Reject rows on the General tab of the Link Properties dialog. See Set Properties for Handling Mismatched Data to learn how to handle mismatched data.

  6. This message is typical for the case in which you import a table whose primary key is derived from another table's primary key. In this case the table the primary key belongs to must also be imported. For example, the PD_GENERAL table primary key, CMPNT_ID, is derived from the COMPONENT table. Therefore, the PD_GENERAL table primary key value must exist in the COMPONENT table.

  7. This message is reported by your SQL platform. The name of the field the problem occurred in appears under Column Name in the Import Report. In this case we highly recommend that you refer also to the information regarding this import attempt in your log file.

  8. Most Smart Instrumentation tables contain a Zero-ID row that is used to maintain the linkage between the tables in the database. During the import process this row is not transferred from the source data to the target data, in which case the Import Utility displays an appropriate message in the Import report.