• Random Seed

• Model Search

• Remove Small Components

• Convergence Tolerance GLMS_CONV_TOLERANCE

• Number of Iterations GLMS_NUM_ITERATIONS

• Batch Rows GLMS_BATCH_ROWS

• Solver GLMS_SOLVER

• Sparse Solver GLMS_SPARSE_SOLVER

• Approximate Computation ODMS_APPROXIMATE_COMPUTATION

• Categorical Predictor Treatment GLMS_SELECT_BLOCK

• Sampling for Feature Identification GLMS_FTR_IDENTIFICATION

• Feature Acceptance GLMS_FTR_ACCEPTANCE

• Levels of Details KMNS_DETAILS

• Random Seeds KMNS_RANDOM_SEEDS

• Growth Factor

• Solver SVMS_SOLVER

• Number of Iterations SVMS_NUM_ITERATIONS

• Regularizer SVMS_REGULARIZER

• Batch RowsSVMS_BATCH_ROWS

• Number of Pivots SVMS_NUM_PIVOTS

  Note:

  Applies to Gaussian kernel function only.

• Active Learning

• Cache Size SVMS_KERNEL_CACHE_SIZE

  Note:

  Applies to Gaussian kernel function only.

• Solver SVDS_SOLVER

• Tolerance SVDS_TOLERANCE

• Random SeedSVDS_RANDOM_SEED

• Over sampling SVDS_OVER_SAMPLING

• Power Iteration SVDS_POWER_ITERATION

• Approximate Computation ODMS_APPROXIMATE_COMPUTATION

• The R Extensible node does not work in Oracle Data Miner if you are connected to Oracle Autonomous Database.

• Association Model Build node cannot consume data coming directly from JSON Query node.

  Users must persist the data coming from the JSON Query node through Create Table node, and then use the persisted data as input to the Associate Model Build node.

• Classification nodes and Regression Model Build nodes are unable to consume data directly coming from JSON Query node if JSON Aggregations (with Sub Group By) are defined.

  Users must persist the data coming from the JSON Query node through Create Table node, and then use the persisted data as input to these Build nodes.

  Note:

  Build nodes can consume data directly coming from JSON Query nodes if JSON Aggregations (without Sub Group By) are not defined.

• Setting Parallel Query for a node that queries JSON data can result in a workflow runtime error. JSON queries will fail if they are run with the database Parallel Query set to ON. The following error message is displayed ORA-12805: Parallel Query server died unexpectedly.

  You can configure Parallel Query through Oracle Data Miner at the node level:

  • The Node context menu has the option to set Parallel Query. Click Parallel Query and select the nodes to configure the parallel settings.

  • The View Data viewer provides the option to set Parallel Query to ON when querying the selected Data Nodes.

    In both the cases, the error occurs and the same error message is displayed.

• Multi byte character data is not supported in Oracle Data Miner with Oracle Database 12.1 because of database issues. To address the multibyte issue, apply the Oracle Database 12.1.0.2 patch. It is also recommended to use the AL32UTF8 character set.

  Note:

  Request the Oracle Database 12.1.0.2 patch through Oracle Support.
• When installing Oracle Data Miner repository, error messages are generated which can be ignored. The error messages are related to database objects that are loaded during installation. After all the database objects are installed, a complete re-compilation is performed. If there are invalid objects, then an exception is raised. If the script does not raise any exceptions, then it means that the installation of Oracle Data Miner repository is successful.

  Note:

  You can ignore these error messages during Oracle Data Miner 18.4 or later installation, if no exceptions are generated.

