ODI 12c Standalone Agent Not Picking Environment Variables when Started with "agent.cmd/sh"
(Doc ID 2507268.1)
Last updated on JUNE 12, 2023
Applies to:
Oracle Data Integrator - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
An Oracle Data Integrator (ODI) 12.2.1.3.0 package implements an OdiOSCommand step, where the system command to execute uses environment variables.
For example:
- On Unix / Linux operating system, the following command is expected to list the environment variables set:
OdiOSCommand "-OUT_FILE=<FULL PATH><OUT FILE>" "-ERR_FILE=<FULL PATH><ERROR FILE>" "-FILE_APPEND=NO" "-WORKING_DIR=<FULL PATH>"...
/bin/env
- On Windows operating system, the following command is expected to list the environment variables set:
OdiOSCommand "-OUT_FILE=<FULL PATH><OUT FILE>" "-ERR_FILE=<FULL PATH><ERROR FILE>" "-FILE_APPEND=NO" "-WORKING_DIR=<FULL PATH>"...
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:
OdiOSCommand "-OUT_FILE=<FULL PATH><OUT FILE>" "-ERR_FILE=<FULL PATH><ERROR FILE>" "-FILE_APPEND=NO" "-WORKING_DIR=<FULL PATH>"...
dir #<PROJECT CODE>.<VARIABLE NAME>
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).
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |