none
Random Username and passwords fails ADF oracle(on-prem) -> sql (azure)

    Question

  • After a recent update to the Self Hosted Integration Runtime, i started getting random Oracle Username and Password Failures on random activities on my pipeline. Is there a way to rollback the update or is there any solution for this ?


    • Edited by jgtaveras Sunday, October 21, 2018 5:39 PM
    Sunday, October 21, 2018 5:39 PM

All replies

  • In recent release of self-hosted IR, there is an Oracle driver regression which may cause this failure . 

     

    To quickly mitigate the issue, please roll back the Oracle driver to previous version.  Below are the steps:

    1. Stop self-hosted IR
    2. Backup the file C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\msora28.dll
    3. Download the previous version of msora28.dll and place it under C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\
    4. Start self-hosted IR

    Regards,

    Gary

    • Proposed as answer by porkpie84 Tuesday, October 23, 2018 10:35 AM
    Monday, October 22, 2018 2:50 AM
  • We are also having this problem, replacing the DLL doesn't fix the issue for us. 

    DLL was 08.02.2148 downgraded to 08.0.2.2016 with the same result. ADF Integration Runtime is version 3.10.6838.1


    Monday, October 22, 2018 3:15 PM
  • Is there any official source to download this DLL ??
    Monday, October 22, 2018 4:04 PM
  • In recent release of self-hosted IR, there is an Oracle driver regression which may cause this failure . 

     

    To quickly mitigate the issue, please roll back the Oracle driver to previous version.  Below are the steps:

    1. Stop self-hosted IR
    2. Backup the file C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\msora28.dll
    3. Download the previous version of msora28.dll and place it under C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\
    4. Start self-hosted IR

    Regards,

    Gary

    This has worked for us.

    I'm a little amazed how this was changed automatically to break all the Oracle connections we have setup.

    Will there be further driver updates which break/fix these connections?







    • Edited by porkpie84 Tuesday, October 23, 2018 10:43 AM
    Tuesday, October 23, 2018 10:41 AM
  • We are also having this problem, replacing the DLL doesn't fix the issue for us. 

    DLL was 08.02.2148 downgraded to 08.0.2.2016 with the same result. ADF Integration Runtime is version 3.10.6838.1



    Did you restart the self-hosted IR?  What's the error message did you see?
    Tuesday, October 23, 2018 3:01 PM
  • In recent release of self-hosted IR, there is an Oracle driver regression which may cause this failure . 

     

    To quickly mitigate the issue, please roll back the Oracle driver to previous version.  Below are the steps:

    1. Stop self-hosted IR
    2. Backup the file C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\msora28.dll
    3. Download the previous version of msora28.dll and place it under C:\Program Files\Microsoft Integration Runtime\3.0\Shared\ODBC Drivers\Microsoft Oracle ODBC Driver\lib\
    4. Start self-hosted IR

    Regards,

    Gary

    Our project has exactly the same issue. After the automated update of the Self Hosted Integration runtime, the issue occurred. In our case the problem exists just for one of three different Oracle source systems we read data from. 

    We compared the passwords of the three connections. The problematic connection contained special characters in the password, the two working ones didn't.

    So the driver update which came with the update of the self hosted IR seem to cause this issue. We are running Integrated Runtime Version 3.11.6876.3 (last updated on 2018-11-18) and having this issue.

    The new driver might not work with special characters. After the password change without special characters we could run our ADF pipelines again. But of course this should not be a long term fix.

    Conclusion:

    There are at least two workarounds:

    1. replacement of the driver like described in the post of porkpie84 (link is not working any more)
    2. reset of the Oracle password to a new one without special characters (no manual driver update required)

    @Microsoft please fix this problem with your IR asap, that a usage of secure passwords with special characters will be possible soon again.

    For long term the usage of secure passwords is essentially, they should include special characters.

    Thanks.

    Marco

    • Proposed as answer by m_Fischer Monday, December 3, 2018 4:14 PM
    Monday, December 3, 2018 4:13 PM