User Profile

vikash_SB

New Contributor

Joined 4 years ago

3 Posts1 Solution

View All Badges

User Widgets

Contributions

Re: Unable to connect to Oracle database with service name (no SID)
Dear Rich, Thanks much for your response. I found and applied a working solution yesterday. That solutions resonates with what you have mentioned. What I did - 1. In Settings (readyAPI) -> JDBC . Added new Driver and Connection String Template to accommodate Oracle ServiceName (jdbc:oracle:thin:<USER>/<PASSWORD>@<HOST:127.0.0.1>:<PORT:1521>/<ODBC_DSN_NAME>) connection. 2. Since my ServiceName was containing "_" character. I received below warning and hence as suggested added the following parameter to \bin\ReadyAPI.vmoptions file. "The character '_' is not supported in JDBC connections strings since Java 17.0.3 and since ReadyAPI 3.41.0. Please remove the invalid characters or please try to use the JVM option -Dcom.sun.jndi.ldapURLParsing="legacy". " 3. I received this error message-"java.sql.SQLException: ORA-28040: No matching authentication protocol" , so downgraded the oracle jdbc connecter jar from ojdbc14.jar to ojdbc8.jar in \bin\ext folder. This solution worked for me and hope this solution helps someone ! Cheers, Vikash
2 years ago Place ReadyAPI Questions
482Views
0likes
0Comments
Unable to connect to Oracle database with service name (no SID)
I am using Licensed ReadyAPI version 3.48.0. Recently our Oracle DBA changed the SID way of connecting to Database and now only Service name is allowed for connection. I am able to connect to Oracle Database through SQL developer but not through Ready API tool. Earlier using SID I was able to connect through tool as well after putting ojdbc jar in /bin/ext folder. Could you please provide me a way . Thanks. I have tried this but still did not get success - https://support.smartbear.com/readyapi/docs/testing/data-driven/drivers/connection-string.html.
Solved
2 years ago Place ReadyAPI Questions
Configuration
1.3KViews
0likes
2Comments
Getting random validation failure in Jenkins - null / empty response body
Hi SmartBear (ReadyAPI) Community, I am observing one strange random behavior. Locally(local ready API installation at my computer) my Ready API project is running fine , but when I am pushing it to Jenkins then there it is failing with "null / empty response body" error message. The behavior is very random and is appearing for a random test case. So sometimes one test case is failing with this error , sometimes another. Also locally it is always running fine and passing. Could you please help / suggest. I am doing a REST API functional testing with Ready API (version 3.9.1) and Jenkins (version 2.263.1) integration. Thanks.
Solved
4 years ago Place ReadyAPI Questions
Assertions
Automation Environments
REST
1.2KViews
0likes
2Comments