But somehow I could’t get it to connect to our Oracle test DB. I tried all combinations of the connection settings, but I always get either of these error messages whenever I press the connect button:
- ORA-06401: NETCMN: Invalid driver designator
- ORA-12560: TNS: protocol adapter error
I stopped my experiment with TOra because my colleague suggested us to settle with Oracle’s SQL Developer instead. I noticed that SQL Developer is a Java-based Windows application, so I already anticipated that it is going to be much slower than native Windows application.
So after months of occasionally frustrated by SQL Developer’s slowness and memory-hogging, I return back to trying to get TOra connected. Hoping that my fortune is improved this time. And it does improved 😀
I installed TOra (the latest stable version is still 2.0) and then visited TOra’s community forum for clues. Then I found out someone mentioned that TOra 2.0 was build based on Oracle Instant Client 10. Hmm.. I am still using Oracle 9.2 Instant Client. This could be the main cause why TOra unable to connect.
So I downloaded Oracle’s Instant Client v. 10.2 and extracted its content to my TOra installation folder. Then I tried the following settings:
Voila!!! It works!!!
Unfortunately, I am still unable to use TNS record to get TOra connected. I’ll update again once I have success getting TOra connected using TNS records.
To make TOra able to use TNS, please set the following Environment Variables:
- TNS_ADMIN. Value: fullpath of TNSNames.ORA’s directory
- ORACLE_HOME. Value: fullpath of Oracle’s installation directory
Once you’ve done above steps, a new connection provider [Oracle (TNS)] will be available.
tora oracle, tora oracle connection, tora oracle_home, tora for oracle library mismatch error, tora connection provider, tora oracle sql, TNS entered in tnsnames org doesnt reflect in Tora, tora oci dll, tora connetin provider oracle doesnt show, tora connect to oracle db, use tora sql ORACLE_HOME