Skip Headers
Oracle® Warehouse Builder OMB*Plus Command Reference
11g Release 2 (11.2)

Part Number E14406-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
Mobi · ePub

OMBIMPACT

Purpose

To fetch the impact of a change for an object.

Prerequisites

In the context of an object's parent module.

Syntax

parseImpactCommand =  OMBIMPACT DEPENDENCYTYPE "parseType" "parseFCO" [ 
          "parseSCO" ] [ "parseDetail" ]
     parseType =  "QUOTED_STRING"
     parseFCO =  ( ADVANCED_QUEUE | ALTERNATIVE_SORT_ORDER | CUBE | DATA_RULE | 
          DIMENSION | DRILL_PATH | DRILL_TO_DETAIL | EXTERNAL_TABLE | FLAT_FILE 
          | FUNCTION | WEB_SERVICE | ITEM_FOLDER | LOGICAL_TABLE | 
          LIST_OF_VALUES | MATERIALIZED_VIEW | NESTED_TABLE | OBJECT_TYPE | 
          PLUGGABLE_MAPPING | PROCEDURE | QUEUE_TABLE | REGISTERED_FUNCTION | 
          SEQUENCE | TABLE | TIME_DIMENSION | VARYING_ARRAY | VIEW ) 
          "QUOTED_STRING"
     parseSCO =  "UNQUOTED_STRING" "QUOTED_STRING" { "UNQUOTED_STRING" 
          "QUOTED_STRING" }
     parseDetail =  GET MAPPING CONTENTS

Parameters

parseImpactCommand

Specify OMBIMPACT command.

parseType

The type of impact. Allowable values are: DATAFLOW or DEPLOYMENT.

parseFCO

The object whose impact needs to be fetched.

parseSCO

The second class object whose impact needs to be fetched, specified in the form: SCO_type SCO_name. The second class object has to belong to the first class object specified by the previous clause. If the second class object is not direct child of the first class object, then the whole hierarchy path has to be listed (for example: parent_SCO_type parent_SCO_name child_SCO_type child_SCO_name).

parseDetail

Expands mappings and show operators involved in the impact.