ODI 12c Standalone Agent Not Picking Environment Variables when Started with "agent.cmd/sh"
(Doc ID 2507268.1)
Last updated on OCTOBER 18, 2019
Applies to:Oracle Data Integrator - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
An Oracle Data Integrator (ODI) 18.104.22.168.0 package implements an OdiOSCommand step, where the system command to execute uses environment variables.
- On Unix / Linux operating system, the following command is expected to list the environment variables set:
- On Windows operating system, the following command is expected to list the environment variables set:
- In ODI Studio, a Project Variable <VARIABLE NAME> has been defined to return the value of an environment variable that corresponds to an existing directory (%ENVIRONMENT VARIABLE%, created as system variable on Windows), then used in OdiOSCommand to display the contents of that directory:
The execution of Package or Scenario produces the expected result when using Local (No Agent), or a standalone Agent started with the startComponent.cmd/sh command.
When the Agent is started using agent.cmd/sh, the environment variable is not substituted to its value, eventually causing the execution to fail (receiving a failure or not depends on how precisely the environment variables are to be used by ODI).
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document