Advisory regarding updating Omniscope to 2021.2

Omniscope 2021.2 comes with a new data engine, responsible for providing queryable data to power the visualisations in your reports. 

This upgrade has many improvements in robustness, diagnostics and troubleshooting, and is strongly recommended for production servers, but may need attention regarding 2 aspects when upgrading.

Audience:

• Windows and Mac desktop users should not need to take any special action when upgrading, unless using the Storage Block (unlikely). 
• Production server administrators on any platform should read on and may need to take action.
• Linux server administrators will need to take action and follow this advisory in full.

1. Re-populating the data storage 

On all platforms, when you upgrade to Omniscope 2021.2, the data engine's previous stored queryable data (the "dbfarm") will be discarded for compatibility reasons, and in most cases it will be rebuilt automatically from raw execution data.  This will happen on demand when next opening the report in question, with a small delay. This will only not happen automatically where a Storage Block is linked directly to a report.

If you wish to do this proactively after upgrading, you should click the "Refresh tables" button in Admin (see /_admin_/dataengine/), which will immediately update all report data, including Storage Blocks. 

If you have any Storage Blocks used in production reports, you must the "Refresh tables" button, or alternatively can refill them individually by opening the workflows in question and executing the block in "fill" mode. If you do not do either of these, reports linked directly to Storage Blocks will show an error.

2. Updating MonetDb  (Linux systems only)

Behind the scenes, Omniscope uses MonetDb, a columnar database optimised for BI queries. Omniscope 2021.2 is built to work with specifically MonetDb 11.39.17, which is a major upgrade to the previous version used by Omniscope 2021.1 and earlier. 

On Windows and Mac, this is bundled as part of Omniscope; you do not need to upgrade MonetDb when upgrading Omniscope. On Linux servers, you must upgrade MonetDb at the same time as upgrading Omniscope. Failure to do that may result in performance or reliability issues when upgrading Omniscope and also when later upgrading MonetDb. 

To update MonetDb on a Linux server:

1. First, if you are installing Omniscope on a new Linux machine you need to add Monetdb repositories by following the instructions here https://www.monetdb.org/Downloads  and here  https://help.visokio.com/support/solutions/articles/42000016081-linux-installation-2018-
   
   
2. Once the monetdb repositories are available on your system (and for existing systems being upgraded), make sure Omniscope is not running, and install monetdb using the package manager of your distribution. For example on Debian based system you can use the following command:
   
   sudo apt update && sudo apt install monetdb5-sql=11.39.17 monetdb5-server=11.39.17 monetdb-client=11.39.17

3. Deleting the old data engine data (Optional)

Omniscope 2021.2 will use a new data engine. The data associated to the old data engine is not automatically deleted from disk.

You can manually delete data associated to the old data engine by deleting the folder 'visokio_DEC2016' inside the 'dbfarm' folder inside 'MonetDB Data Engine' folder.

You can find the Monetdb data Engine folder in the disk manager section of the admin app.

By default, the folder associated to the old data engine is:

Windows

%LOCALAPPDATA%\Visokio\Omniscope\MonetDb\dbfarm\visokio_DEC2016

Linux

~/.visokioappdata/Visokio/Omniscope/MonetDb/dbfarm/visokio_DEC2016

Mac

~/Library/Application Support/Visokio/Omniscope/MonetDb/dbfarm/visokio_DEC2016

N.B. Both the new and the old data engine files can be deleted by clicking on the 'Reset' button in the admin Data engine page in the admin app.

If you have any concerns or need help with any of this, please contact support@visokio.com.

1 Votes