CREATE OR REPLACE VIEW ODMRSYS.ODMR_ALL_WORKFLOW_JOBS AS SELECT * FROM 
( 
  WITH WF_JOBS AS 
  ( 
  SELECT WORKFLOW_ID, WORKFLOW_JOB_ID, CREATION_TIME FROM 
ODMRSYS.ODMR$WORKFLOW_JOBS 
  ), 
  CHAIN_JOBS AS 
  ( 
  SELECT JOB_NAME, STATE FROM ALL_SCHEDULER_JOBS WHERE JOB_TYPE = 'CHAIN' 
  ) 
  SELECT 
      ODMR$PROJECTS.USER_NAME, 
      ODMR$PROJECTS.PROJECT_ID, 
      ODMR$PROJECTS.PROJECT_NAME, 
      ODMR$WORKFLOWS.WORKFLOW_NAME, 
      ODMR$WORKFLOWS.CHAIN_NAME "WORKFLOW_CHAIN_NAME", 
      WF_JOBS.WORKFLOW_ID, 
      WF_JOBS.WORKFLOW_JOB_ID "WORKFLOW_JOB_NAME", 
      WF_JOBS.CREATION_TIME "JOB_CREATION_TIME", 
      CASE UPPER(NVL(CHAIN_JOBS.STATE, 'completed')) 
      WHEN 'DISABLED' THEN 'FAILED' 
      WHEN 'SCHEDULED' THEN 'SCHEDULED' 
      WHEN 'RUNNING' THEN 'RUNNING' 
      WHEN 'COMPLETED' THEN 'SUCCEEDED' 
      WHEN 'STOPPED' THEN 'STOPPED' 
      WHEN 'BROKEN' THEN 'FAILED' 
      WHEN 'RETRY SCHEDULED' THEN 'SCHEDULED' 
      WHEN 'SUCCEEDED' THEN 'SUCCEEDED' 
      WHEN 'CHAIN_STALLED' THEN 'FAILED' 
      ELSE CHAIN_JOBS.STATE END "WORKFLOW_STATUS" 
  FROM 
      WF_JOBS, 
      ODMRSYS.ODMR$WORKFLOWS, 
      ODMRSYS.ODMR$PROJECTS, 
      CHAIN_JOBS 
  WHERE 
      ODMR$PROJECTS.PROJECT_ID = ODMR$WORKFLOWS.PROJECT_ID (+) 
      AND ODMR$WORKFLOWS.WORKFLOW_ID = WF_JOBS.WORKFLOW_ID (+) 
      AND WF_JOBS.WORKFLOW_JOB_ID = CHAIN_JOBS.JOB_NAME (+) 
); 


CREATE OR REPLACE VIEW ODMRSYS.ODMR_ALL_PROJECT_WORKFLOW AS SELECT * FROM 
( 
  WITH WF_JOBS AS 
  ( 
  SELECT WORKFLOW_ID, WORKFLOW_JOB_ID, CREATION_TIME 
    FROM ( 
      SELECT t.*, row_number () OVER (partition by WORKFLOW_ID ORDER BY 
CREATION_TIME DESC) rid 
      FROM ODMRSYS.ODMR$WORKFLOW_JOBS t ) 
    WHERE rid = 1 
  ), 
  CHAIN_JOBS AS 
  ( 
  SELECT JOB_NAME, STATE FROM ALL_SCHEDULER_JOBS WHERE JOB_TYPE = 'CHAIN' 
  ) 
  SELECT 
      ODMR$PROJECTS.USER_NAME, 
      ODMR$PROJECTS.PROJECT_ID, 
      ODMR$PROJECTS.PROJECT_NAME, 
      ODMR$PROJECTS.CREATION_TIME PJ_CREATION_TIME, 
      ODMR$PROJECTS.LAST_UPDATED_TIME PJ_LAST_UPDATED_TIME, 
      ODMR$PROJECTS.COMMENTS PJ_COMMENTS, 
      ODMR$WORKFLOWS.WORKFLOW_ID, 
      ODMR$WORKFLOWS.WORKFLOW_NAME, 
      ODMR$WORKFLOWS.WORKFLOW_DATA, 
      ODMR$WORKFLOWS.CHAIN_NAME, 
      ODMR$WORKFLOWS.CREATION_TIME WF_CREATION_TIME, 
      ODMR$WORKFLOWS.LAST_UPDATED_TIME WF_LAST_UPDATED_TIME, 
      ODMR$WORKFLOWS.COMMENTS WF_COMMENTS, 
      CASE UPPER(NVL(CHAIN_JOBS.STATE, 'completed')) 
      WHEN 'DISABLED' THEN 'FAILED' 
      WHEN 'SCHEDULED' THEN 'SCHEDULED' 
      WHEN 'RUNNING' THEN 'RUNNING' 
      WHEN 'COMPLETED' THEN 'SUCCEEDED' 
      WHEN 'STOPPED' THEN 'STOPPED' 
      WHEN 'BROKEN' THEN 'FAILED' 
      WHEN 'RETRY SCHEDULED' THEN 'SCHEDULED' 
      WHEN 'SUCCEEDED' THEN 'SUCCEEDED' 
      WHEN 'CHAIN_STALLED' THEN 'FAILED' 
      ELSE CHAIN_JOBS.STATE END "STATUS" 
  FROM 
      WF_JOBS, 
      ODMRSYS.ODMR$WORKFLOWS, 
      ODMRSYS.ODMR$PROJECTS, 
      CHAIN_JOBS 
  WHERE 
      ODMR$PROJECTS.PROJECT_ID = ODMR$WORKFLOWS.PROJECT_ID (+) 
      AND ODMR$WORKFLOWS.WORKFLOW_ID = WF_JOBS.WORKFLOW_ID (+) 
      AND WF_JOBS.WORKFLOW_JOB_ID = CHAIN_JOBS.JOB_NAME (+) 
);