Getting Sqldeveloper 19.1 64-bit working with instantclient_12_2 on Windows enterprise PC without admin privileges?

Question

I\'ve installed Sqldeveloper Version 19.1 64-bit Version on an enterprise PC with Win7-64bit.

It works fine with embedded jdbc-client, but I need to get it working u

Answer 1

Without admin privileges and no permission to change your %PATH% env permanently, you only need to install the whole directory somewhere and add a .BAT file, that changes environment temporarily before calling SQL-Developer.

1. Install complete SQL-Developer e.g. in C:\myprogs\sqldeveloper
2. Install instant-client somewhere, e.g. in C:\myprogs\instantclient_12_2
3. Create .BAT file, e.g. C:\myprogs\sqldeveloper\startsqldev.bat with following content:

set PATH=C:\myprogs\instantclient_12_2;%PATH%
REM start sqldeveloper
"C:\myprogs\sqldeveloper\sqldeveloper.exe"

It works for versions > 20 as well ;-)

Answer 2

Meanwhile, I've solved it.

Result of testing:

Testing the Instant Client located at C:\Users\myuser\Oracle\instantclient_12_2
Testing client directory ... OK
Testing loading Oracle JDBC driver ... OK
Testing checking Oracle JDBC driver version ... OK
  Driver version: 12.2.0.1.0
Testing testing native OCI library load ... OK
Success! 

Reason were following mistakes:

1. Forgot "set" in front of Variable assignment (because I'm usually using Unix)
2. Used quotation marks during Variable assignment, which are taken as part of the value (also different to UNIX).
3. Added JAVA_HOME and JRE_PATH

See below my complete bat-file (adapted, because of some secret information within pathnames):

REM Optional: setting of USE_OS_DATETIME_FORMAT changes DATE-Format
set USE_OS_DATETIME_FORMAT=1
set PATH=%USERPROFILE%\OneDrive - myCompany\Oracle\instantclient_12_2;%JAVA_HOME%;%PATH%

REM start your preferred sqldeveloper
"%USERPROFILE%\OneDrive - myCompany\Oracle\sqldeveloperx64.20.2\sqldeveloper.exe"C:\Users\myuser\OneDrive - myCompany\Oracle\sqldeveloperx64.19.1\sqldeveloper.exe"

Additionally, I've added a shortcut to the bat-file and now I can start it simply with CRTL-SHIFT-S ;-)

BTW: Same solution works fine on Win10 as well