registry or environment variables?

[pablodc]

Hello,

I was helping a user who had the "fat" version of the Oracle client installed to use the "thin" version instead and after assigning environment variables such as ORACLE_HOME, TWO_TASK,TNS_ADMIN, etc. PLSQL Developer still kept giving priority to the Windows registry values and because of this I never got to use the "thin" client. Is there any way to tell PLSQL Developer to prioritize environment variables and not registry values? The only solution we found to get it to use the thin client was to completely uninstall the "fat" client. Thank you very much.

 

[Marco Kalter]

PL/SQL Developer will always prioritize the environment variables. Can you give an example where this is not the case?

 

[pablodc]

Actually the user already uninstalled the "heavy" version of Oracle he had installed and from then on PLSQL Developer started without problems (using the "instant" client). So I was left without tests to test what was going on.

The only thing I remember is that after loading the environment variables and starting PLSQL Developer, the first message in the startup window was that it was reading the Windows registry. I don't know if it always does that or only in the presence of the "heavy" oracle client installation.

If I encounter this situation again I will remember to get some screenshots, but I also remember that even after creating for example the environment variable "ORACLE_HOME" and assigning it to the directory where the "instant" client was installed in the PLSQL Developer help and information window the value of "ORACLE_HOME" was still pointing to the path where the "heavy" client was installed. Weird.

Thanks for the reply anyway.

Regards.