...
In this scenario, the workaround to the issue is:
On the EBS application server that is acting as the endpoint for the failing operation, install a newer version of the Oracle client or instant client (must be 10.2 or higher) into a separate location.
Create a custom shell or bat file that will execute the EBS Source script and then update the path to point to the new Oracle client instead of the default one. Here is a sample shell script that does this:
...
EBS_custom_env.sh
| Code Block |
|---|
source /u01/oracle/VIS/EBSapps.env run export PATH=/u01/oracle/VIS/11.2.0/bin:$PATH |
...
3. On the Topology screen, change the EBS Source Script to run the new custom_env script and then add the required proxy user syntax for the EBS Database User property.
...
With these changes, a database proxy user can be used with the EBS plugin.