RE: [Control-X] Issue with Control-M 6.4 and Running Concurrent Manager Oracle Jobs
I would suggest place debug on when running this job. This will provide greater insight into the issue.
We recently upgraded to Oracle 11g and after doing so, we have a limited number of payroll related Oracle concurrent manager jobs that will not run and receive the followig error:
CM for OEBS: Failure: Request_id is not a valid value
Any and all help is greatly appreciated.
Note that if the client runs the concurrent manager job directly themselves rather than using Control-M, they have no problems.