java.sql.SQLException : ORA-12269: client uses weak encryption/crypto-checksumming version
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2021
05:59 AM
12-17-2021
05:59 AM
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 I get while executing same query on SQL Developer for the same connection.
Any particular reason why this is happening and what can be done to resolve this issue?
Solved! Go to Solution.
Labels:
- Labels:
-
Configuration
-
Data-Driven Testing
3 REPLIES 3
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2021
04:19 PM
12-17-2021
04:19 PM
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
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
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2021
08:19 PM
12-19-2021
08:19 PM
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!
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2021
04:10 AM
12-20-2021
04:10 AM
Thank you for helping to solve this, Richie! Well done!
@a_anand great to hear the solution worked! Thank you so much for sharing!
Sonya Mihaljova
Community and Education Specialist
