My Oracle Support Banner

ODI 12c "startcmd.sh" Fails when Executed from KSH Shell on IBM AIX Operating System and the Tool Executed (OdiExportLog, etc) Uses a Property containing Spaces Such As -FROMDATE or -TODATE (Doc ID 2512726.1)

Last updated on NOVEMBER 10, 2020

Applies to:

Oracle Data Integrator - Version 12.2.1.3.0 to 12.2.1.4.200618 [Release 12c]
IBM AIX on POWER Systems (64-bit)

Symptoms

An Oracle Data Integrator (ODI) 12c "startcmd.sh" command fails when executed from ksh shell on an IBM AIX operating system, and the tool executed (such as OdiExportLog, etc) is set to use a datetime property such as -FROMDATE and -TODATE.

For example, the execution of the following OdiExportLog tool:

startcmd.sh -INSTANCE=<AGENT NAME> OdiExportLog ... "-FROMDATE=201901/01 12:33:00" "-TODATE=2019/12/31 12:34:00"...

... fails when executed from the ksh shell, and the following message is received:

...
Caused by: oracle.odi.oditools.OdiToolInvalidParameterException:
ODI-30151: Error while setting parameters on tool: OdiExportLog ... "-FROMDATE=2019/01/01" "00:00:00" "-TODATE=2019/12/31" "00:00:00"...

Caused by: java.lang.Exception: ODI-30044: Invalid parameter: 00:00:00

The same tool execution (OdiExportLog in the example above) succeeds if executed from ODI Studio UI.

In another example, when the startcscen command is used with variable values containing blank characters, the values are truncated. 

Note that according to the ODI documentation relative to OdiExportLog, -FROMDATE and -TODATE parameters should be specified "using the format yyyy/MM/dd hh:mm:ss".

The syntax used in the example provided is therefore correct.

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
Cause
Solution
References


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