Managing Workflow Execution

Oracle Data Miner submits workflows to Oracle Database Scheduler for execution as Scheduler Jobs. Oracle Scheduler supports a variety of features that control how system resources are allocated. You can configure Oracle Scheduler to effectively manage a large pool of run requests.

Oracle Data Miner uses the default Scheduler job class, DEFAULT_JOB_CLASS as its own default. In a resource plan, jobs that run as DEFAULT_JOB_CLASS are not assigned to any consumer group; access to system resources is not restricted for jobs that have the default class. You can change the job class to a class that is based on a consumer group by setting the Oracle Data Miner repository property WORKFLOW_JOB_CLASS.

Example 6-3 shows you could create a MINING_CLASS job class based on a consumer group HEAVY_LOAD_RESOURCE_GROUP, which was previously created to allocate high CPU for heavy workload jobs. When you update WORKFLOW_JOB_CLASS, the workflow will run with access to system resources that are restricted to this consumer group.The resource plan for the assigned HEAVY_LOAD_RESOURCE_GROUP group must be active when the workflow is run. You can set up Scheduler windows to activate specific resource plans at specific time periods.

See Also:

Example 6-3 Changing the Scheduler Job Class for Oracle Data Miner Workflows

connect sys as sysdba;
Enter password: password
EXEC DBMS_SCHEDULER.CREATE_JOB_CLASS(
              job_class_name => 'MINING_CLASS', 
              resource_consumer_group => 'HEAVY_LOAD_RESOURCE_GROUP');
GRANT EXECUTE ON MINING_CLASS to DMUSER;
-- update WORKFLOW_JOB_CLASS
UPDATE ODMRSYS.ODMR$REPOSITORY_PROPERTIES
   SET property_str_value = 'MINING_CLASS'
   WHERE property_name = 'WORKFLOW_JOB_CLASS';
-- commit change
commit;
-- verify value of WORKFLOW_JOB_CLASS after update
SELECT property_name, property_str_value 
   FROM ODMRSYS.ODMR$REPOSITORY_PROPERTIES
   WHERE property_name = 'WORKFLOW_JOB_CLASS';