My Oracle Support Banner

ODI Scenario Startup Value Not Suggested as Input Parameter When Generating Scenario (Doc ID 1913662.1)

Last updated on JUNE 16, 2022

Applies to:

Oracle Data Integrator - Version to [Release 12c]
Information in this document applies to any platform.


In ODI 11g it was possible to use a variable in the first and last steps of every IKM for custom logging purposes.
It was also possible to use that variable  as a startup parameter in a interface and any scenario generated from that interface.
This is not the case anymore in 12c, resulting in not being able to pass any value as a parameter.

The following error occurs:

The issue can be reproduced at will with the following steps:
1. - Create a Global variable (numeric, no history, with a default value and no refresh query).
- Add a step in an IKM using that variable.
- Create a mapping using that IKM.
- Generate a Scenario of the mapping. Expected : Dialog Box asking if #GLOBAL.LOG_JOB_ID should be used as Startup Parameter. This doesn't happen.
- Call the scenario using OdiStartScen and passing the value of the variable, using Log Level 6. Expected : the scenario use that value for the variable and it can be seen in the operator thanks to log level 6.




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

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