During a recent DataMiner upgrade to 9.6 CU16, these errors were observed. Looking at the ‘C:\Skyline DataMiner\Tools\CentralTableDefSQLserver.sql‘ script used to create the central database, the columns being reported are defined as specified in the script.
Can these errors be ignored as it looks like a wrong check is being done?
10.185.134.116|2020-07-22 08:18:38|step|Step 19/30: UpgradeDB
10.185.134.116|2020-07-22 08:18:39|progress|Checking local database…
10.185.134.116|2020-07-22 08:18:39|progress|Checking central database…
10.185.134.116|2020-07-22 08:18:40|progress|9 tables found in database
10.185.134.116|2020-07-22 08:18:41|error|Different column definition for ‘alarm.Toa’: Expected = ‘DATETIME2’ Was = ‘datetime NOT NULL’
10.185.134.116|2020-07-22 08:18:41|error|Different column definition for ‘alarm.UserStatus’: Expected = ‘SMALLINT NOT NULL’ Was = ‘smallint’
10.185.134.116|2020-07-22 08:18:41|error|Different column definition for ‘info.Toa’: Expected = ‘DATETIME2’ Was = ‘datetime’
The errors reported are correct. The definition check is executed by SLDatabase which does not rely on the ‘C:\Skyline DataMiner\Tools\CentralTableDefSQLserver.sql’ for the definitions. This mismatch can occur on servers that have their schema created on a SQL version older than SQL 2005 and have been updated to a more recent version.
It is advised to update the reported columns to the expected definition using the correct ALTER TABLE syntax for you CentralDB-setup (See the SQL documention for more info).
A task could be created for software to update the ‘CentralTableDefSQLserver.sql’ and to have SLDatabase update the incorrect definitions to the expected ones when a mismatch is detected.