We have the following situation: We are Using PL/SQL Developer (16.0.8) in an environment where multiple Oracle Full Clients are installed and we would like to use the latest Oracle Instantclient (23.26) in PL/SQL Developer. The issue here is: PL/SQL Developer uses the Primary Oracle Home from the Oracle Home Registry (set with Oracle Home Selector). The Instantclient is not in this registry and we don't want to remove the Oracle Home registry. We could configure PL/SQL developer to use the Instantclient, but for this we would need to change the PL/SQL Developer user settings or ensure that PL/SQL Developer is always started with the command-line parameter "InstantClient". Is there any other option? I was looking for an environment variable with an equivalent behavior like the "Instantclient" command-line parameter that we could set to override the Oracle client selection of PL/SQL Developer, but I was not able to find any.
How to use Oracle Instantclient with Full Clients being installed
- Thread starter nic
- Start date
You can set any command-line parameter in the Params.ini file in the PL/SQL Developer installation directory. This ensures that the parameter is used, regardless how PL/SQL Developer is started.
@Marco Kalter Thank you for this quick response. This already helps a lot. However, given that application updates are done by our CIT department, I expect that any changes we make on the params.ini will be overridden as soon as the next PL/SQL Developer Update will be installed by the CIT department. It will probably be error-prone to establish a workflow that ensures, that the params.ini file will be updated together with every application update. Are there currently any other options? Perhaps to define params.ini in a more "persistent" path? Or could you perhaps consider an extension for this use case in an upcoming version of PL/SQL Developer? This could perhaps be, e.g., a params.ini in different location or environment variable that takes precedence.
