Update to 26 has been installed (see Error itgenobr344: Missing state - #16).
The environment follows the following structure:
- OEM licence
- 3 Exact Online environments
- 1 Invantive Cloud service account
- At server level, there are two configurations
- Configuration 1
- Configuration 2
The conclusion here is that the connection on configuration 1 is successful.
When connecting to configuration 2, it always connects to configuration 1.
What information can assist in debugging this?
An update can be found at:
Do the databases being swapped have the same data container aliases?
In another OEM environment where this issue occurred as recently as last Friday, this problem is not reproducible under release 26.0.165.
The same data container aliases do indeed appear across the two connections:
- Configuration 1
- Configuration 2
- Database 2 - eolbe
- Database 3 - eolbevariant
The advice is to put the latest version 26.0.167 of Invantive Data Hub into production. This should solve the issue. The latest version 26.0.167 or newer can be found at:
Connection seems to be working again at first glance.
We will continue to monitor during the renewal process.
The issue with incorrectly chosen connections still occurs in version 26.0.168. The root cause lies in a fallback scenario where only the database name is matched during retrieval, without also considering the database group name.
Possible workaround 1 is:
- Add an
id=GUID to each <connection>.
This enables the Invantive UniversalSQL engine to accurately determine the desired one.
Possible workaround 2 is:
- Rename the database, for instance by including the environment name.
This ensures that the database name is unique, even if the group name is not taken into account in the comparison.
An improvement has been implemented from release 26.0.169 onwards that resolves this issue.