Fail during database init error

In some situations the installer may fail with a message “failed during database init”. This typically means that the first execution of the driver (which populates the settings database) failed.
As the installer redirects stderr / stdout the reason can not be seen directly.

View output log

In builds 6.0.570+ the output is redirected to dbint.log (in the current directory) as noted in the message.

In earlier builds you can run "./upddenv ./updd -dbinitonly" to view the output.

Please review the output to identify issues likely to be the cause of the error. e.g.

In this particular case a Linux package was available to install the missing lib.

Load the driver in a cmd window 

Loading the driver from the command line will also reveal initialisation errors

The command 'sudo /opt/updd/upddenv /opt/updd/updd -e' reported the error ...

"error while loading shared libraries: lbgthread-2.0.so.0 cannot open shared object file: no such file or directory"

We ship the correct version as /opt/updd/usrlib/libgthread-2.0.so all should be OK.  If this does occur try setting a symbolic link as below: