Migrating Batch Job Stream Definitions
Batch Job Stream Definitions can be migrated to other environments using the CMA (Configuration Migration Assistant) process or the Process Automation Tool. A Criteria Based Migration Request needs to be created as a pre-requisite before migrating the Batch Job Stream Definitions.
Once the Batch Job Stream Definitions are migrated to other environments, any Scheduler Programs that are referenced by Batch Job Stream Definitions should be activated in the target environment for a corresponding program to be created in the Oracle Scheduler. If the scheduler program already exists in target environment, then the scheduler program should be re-activated so latest changes can be sent to Oracle Scheduler.
Once all referenced scheduler programs are activated, the respective Batch Job Stream Definitions should be activated so the stream definition can be created and activated in Oracle Scheduler to run periodically.
If a Batch Job Stream Definition already exists in the target environment and is in Active state, the status is set to Active Pending Changes when the Batch Job Stream Definition is migrated. The Batch Job Stream Definition should be manually re-published/activated so the stream updates can be sent to Oracle Scheduler.
Note:
Migration of batch job stream definitions and scheduler programs via bundling is not supported. Please ensure CMA/Process Automation Tool is used for migration of these entities.