Installing DVB

In general, all Datavault Builder containers are stateless, as all information is directly stored on the processing database. Therefore, the datavault builder modules (webgui, api, core, scheduler) can be restartet without loosing data. Please be aware, that a restart will cause running loads to fail.

Problem

Possible Cause

Possible Resolution

Module

Webgui shows error: Connection error: could not connect to server: Connection refused Is the server running on host 127.0.0.1 and accepting TCP/IP connections on port 5432

The API service is running but has no connection to the core module. And the core module is NOT running

Restart the core container

webgui

Webgui shows error: JWT secret not known

The API service is running but has no connection to the core module. But the core module is running

Restart the API container

api

MSSQL: Error response from daemon: invalid mount config for type “bind”: invalid mount path: ‘$(pwd)/secrets/authenticator_password.txt’ mount path must be absolute. See ‘docker run –help’.

Using PowerShell

Use CMD instead of PowerShell

Client DB

Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..

  • localhost does not work with docker

  • MSSQL instance is not recognized.

  • Use host.docker.internal instead of localhost

  • only use the hostname.

Core

Exasol: NOTICE: dvb_core.f_test_fdb_connection_jdbc() = Could not establish connection: SQL Error in DatbaseConnection.getConnection: syntax error, unexpected identifier_chain2, expecting assignment_operator or ‘:’ [line 1, column 13] (Session: 1643732619895821890)

Wrong Exasol version

“Impersonate” is only supported from version 6.1.

Core
Is there an interdependency between the DVB version and the database?

  • No, you should just respect the minimal requirements for your own database.

Do you support Microsoft Azure for cloud deployment?

  • Generally: If a database runs in a cloud, then the Datavault Builder itself should also be running in the cloud near the database. In this case, it would be best to install the Datavault Builder in the same data center to keep latencies short.

  • As far es we know, there are three SQL Server variants in the Microsoft Azure environment:

    • SQL Server on Azure Virtual Machines. Supported.

    • Azure SQL Database. Supported.

      • Single Database

      • Elastic Pool

      • Managed Instance

    • Azure SQL Data Warehouse. Not supported.

Note

With the Azure SQL Database we have already tested the Single Database. Elastic Pool and Managed Instance hasn’t been tested yet, but we don’t see any reason why it shouldn’t work. If this case becomes more relevant, we can gladly create a test environment and run our regression tests.