Oracle JDBC TLS connection fails (handshake_failure) after OS upgrade












0















I have an Oracle Database 12.1 server running on Oracle Linux 6.



Secure (TLS) connections were working fine until I decided to update the underlying operating system (yum update) and reboot the server. A total of 62 packages were updated (yum update log) including the kernel and OpenSSL.



Now, secure connections, from the JDBC clients and from SQL*Plus fails with handshake_failure or ORA-28860.



I have a verbose TLSv1.2 log from my JDBC client but I can't figure out what is wrong with the TLS connection.



listener.ora and sqlnet.ora



sqlnet.ora and listener.ora do not contain SSL_CIPHER_SUITES



I am sure that nothing was changed or updated on the client (either JDBC or SQL*Plus). Few minutes before the upgrade/reboot, there was no problem establishing the TLS connection.



The server runs Oracle 12.1.0.1. The TLS connection issue occurs with all tested clients which previously succeeded in establishing a secure connection:




  • ojdbc8.jar 12.2.0.1

  • ojdbc7.jar 12.1.0.2

  • SQL*Plus 12.1.0.2.0.


The SQL*Plus trace file contains an ORA-28862 ("peer closed the connection") which may be more specific than the previous ORA-28860. I will try to get the same trace file on the server side.










share|improve this question
















bumped to the homepage by Community 1 min ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0















    I have an Oracle Database 12.1 server running on Oracle Linux 6.



    Secure (TLS) connections were working fine until I decided to update the underlying operating system (yum update) and reboot the server. A total of 62 packages were updated (yum update log) including the kernel and OpenSSL.



    Now, secure connections, from the JDBC clients and from SQL*Plus fails with handshake_failure or ORA-28860.



    I have a verbose TLSv1.2 log from my JDBC client but I can't figure out what is wrong with the TLS connection.



    listener.ora and sqlnet.ora



    sqlnet.ora and listener.ora do not contain SSL_CIPHER_SUITES



    I am sure that nothing was changed or updated on the client (either JDBC or SQL*Plus). Few minutes before the upgrade/reboot, there was no problem establishing the TLS connection.



    The server runs Oracle 12.1.0.1. The TLS connection issue occurs with all tested clients which previously succeeded in establishing a secure connection:




    • ojdbc8.jar 12.2.0.1

    • ojdbc7.jar 12.1.0.2

    • SQL*Plus 12.1.0.2.0.


    The SQL*Plus trace file contains an ORA-28862 ("peer closed the connection") which may be more specific than the previous ORA-28860. I will try to get the same trace file on the server side.










    share|improve this question
















    bumped to the homepage by Community 1 min ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0


      1






      I have an Oracle Database 12.1 server running on Oracle Linux 6.



      Secure (TLS) connections were working fine until I decided to update the underlying operating system (yum update) and reboot the server. A total of 62 packages were updated (yum update log) including the kernel and OpenSSL.



      Now, secure connections, from the JDBC clients and from SQL*Plus fails with handshake_failure or ORA-28860.



      I have a verbose TLSv1.2 log from my JDBC client but I can't figure out what is wrong with the TLS connection.



      listener.ora and sqlnet.ora



      sqlnet.ora and listener.ora do not contain SSL_CIPHER_SUITES



      I am sure that nothing was changed or updated on the client (either JDBC or SQL*Plus). Few minutes before the upgrade/reboot, there was no problem establishing the TLS connection.



      The server runs Oracle 12.1.0.1. The TLS connection issue occurs with all tested clients which previously succeeded in establishing a secure connection:




      • ojdbc8.jar 12.2.0.1

      • ojdbc7.jar 12.1.0.2

      • SQL*Plus 12.1.0.2.0.


      The SQL*Plus trace file contains an ORA-28862 ("peer closed the connection") which may be more specific than the previous ORA-28860. I will try to get the same trace file on the server side.










      share|improve this question
















      I have an Oracle Database 12.1 server running on Oracle Linux 6.



      Secure (TLS) connections were working fine until I decided to update the underlying operating system (yum update) and reboot the server. A total of 62 packages were updated (yum update log) including the kernel and OpenSSL.



      Now, secure connections, from the JDBC clients and from SQL*Plus fails with handshake_failure or ORA-28860.



      I have a verbose TLSv1.2 log from my JDBC client but I can't figure out what is wrong with the TLS connection.



      listener.ora and sqlnet.ora



      sqlnet.ora and listener.ora do not contain SSL_CIPHER_SUITES



      I am sure that nothing was changed or updated on the client (either JDBC or SQL*Plus). Few minutes before the upgrade/reboot, there was no problem establishing the TLS connection.



      The server runs Oracle 12.1.0.1. The TLS connection issue occurs with all tested clients which previously succeeded in establishing a secure connection:




      • ojdbc8.jar 12.2.0.1

      • ojdbc7.jar 12.1.0.2

      • SQL*Plus 12.1.0.2.0.


      The SQL*Plus trace file contains an ORA-28862 ("peer closed the connection") which may be more specific than the previous ORA-28860. I will try to get the same trace file on the server side.







      oracle oracle-12c connectivity ssl






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 14 '18 at 13:10









      Paul White

      50.7k14277447




      50.7k14277447










      asked Feb 16 '18 at 10:09









      David Le BorgneDavid Le Borgne

      11




      11





      bumped to the homepage by Community 1 min ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 1 min ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Restarting the listener solved the issue... I can't understand what happened, as the listener was already restarted during the server reboot.



          I should have tried that before.



          Thanks to everyone who has taken time to help.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "182"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f198096%2foracle-jdbc-tls-connection-fails-handshake-failure-after-os-upgrade%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Restarting the listener solved the issue... I can't understand what happened, as the listener was already restarted during the server reboot.



            I should have tried that before.



            Thanks to everyone who has taken time to help.






            share|improve this answer




























              0














              Restarting the listener solved the issue... I can't understand what happened, as the listener was already restarted during the server reboot.



              I should have tried that before.



              Thanks to everyone who has taken time to help.






              share|improve this answer


























                0












                0








                0







                Restarting the listener solved the issue... I can't understand what happened, as the listener was already restarted during the server reboot.



                I should have tried that before.



                Thanks to everyone who has taken time to help.






                share|improve this answer













                Restarting the listener solved the issue... I can't understand what happened, as the listener was already restarted during the server reboot.



                I should have tried that before.



                Thanks to everyone who has taken time to help.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 21 '18 at 16:56









                David Le BorgneDavid Le Borgne

                11




                11






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Database Administrators Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f198096%2foracle-jdbc-tls-connection-fails-handshake-failure-after-os-upgrade%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Liste der Baudenkmale in Friedland (Mecklenburg)

                    Single-Malt-Whisky

                    Czorneboh