SQL Server 2017 – Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase

At the beginning of October, the SQL Server 2017 was officially released. A few days later after the official announcement I wanted to install it in my virtual environment to take a look at newest features. During SQL Server 2017 installation I faced “Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase” error and I was not able to proceed.

feature rules window Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase error

This computer does not have the Oracle Java SE Runtime Environment Version 7 Update 51 (64-bit) or higher installed. The Oracle Java SE Runtime Environment is software provided by a third party. Microsoft grants you no rights for such third-party software. You are responsible for and must separately locate, read and accept applicable third-party license terms. To continue, download the Oracle SE Java Runtime Environment from https://go.microsoft.com/fwlink/?LinkId=526030.

It is a known error since SQL Server 2016 introduced Polybase feature. If you don’t want to use Polybase you can easily fix it by unchecking the proper checkbox in Feature Selection window.

feature selection - no polybase

That will reduce the number of rules to check.

feature rules - no polybase

However, I wanted to install Polybase so I had to install Oracle JRE.  According to the error message, it needs to be JRE 7 Update 51 or newer. Currently, the newest available version is JRE 9.0.1 and can be downloaded here: http://www.oracle.com/technetwork/java/javase/downloads/jre9-downloads-3848532.html. Installation is very easy.

JRE installationJava Runtime Environment 9 was installed and is visible in system.

jre 9 installed

To my huge surprise, it didn’t help.

feature rules window

To solve this issue I decided to install JRE version 8.

jre 8 installed

It solved my problem.

All checks passed


Apparently, there is a bug in SQL Server 2017 installer. Because of it, the installer doesn’t recognize JRE 9. Fortunately, there is a very simple workaround. To install Polybase you have to install JRE 8. This will pass all checks and you will be able to continue with your installation.

If you found it annoying then you can upvote this connect item: https://connect.microsoft.com/SQLServer/Feedback/Details/3141825


Connect was moved to Azur User Voice. Here you can find migrated connect item: https://feedback.azure.com/forums/908035-sql-server/suggestions/32899312-sql-server-2017-installer-should-recognize-java-jd


Share it:

22 thoughts on “SQL Server 2017 – Oracle JRE 7 Update 51 (64-bit) or higher is required for Polybase”

  1. A bit late on this, so some links on this and other articles no longer work. And some updates don’t seem to be still available. Anyway, I was having this problem installing Polybase on SQL 2016 and received the error. Knowing nothing about Java, I didn’t know what I was looking for and was struggling to progress. I installed a JDK, which didn’t work, then thankfully found this article.
    Eventually went to https://www.java.com/en/download/ and simply clicked on “Download Java”, which downloaded jre-8u371-windows-x64.exe. I installed this, which allowed the Polybase install to succeed.

    Thanks Marek.

  2. I had both 32 bit and 64 bit installed and enabled. I had to disable 32 bit from the Java applet in control panel to get past this validation error

  3. Good post. I learn something new and challenging on websites I stumbleupon every day.

    It’s always interesting to read content from other authors and
    use a little something from their web sites.

    1. As described in the post Summary you need to have JRE 7 or 8 to install SQL Server 2017 RTM. JRE 9 is not recognized by installer and installation fails.

  4. Super Awesome!!!
    – Thanks Bro, I’ve spend over 4 hours on looking work around for this installation until I found your Blog. I appreciate the help.

  5. Installed 1.8.0_171-b11 on my windows 10 box (and no other versions of Java) and the SQL installer couldn’t identify it.

  6. Thank you. It really works; just take update 144 (maybe anotherone), 171 doesn´t work for this solution

Leave a Reply

Your email address will not be published. Required fields are marked *

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.