If you experience an error with Data Engine during app initialisation, Omniscope will warn you by showing a warning message in the app welcome page header and in the app project toolbar.
The message looks like this:
Data Engine was not initialised correctly.
You will not be able to query data in Views.
See app logs for more info about the error.
This error can happen after an Omniscope upgrade on some environments, e.g. on Linux where the packages required are not properly installed.
Go to Admin web app -> Logs section and open the “main_log.txt” log (e.g. https://youromniscopeaddress/_admin_/logs/server )
Look for the “Could not complete Omniscope Data Engine initialisation” message and gather the information around that line.
You may find yourself in one of these scenarios, looking at what the Omniscope log messages contains:
- A ) “MonetDb server not found on your Linux OS.”
This means you have to install the Linux packages , by following the instructions present in the logs / or by looking at the Linux installation setup guide.
Stop Omniscope, install the packages required and start Omniscope again. You should be good afterwards.
B ) “The Monetdb installation found is not the recommended version of Monetdb” (Linux)
This means you have wrong packages version on your machine and you have to install the recommended one. In the logs you will find which is the recommended package version to install.
Follow the Linux installation setup guide to install the Linux MonetDB packages.
(The command to install the packages is something like:
sudo apt-get install monetdb5-sql=MONETDB_VERSION monetdb5-server=MONETDB_VERSION monetdb-client=MONETDB_VERSION
where MONETB_VERSION is the recommended version number, e.g. 11.29.7 .
As above, follow the setup guide, stop Omniscope, install the packages and restart Omniscope.
C ) "Your system is configured to use HTTP or SOCKS proxy on localhost / 127.0.0.1"
If you have network proxy enabled on all protocols and on any address, localhost included, Omniscope may not start correctly.
To fix the issue you have to disable proxy to be used on localhost address, and surely on other protocols which are not HTTP / HTTPS / FTP.
On Windows 7 in the proxy settings untick "use the same proxy server for all protocols" , confirm the changes and then restart Omniscope.
On Windows 10 you need to add "localhost" to the list of addresses to exclude:
D ) Any other case (if MonetDB cannot start for another reason)
Check the logs carefully, if Omniscope recognises a known issue you will find the solution explained step by step in the logs so you can solve it on your side.
Otherwise send us the logs file content, and we will be in touch.
You can download all logs as zip by following the link in the app warning, or by visiting the admin app - data engine section at youromniscopeaddress/_admin_/dataengine/
Scenario D : Last resort, let Omniscope fix your tables
If you have installed Omniscope and MonetDB packages correctly, and Data Engine cannot be initialised when starting Omniscope especially after a major version upgrade, and you are in error scenario D and no solution was suggested in the logs,, you can try the following step to have Omniscope rebuild your tables
Backup LocalStorageRegistry.xml file.
on Windows in he Visokio/Omniscope folder in the %LOCALAPPDATA% folder, e.g. from C:\Users\MyUsername\AppData\Local\Visokio\Omniscope
on Linux / Mac in ".visokioappdata" folder in the home directory.
Backup the MonetDB Data Engine folder, usually located in the same folder as above, but user customisable. Found the location in the Admin web app -> Disk manager section (e.g. at http://youromniscopeaddress/_admin_/diskmanager/ )
Rename the “dbfarm” folder located in the MonetDB Data Engine folder to “dbfarm_old”.
If Data Engine is running correctly proceed to step 7, otherwise if you still have the warning / error complaining about “Data Engine was not initialised correctly” stop here and contact us.
Go to the Admin web app
Go to Data Engine and Storage section
Click on “Fix all tables” button and wait until all tables have been fixed.
This can take long time depending on how many tables and how much data Omniscope has to fix.
Once you are completely satisfied the data has been restored correctly, you can delete dbfarm_old from step 4, and backups created in steps 2 and 3.