Hi arvndv
The reason why I asked if you have Oracle client installed is because Oracle client software uses a file called tnsnames.ora to create and configure database connections. Quite often if you install some software to interrogate the oracle database (like SQLDeveloper etc.), the software will use the db connection defined in the tnsnames.ora file rather than use Oracle's thin driver (the JDBC connection string option) and you'll think your using the JDBC connection string - but in fact the software uses the tnsnames.ora file.
Admittedly this was about 5 years ago - perhaps things have changed since I last used Oracle.
DBVisualiser is a DB interrogation tool that cannot use Oracle's tnsnames.ora file (or at least it couldn't 5 years ago) - if you could connect to the same db via DBVisualiser it would confirm the problem was with ReadyAPI! config.
Unfortunately I didn't read your original post properly. You already have a soapui instance on the same machine as your readyapi! machine and you can connect to the database fine with soapui.
I did come across this about 3 months ago with SQLServer - I could connect to the DB using SoapUI (windows authentication) fine - but ReadyAPI! couldn't connect (using the windows authentication) - despite using the correct drivers etc.
I had to change the authentication to SQLAuthentication instead before it connected but that doesn't solve your problem.
I've noticed when setting up db connections for certain databases in soapui - I've had to add in a new connection string as the default connection string doesn't always do what is necessary. i.e. your database instance might need some extra parameters that aren't represented in the default connection string.
have a look at the following link
cheers,
richie
