Recommendation for consistency checks when using Database Table Definitions for Component Types

Last update: 4 August 2017

Recommendation for consistency checks when using Database Table Definitions for Component Types

Summary

We have improved our software products beginning with Fabasoft Folio 2014 Spring Release in dealing with unexpected situations when using Database Table Definitions for Component Types. We recommend customers with lower versions to execute a basic check for the existence of such unexpected situations.

Information

To check if you could be affected please run the following Fabasoft Folio Kernel Expression. This expression performs a sanity check for your Database Table Definitions and no check on user data. Findings during this check will be written to the Fabasoft Tracer. If there is a finding this is not a conclusive information that there is a problem in your installation. But it is recommended to do further checks together with Fabasoft Support.

How to evaluate a Fabasoft Kernel expression is described in the following article:
Executing Expressions without Expression Tester
Our recommendation is to use the “-file” option of fsceval.exe and to save the kernel expression below to a corresponding file on your server. For Microsoft Windows systems tracer.exe (C:\Program Files\Fabasoft\Components\Management\Tools\Tracer.exe) has to be started prior to execution. For Linux systems the trace-output is written to the shell from which fsceval is executed. This output can be captured by piping the output into a file.

Download

Database Sanity Check.zip
(SHA-1: AA47485803B98028CC0DDEE543CF370D2CC97B79)

Expression expression output explained:

#######################################################
Checking COOSVC1 (COO.10.7690.1.2)
Found 6 definitions
-- Skipped table definition for non-compound type 'Object' (COO.1.1.1.402) in 'COOSVC1' (COO.10.7690.1.2)
-- Result ok in 'COOSVC1' (COO.10.7690.1.2) for compound type 'List of Object Versions' (COO.1.1.1.44)
-- Result ok in 'COOSVC1' (COO.10.7690.1.2) for compound type 'Content With Additional Information' (COO.1.1.1.42)
-- Result ok in 'COOSVC1' (COO.10.7690.1.2) for compound type 'Currency' (COO.1.1.1.3611)
-- Result ok in 'COOSVC1' (COO.10.7690.1.2) for compound type 'List of Log Content Mappings' (COO.1.1.1.6625)
++ Found possible match in 'COOSVC1' (COO.10.7690.1.2) for compound type 'AttrTypeDefXY' (COO.XX.XXX.X.XXXX)
== Result  =============================================
Checked 1 services with 6 table definitions
Verified 5 compound type table definitions and found 1 possibly affected definitions
As a result the expression has checked COO-Service COOSVC1 and found 6 table defintins. One is skipped as this one cannot be affected, the check for 4 table definitions results OK and one table definition (in this case “AttrTypeDefXY” with the object address COO.XX.XXX.X.XXXX) is identified as a possible match which should be further analyzed with Fabasoft Support.

Applies to

  • Fabasoft Folio (all versions)
  • Fabasoft eGov-Suite (all versions)
  • Fabasoft eCRM-Suite(all versions)

References