Fatal Errors - Intergraph Smart Reference Data - Version 10.1 - Training - Hexagon

Intergraph Smart Reference Data Training (10.1)

Language
English
Product
Intergraph Smart Reference Data
Search by Category
Training
Smart Materials/Smart Reference Data Version
10.1

Fatal errors are those that prevent the job from continuing. Once such an error occurs, changes to the database are rolled back. The only changes that are undone are those that were part of the actual stage. After removal of the error cause, you can continue with your work without having to start from the scratch. An example:

Errors and Stages

Imagine you start a job covering all five stages. The first stage succeeds, but the second, writing the interface data into an XLSX workbook, raises an error. In this case, the interface tables remain filled, because this stage was already finished. If the error in stage 2 is caused by an invalid path specification for the export workbook, it is possible to correct the path and start the same job run again. The process does not fill the interface tables again. It starts directly with the second stage.

The following picture displays another case: it shows job status ERROR, which signals a program halt. The job goal was Write to file but the stage finished is No stage is passed yet. Also, in the Summary field, you can see where the error appeared. In this case, if you change the configuration and start the same run again, the interface tables are empty; Fill interface tables is automatically started to fill them. So in this latter case, it is the same as if you start a new job run.

25

Config Validation

Before the first stage starts, the job goes through a validation phase. The same validation can be triggered manually if the user clicks the Initialize Job button.

Validation checks some basic prerequisites, and it also prepares some job-related data. For example, if the user chooses to automatically select all commodity codes for export that are in the spec the user assigned to this job, copying the commodity codes into the Idents tab is done during validation.

Errors in Progress Display

If fatal errors occur in a stage, they are written into the related logfile, which can be seen on the Logf iles tab of Integration->Smart 3D->Smart 3D Transfer Jobs->Transfer Jobs.

Logfile name

The logfile name starts with "SP3D_EJ_", and the job_id is formatted with leading zeros. The job_id is identical for all files of the same job name and same run number.

Following the job_id is the stage to which the logfile belongs.

Finding the error in the logfile

It may be that there are multiple log files displayed on Integration->Smart 3D->Smart 3D Transfer Jobs->Transfer Jobs for the same stage. This happens if the job ends in error and the stage is restarted after the user thinks he solved the problem. The log files are sequenced and ordered in descending order, so the uppermost logfile is the actual one.

The logfile contents can be accessed by double-clicking the logfile on Integration->Smart 3D->Smart 3D Transfer Jobs->Transfer Jobs.

However, if the log files are big, it might be faster to set up a network share to the logfile directory on the database server, and open the file with a text editor.

In certain cases, the logfile is not completely written to disk. If you do not see an error message at the end of the logfile and do not see a success message, the logwriter process of the database might not have unloaded its buffer into the file yet.

A fatal error can always be found at the end of the logfile.