Issue
Sigma server fails when a Data Import is initiated during a Sigma transition
Product Line
EcoStruxure Building Operation, Satchwell Sigma
Environment
- Sigma
- Building Operation Enterprise Server
Cause
Sigma server fails when an EBO data import is initiated.
Resolution
It is important that the Sigma Database is checked with the Doctor utility (found in SigmaX) before a Sigma transition into EBO is undertaken.
- Longtext - Longtext file contains 'mandarin' type characters - probably from previous BAS/Sigma upgrades. If the file contains these, then Longtext has probably not been used in the past or not used currently. Delete the file (located c:\sigma\data), it will self re-create.
- Shorttext - Shorttext contains an incorrectly formatted entry. Find entry and correct. To find, delete 1 -250, if it continues to fails, the entry in question will be in the range 251 to 500 and keep halving until the entry is found.
- Index A errors - index contains a looping segment, where the page references itself. Correct index as necessary using SigmaX - Doctor.
- Index A errors - page is referenced more than once, i.e. the index page can be opened via two (or more) routes. Correct Index as necessary using SigmaX - Doctor.
Note: the Index should be checked with SigmaX before a transition. - Object corruption - open object in Sigma, if it fails to open, then correct by whatever means that is required, Sigma server will fail at a point during the Data Import.
- Log Sets - Fail to import log sets. To find, in Sigma, locate the logset.rec in the c:\sigma\data\server...folder file, take a copy.
In Sigma, delete 50% of the log sets and try the import again. If it fails, delete another 50% and repeat. Or if it succeeds, then the issue may lie in the 50% of log sets originally deleted, re-instate these using the copied logset.rec file and try again by deleting the other 50% and so forth.
