Forum Discussion

a_anand's avatar
a_anand
New Contributor
3 years ago
Solved

java.sql.SQLException : ORA-12269: client uses weak encryption/crypto-checksumming version

I am getting following error while building query (Data Connection) in ReadyAPI (3.5.1): java.sql.SQLException : ORA-12269: client uses weak encryption/crypto-checksumming version but no such error...
Configuration
Data-Driven Testing
  • richie's avatar
    richie
    3 years ago
    Hey a_anand,

    Have you confirmed SQLDeveloper is using the same jdbc driver?

    Assuming SQLDeveloper and ReadyAPI! are installed on the same machine, using the same connection string and the same version of JRE, i cant see how any other option will cause different behaviour (like youre seeing) unless youre using different driver files.

    Maybe someone else has an idea, but thats the only option i can see that would cause a difference. If SQLDeveloper and ReadyAPI are installed on different machines then youd need to compare everything (JRE, connection string and driver), but if theyre on the same machine the only difference could be the driver as these are saved in separate locations on your hard disk.

    Cheers,

    Rich
richie's avatar
richie
Community Hero
3 years ago
Hey a_anand,

Have you confirmed SQLDeveloper is using the same jdbc driver?

Assuming SQLDeveloper and ReadyAPI! are installed on the same machine, using the same connection string and the same version of JRE, i cant see how any other option will cause different behaviour (like youre seeing) unless youre using different driver files.

Maybe someone else has an idea, but thats the only option i can see that would cause a difference. If SQLDeveloper and ReadyAPI are installed on different machines then youd need to compare everything (JRE, connection string and driver), but if theyre on the same machine the only difference could be the driver as these are saved in separate locations on your hard disk.

Cheers,

Rich
  • a_anand's avatar
    a_anand
    New Contributor
    3 years ago

    Thanks!

     

    I compared all details and found that the driver used in SQLDeveloper was of different version (older).

    I used the same driver in ReadyAPI and it worked!

     

     

    • sonya_m's avatar
      sonya_m
      SmartBear Alumni (Retired)
      3 years ago

      Thank you for helping to solve this, Richie! Well done!

       

      a_anand great to hear the solution worked! Thank you so much for sharing!