HOW TO: Restart the licence node

Welcome back for the fourth instalment of the AdminSeries. Catch up on the previous posts here:

For this post we’ll be restarting the licence node.

To do this, I recommend you follow all the steps in the above posts beforehand.

That said, head over to the Nodes tab in ExaOperation. Scroll down past the nodes (if you have a few!).


In the License Nodes section, click Reboot. If all goes well, this will take down the page you are viewing, indeed all of ExaOperation (as it primarily resides on the licence node). You should be left with your browser’s page not found or something similar.

Again, I hope you have your patience ready. For me, this step takes around 5 minutes, in which cold sweats ensue (WTF have I done!). But it’s ok.

Refresh the page periodically until ExaOperation comes back.

This concludes Restarting the licence node.


2016 round-up


Hi everyone! Thanks for continuing to read my blog. 2016 has been full of progress and meeting new people. We had the Exasol Xperience event in the summer, and the recent release of Version 6.

The blog has grown too! This year I’ve had over 2000 views of my Exasol related content, from literally all over the world. It’s great to see the adoption of Exasol expand, as I see your interest in my content. As always, I love getting your comments, and if you’d like to get in touch, please see the About section.

My role too has started to change at work. I am no longer only a Database Architect; I’m leading the Data team at Atheon, as well as being the Information Security Officer; hence why I’ve been a bit quiet on the posts recently! In the coming posts, I’ll be posting a link to a blog written by one of my upcoming developers, which I’m excited to share with you.

I’m looking forward to what 2017 has to bring, here’s to another good year!

5.0.16 and another teaser for Version 6

Last week Exasol sent out a newsletter teasing Version 6 for release in October. Exciting times!

As a precursor, there’s also been a release as version 5.0.16.

Some key notes were that the JDBC driver now requires at least Java 1.5, with Java 1.4 no longer compatible.

The release of 5.0.16 covers quite a few bugs, but also the addition of functionality for Import and Export to Amazon S3 buckets, which is a good addition.

Bug Wrong results in some combinations of equi and cross join
Bug Avoid unnecessary overhead in commit when a table is created and dropped within the same transaction
Bug UNION ALL queries may produce wrong results in some special cases
Bug Possible IMPORT failure when using ERRORS INTO clause
Bug SqlProcess terminates with SIGSEGV in cases of many expressions in select list
Bug AWS node names during boot (Stage 2-3) are wrong (n267,n268,n269)
Bug AWS cannot reboot or shut down nodes through EXAoperation
Bug EXAoperation possibly shows wrong database connection strings in Amazon AWS™ clusters
Bug Undetected node malfunction in case of only partially responsive nodes when using remote syslog servers
Bug Unusually high process-load
Bug Unexpected data exception by using GROUP_CONCAT in the HAVING clause
Bug Network reconfiguration via maintenance user may lead to misleading error message
Bug Reduced usability and transaction throughput in the case when client aborts occur during big commit
Bug ODBC: values may be truncated, when retrieving DECIMAL values as SQL_C_WCHAR
Bug Running query profiling causes reduced resource values in last day profiling views
New Feature Import/Export from/to Amazon S3™ buckets
Improvement EXAoperation: Replacing HTTPS certificates for clusters installed before version 5.0.7
Improvement EXADataProcessingExtension for VS 2013
Bug An unlikely race condition can deadlock EXASolution and EXAoperation
Bug Doubled audit entry through reconnects caused by networking issues
Bug Unexpected NULL values in RESOURCES column of auditing and SQL statistics
Improvement Improved errors messages for failed parallel connections

For more information on 5.0.16, or to download the update, take a look here on Exasol’s site.


Exasol in my backpack

Exasol turned out to be quite interested in the mini cluster that I developed and talked about here.

So much so, that my cluster has now been christened as “Exasol in my backpack”, and featured:

It’s great to know that people are interested in the stuff I’m building and sharing. As always, if you’d like to know more, please get in touch.



Exasol training

This week I have been at Exasol’s headquarters in Nuremberg, Germany, getting trained up on behalf of my company Atheon Analytics.

I spent two days, covering topics on Performance and Exasol’s Powerlytics (including scripting and UDFs in Python, R and Java).

It was great meeting the team behind the product, and they’re a great bunch! Danke to them for their hospitality, and showing me the city!

I’ve already made some performance based improvements to my code base, reducing execution time by a factor of 7! Great stuff!

Once I can document some examples, I’ll get some posts up about what I’m now looking out for in my Exasol queries to tune for performance.


HOW TO: Connecting Alteryx to EXASOL

Connecting Alteryx to EXASOL has three parts, downloading the relevant EXASOL driver,  Creating an ODBC Data source for EXASOL and finally configuring that in Alteryx.

Downloading the EXASOL Driver

With the Alteryx free download there is currently no EXASOL driver by default.

Download Download ODBC Driver from the EXASOL website

Install the driver.

Open up the ODBC Data Source Administrator, and go to the Drivers tab. You will see that the EXASolution Driver is now installed.


Create an EXASOL Data Source

Still in the ODBC Data Source Administrator, go to the System DSN tab. Select Add. Then, in the EXASolution ODBC configuration window, enter in the details for your EXASOL instance. You can also provide the default schema, or leave it blank to be flexible.exasol_odbc_config

This is what your EXASOL data source should look like.exasol_ds

Configuring EXASOL as a Database Connection in Alteryx

Now we have the EXASOL data source configured we can head to Alteryx. In this case we are going to use an Output with EXASOL.

With your ETL process already setup, drag on Output Data block.

In the Write to File or Database dropdown, select Database Connection, then New ODBC Connection.


Next, select the Data Source Name you just created. If it’s not in the dropdown, use ODBC Admin to select it. If you did not specify your credentials in the data source, enter them in here.


Alteryx will then ask you to specify a table name. IMPORTANT: list the EXASOL schema first.


Then, your EXASOL destination is ready to go.alteryx_exasol_output


Hello world!

How very apt a title by WordPress.

This blog aims to document my stumblings, ahem, chartered course in my attempt to tame this world of data we live in.

I’m aiming to create a place for all the things I’ve picked up, in case they’re useful again, for me or anyone else.