To use the wallet feature with SQLDeveloper -
1/get wallet working for sqlplus,
2/use jdbc oci thick,
3/no username or password,
4/check OS_AUTHENTICATION (which means username is not required and you are passed back to the jdbc oci thick).
5/use TNS->connection identifier.
Tested with 11.2.0.2 server software providing OCI.
Experience:
11g DBA OCP / VM / Docker / REST / SQLcl / SQLDeveloper / macOS / Linux / Java Developer
Continuous improvement
The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.
Friday, 11 November 2011
Thursday, 7 April 2011
SQLDeveloper 3.0 production is supplied with the thin driver 11.2.0.2
it needs 11.2.0.2 version to use thick which has a few additional features over thin.
To avoid confusion with other Oracle software you can set the ORACLE_HOME in the session you start sqldeveloper in as described below:
The version mismatch is often because SQLDeveloper is trying to use the 'thick' driver and 11.2.0.2 thick is not available,
try
thin by:
1/(uncheck Tools->preferences->Datababae->advanced->use OCI/thick driver, and
2/If necessary, set ORACLE_HOME for your cmd.exe session where sqldev is started from to where sqldeveloper is where %ORACLE_HOME%\jdbc\lib exists, (so SQLDeveloper does not try your existing ORACLE_HOME) and
3/use Connection Type TNS -> Network Alias.
4/You may need to set Tools->preferences->Datababase->advanced->Tnsname directory to the directory containing tnsnames.ora
-Turloch
Edit 25 Sep 2011
P.S. PATH (and LD_LIBRARY_PATH ??) settings may be needed to find the new .dll (Windows) and .so (Linux) files.
it needs 11.2.0.2 version to use thick which has a few additional features over thin.
To avoid confusion with other Oracle software you can set the ORACLE_HOME in the session you start sqldeveloper in as described below:
The version mismatch is often because SQLDeveloper is trying to use the 'thick' driver and 11.2.0.2 thick is not available,
try
thin by:
1/(uncheck Tools->preferences->Datababae->advanced->use OCI/thick driver, and
2/If necessary, set ORACLE_HOME for your cmd.exe session where sqldev is started from to where sqldeveloper is where %ORACLE_HOME%\jdbc\lib exists, (so SQLDeveloper does not try your existing ORACLE_HOME) and
3/use Connection Type TNS -> Network Alias.
4/You may need to set Tools->preferences->Datababase->advanced->Tnsname directory to the directory containing tnsnames.ora
-Turloch
Edit 25 Sep 2011
P.S. PATH (and LD_LIBRARY_PATH ??) settings may be needed to find the new .dll (Windows) and .so (Linux) files.
Subscribe to:
Posts (Atom)