RayVentory Data Hub 12.5

Standard transformation process ignores Oracle instances

Issue:
Standard transformation process does not respect Oracle instance names. As such, they are treated as duplicates and can lead to incorrect results.

Solution:
See a detailed description under the following link: 

RVY200823: RayVentory Data Hub 12.5 ignores Oracle instances in transformation process

MariaDB is not configurable in the installer (MSI)

Issue:
It is not possible to configure or create a Maria DB database. Only SQL Server is supported.

Workaround:
In order to use MariaDB, skip the database creation step during the installation and adjust the configuration before starting the product for the first time. This does not affect Docker-based installation, where the selection of the database type is determined by using a specific environment variable.

Standard reports are not compatible with Maria DB

Issue:
Standard reports are available in SQL Server flavor only. This is due to a number of auxiliary tasks that perform report optimizations, which are written with SQL Server in mind.

Workaround:
Required tasks have to be rewritten to use Maria DB syntax and target a MariaDB database.

Import of XLS files does not work with Maria DB

Issue:
For container tasks, it is not possible to import XLS files, when the database type is set to Maria DB.

Workaround:
Convert your Excel files to CSV format, and import CSV files instead.

Some settings may be lost when upgrading (Windows / MSI)

Issue:
On Windows, when upgrading an existing version of Data Hub server, previous settings like KeyCloak connection or database settings may be lost.

Workaround:
It is recommended to back up the file and restore it after the installation is finished.

Missing ComputedNextRun Column in Task Table After Data Hub U6 Upgrade

Affected version:
RayVentory Data Hub 12.5.5206.116 [Update 6] — when upgrading to any newer version starting from 12.6

Issue:
When upgrading from RayVentory Data Hub 12.5.5206.116 [Update 6] to any newer version, the migration step that adds the column ComputedNextRun to the Task table is silently skipped. The upgrade completes without any error and appears successful, but the column is never created. The missing column only becomes visible at runtime, when the following error appears in the Windows Event Viewer:

1 Invalid column name 'ComputedNextRun'

Workaround:
To verify whether the column is missing on an instance, run the following SQL statement against the system database:

1 SELECT COLUMN_NAME
2 FROM INFORMATION_SCHEMA.COLUMNS
3 WHERE TABLE_NAME = 'Task'
4 AND COLUMN_NAME = 'ComputedNextRun'

If the query returns no results, execute the following script against the system database:

1 IF NOT EXISTS (
2    SELECT *
3    FROM INFORMATION_SCHEMA.COLUMNS
4    WHERE TABLE_NAME = 'Task'
5    AND COLUMN_NAME = 'ComputedNextRun')
6        BEGIN
7    ALTER TABLE [Task] ADD [ComputedNextRun] datetime2(7) NULL;
8        END;