Secondary class object in CoreSpatialIndex table - Intergraph Smart 3D - Administration

Intergraph Smart 3D Database Integrity Administration

Language
English
Product
Intergraph Smart 3D
Subproduct
Database Integrity
Search by Category
Administration & Configuration
Smart 3D Version
11 (2016)

Message

Secondary class object in CoreSpatialIndex table.

Severity

Normal.

Detailed Description

A secondary class object should not be in CoreSpatialIndex. This situation might cause performance issues because the spatial index is used for in the filter functionality.

Possible Cause

A seam or profile by projection puts the base landing curve in the CoreSpatialIndex table. This is a bug in the code.

In certain cases, the geometry object is placed in this table, too. This is caused by inconsistency of the control cache flag setting during the modification.

Possible Impacts

The primary impact of this problem is in the performance of the software.

What You Should Do

  1. Open the model.

  2. Run the Clean Database custom command to correct this problem. Check the box beside the object to be fixed and run the clean operation.

  3. Re-run the Check Database Integrity custom command and the DBIntegrity report.

  4. If the object is still posted, contact Smart 3D Support.