Schedule Concurrent Request Does Not Get The Correct Parameter to Run Every Time (Doc ID 1384381.1)

Last updated on OCTOBER 07, 2016

Applies to:

Oracle Concurrent Processing - Version 12.1.2 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms


When scheduling a concurrent request set, using a dynamic parameter with SQL statement in the request set definition, the parameter always retains the initial value and does not update the dynamic parameter on each submission of the request set.

Steps to Reproduce
1) Schedule a request set
2) Use dynamic parameter, "SQL Statement" in the request set definition.
3) Parameter has not changed, first parameter value is retained.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms