My Oracle Support Banner

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 12.2.1.3.0 and later
Information 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:

OdiOSCommand "-OUT_FILE=<FULL PATH><OUT FILE>" "-ERR_FILE=<FULL PATH><ERROR FILE>" "-FILE_APPEND=NO" "-WORKING_DIR=<FULL PATH>"...
/bin/env

OdiOSCommand "-OUT_FILE=<FULL PATH><OUT FILE>" "-ERR_FILE=<FULL PATH><ERROR FILE>" "-FILE_APPEND=NO" "-WORKING_DIR=<FULL PATH>"...
set

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!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.