| Oracle® Warehouse Builder API and Scripting Reference 10g Release 2 (10.2) Part Number B28225-01 |
|
|
View PDF |
| Oracle® Warehouse Builder API and Scripting Reference 10g Release 2 (10.2) Part Number B28225-01 |
|
|
View PDF |
This chapter contains an alphabetical listing of the navigation, service, administrative, and shell commands you can use in OMB Plus. Commands for metadata manipulation are contained in separate chapters.
Purpose
Change Active Configuration command allows users to set as active another Configuration in a Project.
Prerequisites
Must be in a Project context.
Syntax
parseChangeActiveConfigurationCommand = OMBCAC "QUOTED_STRING"
Examples
OMBCAC 'MY_CONFIGURATION_2'
This will set the 'MY_CONFIGURATION' configuration as active.
See Also
OMBDAC
Purpose
Change Context command allows users to change the current context to the desired location in OWB tree. The target context can be specified
either as an absolute path starting from the root ('/') or as a relative
path starting from the current context. Also, the path can contain '..',
which allows to navigate "up" to the parent context.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseChangeContextCommand = OMBCC "QUOTED_STRING"
Keywords And Parameters
parseChangeContextCommand
Specify change context command.
QUOTED_STRING
The target context to switch to.
Examples
OMBCC '/'
changes the context to the root.
OMBCC '/MY_PROJECT/ORACLE_1'
changes the context to Oracle module 'ORACLE_1', within project
'MY_PROJECT'.
OMBCC '..'
changes the context to the parent of current context (to the project
level, if the current context is an Oracle module, for example).
See Also
OMBDCC
Purpose
Perform commit action on the repository.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseCommitCommand = OMBCOMMIT
Keywords And Parameters
parseCommitCommand
Specify commit command.
Examples
OMBCOMMIT
See Also
OMBROLLBACK
Purpose
Change management is a key piece of metadata management. This comand provides comparison services of any complex object
model in the repository. This command writes the diff between
snapshot/component to XML file.
Prerequisites
Snapshots can be compared from any context and either with another snapshot
or the current repository objects.
Syntax
parseCompareCommand = OMBCOMPARE "compareSnapshotCommand"
compareSnapshotCommand = ( ( SNAPSHOT "QUOTED_STRING" ) WITH
"getCompareWith" OUTPUT TO "QUOTED_STRING" WRITE ( ALL |
FOUND_IN_TARGET | FOUND_IN_SOURCE | UPDATED | CHANGED | UNCHANGED ) )
getCompareWith = SNAPSHOT "QUOTED_STRING" [ FOR ( "UNQUOTED_STRING"
"QUOTED_STRING" ) ] | ( CURRENT FOR ( "UNQUOTED_STRING"
"QUOTED_STRING" ) )
Keywords And Parameters
parseCompareCommand
Root production of OMBCOMPARE SNAPSHOT.
compareSnapshotCommand
To compare components of snapshots.
QUOTED_STRING
Name of source snapshot which needs to be compared with the target
snapshot.
OUTPUT
Specifies output filename where the XML comparison result will written.
WRITE
Specifies filter clause which will make the diff engine only write
specified objects of a certain diff state.
getCompareWith
Target of the comparison.
SNAPSHOT
Target snapshot which will be compared with the source snapshot.
FOR
Specifies component which exists in the current repository.
CURRENT
Indicates current component's definition as the target of compare action.
Examples
OMBCOMPARE SNAPSHOT 'S1' WITH SNAPSHOT 'S2' OUTPUT TO 'd:diff.xml' WRITE
CHANGED
This command compares snapshot S1 with S2, and writes objects with CHANGED
state into diff.xml, Though the diff engine allows to compare any two
snapshot, even two unrelate snapshots with totaly different components in
them. CHANGED filter writes FOUND_IN_SOURCE or FOUND_IN_TARGET or UPDATED
components, CHANGED state represents whole diff,
OMBCOMPARE SNAPSHOT 'S1' WITH SNAPSHOT 'S2' OUTPUT TO 'd:diff.xml' WRITE
FOUND_IN_SOURCE
This command writes objects which are only found in snapshot S1.
OMBCOMPARE SNAPSHOT 'S1' WITH CURRENT FOR TABLE '/Project1/WH1/T1' OUTPUT
TO 'd:diff.xml' WRITE ALL
This command writes all table objects with any diff state.
See Also
OMBCREATE SNAPSHOT, OMBALTER SNAPSHOT, OMBDROP SNAPSHOT, OMBRESTORE SNAPSHOT, OMBLIST SNAPSHOT, OMBRETRIEVE SNAPSHOT
Purpose
This command compiles an repository object. The results are generated in a file in a user defined directory.
Prerequisites
In the context of a Oracle Module.
Syntax
parseCompileCommand = OMBCOMPILE ( ( EXPERT | EXPERT_MODULE | TABLE | VIEW
| SEQUENCE | MATERIALIZED_VIEW | DIMENSION | CUBE | DATA_AUDITOR |
MAPPING | REAL_TIME_MAPPING | TRANSPORTABLE_MODULE |
BUSINESS_PRESENTATION_MODULE | BUSINESS_DEFINITION_MODULE |
EXTERNAL_TABLE | OBJECT_TYPE | NESTED_TABLE | VARYING_ARRAY |
COLLECTION | CONNECTOR | PRESENTATION_TEMPLATE |
ALTERNATIVE_SORT_ORDER | LIST_OF_VALUES | DRILL_TO_DETAIL |
BUSINESS_AREA | DRILL_PATH | ITEM_FOLDER | REGISTERED_FUNCTION |
PACKAGE | FUNCTION | PROCEDURE | TABLE_FUNCTION | PLSQL_RECORD_TYPE |
PLSQL_TABLE_TYPE | PLSQL_REF_CURSOR_TYPE PROCESS_FLOW_PACKAGE |
ADVANCED_QUEUE | STREAMS_QUEUE | QUEUE_TABLE | QUEUE_PROPAGATION |
STREAMS_CAPTURE_PROCESS | PROCESS_FLOW_PACKAGE | PROCESS_FLOW_MODULE |
CALENDAR | CALENDAR_MODULE ) "QUOTED_STRING" [
"getOutputValidationResults" ] [ "getOutputGeneratedScripts" ] )
getOutputValidationResults = OUTPUT [ VALIDATION_RESULT ] TO (
"QUOTED_STRING" | ( FILE "QUOTED_STRING" ) ) WRITE ( ( "(" ( ( SUCCESS
| WARNING | ERROR ) [ "," ] )+ ")" ) | ALL | SUCCESS | WARNING |
ERROR )
getOutputGeneratedScripts = OUTPUT GENERATION_SCRIPTS TO ( "QUOTED_STRING"
| ( FILE "QUOTED_STRING" ) )
Keywords And Parameters
parseCompileCommand
This command compiles a repository object.
QUOTED_STRING
The name of the object.
getOutputValidationResults
This clause outputs the validation results to one or more files in the
specified folder.
QUOTED_STRING
A file or directory where validation results are stored.
getOutputGeneratedScripts
This clause outputs the generated scripts for an object to one or more
files in specified folder.
QUOTED_STRING
A file or directory where generated scripts are stored.
Examples
OMBCOMPILE TABLE 'T1' OUTPUT VALIDATION_RESULT TO '/tmp' WRITE SUCCESS
OUTPUT GENERATION_SCRIPTS TO '/tmp'.
OMBCOMPILE TABLE 'T1' OUTPUT GENERATION_SCRIPTS TO '/tmp'
The first example gets the validation results and generated scripts for
the table, whereas the second example gets only the generated scripts.
See Also
OMBVALIDATE
Purpose
To connect to a OWB repository.
Prerequisites
Must not be connected to another OWB repository. If connected to another
repository, use OMBDISCONNECT to disconnect first.
Syntax
parseConnectCommand = ( ( OMBCONNECT | OMBCONN ) "UNQUOTED_STRING" [ USE (
REPOSITORY | REPOS ) "QUOTED_STRING" ] [ USE ( SINGLE_USER_MODE |
MULTIPLE_USER_MODE ) ] )
Keywords And Parameters
parseConnectCommand
Specify connect command.
UNQUOTED_STRING
Specify the connection string to the database, in the format:
username/password@host:port:service name
QUOTED_STRING
Optionally, specify the name of a repository to work on. If not provided,
the default repository will be used.
SINGLE_USER_MODE
If specified, the user will use the repository exclusively.
MULTIPLE_USER_MODE
If specified, more than one session can work on the same repository at the
same time. This is the default mode.
Examples
OMBCONNECT owb_normal_user/welcome@dwsun42:1521:dev817 USE REPOSITORY
'owb_repos' USE SINGLE_USER_MODE
will connect a normal user owb_normal_user to database and work on
repository named 'owb_repos' in single user mode.
See Also
OMBDISCONNECT
Purpose
To connect to a OWB repository.
Prerequisites
Must not be connected to another OWB repository. If connected to another
repository, use OMBDISCONNECT to disconnect first.
Syntax
parseConnectCommand = ( ( OMBCONNECT | OMBCONN ) "UNQUOTED_STRING" [ USE (
REPOSITORY | REPOS ) "QUOTED_STRING" ] [ USE ( SINGLE_USER_MODE |
MULTIPLE_USER_MODE ) ] )
Keywords And Parameters
parseConnectCommand
Specify connect command.
UNQUOTED_STRING
Specify the connection string to the database, in the format:
username/password@host:port:service name
QUOTED_STRING
Optionally, specify the name of a repository to work on. If not provided,
the default repository will be used.
SINGLE_USER_MODE
If specified, the user will use the repository exclusively.
MULTIPLE_USER_MODE
If specified, more than one session can work on the same repository at the
same time. This is the default mode.
Examples
OMBCONNECT owb_normal_user/welcome@dwsun42:1521:dev817 USE REPOSITORY
'owb_repos' USE SINGLE_USER_MODE
will connect a normal user owb_normal_user to database and work on
repository named 'owb_repos' in single user mode.
See Also
OMBDISCONNECT
Purpose
To connect to a Control Center.
This command can either be used when you are already connected to a Design
Repository or it can be used independently of a Design Repository.
With Design Repository connection:
This command will connect you to the Control Center that is associated with
the current Active Configuration.
If this is the DEFAULT_CONTROL_CENTER and it does not have a user and
password specified, then you will be connected to the Control Center as the
currently connected Design Repository User. This is the typical
out-of-the-box scenario. If the DEFAULT_CONTROL_CENTER has a user specified
then you will be connected as that user. Note in this case you may have to
provide a password.
If this is not the DEFAULT_CONTROL_CENTER, then you will either connect as
the user specified against the Control Center or you will have to provide a
user with this command. Note that in this situation you will probably have
to supply a password.
Without Design Repository connection:
This command can be used to connect to a Control Center independently of a
Design Repository. For example, you may want to OMBDEPLOY a deployment
specification that had been previously deployed to the file system or
OMBSTART a job. In this case you will have to provide the complete
connection details.
Prerequisites
With Design Repository connection:
A Design Repository connection, at least a PROJECT context and the Active
Configuration's Selected CONTROL_CENTER must be defined.
Without Design Repository connection:
There must not be a Design Repository connection whenever this method is
used.
Syntax
parseConnectRuntimeCommand = ( ( OMBCONNECT | OMBCONN ) CONTROL_CENTER [ (
USE "QUOTED_STRING" ) | ( "UNQUOTED_STRING" USE ( REPOSITORY | REPOS
) "QUOTED_STRING" ) ] )
Keywords And Parameters
parseConnectRuntimeCommand
Specify Control Center connect command.
QUOTED_STRING
Specific Control Center:
Examples
With Design Repository connection:
OMBCONNECT CONTROL_CENTER USE 'RepositoryUserName/RepositoryUserPassword'
OMBCONNECT CONTROL_CENTER USE 'RepositoryUserPassword'
OMBCONNECT CONTROL_CENTER
Without Design Repository connection:
OMBCONNECT CONTROL_CENTER
RepositoryUserName/RepositoryUserPassword@HostName:PortNumber:OracleServiceName
USE REPOSITORY 'RepositorySchema'
See Also
OMBDISCONNECT CONTROL_CENTER
Purpose
To connect to a Control Center.
This command can either be used when you are already connected to a Design
Repository or it can be used independently of a Design Repository.
With Design Repository connection:
This command will connect you to the Control Center that is associated with
the current Active Configuration.
If this is the DEFAULT_CONTROL_CENTER and it does not have a user and
password specified, then you will be connected to the Control Center as the
currently connected Design Repository User. This is the typical
out-of-the-box scenario. If the DEFAULT_CONTROL_CENTER has a user specified
then you will be connected as that user. Note in this case you may have to
provide a password.
If this is not the DEFAULT_CONTROL_CENTER, then you will either connect as
the user specified against the Control Center or you will have to provide a
user with this command. Note that in this situation you will probably have
to supply a password.
Without Design Repository connection:
This command can be used to connect to a Control Center independently of a
Design Repository. For example, you may want to OMBDEPLOY a deployment
specification that had been previously deployed to the file system or
OMBSTART a job. In this case you will have to provide the complete
connection details.
Prerequisites
With Design Repository connection:
A Design Repository connection, at least a PROJECT context and the Active
Configuration's Selected CONTROL_CENTER must be defined.
Without Design Repository connection:
There must not be a Design Repository connection whenever this method is
used.
Syntax
parseConnectRuntimeCommand = ( ( OMBCONNECT | OMBCONN ) CONTROL_CENTER [ (
USE "QUOTED_STRING" ) | ( "UNQUOTED_STRING" USE ( REPOSITORY | REPOS
) "QUOTED_STRING" ) ] )
Keywords And Parameters
parseConnectRuntimeCommand
Specify Control Center connect command.
QUOTED_STRING
Specific Control Center:
Examples
With Design Repository connection:
OMBCONNECT CONTROL_CENTER USE 'RepositoryUserName/RepositoryUserPassword'
OMBCONNECT CONTROL_CENTER USE 'RepositoryUserPassword'
OMBCONNECT CONTROL_CENTER
Without Design Repository connection:
OMBCONNECT CONTROL_CENTER
RepositoryUserName/RepositoryUserPassword@HostName:PortNumber:OracleServiceName
USE REPOSITORY 'RepositorySchema'
See Also
OMBDISCONNECT CONTROL_CENTER
Purpose
Copy one or more objects of the same object type. The replace option enables you to overwrite.
Prerequisites
Use of relative path specifications requires awareness of the current
context.
Syntax
parseCopyCommand = OMBCOPY "copyObjectType" "QUOTED_STRING" TO
"QUOTED_STRING" [ USE REPLACE_MODE ]
copyObjectType = ( "UNQUOTED_STRING" )
Keywords And Parameters
parseCopyCommand
Specifies the source object type, source path, and target path for the
object to copy. Copying objects is subject to the following restrictions:
1. You cannot copy an entire project. 2. When copying objects between
projects, you can only copy objects into the current project; you cannot
copy objects out to other projects.
QUOTED_STRING
Source and target path specifications can be absolute or relative. To copy
multiple objects, include a regular expression as the final step of the
source path. If you are copying multiple objects, the final step of the
target path must be the folder to which the objects are being copied. If
you are only copying one object, you can specify the object's original name
or a new name as the final step of the target path.
REPLACE_MODE
Use this option to overwrite existing target objects.
copyObjectType
The type of the object(s) to be copied. Valid types are: PROJECT,
ORACLE_MODULE, FLAT_FILE_MODULE, BUSINESS_DEFINITION_MODULE,
BUSINESS_PRESENTATION_MODULE, SAP_MODULE, CMI_MODULE, PROCESS_FLOW_MODULE,
PROCESS_FLOW_PACKAGE, PROCESS_FLOW, EXPERT_MODULE, EXPERT, LOCATION,
CONTROL_CENTER, CONFIGURATION, FLAT_FILE, ADVANCED_QUEUE, STREAMS_QUEUE,
QUEUE_TABLE, QUEUE_PROPAGATION, STREAMS_CAPTURE_PROCESS, OBJECT_TYPE,
VARYING_ARRAY, NESTED_TABLE, TABLE, VIEW, MATERIALIZED_VIEW, SEQUENCE,
DIMENSION, CUBE, DATA_AUDITOR, DATA_PROFILE, DATA_RULE, DATA_RULE_MODULE,
MAPPING, REAL_TIME_MAPPING, PACKAGE, FUNCTION, PROCEDURE, BUSINESS_AREA,
COLLECTION, EXTERNAL_TABLE, REGISTERED_FUNCTION, ITEM_FOLDER, DRILL_PATH,
LIST_OF_VALUES, DRILL_TO_DETAIL, ALTERNATIVE_SORT_ORDER,
PRESENTATION_TEMPLATE and any user defined object types.
Examples
OMBCOPY TABLE 'MY_TABLE1' TO 'MY_TABLE2' USE REPLACE_MODE
OMBCOPY ORACLE_MODULE '/MY_PROJECT/WH1' TO '/MY_PROJECT/WH2'
OMBCOPY TABLE 'MY_.*' TO '/MY_PROJECT/WH2'
See Also
OMBMOVE
Purpose
Display the name of the active configuration of a project.
Prerequisites
Must be in the context of a project.
Syntax
parseDisplayActiveConfigurationCommand = OMBDAC
Keywords And Parameters
parseDisplayActiveConfigurationCommand
Specify Display Active Configuration command.
Examples
OMBDAC
This will display a name of the active configuration of a project.
See Also
OMBCAC
Purpose
Display Current Context command displays the current context (location) and, for contexts other than the root ('/'), the type of the
current folder.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseDisplayCurrentContextCommand = OMBDCC
Keywords And Parameters
parseDisplayCurrentContextCommand
Specify display current context command.
Examples
OMBDCC
will display
/
if the current context is the root.
OMBDCC
will display
PROJECT /MY_PROJECT
if the current context is the project 'MY_PROJECT'.
See Also
OMBCC
Purpose
Debug a mapping by stepping through map execution one operator at a time.
Prerequisites
The current context must be in an Oracle module which contains at least one
map.
Syntax
debugMappingCommand = OMBDEBUG MAPPING "mappingName" "debugClause"+
mappingName = "QUOTED_STRING"
debugClause = START [ DEBUG ] SESSION | END [ DEBUG ] SESSION | STEP | SKP
| RESUME | DISPLAY ( [ "INTEGER_LITERAL" ROWS OF ] [
"dataDisplayGroupDirection" ] DEBUG_DATA [ FOR "groupBottomUpLocator"
] | CURRENT_STEP_GROUP ) | SET BREAKPOINT AT "operatorBottomUpLocator"
| CLEAR BREAKPOINT AT "operatorBottomUpLocator" | REINITIALIZE |
RESET
dataDisplayGroupDirection = INPUT | OUTPUT
groupBottomUpLocator = GROUP "groupName" OF "operatorBottomUpLocator"
operatorBottomUpLocator = OPERATOR "operatorName" [
"pluggableMapBottomUpLocator" ]
groupName = "QUOTED_STRING"
operatorName = "QUOTED_STRING"
pluggableMapBottomUpLocator = ( OF PLUGGABLE_MAPPING "pluggableMapName" [
"pluggableMapBottomUpLocator" ] )
pluggableMapName = "QUOTED_STRING"
Keywords And Parameters
mappingName
Name of the mapping.
groupBottomUpLocator
Location of a mapping group.
operatorBottomUpLocator
Location of a mapping operator.
groupName
Name of a mapping group.
operatorName
Name of a mapping operator.
pluggableMapBottomUpLocator
Location of a child pluggable mapping within a mapping or another pluggable
mapping.
pluggableMapName
Name of the pluggable map.
Examples
#
# Script to run the mapping debugger for map
/OWB_MAPPING_TS/TEST_MODULE/JOIN7_MAP_INSERT
# Assumes that this map has been created, and has an operator 'JOIN1'
# This map is created by the 'mapping codegen' development acceptance test
#
OMBCONNECT rep_XXXX/rep_XXXX@localhost:1521:ora10.us.oracle.com
OMBCC '/OWB_MAPPING_TS/TEST_MODULE'
OMBCONNECT CONTROL_CENTER 'DEFAULT_CONTROL_CENTER'
# puts "CONNECTED"
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' START SESSION
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' SET BREAKPOINT AT OPERATOR 'JOIN1'
#
# Resume execution until breakpoint at "JOIN1" is hit
#
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' RESUME
#
# Step through one row of data
#
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' STEP
#
# Step through 2 rows of data
#
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' STEP STEP
# Display the debug data for the current step group. Should be 3 rows,
since we have stepped
# 3 rows into this operator.
# WARNING: will not work if "DATA" is used instead of "DEBUG_DATA",
# since "DATA" is already a reserved keyword used for another command
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' DISPLAY DEBUG_DATA
#
# Display 10 rows of output data for group "EMP.INOUTGRP1"
#
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' DISPLAY 10 ROWS OF OUTPUT DEBUG_DATA
FOR GROUP 'INOUTGRP1' OF OPERATOR 'EMP'
#
# Set the column width for debug data to 10 (default is 20)
#
set COLUMN_WIDTH 10
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' DISPLAY 10 ROWS OF OUTPUT DEBUG_DATA
FOR GROUP 'INOUTGRP1' OF OPERATOR 'EMP'
#
# Reset the debug session - reinitialize data and start execution at
beginning of map
#
#OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' RESET
#
# Reinitialize the debug session - regenerate and deploy debug code. Do
this if the map
# is edited.
#
#OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' REINITIALIZE
#
# Skip through the first operator, next step will go to next operator in
graph.
#
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' SKIP
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' DISPLAY CURRENT_STEP_GROUP
OMBDEBUG MAPPING 'JOIN7_MAP_INSERT' END SESSION
Purpose
To define an association between two classes (types).
Prerequisites
Association definition to be defined should not already exist. User must
have CREATE_EXTENSIONMODEL system privilege and has to be connected in
single user mode to run this command.
Syntax
parseDefineAssociationCommand = OMBDEFINE ASSOCIATION_DEFINITION
"QUOTED_STRING" "setAssociationDefinitionPropertiesClause" {
"addDependencyDefinitionClause" }
setAssociationDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
addDependencyDefinitionClause = ADD DEPENDENCY_DEFINITION "QUOTED_STRING"
[ "setDependencyDefinitionPropertiesClause" ]
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyValueList = "propertyValue" { "," "propertyValue" }
setDependencyDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
propertyNameClause = ( "UNQUOTED_STRING" )
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
parseDefineAssociationCommand
Define an association between two classes..
setAssociationDefinitionPropertiesClause
Basic properties for ASSOCIATION_DEFINITION:
Name: DESCRIPTION
Type: STRING(4000)
Valid Values: N/A
Default: N/A
A descriptive text for this association.
Name: CLASS_1
Type: STRING(200)
Valid Values: N/A
Default: N/A
Class on one side of the association.
NAME: CLASS_2
Type: STRING(200)
Value Values: N/A
Default: N/A
Class on the other side of the association.
Name: ROLE_1
Type: STRING(200)
Valid Values: N/A
Default: N/A
Role on one side of the association.
Name: ROLE_2
Type: STRING(200)
Valid Values: N/A
Default: N/A
Role on the other side of the association.
Name: ROLE_1_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 1. Value can be positive integer.
Name: ROLE_1_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 1. Value can be positive integer or 'INFINITE'.
Name: ROLE_1_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 1.
Name: ROLE_2_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 2. Value can be positive integer.
Name: ROLE_2_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 2. Value can be positive integer or 'INFINITE'.
Name: ROLE_2_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 2.
addDependencyDefinitionClause
Mark this association so that the dependency engine will consider it when
computing the lineage and impact dependencies. The only dependency type
allowed here for now is 'DATAFLOW'.
propertyNameList
The list of property names.
propertyValueList
The list of property values being set.
setDependencyDefinitionPropertiesClause
Basic dependency-related properties for this association:
Name: SOURCE_ROLE_ID
Type: STRING(200)
Valid Values: ROLE_1, ROLE_2
Default: If one of the ends is a OWB class, then that is the default
source. If both ends are user defined classes, then the association is
default bidirectional.
Identifies the role (end) of the association which serves as the source for
the dependency flow.
Name: BIDIRECTIONAL
Type: BOOLEAN
Valid Values: true, false
Default: If one of the ends is a OWB class, then default is false. If both
ends are user defined classes, then default is true.
Specifies whether the association is bi-directional for the dependency
flow.
propertyNameClause
Name of a property.
propertyValue
Value of a property.
Examples
OMBDEFINE ASSOCIATION_DEFINITION 'UD_ASSOC1'
SET PROPERTIES (CLASS_1, CLASS_2, ROLE_1, ROLE_2, ROLE_1_MAX_CARDINALITY,
ROLE_1_NAVIGABLE) VALUES ('UD_REPORT', 'TABLE', 'REF_TABLES', 'REF_REPORT',
'INFINITE', 'true') ADD DEPENDENCY_DEFINITION 'DATAFLOW'
This will define a new association between class UD_REPORT and TABLE, and
define DATAFLOW dependency on this association.
See Also
OMBDESCRIBE ASSOCIATION_DEFINITION
Purpose
To define a class (user defined object type).
Prerequisites
Class definition to be defined should not already exist.
Syntax
parseDefineClassCommand = OMBDEFINE [ ( FIRST_CLASS_OBJECT |
SECOND_CLASS_OBJECT | FOLDER | MODULE ) ] CLASS_DEFINITION
"QUOTED_STRING" [ ( "setClassDefinitionPropertiesClause" |
"setClassDefinitionIconSetClause" ) ] [ "addSubDefinitionsClause" ]
setClassDefinitionPropertiesClause = SET PROPERTIES "(" "propertyNameList"
")" VALUES "(" "propertyValueList" ")"
setClassDefinitionIconSetClause = SET REF ICONSET "QUOTED_STRING"
addSubDefinitionsClause = ( "addPropertyDefinitionClause" |
"addPropertyGroupDefinitionClause" | "addChildTypeClause" )+
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyValueList = "propertyValue" { "," "propertyValue" }
addPropertyDefinitionClause = ( ADD [ ( ( CONFIGURATION |
PHYSICAL_CONFIGURATION ) | LOGICAL | USER_DEFINED ) ]
PROPERTY_DEFINITION "QUOTED_STRING"
"setPropertyDefinitionPropertiesClause" )
addPropertyGroupDefinitionClause = ADD PROPERTY_GROUP_DEFINITION
"QUOTED_STRING" "setPropertyGroupDefinitionPropertiesClause"
addChildTypeClause = ( ADD CHILD_TYPE "QUOTED_STRING" )
propertyNameClause = ( "UNQUOTED_STRING" )
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
setPropertyDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
setPropertyGroupDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
Keywords And Parameters
parseDefineClassCommand
Define a class.
FOLDER
Class definition is folder.
MODULE
Class definition is module.
QUOTED_STRING
Name of the class.
setClassDefinitionPropertiesClause
Set the properties on the class definition. Valid properties are
BUSINESS_NAME, DESCRIPTION, DISPLAY_NAME, PLURAL_NAME.
setClassDefinitionIconSetClause
Assign an icon to the class definition.
propertyNameList
The list of property names.
propertyValueList
The list of values.
addPropertyDefinitionClause
Add a property definition to the class definition.
addPropertyGroupDefinitionClause
Add a property group definition to the class definition.
addChildTypeClause
Add a aggregate child type to the class definition.
propertyNameClause
The name of the property.
UNQUOTED_STRING
The name of the property for the class definition.
propertyValue
The value of the property.
QUOTED_STRING
The value in string format of the property for the class definition.
INTEGER_LITERAL
The integer value of the property for the class definition.
FLOATING_POINT_LITERAL
The float value of the property for the class definition.
setPropertyDefinitionPropertiesClause
Set the properties for the property definition. Valid properties are TYPE,
DEFAULT_VALUE, POSITION, HIDDEN.
Examples
OMBDEFINE MODULE CLASS_DEFINITION 'UD_MODULE1'
SET PROPERTIES (DISPLAY_NAME, PLURAL_NAME) VALUES ('FINANCE', 'FINANCES')
ADD PROPERTY_DEFINITION 'P1'
SET PROPERTIES (TYPE, DEFAULT_VALUE) VALUES ('INTEGER', '2')
This will define a new module class, and has one property definition whose
type is integer and default value is 2.
OMBDEFINE FIRST_CLASS_OBJECT CLASS_DEFINITION 'UD_FCO1'
SEY PROPERTIES (DISPLAY_NAME, PLURAL_NAME) VALUES ('REPORT', 'REPORTS')
This will define a new first class object class definition.
See Also
OMBDESCRIBE CLASS_DEFINITION
Purpose
To define a component definition.
Prerequisites
The class definition for the component should already exist. The class must
be a first class object.
Syntax
parseDefineComponentCommand = OMBDEFINE COMPONENT_DEFINITION
"QUOTED_STRING" [ "addChildClassesClause" ]
addChildClassesClause = "addChildClassClause"+
addChildClassClause = ( ADD "QUOTED_STRING" )
Examples
OMBDEFINE COMPONENT_DEFINITION 'UD_FCO1'
ADD 'UD_SCO1'
This will define a component for class UD_FCO1, and has one second class
definition in the component.
Purpose
To define a domain.
Prerequisites
Domain is a type with constraints on some other type. For example, you can
define a domain which contains a list of valid values of some existing
type, or you can define a domain which contains ranges of some existing
type.
Syntax
parseDefineDomainCommand = OMBDEFINE DOMAIN_DEFINITION "QUOTED_STRING"
"setDomainPropertiesClause" { "addRangeClause" | "addValueClause" }
setDomainPropertiesClause = SET PROPERTIES "(" "propertyNameList" ")"
VALUES "(" "propertyValueList" ")"
addRangeClause = ADD RANGE_DEFINITION "QUOTED_STRING"
"setRangePropertiesClause"
addValueClause = ADD DOMAIN_VALUE "QUOTED_STRING"
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyValueList = "propertyValue" { "," "propertyValue" }
setRangePropertiesClause = SET PROPERTIES "(" "propertyNameList" ")"
VALUES "(" "propertyValueList" ")"
propertyNameClause = ( "UNQUOTED_STRING" )
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
parseDefineDomainCommand
Define a domain.
QUOTED_STRING
Name of the domain.
setDomainPropertiesClause
Set the properties on the domain. Valid properties are BASE_TYPE,
DESCRIPTION.
addRangeClause
Add range to the domain.
addValueClause
Add value to the domain.
propertyNameList
The list of property names.
propertyValueList
The list of values.
setRangePropertiesClause
Set the properties on the range. Valid properties are MIN_VALUE_STRING,
MIN_VALUE_INCLUSIVE, MAX_VALUE_STRING, MAX_VALUE_INCLUSIVE, DESCRIPTION.
MIN_VALUE_STRING is the minimum value for this range. MIN_VALUE_INCLUSIVE
equal to true means the minimum value is in the range. MAX_VALUE_STRING is
the maximum for this range. MAX_VALUE_INCLUSIVE equal to true means the
maximum value is in the range.
propertyNameClause
The name of the property.
UNQUOTED_STRING
The name of the property for the class definition.
propertyValue
The value of the property.
QUOTED_STRING
The value in string format of the property for the class definition.
INTEGER_LITERAL
The integer value of the property for the class definition.
FLOATING_POINT_LITERAL
The float value of the property for the class definition.
Examples
OMBDEFINE DOMAIN_DEFINITION 'UD_DOMAIN1'
SET PROPERTIES (BASE_TYPE) VALUES ('INTEGER') ADD RANGE_DEFINITION 'R1'
SET PROPERTIES (MIN_VALUE_STRING, MAX_VALUE_STRING) VALUES ('1', '9')
This will define a new domain of integer type, and has one range of value
from 1 to 9.
OMBDEFINE DOMAIN_DEFINITION 'UD_DOMAIN2'
SEY PROPERTIES (BASE_TYPE) VALUES ('STRING') ADD DOMAIN_VALUE 'string value
1'
ADD DOMAIN_VALUE 'string value 2'
This will define a new domain of string type, and has 2 valid values
'string value 1' and 'string value 2'.
See Also
OMBDESCRIBE DOMAIN_DEFINITION
Purpose
To define a folder definition.
Prerequisites
The class definition for the folder should already exist. The class must be
a folder.
Syntax
parseDefineFolderCommand = OMBDEFINE FOLDER_DEFINITION "QUOTED_STRING" [
"addChildClassesClause" ]
addChildClassesClause = "addChildClassClause"+
addChildClassClause = ( ADD "QUOTED_STRING" )
Examples
OMBDEFINE FOLDER_DEFINITION 'UD_MODULE1'
ADD 'UD_FCO1'
This will define a folder for class UD_MODULE1, and has one class
definition in the folder.
Purpose
Drop or deinstall OWB repository.
Prerequisites
To deinstall OWB repository, within the same OMBPlus session, no other OMB
commands should be issued before or after the OMBDEINSTALL OWB_REPOSITORY
command.
Syntax
parseDeinstallOWBRepositoryCommand = OMBDEINSTALL OWB_REPOSITORY
"UNQUOTED_STRING" USING CREDENTIAL "UNQUOTED_STRING" [
NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseDeinstallOWBRepositoryCommand
Specify an OMBDEINSTALL OWB_REPOSITORY command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name, OR specify the user name and
password pair using this format: username/password.
Examples
1. OMBDEINSTALL OWB_REPOSITORY h_rep5/h USING CREDENTIAL
sys/sys@localhost:1521:orcl92
This drops or de-installs an OWB repository.
Purpose
Drop or de-install an OWB target user.
Prerequisites
OWB REPOSITORY must exist on the database server.
Syntax
parseDeinstallTargetUserCommand = OMBDEINSTALL OWB_TARGET_USER
"UNQUOTED_STRING" USING OWB_REPOSITORY "UNQUOTED_STRING" USING
CREDENTIAL "UNQUOTED_STRING" [ NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseDeinstallTargetUserCommand
Specify an OMBINSTALL OWB_TARGET_USER command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name OR specify the user name and
password using this format username/password.
Examples
1. OMBDEINSTALL OWB_TARGET_USER h_tu1/h USING OWB_REPOSITORY h_rep1/h
USING CREDENTIAL sys/sys@localhost:1521:orcl92
This drops or de-installs a target user.
Purpose
To Deploy Action Plans to Control Centers or File Systems.
Prerequisites
If the Deployment is NOT from a Deployment Specification XML file then the
following are true. A Control Center connection and a named Deployment
Action Plan are required. Also, the current Context must be either an
Oracle Module, a Process Flow Module or a Location.
Syntax
parseDeployCommand = OMBDEPLOY ( ( DEPLOYMENT_ACTION_PLAN "QUOTED_STRING"
[ ( AS ( SPECIFICATION | SCRIPT ) TO "QUOTED_STRING" ) |
CONTROL_CENTER_ONLY ] ) | ( SPECIFICATION FROM "QUOTED_STRING" ) ) [
ASYNCHRONOUS ]
Keywords And Parameters
parseDeployCommand
Specify Deploy command.
DEPLOYMENT_ACTION_PLAN
Deploy a Deployment Action Plan.
QUOTED_STRING
The Deployment Action Plan name. Or, the directory (if AS SCRIPT) or file
name (if AS SPECIFICATION) into which the deployment is performed. Or, the
source XML filename (if SPECIFICATION FROM).
AS
Perform the Deployment to a File System.
SPECIFICATION
Deploy as a Deployment Specification XML file.
SCRIPT
Deploy as a set of Oracle Script files.
CONTROL_CENTER_ONLY
Do not perform a Deployment but only update the Control Center Audit.
FROM
Perform the Deployment from a file on a File System.
ASYNCHRONOUS
Deploy in an asynchronous mode.
Examples
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'MY_DEPLOY_PLAN'
Purpose
Derives business definition objects from OWB design objects.
Prerequisites
Should be in an appropriate context for the design object or use the full
path for the design object.
The Business Definition Module named in the TO clause should already exist
within the current project.
Any Business Areas named should already exist within the Business
Definition Module.
Syntax
parseDeriveCommand = OMBDERIVE ( ORACLE_MODULE | DIMENSION | CUBE | TABLE
| VIEW | EXTERNAL_TABLE | FUNCTION | COLLECTION ) "QUOTED_STRING" TO
BUSINESS_DEFINITION_MODULE "QUOTED_STRING" [ BUSINESS_AREAS "("
"BANameList" ")" ] [ "parseDeriveCommandParams" ]
BANameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
parseDeriveCommandParams = "parseRuleParameters" { "parseRuleParameters" }
parseRuleParameters = SET [ ( ORACLE_MODULE | DIMENSION | CUBE | TABLE |
VIEW | EXTERNAL_TABLE | FUNCTION | COLLECTION ) ] "("
"parameterNameList" ")" VALUES "(" "parameterValueList" ")"
parameterNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
parameterValueList = "parameterValue" { "," "parameterValue" }
parameterValue = ( "QUOTED_STRING" )
Keywords And Parameters
parseDeriveCommand
Derives business definition objects from OWB design objects.
The quoted string following TO should be the name of a Business Definition
Module in the current project, into which the business definition objects
are derived.
Examples
OMBDERIVE TABLE 'MOD1/T1' TO BUSINESS_DEFINITION_MODULE 'IM1'
BUSINESS_AREAS ('BA1', 'BA2')
This sets up or updates business definition objects in Business Definition
Module 'IM1' for table 'T1' within Oracle module 'MOD1', creating shortcuts
in business areas BA1 and BA2.
OMBDERIVE ORACLE_MODULE 'MOD1' TO BUSINESS_DEFINITION_MODULE 'IM2'
This sets up or updates business definition objects in Business Definition
Module 'IM2' for the design objects within Oracle module 'MOD1'.
Note that deriving an Oracle Module does not derive the functions in that
module
OMBDERIVE FUNCTION 'WB_CUSTOM_TRANS/ARITHMETIC_CUSTOM' TO
BUSINESS_DEFINITION_MODULE 'IM_ORDERENTRY'
This derives the custom function ARITHMETIC_CUSTOM. Note that all custom
functions reside in module WB_CUSTOM_TRANS
OMBDERIVE FUNCTION 'WB_CUSTOM_TRANS/PACK1/CUSTOM_F1' TO
BUSINESS_DEFINITION_MODULE 'IM_ORDERENTRY'
This derives from the package PACK1 the custom function CUSTOM_F1.
OMBDERIVE COLLECTION 'C1' TO BUSINESS_DEFINITION_MODULE 'IM3'
This sets up or updates business definition objects in Business Definition
Module 'IM3' for the design objects in collection 'C1'.
To modify the global and rule derivation parameters use the following -
OMBDERIVE COLLECTION 'C1' TO BUSINESS_DEFINITION_MODULE 'EUL1'
SET (LOGLEVEL, LOGFILE) VALUES ('INFO', '/tmp/logFile')
SET DIMENSION (BUILDLEVELFOLDERS) VALUES ('TRUE')
This sets up or updates business definition objects in Business Definition
Module 'EUL1' for the design objects in collection 'C1' passing the value
'INFO' to global parameter LOGLEVEL, the value '/tmp/logFile' to the global
parameter LOGFILE and the value 'TRUE' to the Dimension rule parameter
BUILDLEVELFOLDERS.
Valid global derivation parameters are -
PRESERVEUSERCHANGES ('TRUE', 'FALSE')
LOGLEVEL ('ERROR', 'WARNING', 'INFO', 'TRACE')
LOGFILE - path and name identifying the log file location
VALIDATEBEFOREDERIVE ('TRUE', 'FALSE')
INITIALCAPITALS ('0', '1', '2')
Process business names as follows -
'0' leaves name as is,
'1' capitalizes first letter of all words in name,
'2' capitalizes first letter of first word only,
any other values are ignored
REPLACEUNDERSCORES ('TRUE', 'FALSE')
ABORTONERROR ('TRUE', 'FALSE')
Valid rule parameters for DIMENSION
FORCEBUILDDIMENSIONFOLDER ('TRUE', 'FALSE')
BUILDLEVELFOLDERS ('TRUE', 'FALSE')
DRILLPATHSONLEVELFOLDERS ('TRUE', 'FALSE')
PREFIXITEMS ('TRUE', 'FALSE')
PREFIXSEPARATOR - separator to follow prefix in business names
SORTFOLDERITEMS ('TRUE', 'FALSE')
BUILDDIMROLES ('TRUE', 'FALSE')
Valid rule parameters for CUBE
SORTFOLDERITEMS ('TRUE', 'FALSE')
Valid rule parameters for TABLE, VIEW and EXTERNAL_TABLE
BOUNDTABLESUFFIX - string to append to bound table names (default 'TAB')
DEFAULTAGGREGATE ('Detail', 'AVG', 'COUNT', 'MAX', 'MIN', 'SUM')
REMOVECOLUMNPREFIX ('TRUE', 'FALSE')
SORTFOLDERITEMS ('TRUE', 'FALSE')
Purpose
To describe an association definition.
Prerequisites
Association definition must be already exist. This command can be executed
for any association definition regardless of current context.
Syntax
parseDescribeAssociationCommand = OMBDESCRIBE ASSOCIATION_DEFINITION
"QUOTED_STRING" ( GET ( "getAssociationPropertiesClause" |
DEPENDENCY_DEFINITIONS ) | ( DEPENDENCY_DEFINITION "QUOTED_STRING" GET
"getDependencyPropertiesClause" ) )
getAssociationPropertiesClause = PROPERTIES "(" "propertyNameList" ")"
getDependencyPropertiesClause = PROPERTIES "(" "propertyNameList" ")"
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyNameClause = ( "UNQUOTED_STRING" )
Keywords And Parameters
parseDescribeAssociationCommand
Describe an association definition.
getAssociationPropertiesClause
Basic properties for ASSOCIATION_DEFINITION:
Name: DESCRIPTION
Type: STRING(4000)
Valid Values: N/A
Default: N/A
A descriptive text for this association.
Name: CLASS_1
Type: STRING(200)
Valid Values: N/A
Default: N/A
Class on one side of the association.
NAME: CLASS_2
Type: STRING(200)
Value Values: N/A
Default: N/A
Class on the other side of the association.
Name: ROLE_1
Type: STRING(200)
Valid Values: N/A
Default: N/A
Role on one side of the association.
Name: ROLE_2
Type: STRING(200)
Valid Values: N/A
Default: N/A
Role on the other side of the association.
Name: ROLE_1_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 1. Value can be positive integer.
Name: ROLE_1_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 1. Value can be positive integer or 'INFINITE'.
Name: ROLE_1_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 1.
Name: ROLE_2_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 2. Value can be positive integer.
Name: ROLE_2_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 2. Value can be positive integer or 'INFINITE'.
Name: ROLE_2_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 2.
getDependencyPropertiesClause
Basic dependency-related properties for this association:
Name: SOURCE_ROLE_ID
Type: STRING(200)
Valid Values: ROLE_1, ROLE_2
Default: If one of the ends is a OWB class, then that is the default
source. If both ends are user defined classes, then the association is
default bidirectional.
Identifies the role (end) of the association which serves as the source for
the dependency flow.
Name: BIDIRECTIONAL
Type: BOOLEAN
Valid Values: true, false
Default: If one of the ends is a OWB class, then default is false. If both
ends are user defined classes, then default is true.
Specifies whether the association is bi-directional for the dependency
flow.
propertyNameList
The list of property names.
propertyNameClause
Name of a property.
Examples
OMBDESCRIBE ASSOCIATION_DEFINITION 'UD_ASSOC4' GET PROPERTIES (CLASS_1,
CLASS_2, ROLE_1, ROLE_2)
This would retrieve the names of the two classes participating in this
association, as well as their role names.
See Also
OMBDEFINE ASSOCIATION_DEFINITION
Purpose
To describe a class definition or its property definitions.
Prerequisites
Class definition must be already exist. This command can be executed for
any class definition regardless of current context.
Syntax
parseDescribeClassCommand = OMBDESCRIBE CLASS_DEFINITION "QUOTED_STRING" (
( PROPERTY_DEFINITION "QUOTED_STRING" GET
"getPropertyDefinitionPropertiesClause" ) | ( GET ( [ USER_DEFINED |
CORE | LOGICAL | ( CONFIGURATION | PHYSICAL_CONFIGURATION ) ]
PROPERTY_DEFINITIONS ) ) | GET "getClassDefinitionPropertiesClause" |
GET CHILD_TYPES | GET ASSOCIATION_DEFINITIONS )
getPropertyDefinitionPropertiesClause = PROPERTIES "(" "propertyNameList"
")"
getClassDefinitionPropertiesClause = PROPERTIES "(" "propertyNameList" ")"
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyNameClause = ( "UNQUOTED_STRING" )
Keywords And Parameters
parseDescribeClassCommand
Describe a class definition.
QUOTED_STRING
Name of the class definition.
PROPERTY_DEFINITIONS
Get the list of property definitions for the class definition.
propertyNameList
List of the names of the properties.
propertyNameClause
Name of the property.
UNQUOTED_STRING
Name of the property.
Examples
OMBDESCRIBE CLASS_DEFINITION 'TABLE'
GET PROPERTY_DEFINITIONS
This will list all property definitions in this class definition.
OMBDESCRIBE CLASS_DEFINITION 'TABLE'
GET PROPERTIES (STEREOTYPE, IS_ABSTRACT, DESCRIPTION)
This will give the information about this class.
OMBDESCRIBE CLASS_DEFINITION 'TABLE' PROPERTY_DEFINITION 'tbl_udp'
GET PROPERTIES (TYPE, DEFAULT_VALUE, BUSINESS_NAME)
This will give the information about the property definition.
See Also
OMBDEFINE CLASS_DEFINITION, OMBREDEFINE CLASS_DEFINITION
Purpose
To describe a model. A model is usually composed of types and relationships among them. The only model currently supported is
'OWB'. Using this command you can introspect 'OWB' model to list classes
and other type definitions, association definitions and domain definitions.
Prerequisites
Must be connected to a repository.
Syntax
parseDescribeModelCommand = OMBDESCRIBE MODEL "QUOTED_STRING" GET (
CLASS_DEFINITIONS | TYPE_DEFINITIONS | DOMAIN_DEFINITIONS |
ASSOCIATION_DEFINITIONS | PRIMITIVE_TYPES )
Keywords And Parameters
parseDescribeModelCommand
Describe a model. The only model currently supported is 'OWB'.
Examples
OMBDESCRIBE MODEL 'OWB' GET CLASS_DEFINITIONS
This would retrieve the names of all classes in 'OWB' model, including the
user defined ones.
OMBDESCRIBE MODEL 'OWB' GET ASSOCIATION_DEFINITIONS
This would retrieve the names of the user defined associations in 'OWB'
model.
Purpose
To disconnect from a OWB repository or the named Control Center.
Prerequisites
Currently need to be connected to a OWB repository or the named Control
Center.
Syntax
parseDisconnectCommand = ( ( OMBDISCONNECT | OMBDISC ) [ CONTROL_CENTER ]
)
Keywords And Parameters
parseDisconnectCommand
Specify disconnect command.
Examples
OMBDISCONNECT
See Also
OMBCONNECT
Purpose
To disconnect from a OWB repository or the named Control Center.
Prerequisites
Currently need to be connected to a OWB repository or the named Control
Center.
Syntax
parseDisconnectCommand = ( ( OMBDISCONNECT | OMBDISC ) [ CONTROL_CENTER ]
)
Keywords And Parameters
parseDisconnectCommand
Specify disconnect command.
Examples
OMBDISCONNECT
See Also
OMBCONNECT
Purpose
To disconnect from a OWB repository or the named Control Center.
Prerequisites
Currently need to be connected to a OWB repository or the named Control
Center.
Syntax
parseDisconnectCommand = ( ( OMBDISCONNECT | OMBDISC ) [ CONTROL_CENTER ]
)
Keywords And Parameters
parseDisconnectCommand
Specify disconnect command.
Examples
OMBDISCONNECT
See Also
OMBCONNECT
Purpose
To disconnect from a OWB repository or the named Control Center.
Prerequisites
Currently need to be connected to a OWB repository or the named Control
Center.
Syntax
parseDisconnectCommand = ( ( OMBDISCONNECT | OMBDISC ) [ CONTROL_CENTER ]
)
Keywords And Parameters
parseDisconnectCommand
Specify disconnect command.
Examples
OMBDISCONNECT
See Also
OMBCONNECT
Purpose
Displays the current connection mode to the repository. Returns either SINGLE_USER_MODE (that is exclusive) or
MULTIPLE_USER_MODE.
Prerequisites
Must be connected to an OWB repository. If not already connected, use
OMBCONNECT first.
Syntax
parseDisplayModeCommand = ( OMBDISPLAYCURRENTMODE | OMBDCM )
Keywords And Parameters
parseDisplayModeCommand
Specify display mode command.
Examples
OMBDISPLAYCURRENTMODE
See Also
OMBSWITCHMODE, OMBCONNECT, OMBSAVE, OMBREVERT
Purpose
This command will list the values for all set OMBPlus environment variables. OMBPlus environment variables are regular Tcl variables, so they
can be set using standard Tcl "set" command, and unset using standard
"unset" command.
Prerequisites
None.
Syntax
parseEnvironmentCommand = OMBENV
Keywords And Parameters
parseEnvironmentCommand
Specify environment command. The environment variables recognized by
OMBPlus are:
OMBPROMPT if set, will display the current context as the prompt
OMBLOG if set with a file name, will log the output to that file
OMBTIMER if set, will display the time taken by the executed command.
Note that the elapsed time will be appended to the command result,
therefore the user should not set this variable when the result of the
command is expected to be processed
OMBCONTINUE_ON_ERROR if set, will continue the execution of the
script, even when some OMB commands fail. Note that if this variable is
set, OMB commands no longer return Tcl errors, so any enclosing 'catch'
command will not be effective.
Examples
OMBENV
Purpose
Exports current metadata, metadata definitions, or snapshot metadata to a metadata loader file.
Prerequisites
Connection must be established to repository to be exported from.
Syntax
ExportCommand = OMBEXPORT ( ( [ TO ] MDL_FILE "QUOTED_STRING" [ FROM ] [
"projectClause" ] [ "componentsClause" ] [ ( "classesClause" |
ALL_CLASS_DEFINITIONS ) ] [ WITH ] [ "dependeeDepthClause" ] [
"includeGrantsClause" ] [ "includeCMIDefsClause" ] [
"useFieldSeparatorClause" ] [ "controlFileClause" ] [
"includeUserDefsClause" ] [ "supportedLangsClause" ] [
"outputLogClause" ] ) )
projectClause = PROJECT "QUOTED_STRING"
componentsClause = COMPONENTS "(" "componentsList" ")"
classesClause = CLASS_DEFINITIONS "(" "QUOTED_STRING" { ","
"QUOTED_STRING" } ")"
dependeeDepthClause = DEPENDEE_DEPTH ( MAX | "INTEGER_LITERAL" )
includeGrantsClause = INCLUDE_GRANTS
includeCMIDefsClause = INCLUDE_CMI_DEFINITIONS
useFieldSeparatorClause = [ USE ] FIELD_SEPARATOR "UNQUOTED_STRING"
controlFileClause = CONTROL_FILE "QUOTED_STRING"
includeUserDefsClause = INCLUDE_USER_DEFINITIONS
supportedLangsClause = SUPPORTED_LANGUAGES "(" "supportedLangsList" ")"
outputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
componentsList = "newObjectTypeValue" "QUOTED_STRING" { ","
"newObjectTypeValue" "QUOTED_STRING" }
supportedLangsList = "QUOTED_STRING" { "," "QUOTED_STRING" }
newObjectTypeValue = "UNQUOTED_STRING"
Keywords And Parameters
ExportCommand
Export metadata and optionally metadata definitions to a file.
QUOTED_STRING
Enclose the name of the export metadata file in single quotes.
projectClause
Specify the project to be exported.
QUOTED_STRING
Enclose the name of the project to be exported in single quotes.
componentsClause
List components to be exported.
dependeeDepthClause
Specify how many levels of dependent objects should be exported for
components specified for export. Use MAX for all dependents, 0 for no
dependents, 1 for one level of dependents. The default is 0.
includeGrantsClause
Use to request that security related metadata be included in the export.
includeCMIDefsClause
Use to request that related CMI Definitions for CMI Modules be included in
the export.
useFieldSeparatorClause
Do not use this option. It is an obsolete option that was used to specify
character to be used as the field separator in the old metadata file
format.
UNQUOTED_STRING
Do not use this option. Obsolete metadata file field separator for old MDL
file format. Use BAR or CARAT. The default is BAR.
controlFileClause
Specify a control file with export options not directly supported by
OMBEXPORT command.
QUOTED_STRING
Enclose the control file name in single quotes.
includeUserDefsClause
Use to request that metadata definitions be included in the export.
supportedLangsClause
List supported languages to be exported.
outputLogClause
Export log file for export messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
componentsList
Comma separated list of components to be exported.
QUOTED_STRING
Enclose in single quotes the absolute or relative path name of an object
(for example 'MODULE_X/TABLE_Y').
supportedLangsList
Comma separated list of supported languages to be exported.
QUOTED_STRING
Language name or ISO id of supported language (for example 'German' or 'de_DE').
Examples
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT' OUTPUT
LOG TO 'd:/mdl/exp1.log'
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT' WITH
DEPENDEE_DEPTH MAX OUTPUT LOG TO 'd:/mdl/exp1.log'
OMBEXPORT MDL_FILE 'd:/mdl/exp1.mdl' PROJECT 'MY_PROJECT' COMPONENTS
(ORACLE_MODULE 'DW1', TABLE 'EMP', VIEW 'DEPT_VW') OUTPUT LOG
'd:/mdl/exp1.log'
OMBEXPORT MDL_FILE 'd:/mdl/snap1.mdl' COMPONENTS (SNAPSHOT
'MY_PROJECT_SNAP1') OUTPUT LOG 'd:/mdl/snap1.log'
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT'
INCLUDE_USER_DEFINITIONS OUTPUT LOG TO 'd:/mdl/exp1.log'
See Also
OMBIMPORT
Purpose
Exports current metadata, metadata definitions, or snapshot metadata to a metadata loader file.
Prerequisites
Connection must be established to repository to be exported from.
Syntax
ExportCommand = OMBEXPORT ( ( [ TO ] MDL_FILE "QUOTED_STRING" [ FROM ] [
"projectClause" ] [ "componentsClause" ] [ ( "classesClause" |
ALL_CLASS_DEFINITIONS ) ] [ WITH ] [ "dependeeDepthClause" ] [
"includeGrantsClause" ] [ "includeCMIDefsClause" ] [
"useFieldSeparatorClause" ] [ "controlFileClause" ] [
"includeUserDefsClause" ] [ "supportedLangsClause" ] [
"outputLogClause" ] ) )
projectClause = PROJECT "QUOTED_STRING"
componentsClause = COMPONENTS "(" "componentsList" ")"
classesClause = CLASS_DEFINITIONS "(" "QUOTED_STRING" { ","
"QUOTED_STRING" } ")"
dependeeDepthClause = DEPENDEE_DEPTH ( MAX | "INTEGER_LITERAL" )
includeGrantsClause = INCLUDE_GRANTS
includeCMIDefsClause = INCLUDE_CMI_DEFINITIONS
useFieldSeparatorClause = [ USE ] FIELD_SEPARATOR "UNQUOTED_STRING"
controlFileClause = CONTROL_FILE "QUOTED_STRING"
includeUserDefsClause = INCLUDE_USER_DEFINITIONS
supportedLangsClause = SUPPORTED_LANGUAGES "(" "supportedLangsList" ")"
outputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
componentsList = "newObjectTypeValue" "QUOTED_STRING" { ","
"newObjectTypeValue" "QUOTED_STRING" }
supportedLangsList = "QUOTED_STRING" { "," "QUOTED_STRING" }
newObjectTypeValue = "UNQUOTED_STRING"
Keywords And Parameters
ExportCommand
Export metadata and optionally metadata definitions to a file.
QUOTED_STRING
Enclose the name of the export metadata file in single quotes.
projectClause
Specify the project to be exported.
QUOTED_STRING
Enclose the name of the project to be exported in single quotes.
componentsClause
List components to be exported.
dependeeDepthClause
Specify how many levels of dependent objects should be exported for
components specified for export. Use MAX for all dependents, 0 for no
dependents, 1 for one level of dependents. The default is 0.
includeGrantsClause
Use to request that security related metadata be included in the export.
includeCMIDefsClause
Use to request that related CMI Definitions for CMI Modules be included in
the export.
useFieldSeparatorClause
Do not use this option. It is an obsolete option that was used to specify
character to be used as the field separator in the old metadata file
format.
UNQUOTED_STRING
Do not use this option. Obsolete metadata file field separator for old MDL
file format. Use BAR or CARAT. The default is BAR.
controlFileClause
Specify a control file with export options not directly supported by
OMBEXPORT command.
QUOTED_STRING
Enclose the control file name in single quotes.
includeUserDefsClause
Use to request that metadata definitions be included in the export.
supportedLangsClause
List supported languages to be exported.
outputLogClause
Export log file for export messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
componentsList
Comma separated list of components to be exported.
QUOTED_STRING
Enclose in single quotes the absolute or relative path name of an object
(for example 'MODULE_X/TABLE_Y').
supportedLangsList
Comma separated list of supported languages to be exported.
QUOTED_STRING
Language name or ISO id of supported language (for example 'German' or 'de_DE').
Examples
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT' OUTPUT
LOG TO 'd:/mdl/exp1.log'
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT' WITH
DEPENDEE_DEPTH MAX OUTPUT LOG TO 'd:/mdl/exp1.log'
OMBEXPORT MDL_FILE 'd:/mdl/exp1.mdl' PROJECT 'MY_PROJECT' COMPONENTS
(ORACLE_MODULE 'DW1', TABLE 'EMP', VIEW 'DEPT_VW') OUTPUT LOG
'd:/mdl/exp1.log'
OMBEXPORT MDL_FILE 'd:/mdl/snap1.mdl' COMPONENTS (SNAPSHOT
'MY_PROJECT_SNAP1') OUTPUT LOG 'd:/mdl/snap1.log'
OMBEXPORT TO MDL_FILE 'd:/mdl/exp1.mdl' FROM PROJECT 'MY_PROJECT'
INCLUDE_USER_DEFINITIONS OUTPUT LOG TO 'd:/mdl/exp1.log'
See Also
OMBIMPORT MDL_FILE
Purpose
To change the default object privilege setting property of a user, basically it will grant a list of default object
privileges to a list of users or roles. These object privileges will really
be granted to the specified user or role on the new objects whenever the
owner creates them.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseGrantDefObjPrivCommand = OMBGRANT DEFAULT ( OBJ_PRIV |
OBJECT_PRIVILEGE ) "objPrivNameList" TO ( USER "userOrRoleNameList" |
ROLE "userOrRoleNameList" ) [ FOR USER "QUOTED_STRING" ]
objPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseGrantDefObjPrivCommand
This clause change the default object privilege setting property of a user
through granting a list of default object privileges to a list of users or
roles.
objPrivNameList
Object privileges. Valid object privileges are: READ, COMPILE, EDIT,
FULL_CONTROL.
Examples
OMBGRANT DEFAULT OBJ_PRIV EDIT TO ROLE 'DEVELOPMENT_ROLE'
the current login user grants default object privilege EDIT to role
DEVELOPMENT_ROLE, thus whenever the current login user creates an object,
the role DEVELOPMENT_ROLE will be granted EDIT privilege on that object.
OMBGRANT DEFAULT OBJ_PRIV EDIT TO ROLE 'DEVELOPMENT_ROLE' FOR USER
'USER1'
the current user grants default object privilege EDIT to role
DEVELOPMENT_ROLE on behalf of user USER1, thus whenever the user USER1
creates an object, the role DEVELOPMENT_ROLE will be granted EDIT privilege
on that object.Note if the current login user does not change the default
object privilege setting for himself, the FOR USER statement is required.
See Also
OMBREVOKE DEFAULT OBJ_PRIV, OMBLIST DEFAULT OBJ_PRIVS
Purpose
To grant a list of object privileges on the specified objects to a list of users or roles.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseGrantObjPrivCommand = OMBGRANT ( OBJ_PRIV | OBJECT_PRIVILEGE )
"objPrivNameList" ON "UNQUOTED_STRING" "QUOTED_STRING" [ CASCADE ] TO
( USER "userOrRoleNameList" | ROLE "userOrRoleNameList" )
objPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseGrantObjPrivCommand
This clause grants a list of object privileges on the specified objects to
a list of users or roles.
UNQUOTED_STRING
The type of the objects to be listed.Valid object types are: PROJECT,
ORACLE_MODULE, FLAT_FILE_MODULE, PROCESS_FLOW_MODULE, SAP_MODULE,
BUSINESS_DEFINITION_MODULE, BUSINESS_PRESENTATION_MODULE,
TRANSFORMATION_MODULE, PACKAGE, ADVANCED_QUEUE, BUSINESS_AREA, COLLECTION,
CONNECTOR, CUBE, DIMENSION, EXTERNAL_TABLE, FLAT_FILE, FUNCTION,
REGISTERED_FUNCTION, MAPPING, MATERIALIZED_VIEW, OBJECT_TYPE, PROCEDURE,
ITEM_FOLDER, DRILL_PATH, DRILLS_TO_DETAIL, ALTERNATIVE_SORT_ORDER,
LISTS_OF_VALUE, PRESENTATION_TEMPLATE, SEQUENCE, TABLE, PROCESS_FLOW,
PROCESS_FLOW_PACKAGE, LOCATION, CONTROL_CENTER, CONFIGURATION, DEPLOYMENT,
VIEW.
QUOTED_STRING
an object name or a regular expression refers to a list of objects whose
name matches the regular expression.
CASCADE
grant the specified object privileges on a folder object and all its child
objects cascade down. Note: if CASCADE is used, the string used to specify
the object can only refer to one object and not be a regular experssion .
objPrivNameList
Object privileges. Valid object privileges are: READ, COMPILE, EDIT,
FULL_CONTROL.
Examples
OMBGRANT OBJ_PRIV EDIT ON ORACLE_MODULE '/MY_PROJECT/WH' TO USER 'USER1'
will grant EDIT on module WH to user USER1
OMBGRANT OBJ_PRIV EDIT ON PROJECT 'MY_PROJECT' CASCADE TO ROLE 'EVERYONE'
will grant object privilege EDIT to role EVERYONE on project MY_PROJECT
and all its child objects cascade.
OMBGRANT OBJ_PRIV READ ON TABLE '/MY_PROJECT/WH/EMP*' TO USER 'USER1'
will grant READ to user USER1 on all tables under module /MY_PROJECT/WH
whose names match regular expression EMP*.
See Also
OMBREVOKE OBJ_PRIV, OMBLIST OBJ_PRIVS
Purpose
To grant a list of Warehouse Builder roles to a list of Warehouse Builder users. Note role cannot be granted to another role.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseGrantRoleCommand = OMBGRANT ROLE "userOrRoleNameList" TO USER
"userOrRoleNameList"
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseGrantRoleCommand
This clause grants a list of Warehouse Builder roles to a list of Warehouse
Builder users.
Examples
OMBGRANT ROLE 'DEV', 'QA' TO USER 'USER1' 'USER2'
will grant Warehouse Builder role 'DEV'and 'QA' to user 'USER1' and
'USER2'
See Also
OMBREVOKE ROLE, OMBLIST ROLES
Purpose
To grant a list of system privileges to a list of users or roles.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseGrantSysPrivCommand = OMBGRANT ( SYS_PRIV | SYSTEM_PRIVILEGE )
"sysPrivNameList" TO ( USER "userOrRoleNameList" | ROLE
"userOrRoleNameList" )
sysPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseGrantSysPrivCommand
This clause grants a list of system privileges to a list of users or roles.
sysPrivNameList
List of system privileges. Valid system privileges are:CREATE_PROJECT,
CREATE_MIVDEFINITION,CREATE_EXTENSIONMODEL, CONTROL_CENTER_ADMIN,
CONTROL_CENTER_DEPLOY, CONTROL_CENTER_EXECUTE, CREATE_SNAPSHOT
Examples
OMBGRANT SYS_PRIV 'CREATE_SNAPSHOT' TO USER 'USER1', 'USER2'
will grant system privilege CREATE_SNAPSHOT to user 'USER1' and 'USER2'
OMBGRANT SYS_PRIV 'CREATE_PROJECT' TO ROLE 'DEVELOPMENT_ROLE'
will grant system privilege 'CREATE_PROJECT' to role 'DEVELOPMENT_ROLE'.
See Also
OMBREVOKE SYS_PRIV, OMBLIST SYS_PRIVS
Purpose
Displays the manual page for OMB commands.
Prerequisites
None.
Syntax
parseHelpCommand = OMBHELP [ HELPID ] [ DETAIL ]
Keywords And Parameters
parseHelpCommand
Specifies the command for which to invoke help.
HELPID
An unquoted string that represents either the command name and the optional
additional parameter on the command.
DETAIL
Use this keyword to display the manual page in long format.
Examples
The following statement shows the manual page for OMBCREATE TABLE in short
format
OMBHELP OMBCREATE TABLE
To show the manual page in long format (including parameters and example
sections), use the DETAIL keyword, like this:
OMBHELP OMBCREATE TABLE DETAIL
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 | ITEM_FOLDER | LIST_OF_VALUES | MATERIALIZED_VIEW |
NESTED_TABLE | OBJECT_TYPE | PLUGGABLE_MAPPING | PRESENTATION_TEMPLATE
| 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
Keywords And 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.
Examples
This command will fetch the impact of a change on table 'EMA01_SRC':
OMBIMPACT DEPENDENCYTYPE 'DATAFLOW' TABLE 'EMA01_SRC'
The result of this command could be for example:
{{TABLE /MY_PROJECT/WH_EMA01/EMA01_SRC} {MAPPING
/MY_PROJECT/WH_EMA01/EMA01} {TABLE /MY_PROJECT/WH_EMA01/EMA01_TGT}}.
The following command would fetch the impact of a column change:
OMBIMPACT DEPENDENCYTYPE 'DATAFLOW' TABLE 'EMA01_SRC' COLUMN 'INTEREST'
Another example would fetch the impact of the field belonging to a record
in a file:
OMBIMPACT DEPENDENCYTYPE 'DATAFLOW' FLAT_FILE 'FILE_MULTI' RECORD 'REC1'
FIELD 'DS'
Purpose
Imports metadata from a Metadata Loader file, or from the default metadata location specified in the module.
Please refer to OMBHELP OMBIMPORT MDL_FILE or OMBHELP OMBIMPORT
METADATA_LOCATION.
Prerequisites
Must be connected to the repository where the import is to be performed.
Syntax
ImportCommand = OMBIMPORT [ FROM ] ( "mdlImportCommand" |
"oracleDBImportCommand" )
mdlImportCommand = ( MDL_FILE "QUOTED_STRING" [ "noUpgradeClause" ] [
"includeUserDefsClause" ] [ "useModeClause" | "asSnapshotClause" ] [
"matchByClause" ] [ "includeGrantsClause" ] [ "includeCMIDefsClause" ]
[ "controlFileClause" ] [ "supportedLangsClause" ] [
"allowDiffBaseLangClause" ] [ "outputLogClause" ] )
oracleDBImportCommand = ( METADATA_LOCATION [ FOR ] IMPORT_ACTION_PLAN
"QUOTED_STRING" [ "setImportOptions" ] )
noUpgradeClause = NO_UPGRADE
includeUserDefsClause = INCLUDE_USER_DEFINITIONS
useModeClause = USE "modeValue"
asSnapshotClause = AS SNAPSHOT "QUOTED_STRING"
matchByClause = MATCH_BY "matchByValue"
includeGrantsClause = INCLUDE_GRANTS
includeCMIDefsClause = INCLUDE_CMI_DEFINITIONS
controlFileClause = CONTROL_FILE "QUOTED_STRING"
supportedLangsClause = SUPPORTED_LANGUAGES "(" "supportedLangsList" ")"
allowDiffBaseLangClause = ALLOW_DIFFERENT_BASE_LANGUAGE
outputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
setImportOptions = SET OPTIONS "(" "optionNameList" ")" VALUES "("
"optionValueList" ")"
modeValue = ( CREATE_MODE | REPLACE_MODE | UPDATE_MODE | MERGE_MODE |
TRANSLATION_DIRECT_LOAD_MODE )
matchByValue = ( UNIVERSAL_IDENTIFIER | NAMES )
supportedLangsList = "QUOTED_STRING" { "," "QUOTED_STRING" }
optionNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
optionValueList = "optionValue" { "," "optionValue" }
optionValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
ImportCommand
Import metadata from a Metadata Loader file, or from the default metadata
location specified in the module.
mdlImportCommand
Import metadata from a file.
oracleDBImportCommand
To import from the default metadata location based on the import action
plan.
QUOTED_STRING
The name of the transient action plan.
noUpgradeClause
Specify that MDL files that are not compatible with current repository
version should not be automatically upgraded. The default is to
automatically upgrade unless this clause is used.
includeUserDefsClause
Use to request that any metadata definitions in the MDL file be imported.
useModeClause
Specify import mode for importing metadata file.
asSnapshotClause
Specify a new snapshot name into which the contents of the MDL file are to
be imported. Use this option to import old archive files as snapshots.
QUOTED_STRING
Enclose the new snapshot name in single quotes.
matchByClause
Specify whether import should search for already existing objects using
universal identifiers or physical names.
includeGrantsClause
Use to request that security related metadata be imported.
includeCMIDefsClause
Use to request that related CMI Definitions for CMI Modules be imported.
controlFileClause
Specify a control file with import options not directly supported by the
OMBIMPORT command.
QUOTED_STRING
Enclose the control file name in single quotes.
supportedLangsClause
List supported languages to be imported.
allowDiffBaseLangClause
Use to specify that MDL files with a different base langugae than that of
the import target repository can be imported.
outputLogClause
Log file for import messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
setImportOptions
Currently no import options are available to be set.
modeValue
Import mode. Use CREATE_MODE, REPLACE_MODE, UPDATE_MODE, MERGE_MODE, or
TRANSLATION_DIRECT_LOAD_MODE. The default is CREATE_MODE.
CREATE_MODE: create new metadata only
REPLACE_MODE: replace existing objects only
UPDATE_MODE: replace existing objects and create new metadata
MERGE_MODE: merge existing objects and create new metadata
TRANSLATION_DIRECT_LOAD_MODE: import language translation metadata only
matchByValue
Use UNIVERSAL_IDENTIFIER or NAMES. The default is UNIVERSAL_IDENTIFIER.
supportedLangsList
Comma separated list of supported languages to be imported.
QUOTED_STRING
Language name or ISO id of supported language (for example 'German' or 'de_DE').
Examples
OMBIMPORT FROM MDL_FILE 'd:/mdl/exp1.mdl' OUTPUT LOG TO
'd:/mdl/exp1_imp.log'
OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'PLAN1'
See Also
OMBIMPORT MDL_FILE, OMBIMPORT METADATA_LOCATION
Purpose
Imports metadata and metadata definitions from a Metadata Loader file.
Prerequisites
Must be connected to the repository where the import is to be performed.
Syntax
mdlImportCommand = ( MDL_FILE "QUOTED_STRING" [ "noUpgradeClause" ] [
"includeUserDefsClause" ] [ "useModeClause" | "asSnapshotClause" ] [
"matchByClause" ] [ "includeGrantsClause" ] [ "includeCMIDefsClause" ]
[ "controlFileClause" ] [ "supportedLangsClause" ] [
"allowDiffBaseLangClause" ] [ "outputLogClause" ] )
noUpgradeClause = NO_UPGRADE
includeUserDefsClause = INCLUDE_USER_DEFINITIONS
useModeClause = USE "modeValue"
asSnapshotClause = AS SNAPSHOT "QUOTED_STRING"
matchByClause = MATCH_BY "matchByValue"
includeGrantsClause = INCLUDE_GRANTS
includeCMIDefsClause = INCLUDE_CMI_DEFINITIONS
controlFileClause = CONTROL_FILE "QUOTED_STRING"
supportedLangsClause = SUPPORTED_LANGUAGES "(" "supportedLangsList" ")"
allowDiffBaseLangClause = ALLOW_DIFFERENT_BASE_LANGUAGE
outputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
modeValue = ( CREATE_MODE | REPLACE_MODE | UPDATE_MODE | MERGE_MODE |
TRANSLATION_DIRECT_LOAD_MODE )
matchByValue = ( UNIVERSAL_IDENTIFIER | NAMES )
supportedLangsList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
mdlImportCommand
Import metadata from a file.
noUpgradeClause
Specify that MDL files that are not compatible with current repository
version should not be automatically upgraded. The default is to
automatically upgrade unless this clause is used.
includeUserDefsClause
Use to request that any metadata definitions in the MDL file be imported.
useModeClause
Specify import mode for importing metadata file.
asSnapshotClause
Specify a new snapshot name into which the contents of the MDL file are to
be imported. Use this option to import old archive files as snapshots.
QUOTED_STRING
Enclose the new snapshot name in single quotes.
matchByClause
Specify whether import should search for already existing objects using
universal identifiers or physical names.
includeGrantsClause
Use to request that security related metadata be imported.
includeCMIDefsClause
Use to request that related CMI Definitions for CMI Modules be imported.
controlFileClause
Specify a control file with import options not directly supported by the
OMBIMPORT command.
QUOTED_STRING
Enclose the control file name in single quotes.
supportedLangsClause
List supported languages to be imported.
allowDiffBaseLangClause
Use to specify that MDL files with a different base langugae than that of
the import target repository can be imported.
outputLogClause
Log file for import messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
modeValue
Import mode. Use CREATE_MODE, REPLACE_MODE, UPDATE_MODE, MERGE_MODE, or
TRANSLATION_DIRECT_LOAD_MODE. The default is CREATE_MODE.
CREATE_MODE: create new metadata only
REPLACE_MODE: replace existing objects only
UPDATE_MODE: replace existing objects and create new metadata
MERGE_MODE: merge existing objects and create new metadata
TRANSLATION_DIRECT_LOAD_MODE: import language translation metadata only
matchByValue
Use UNIVERSAL_IDENTIFIER or NAMES. The default is UNIVERSAL_IDENTIFIER.
supportedLangsList
Comma separated list of supported languages to be imported.
QUOTED_STRING
Language name or ISO id of supported language (for example 'German' or 'de_DE').
Examples
OMBIMPORT FROM MDL_FILE 'd:/mdl/exp1.mdl' OUTPUT LOG TO
'd:/mdl/exp1_imp.log'
OMBIMPORT MDL_FILE 'd:/mdl/exp1.mdl' USE UPDATE_MODE OUTPUT LOG TO
'd:/mdl/exp1_imp.log'
See Also
OMBEXPORT MDL_FILE
Purpose
Import metadata from the default metadata location specified in the module. Currently we only support
tables/views/sequences for Oracle/Gateway/SAP/MIV modules.
Prerequisites
Must be connected to the repository where the import is to be performed.
Syntax
oracleDBImportCommand = ( METADATA_LOCATION [ FOR ] IMPORT_ACTION_PLAN
"QUOTED_STRING" [ "setImportOptions" ] )
setImportOptions = SET OPTIONS "(" "optionNameList" ")" VALUES "("
"optionValueList" ")"
optionNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
optionValueList = "optionValue" { "," "optionValue" }
optionValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
oracleDBImportCommand
To import from the default metadata location based on the import action
plan.
QUOTED_STRING
The name of the transient action plan.
setImportOptions
Currently no import options are available to be set.
Examples
OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'PLAN1'
This command will carry out the import actions specified in import action
plan PLAN1.
See Also
OMBCREATE TRANSIENT IMPORT_ACTION_PLAN
Purpose
Register RAC instance (only for RAC 's second instance onwards).
Prerequisites
This command should be run locally on the database server.
Syntax
parseRegisterRACCommand = OMBINSTALL OWB_RAC [ OWBRT_SYS_PASSWORD
"QUOTED_STRING" ] USING CREDENTIAL "UNQUOTED_STRING" [
NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseRegisterRACCommand
Specify an OMBINSTALL OWB_RAC command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name OR specify the user name and
password using this format username/password.
Examples
1. OMBINSTALL OWB_RAC USING CREDENTIAL sys/sys@localhost:1521:orcl92
This registers a RAC instance.
Purpose
Install OWB repository.
Prerequisites
To install OWB repository, within the same OMBPlus session, no other OMB
commands should be issued before or after the OMBINSTALL OWB_REPOSITORY
command. The value of OWB_SERVER_HOME_CHECK_FLAG can be set to either TRUE
or FALSE. If OWB_SERVER_HOME_CHECK_FLAG is set to TRUE,
OWB_SERVER_ORACLE_HOME must be provided as a valid path which OWB software
is installed.
Syntax
parseInstallOWBRepositoryCommand = OMBINSTALL OWB_REPOSITORY
"UNQUOTED_STRING" [ NAS_PORT "QUOTED_STRING" ] [ DATA_TABLESPACE
"QUOTED_STRING" ] [ INDEX_TABLESPACE "QUOTED_STRING" ] [
TEMPORARY_TABLESPACE "QUOTED_STRING" ] [ SNAPSHOT_TABLESPACE
"QUOTED_STRING" ] [ BASE_LANGUAGE "QUOTED_STRING" ] [
SUPPORTED_LANGUAGES "(" "QUOTED_STRING" { "," "QUOTED_STRING" } ")" ]
[ OWB_SERVER_ORACLE_HOME "QUOTED_STRING" ] [
OWB_SERVER_HOME_CHECK_FLAG "UNQUOTED_STRING" ] [ OWBRT_SYS_PASSWORD
"QUOTED_STRING" ] USING CREDENTIAL "UNQUOTED_STRING" [
NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseInstallOWBRepositoryCommand
Specify an OMBINSTALL OWB_REPOSITORY command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name, OR specify the user name and
password pair using this format: username/password.
QUOTED_STRING
Specify the tablespace name, NAS port number or language name.
Examples
1. OMBINSTALL OWB_REPOSITORY h_rep1/h NAS_PORT '4040' DATA_TABLESPACE
'USERS' INDEX_TABLESPACE 'INDX' TEMPORARY_TABLESPACE 'TEMP'
SNAPSHOT_TABLESPACE 'USERS' BASE_LANGUAGE 'AMERICAN ENGLISH'
SUPPORTED_LANGUAGES ('ARABIC', 'ASSAMESE', 'CANADIAN FRENCH', 'SIMPLIFIED
CHINESE') USING CREDENTIAL sys/sys@localhost:1521:orcl92
This creates an OWB repository using the nondefault NAS port, nondefault
tablespaces and nondefault supporting languages.
2. OMBINSTALL OWB_REPOSITORY h_rep2/h NAS_PORT '4040' DATA_TABLESPACE
'USERS' INDEX_TABLESPACE 'INDX' TEMPORARY_TABLESPACE 'TEMP'
SNAPSHOT_TABLESPACE 'USERS' USING CREDENTIAL sys/sys@localhost:1521:orcl92
This creates an OWB repository using the nondefault NAS port, nondefault
tablespaces and default supporting languages.
3. OMBINSTALL OWB_REPOSITORY h_rep3/h NAS_PORT '4040' USING CREDENTIAL
sys/sys@localhost:1521:orcl92
This creates an OWB repository using the nondefault NAS port, default
tablespaces and default supporting languages.
4. OMBINSTALL OWB_REPOSITORY h_rep4/h USING CREDENTIAL
sys/sys@localhost:1521:orcl92
This creates an OWB repository using the default NAS port, default
tablespaces and default supporting languages.
Purpose
Create or install an OWB target user.
Prerequisites
OWB REPOSITORY must exist on the database server.
Syntax
parseInstallTargetUserCommand = OMBINSTALL OWB_TARGET_USER
"UNQUOTED_STRING" [ DATA_TABLESPACE "QUOTED_STRING" ] [
INDEX_TABLESPACE "QUOTED_STRING" ] [ TEMPORARY_TABLESPACE
"QUOTED_STRING" ] USING OWB_REPOSITORY "UNQUOTED_STRING" USING
CREDENTIAL "UNQUOTED_STRING" [ NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseInstallTargetUserCommand
Specify an OMBINSTALL OWB_TARGET_USER command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name OR specify the user name and
password using this format username/password.
QUOTED_STRING
Specify the tablespace name.
Examples
1. OMBINSTALL OWB_TARGET_USER h_tu2/h USING OWB_REPOSITORY h_rep1/h USING
CREDENTIAL sys/sys@localhost:1521:orcl92
This creates a target user using the default tablespaces.
2. OMBINSTALL OWB_TARGET_USER h_tu1/h DATA_TABLESPACE 'USERS'
INDEX_TABLESPACE 'INDX' TEMPORARY_TABLESPACE 'TEMP' USING OWB_REPOSITORY
h_rep1/h USING CREDENTIAL sys/sys@localhost:1521:orcl92
This creates a target user using the nondefault tablespaces.
Purpose
To fetch the data lineage.
Prerequisites
In the context of an object's parent module.
Syntax
parseLineageCommand = OMBLINEAGE 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 | ITEM_FOLDER | LIST_OF_VALUES | MATERIALIZED_VIEW |
NESTED_TABLE | OBJECT_TYPE | PLUGGABLE_MAPPING | PRESENTATION_TEMPLATE
| 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
Keywords And Parameters
parseLineageCommand
Specify OMBLINEAGE command.
parseType
The type of lineage. Allowable values are: DATAFLOW or DEPLOYMENT.
parseFCO
The object whose lineage needs to be fetched.
parseSCO
The second class object whose lineage 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 lineage.
Examples
This command will fetch the lineage of table 'EMA01_TGT':
OMBLINEAGE DEPENDENCYTYPE 'DATAFLOW' TABLE 'EMA01_TGT'
The result of this command could be for example:
{{TABLE /MY_PROJECT/WH_EMA01/EMA01_SRC} {MAPPING
/MY_PROJECT/WH_EMA01/EMA01} {TABLE /MY_PROJECT/WH_EMA01/EMA01_TGT}}
{{CONFIGURATION /MY_PROJECT/MY_PROJECT/DEFAULT_CONFIGURATION} {TABLE
/MY_PROJECT/WH_EMA01/EMA01_TGT}}
The following command would fetch the lineage of a column:
OMBLINEAGE DEPENDENCYTYPE 'DATAFLOW' TABLE 'EMA01_TGT' COLUMN 'TOTAL'
Another example would fetch the lineage of a level attribute belonging to a
level in a dimension:
OMBLINEAGE DEPENDENCYTYPE 'DATAFLOW' DIMENSION 'GEOGRAPHY' LEVEL 'CITY'
LEVEL_ATTRIBUTE 'CTY_KEY'
Purpose
This command lists the specified Warehouse Builder objects under the current folder. You can also provide a regular expression to list
objects in a different folder, or to list objects with names matching a
pattern, or both. Before displaying the objects, this command first refreshes the
object list from the repository. This means that the list of objects
returned also reflects any additions or deletions by other users.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseListCommand = "listActionPlans" | "listGeneral" listActionPlans = OMBLIST DEPLOYMENT_ACTION_PLANS [ "QUOTED_STRING" ] listGeneral = OMBLIST "UNQUOTED_STRING" [ "QUOTED_STRING" ]
Keywords And Parameters
parseListCommand
Specify the list command.
listActionPlans
Deployment action plans are listed.
listGeneral
OWB objects of the specified type are listed.
UNQUOTED_STRING
The type (plural) of the objects to be listed. Valid object types are:
ACTIVITY_TEMPLATES, ACTIVITY_TEMPLATE_FOLDERS, ADVANCED_QUEUES,
ALTERNATIVE_SORT_ORDERS, BUSINESS_AREAS, BUSINESS_DEFINITION_MODULES,
BUSINESS_PRESENTATION_MODULES, CALENDARS, CALENDAR_MODULES,
CMI_DEFINITIONS, CMI_MODULES, COLLECTIONS, CONFIGURATIONS, CONNECTORS,
CONTROL_CENTERS, CUBES, DATA_AUDITORS, DATA_PROFILES, DATA_RULES,
DATA_RULE_MODULES, DEPLOYMENTS, DEPLOYMENT_ACTION_PLANS, DIMENSIONS,
DRILL_PATHS, DRILLS_TO_DETAIL, EXPERTS, EXPERT_MODULES, EXTERNAL_TABLES,
FLAT_FILES, FLAT_FILE_MODULES, FUNCTIONS, GATEWAY_MODULES, ICONSETS,
ITEM_FOLDERS, LISTS_OF_VALUES, LOCATIONS, MAPPINGS, MATERIALIZED_VIEWS,
NESTED_TABLES, OBJECT_TYPES, ORACLE_MODULES, PACKAGES, PLSQL_RECORD_TYPES,
PLSQL_REF_CURSOR_TYPES, PLSQL_TABLE_TYPES, PLUGGABLE_MAPPINGS,
PLUGGABLE_MAPPING_FOLDERS, PRESENTATION_TEMPLATES, PROCEDURES,
PROCESS_FLOWS, PROCESS_FLOW_MODULES, PROCESS_FLOW_PACKAGES, PROJECTS,
QUEUE_PROPAGATIONS, QUEUE_TABLES, REAL_TIME_MAPPINGS, REGISTERED_FUNCTIONS,
ROLES, SAP_MODULES, SEQUENCES, SNAPSHOTS, STREAMS_CAPTURE_PROCESSES,
STREAMS_QUEUES, TABLES, TABLE_FUNCTIONS, TIME_DIMENSIONS,
TRANSFORMATION_MODULES, TRANSPORTABLE_MODULES, USERS, VARYING_ARRAYS,
VIEWS.
QUOTED_STRING
Mandatory for CONNECTORS, specify a location name; optionally for all other
objects, specify a regular expression, which is used to filter the results.
The syntax of the regular expressions follow the syntax from TCL.
Here are some of the quantifiers:
* -- represents a sequence of 0 or more matches of the atom.
+ -- represents a sequence of 1 or more matches of the atom.
? -- represents a sequence of 0 or 1 matches of the atom.
Here are some of the atoms:
. -- matches any single character
k -- (where k is a non-alphanumeric character) matches that character taken
as an ordinary character,
for example \\ matches a backslash character.
c -- where c is alphanumeric(possibly followed by other characters), an
escape.
(re) -- (where re is any regular expression) matches a match for re, with
the match noted for possible reporting.
[char] -- a bracket expression, matching any one of the chars.
Further documentation on the syntax can be found at the TCL manual page
under the command 'regexp'.
Examples
OMBLIST TABLES
will list the tables under the current Oracle module folder context (if
the current context is not an Oracle module, an error will be produced).
OMBLIST ORACLE_MODULES '/MY_PROJECT/O.*'
will list Oracle modules starting with letter 'O', within project
'MY_PROJECT'.
OMBLIST ORACLE_MODULES '/MY_PROJECT/\[ABC\].*'
will list Oracle modules starting with either letter A or B or C, within
project 'MY_PROJECT'.
OMBLIST LOCATIONS
will list all created locations within the repository.
OMBLIST CONNECTORS 'MY_LOCATION'
will list all connectors of the 'MY_LOCATION' location.
Purpose
To list the default object privileges granted to a specified role or user from the owner. These object privileges will
really be granted to the specified user or role on the new object whenever
the owner creates it.
Prerequisites
The default object privileges can be listed from any context.
Syntax
parseListDefObjPrivs = OMBLIST DEFAULT ( OBJ_PRIVS | OBJECT_PRIVILEGES ) (
OF ( USER | ROLE ) "QUOTED_STRING" ) [ FOR USER "QUOTED_STRING" ]
Keywords And Parameters
parseListDefObjPrivs
This clause will show the default object privilege setting property of a
user, basically will list the default object privileges granted to a
specified role or user from the owner. The default object privileges will
be really ganted to the specified user or role on the newly created object
by the owner.
Examples
OMBLIST DEFAULT OBJ_PRIVS OF USER 'USER1'
will list the default object privileges granted to user 'USER1' from the
owner, by default who is current login user.
OMBLIST DEFAULT OBJ_PRIVS OF ROLE 'EVERYONE' FOR USER 'USER2'
will list the default object privileges granted to role 'EVERYONE' from
owner 'USER2'. Note if the current user want to show other user's default
object privilege setting property, the FOR USER statement is required.
Purpose
To list the icon sets in the current repository.
Prerequisites
Must be connected to a repository, in any context.
Syntax
listIconSetCommand = OMBLIST ICONSETS [ "QUOTED_STRING" ] [ OF
"QUOTED_STRING" ]
Keywords And Parameters
listIconSetCommand
This command lists the iconsets in a repository.
QUOTED_STRING
A regular expression that describes the name of the icon set. Or the name
of the group to which iconsets belong.
Examples
OMBLIST ICONSETS 'ICON.*'
See Also
OMBCREATE ICONSET
Purpose
To list the object privileges granted to a specified user on a specified object.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseListObjPrivs = OMBLIST ( OBJ_PRIVS | OBJECT_PRIVILEGES ) ON
"UNQUOTED_STRING" "QUOTED_STRING" ( OF ( USER | ROLE ) "QUOTED_STRING"
)
Keywords And Parameters
parseListObjPrivs
This clause lists the object privileges granted to a specified user on a
specified object.
UNQUOTED_STRING
The type of the objects to be listed.Valid object types are: PROJECT,
ORACLE_MODULE, FLAT_FILE_MODULE, PROCESS_FLOW_MODULE, SAP_MODULE,
BUSINESS_DEFINITION_MODULE, BUSINESS_PRESENTATION_MODULE,
TRANSFORMATION_MODULE, PACKAGE, ADVANCED_QUEUE, BUSINESS_AREA, COLLECTION,
CONNECTOR, CUBE, DIMENSION, EXTERNAL_TABLE, FLAT_FILE, FUNCTION,
REGISTERED_FUNCTION, MAPPING, MATERIALIZED_VIEW, OBJECT_TYPE, PROCEDURE,
ITEM_FOLDER, DRILL_PATH, DRILLS_TO_DETAIL, ALTERNATIVE_SORT_ORDER,
LISTS_OF_VALUE, PRESENTATION_TEMPLATE, SEQUENCE, TABLE, PROCESS_FLOW,
PROCESS_FLOW_PACKAGE, LOCATION, CONTROL_CENTER, CONFIGURATION, DEPLOYMENT,
VIEW.
Examples
OMBLIST OBJ_PRIVS ON TABLE 'EMP' OF USER 'USER1'
will list object privileges granted to user 'USER1' on table object 'EMP'.
You must be under an oracle module context to succeed.
OMBLIST OBJECT_PRIVILEGES ON TABLE '/MY_PROJECT/MY_MODULE/EMP' OF ROLE
'EVERYONE'/n will list object privileges granted to role 'EVERYONE' on
table 'EMP'.Note that you can reference an object by using a full path
name.
Purpose
parseListRolePurposeTag??
Prerequisites
Warehouse Builder users can be list from any context.
Syntax
parseListRole = OMBLIST ROLES ( [ "QUOTED_STRING" | ( OF USER
"QUOTED_STRING" ) ] )
Keywords And Parameters
parseListRole
This clause lists existing roles or lists existing roles whose names match
the given regular expression or lists the granted roles of a given user.
Examples
OMBLIST ROLES
will list all existing roles.
OMBLIST ROLES 'DEV*ROLE*'
will list all existing roles whose names match regular expression
'DEV*ROLE*'.
OMBLIST ROLES OF USER 'USER1'
will list all roles granted to user USER1.
Purpose
This command lists all the snapshots existing or all snapshots for a specific component.
Prerequisites
Snapshots can be listed from any context.
Syntax
parseListCommand = OMBLIST "listSnapshotCommand"
listSnapshotCommand = SNAPSHOTS [ FOR ( "UNQUOTED_STRING" "QUOTED_STRING"
) ]
Keywords And Parameters
parseListCommand
Root production of OMBLIST SNAPSHOT.
listSnapshotCommand
To list existing snapshots.
SNAPSHOTS
Lists all the snapshots existing in the repository.
FOR
Lists all the snapshots existing for a specific component or folder.
Examples
OMBLIST SNAPSHOTS
This command lists all the snapshots ever taken in the lifetime of the
repository.
OMBLIST SNAPSHOTS FOR TABLE '/Project/WH/T1'
This command lists all the snapshots for table T1. It can be seen as a
version tree of table T1.
See Also
OMBCREATE SNAPSHOT, OMBALTER SNAPSHOT, OMBDROP SNAPSHOT, OMBRESTORE SNAPSHOT, OMBCOMPARE SNAPSHOT, OMBRETRIEVE SNAPSHOT
Purpose
To list the system privileges granted to a user or a role.
Prerequisites
System privileges granted to a user or a role can be listed from any
context.
Syntax
parseListSysPrivs = OMBLIST ( SYS_PRIVS | SYSTEM_PRIVILEGES ) ( OF ( USER
| ROLE ) "QUOTED_STRING" )
Keywords And Parameters
parseListSysPrivs
This clause lists the system privileges granted to a user or a role.
Examples
OMBLIST SYS_PRIVS OF USER 'USER1'
will list system privileges granted to user USER1.
OMBLIST SYSTEM_PRIVILEGES OF ROLE 'DEVELOPMENT_ROLE'
will list system privileges granted to role 'DEVELOPMENT_ROLE'.
Purpose
To list existing roles or list existing roles whose names match the given regular expression or list the granted roles of a given
user.
Prerequisites
Warehouse Builder users can be list from any context.
Syntax
parseListUser = OMBLIST USERS ( [ "QUOTED_STRING" | ( OF ROLE
"QUOTED_STRING" ) ] )
Keywords And Parameters
parseListUser
This clause lists existing Warehouse Builder users or list existing users
matches the given regular expression or list granted users of a given role.
Examples
OMBLIST USERS
will list all existing warehouse builder users.
OMBLIST USERS 'USER*'
will list all users whose names match regular express 'USER*'.
OMBLIST USERS OF ROLE 'DEVELOPMENT_ROLE'
will list the users who have been granted the role 'DEVELOPMENT_ROLE'.
Purpose
Lock one or more objects. If a list of objects is specified, the objects will be locked one by one in the given order. The command will
behave atomically, that is, if it fails to lock any of the objects in the list,
then it will lock none of them.
Prerequisites
No other user should have a lock on any of the objects.
Syntax
parseLockCommand = OMBLOCK "parseTypeNameList"
parseTypeNameList = "objectType" "QUOTED_STRING" { "," "objectType"
"QUOTED_STRING" }
objectType = ( ADVANCED_QUEUE | STREAMS_QUEUE | BUSINESS_AREA | COLLECTION
| CONNECTOR | CONFIGURATION | DEPLOYMENT | CUBE | DIMENSION | EXPERT
| EXPERT_MODULE | EXTERNAL_TABLE | FLAT_FILE_MODULE | FLAT_FILE |
FUNCTION | TABLE_FUNCTION | GATEWAY_MODULE |
BUSINESS_DEFINITION_MODULE | REGISTERED_FUNCTION | LOCATION | MAPPING
| MATERIALIZED_VIEW | OBJECT_TYPE | VARYING_ARRAY | NESTED_TABLE |
ORACLE_MODULE | PACKAGE | PROCEDURE | PROCESS_FLOW |
PROCESS_FLOW_MODULE | PROCESS_FLOW_PACKAGE | PROJECT | ITEM_FOLDER |
DRILL_PATH | LIST_OF_VALUES | DRILL_TO_DETAIL | ALTERNATIVE_SORT_ORDER
| PRESENTATION_TEMPLATE | BUSINESS_PRESENTATION_MODULE |
CONTROL_CENTER | SAP_MODULE | CMI_MODULE | SEQUENCE | TABLE | VIEW |
CMI_DEFINITION | PLSQL_RECORD_TYPE | "UNQUOTED_STRING" )
Keywords And Parameters
parseLockCommand
Specify lock command.
parseTypeNameList
Specify the object or the list of objects to be locked.
QUOTED_STRING
Name of the object to be locked. Can be specified as an absolute path or as
a path relative to the current context. However, there is the restriction
that all objects to be locked must be in the current project.
objectType
Type of the object to be locked.
Examples
OMBLOCK TABLE 'T1', VIEW '/MY_PROJECT/ORACLE_1/V1'
will lock table 'T1' in the current module, and view 'V1' in Oracle
module 'ORACLE_1' from project 'MY_PROJECT'.
See Also
OMBUNLOCK
Purpose
Add more languages into an existing OWB repository to support the object translation.
Prerequisites
OWB repository should already exists in the database.
Syntax
parseUpdateMlsOWBRepositoryCommand = OMBMLSUPDATE OWB_REPOSITORY
"UNQUOTED_STRING" [ SUPPORTED_LANGUAGES "(" "QUOTED_STRING" { ","
"QUOTED_STRING" } ")" ] USING CREDENTIAL "UNQUOTED_STRING" [
NET_SERVICE_NAME "QUOTED_STRING" ]
Keywords And Parameters
parseUpdateMlsOWBRepositoryCommand
Specify an OMBMLSUPDATE OWB_REPOSITORY command.
UNQUOTED_STRING
Specify the connection string to the database using this format:
username/password@host:port:service name, OR specify the user name and
password pair using this format: username/password.
QUOTED_STRING
Specify the language name.
Examples
1. OMBMLSUPDATE OWB_REPOSITORY h_rep4/h SUPPORTED_LANGUAGES ( 'FRENCH',
'Mexican Spanish' ) USING CREDENTIAL sys/sys@localhost:1521:orcl92
This adds two languages 'FRENCH' and 'Mexican Spanish' into an OWB
repository.
Purpose
Move one or more objects of the same object type. The replace option enables you to overwrite.
Prerequisites
Use of relative path specifications requires awareness of the current
context.
Syntax
parseMoveCommand = OMBMOVE "moveObjectType" "QUOTED_STRING" TO
"QUOTED_STRING" [ USE REPLACE_MODE ]
moveObjectType = ( "UNQUOTED_STRING" )
Keywords And Parameters
parseMoveCommand
Specifies the source object type, source path, and target path for the
object to move. Moving objects is subject to the following restrictions: 1.
You can only move objects within the current project; you cannot move
objects between projects. 2. You cannot move an object within the same
parent folder; if your purpose is to rename the object, use the
'OMBALTER...RENAME TO...' command.
QUOTED_STRING
Source and target path specifications can be absolute or relative. To move
multiple objects, include a regular expression as the final step of the
source path. If you are moving multiple objects, the final step of the
target path must be the folder to which the objects are being copied. If
you are only moving one object, you can specify the object's original name
or a new name as the final step of the target path.
REPLACE_MODE
Use this option to overwrite existing target objects.
moveObjectType
The type of the object(s) to be copied. Valid types are: PROJECT,
ORACLE_MODULE, FLAT_FILE_MODULE, BUSINESS_DEFINITION_MODULE,
BUSINESS_PRESENTATION_MODULE, SAP_MODULE, CMI_MODULE, PROCESS_FLOW_MODULE,
PROCESS_FLOW_PACKAGE, PROCESS_FLOW, EXPERT_MODULE, EXPERT, FLAT_FILE,
ADVANCED_QUEUE, STREAMS_QUEUE, QUEUE_TABLE, QUEUE_PROPAGATION,
STREAMS_CAPTURE_PROCESS, OBJECT_TYPE, VARYING_ARRAY, NESTED_TABLE, TABLE,
VIEW, MATERIALIZED_VIEW, SEQUENCE, DIMENSION, CUBE, DATA_AUDITOR,
DATA_PROFILE, DATA_RULE, DATA_RULE_MODULE, MAPPING, REAL_TIME_MAPPING,
PACKAGE, FUNCTION, PROCEDURE, BUSINESS_AREA, COLLECTION, EXTERNAL_TABLE,
REGISTERED_FUNCTION, ITEM_FOLDER, DRILL_PATH, LIST_OF_VALUES,
DRILL_TO_DETAIL, ALTERNATIVE_SORT_ORDER, PRESENTATION_TEMPLATE and any user
defined object types.
Examples
OMBMOVE TABLE 'MY_TABLE1' TO '../WH2/MY_TABLE1' USE REPLACE_MODE
OMBMOVE VIEW 'MY_VIEW1' TO '../WH2/MY_VIEW1'
OMBMOVE TABLE 'MY_.*' TO '/MY_PROJECT1/WH2'
See Also
OMBCOPY
Purpose
To execute the action plans associated with profiling. You can do profiling, correction schema generation and correction map generation
with this command.
Prerequisites
This command must be done in the context of a Data Profile. Furthermore,
the corresponding transient action plans need to have been created before
invoking this command.
Syntax
parseProfileCommand = OMBPROFILE ( ( ANALYZE_ACTION_PLAN "QUOTED_STRING" )
| ( ( CORRECTION_SCHEMA_ACTION_PLAN "QUOTED_STRING" IN ORACLE_MODULE
"QUOTED_STRING" ) [ ( DROP PREVIOUS CORRECTIONS ) ] ) | ( (
CORRECTION_MAPS_ACTION_PLAN "QUOTED_STRING" IN ORACLE_MODULE
"QUOTED_STRING" ) [ ( DROP PREVIOUS CORRECTIONS ) ] ) )
Keywords And Parameters
parseProfileCommand
Executes the analyze action plan.
Examples
OMBPROFILE ANALYZE_ACTION_PLAN 'ANALYZE_PLAN'
Purpose
Synchronize the target metadata definition with the source metadata definition.
Prerequisites
1. The current context of scripting must be a project atleast.
2. The target, or source objects, or both should exist in the current project.
3. No concurrent user is operating on the target.
Syntax
ReconcileCommand = ( OMBRECONCILE | OMBSYNCHRONIZE ) ( "parseIOObject" |
"parseSourceFCOSCO" TO "parseTargetFCOSCO" USE "(" "setStrategyClause"
"," "setStrategyClause" ")" )
parseIOObject = ITEM_FOLDER "QUOTED_STRING"
parseSourceFCOSCO = ( ( DATA_AUDITOR "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( MAPPING "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( REAL_TIME_MAPPING "QUOTED_STRING" [
OPERATOR "QUOTED_STRING" ] ) ) | ( ( FLAT_FILE "QUOTED_STRING" [
RECORD "QUOTED_STRING" ] ) ) | ( PROCESS_FLOW "QUOTED_STRING" [
ACTIVITY "QUOTED_STRING" ] ) | ( TABLE | EXTERNAL_TABLE | VIEW |
MATERIALIZED_VIEW | SEQUENCE | CUBE | DIMENSION | ADVANCED_QUEUE |
OBJECT_TYPE | VARYING_ARRAY | NESTED_TABLE | ACTIVITY_TEMPLATE |
PACKAGE | FUNCTION | TABLE_FUNCTION | PROCEDURE ) "QUOTED_STRING"
parseTargetFCOSCO = ( ( DATA_AUDITOR "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( MAPPING "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( REAL_TIME_MAPPING "QUOTED_STRING" [
OPERATOR "QUOTED_STRING" ] ) ) | ( ( FLAT_FILE "QUOTED_STRING" [
RECORD "QUOTED_STRING" ] ) ) | ( ( PROCESS_FLOW "QUOTED_STRING" [
ACTIVITY "QUOTED_STRING" ] ) ) | ( TABLE | EXTERNAL_TABLE | VIEW |
MATERIALIZED_VIEW | ADVANCED_QUEUE | VARYING_ARRAY | NESTED_TABLE |
OBJECT_TYPE | ACTIVITY_TEMPLATE | FUNCTION ) "QUOTED_STRING"
setStrategyClause = ( RECONCILE_STRATEGY | SYNCHRONIZE_STRATEGY )
"retrieveReconcileStrategyClause" | MATCHING_STRATEGY
"retrieveMatchingStrategyClause"
retrieveReconcileStrategyClause = "QUOTED_STRING"
retrieveMatchingStrategyClause = "QUOTED_STRING"
Keywords And Parameters
ReconcileCommand
Synchronizes the target metadata definition with the source metadata
definition.
setStrategyClause
The strategy to be used for synchronization. Must be one of
RECONCILE_STRATEGY OR MATCHING_STRATEGY
RECONCILE_STRATEGY
MERGE or REPLACE.
MERGE : Updates the matching objects in the target with the metadata
definition in the source object and creates new objects in the target for
source objects that do not match.
REPLACE : Updates the matching objects in the target with the metadata
definition in the source object, creates a new object in the target for
source objects that do not match, and deletes objects in the target that
have no match in the source.
MATCHING_STRATEGY
Indicates the matching strategy to be used between the object types in
source and target. Currently, the list of available matching strategies for
a source and target combination are listed subsequently. For synchronization
between RECORD and EXTERNAL_TABLE, the valid matching strategies are
MATCH_BY_OBJECT_ID, MATCH_BY_OBJECT_NAME, MATCH_BY_OBJECT_POSITION. For
synchronization involving OPERATOR of MAP, the available matching
strategies are MATCH_BY_OBJECT_ID, MATCH_BY_OBJECT_NAME,
MATCH_BY_OBJECT_POSITION, MATCH_BY_OBJECT_ID_AND_NAME,
MATCH_BY_OBJECT_ID_AND_POSITION, MATCH_BY_OBJECT_NAME_AND_POSITION,
MATCH_BY_OBJECT_ID_AND_NAME_AND_POSITION. Note that the source map might be
modified during outbound synchronization of maps, which would require
locking both the source and the target before synchronization invocation.
retrieveReconcileStrategyClause
Must of one of 'MERGE' or 'REPLACE'
retrieveMatchingStrategyClause
String representing the matching paradigm between the source and the target
object. The list varies for every source and target object type.
Examples
OMBRECONCILE EXTERNAL_TABLE 'et1' TO EXTERNAL_TABLE 'et2'
USE (RECONCILE_STRATEGY 'MERGE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_NAME')
OMBRECONCILE MAPPING 'm1' OPERATOR 'o1' TO TABLE 't1'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY
'MATCH_BY_OBJECT_NAME')
OMBRECONCILE MAPPING 'm1' OPERATOR 'o1' TO FLAT_FILE 'f1'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY
'MATCH_BY_OBJECT_NAME')
OMBRECONCILE MAPPING 'm1' OPERATOR 'o1' TO MAPPING 'm1' OPERATOR 'o2'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_ID')
OMBRECONCILE ITEM_FOLDER 'F1'
OMBRECONCILE TABLE 't1' TO DATA_AUDITOR 'a1' OPERATOR 'o2'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_ID')
For Item Folder synchronization the source is obtained from the repository.
For simple item folders the source
is the table that the item folder is based on. For complex item folders
the source is the dependent folders.
The user does not have to specify the source.
Purpose
To redefine an association between two classes (types).
Prerequisites
Association definition to be redefined should already exist. This command
can be executed for any association definition regardless of current
context. User must have CREATE_EXTENSIONMODEL system privilege and has to
be connected in single user mode to run this command.
Syntax
parseRedefineAssociationCommand = OMBREDEFINE ASSOCIATION_DEFINITION
"QUOTED_STRING" ( RENAME TO "QUOTED_STRING" |
"setAssociationDefinitionPropertiesClause" | (
"modifyDependencyDefinitionClause" |
"deleteDependencyDefinitionClause" | "addDependencyDefinitionClause"
)+ )
setAssociationDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
modifyDependencyDefinitionClause = MODIFY DEPENDENCY_DEFINITION
"QUOTED_STRING" "setDependencyDefinitionPropertiesClause"
deleteDependencyDefinitionClause = DELETE DEPENDENCY_DEFINITION
"QUOTED_STRING"
addDependencyDefinitionClause = ADD DEPENDENCY_DEFINITION "QUOTED_STRING"
[ "setDependencyDefinitionPropertiesClause" ]
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyValueList = "propertyValue" { "," "propertyValue" }
setDependencyDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
propertyNameClause = ( "UNQUOTED_STRING" )
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
parseRedefineAssociationCommand
Redefine an association between two classes..
setAssociationDefinitionPropertiesClause
Basic properties for re-defining ASSOCIATION_DEFINITION:
Name: DESCRIPTION
Type: STRING(4000)
Valid Values: N/A
Default: N/A
A descriptive text for this association.
Name: ROLE_1_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 1. Value can be positive integer.
Name: ROLE_1_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 1. Value can be positive integer or 'INFINITE'.
Name: ROLE_1_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 1.
Name: ROLE_2_MIN_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Minimum cardinality of role 2. Value can be positive integer.
Name: ROLE_2_MAX_CARDINALITY
Type: STRING(200)
Valid Values: N/A
Default: N/A
Maximum cardinality of role 2. Value can be positive integer or 'INFINITE'.
Name: ROLE_2_NAVIGABLE
Type: BOOLEAN
Valid Values: true, false
Default: From user defined class side default is true. From OWB class side
default is false.
Navigability of role 2.
modifyDependencyDefinitionClause
Modifies the properties of the specified dependency for this association.
deleteDependencyDefinitionClause
Un-mark this association so that the dependency engine will ignore it when
computing the lineage and impact dependencies of that type.
addDependencyDefinitionClause
Mark this association so that the dependency engine will consider it when
computing the lineage and impact dependencies of the specified type. The
only dependency type allowed here for now is 'DATAFLOW'.
propertyNameList
The list of property names.
propertyValueList
The list of property values being set.
setDependencyDefinitionPropertiesClause
Basic dependency-related properties for this association:
Name: SOURCE_ROLE_ID
Type: STRING(200)
Valid Values: ROLE_1, ROLE_2
Default: If one of the ends is a OWB class, then that is the default
source. If both ends are user defined classes, then the association is
default bidirectional.
Identifies the role (end) of the association which serves as the source for
the dependency flow.
Name: BIDIRECTIONAL
Type: BOOLEAN
Valid Values: true, false
Default: If one of the ends is a OWB class, then default is false. If both
ends are user defined classes, then default is true.
Specifies whether the association is bi-directional for the dependency
flow.
propertyNameClause
Name of a property.
propertyValue
Value of a property.
Examples
OMBREDEFINE ASSOCIATION_DEFINITION 'UD_ASSOC2'
SET PROPERTIES (DESCRIPTION, ROLE_1_MIN_CARDINALITY,
ROLE_1_MAX_CARDINALITY, ROLE_1_NAVIGABLE) VALUES ('Some association
description text', '1', 'INFINITE', 'true') DELETE DEPENDENCY_DEFINITION
'DATAFLOW'
This will redefine association 'UD_ASSOC2' to change the description, as
well as the navigability, minimum and maximum cardinality of role 1. Also
it removes DATAFLOW dependency marking on this association.
See Also
OMBDEFINE ASSOCIATION_DEFINITION, OMBDESCRIBE ASSOCIATION_DEFINITION
Purpose
To redefine a class.
Prerequisites
Class definition to be redefined should already exist. This command can be
executed for any class definition regardless of current context. User must
have CREATE_EXTENSIONMODEL system privilege, and user has to connect in
single user mode.
The valid types to define user defined properties are: INTEGER, STRING,
FLOAT, DOUBLE, DATE, TIMESTAMP, BOOLEAN, LONG, FILE, URL
Syntax
parseRedefineClassCommand = OMBREDEFINE CLASS_DEFINITION "QUOTED_STRING" (
( "setClassDefinitionPropertiesClause" |
"setClassDefinitionIconSetClause" |
"unsetClassDefinitionIconSetClause" ) [ "modifySubDefinitionsClause" ]
| "modifySubDefinitionsClause" )
setClassDefinitionPropertiesClause = SET PROPERTIES "(" "propertyNameList"
")" VALUES "(" "propertyValueList" ")"
setClassDefinitionIconSetClause = SET REF ICONSET "QUOTED_STRING"
unsetClassDefinitionIconSetClause = UNSET REF ICONSET
modifySubDefinitionsClause = ( "addPropertyDefinitionClause" |
"modifyPropertyDefinitionClause" | "deletePropertyDefinitionClause" |
"addPropertyGroupDefinitionClause" |
"modifyPropertyGroupDefinitionClause" |
"deletePropertyGroupDefinitionClause" | "addChildTypeClause" |
"deleteChildTypeClause" )+
propertyNameList = "propertyNameClause" { "," "propertyNameClause" }
propertyValueList = "propertyValue" { "," "propertyValue" }
addPropertyDefinitionClause = ( ADD [ ( ( CONFIGURATION |
PHYSICAL_CONFIGURATION ) | LOGICAL | USER_DEFINED ) ]
PROPERTY_DEFINITION "QUOTED_STRING"
"setPropertyDefinitionPropertiesClause" )
modifyPropertyDefinitionClause = ( MODIFY PROPERTY_DEFINITION
"QUOTED_STRING" ( RENAME TO "QUOTED_STRING" |
"setPropertyDefinitionPropertiesClause" ) )
deletePropertyDefinitionClause = ( DELETE PROPERTY_DEFINITION
"QUOTED_STRING" )
addPropertyGroupDefinitionClause = ADD PROPERTY_GROUP_DEFINITION
"QUOTED_STRING" "setPropertyGroupDefinitionPropertiesClause"
modifyPropertyGroupDefinitionClause = ( MODIFY PROPERTY_GROUP_DEFINITION
"QUOTED_STRING" ( RENAME TO "QUOTED_STRING" |
"setPropertyGroupDefinitionPropertiesClause" ) )
deletePropertyGroupDefinitionClause = ( DELETE PROPERTY_GROUP_DEFINITION
"QUOTED_STRING" )
addChildTypeClause = ( ADD CHILD_TYPE "QUOTED_STRING" )
deleteChildTypeClause = ( DELETE CHILD_TYPE "QUOTED_STRING" )
propertyNameClause = ( "UNQUOTED_STRING" )
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
setPropertyDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
setPropertyGroupDefinitionPropertiesClause = SET PROPERTIES "("
"propertyNameList" ")" VALUES "(" "propertyValueList" ")"
Keywords And Parameters
parseRedefineClassCommand
Redefine a class definition.
CLASS_DEFINITION
Redefine a class definition.
QUOTED_STRING
Name of the class definition.
propertyNameList
The list of properties for the class definition.
propertyValueList
The list of values provided for the class definition.
propertyNameClause
The name of the property.
UNQUOTED_STRING
The name of the property for the class definition.
propertyValue
The value of the property.
QUOTED_STRING
The value in string format of the property for the class definition.
INTEGER_LITERAL
The integer value of the property for the class definition.
FLOATING_POINT_LITERAL
The float value of the property for the class definition.
Examples
OMBREDEFINE CLASS_DEFINITION 'TABLE'
ADD PROPERTY_DEFINITION 'UDP_TBL_1' SET PROPERTIES (TYPE, DEFAULT_VALUE)
VALUES ('INTEGER', '100')
This will add an User-defined property definition to class definition
'TABLE'.
OMBREDEFINE CLASS_DEFINITION 'TABLE' DELETE PROPERTY_DEFINITION 'UDP_TBL_1'
This will delete property definition 'UDP_TBL_1' from class definition
'TABLE'. Property definition must exist before deleting it.
OMBREDEFINE CLASS_DEFINITION 'TABLE' MODIFY PROPERTY_DEFINITION 'UDP_TBL_1'
SET PROPERTIES (DEFAULT_VALUE, BUSINESS_NAME)
VALUES ('99', 'UDP_TBL_2')
This will change the name of property definition to 'UDP_TBL_2' and default
value to 99. Property definition must exist before modifying it. TYPE can
not be changed for property definition.
See Also
OMBDESCRIBE CLASS_DEFINITION
Purpose
Register a location with a Control Center.
Prerequisites
Must be in the context of a project and connected to a Control Center.
Syntax
registerLocationCommand = OMBREGISTER LOCATION "QUOTED_STRING" [ REUSE ]
Keywords And Parameters
registerLocationCommand
Register a location.
QUOTED_STRING
The name of the location to register.
Examples
OMBREGISTER LOCATION 'MY_ORACLE_LOCATION' REUSE
Purpose
To register a database user as a Warehouse Builder user.
Prerequisites
Commit or Rollback is needed if there is any change.
Syntax
parseRegisterUserCommand = ( OMBREGISTER USER "QUOTED_STRING" [ SET
PROPERTIES "(" "propertyNameList" ")" VALUES "(" "propertyValueList"
")" ] [ WITH CREATE DBUSER OPTION IDENTIFIED BY "QUOTED_STRING"
THROUGH SYSDBA CONNECTION "UNQUOTED_STRING" ] )
propertyNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
propertyValueList = "propertyValue" { "," "propertyValue" }
propertyValue = ( "QUOTED_STRING" | "INTEGER_LITERAL" |
"FLOATING_POINT_LITERAL" )
Keywords And Parameters
parseRegisterUserCommand
This command registers a Warehouse Builder user.
propertyNameList
A list of valid properties are as shown.
Basic properties for USER:
Name: BUSINESS_NAME
Type: STRING(200)
Valid Values: N/A
Default: ''
Business name of the User
Name: DESCRIPTION
Type: STRING(4000)
Valid Values: N/A
Default: ''
Description of the User
Name: ISTARGETSCHEMA
Type: BOOLEAN
Valid Values: true, false
Default: false
If true, the user will be set up as target schema for deployment; and also
the property TARGETSCHEMAPWD must be provided when you are setting the
ISTARGETSCHEMA as true.
Name: TARGETSCHEMAPWD
Type: STRING(30)
Valid Values: N/A
Default: N/A
This properties will be provided only when you are seting ISTARGETSCHEMA as
true, so that the necessary target schema objects can be installed into the
potential target schema. And this property cannot be retrieved due to
security consideration.
User preferences:
Name: LOCALE
Type: STRING
Valid Values: Albanian, Arabic, Bulgarian, Byelorussian, Catalan, Chinese,
Croatian, Czech, Danish, Dutch, English, Estonian, French, German, Greek,
Hebrew, Hungarian, Icelandic, Italian, Japanese, Korean, Lithuanian,
Macedonian, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian,
Serbo_Croation, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish,
Ukranian
Default: ''
Name: SHOW_PROJECT
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_MODULE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_LOCATION
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_ACTION
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_TYPE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: DEFAULT_PROFILE_LOCATION
Type: STRING
Valid Values: N/A
Default: ''
Name: ALLOW_UNDO_REDO
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: PAUSE_AFTER_COMPILE
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: PROMPT_FOR_COMMIT
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: PROMPT_FOR_JOB_NAME
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: PROMPT_FOR_EXECUTION_PARAMS
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_MONITOR
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_DEPLOYMENT_COMPLETION
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_DEPLOYMENT_DEPENDENCIES
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_MONITOR_RESULTS
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_MONITOR_LOGFILE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: PERSONALITY
Type: STRING
Valid Values: N/A
Default: Default
Name: SHOW_GUIDED_ASSISTANCE
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: HIDE_WIZARD_WELCOME_PAGES
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_DELETE_CONFIRMATION
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: RECYCLE_DELETED_OBJECTS
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: EMPTY_RECYCLE_BIN
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: CLEAR_CLIPBOARD
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_GENERATION_PROJECT
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_GENERATION_MODULE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: SHOW_GENERATION_LOCATION
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_GENERATION_ACTION
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: SHOW_GENERATION_TYPE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: LOG_FILE_PATH
Type: STRING(1000)
Valid Values: N/A
Default: ''
Name: LOG_FILE_NAME
Type: STRING(1000)
Valid Values: N/A
Default: log
Name: LOG_FILE_MAX_SIZE
Type: STRING
Valid Values: 1-10000000
Default: 100
Name: LOG_ERROR_MESSAGES
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: LOG_WARNING_MESSAGES
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: LOG_INFORMATION_MESSAGES
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: NAMING_MODE
Type: STRING
Valid Values: PHYSICAL_NAMING_MODE, BUSINESS_NAMING_MODE
Default: PHYSICAL_NAMING_MODE
Name: PROPAGATE_NAME_CHANGES
Type: BOOLEAN
Valid Values: true, false
Default: false
Name: DESIGNREPOS_PWD_PERSIST
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: RUNTIMEREPOS_PWD_SHARE
Type: BOOLEAN
Valid Values: true, false
Default: true
Name: DEFAULT_SEC_POLICY
Type: STRING
Valid Values: MINIMUM_SECURITY, MAXIMUM_SECURITY
Default: MINIMUM_SECURITY
Examples
OMBREGISTER USER 'USER1' SET PROPERTIES(BUSINESS_NAME, DESCRIPTION,
ISTARGETSCHEMA,TARGETSCHEMAPWD) VALUES('developer user1', 'one user from
developer group', 'true','passwordForUser1')
WITH CREATE DBUSER OPTION IDENTIFIED BY 'passwordForUser1' THROUGH SYSDBA
CONNECTION sys/change_on_install
This will first using database DBA connection credential to create a
database uesr USER1 idenfied by password passwordForUser1, and then
register the user USER1 with current working repository.
Note: if the database user USER1 already exists, WITH CREATE DBUSER OPTION
should be omitted, for example:
OMBREGISTER USER 'USER1' SET PROPERTIES(BUSINESS_NAME, DESCRIPTION,
ISTARGETSCHEMA) VALUES('developer user1', 'one user from developer
group','false')
See Also
OMBUNREGISTER USER, OMBALTER USER, OMBRETRIEVE USER
Purpose
A snapshot is a history point of individual or group of components. The user can recover the components' previously captured
states by using the snapshot restore functionality.
Prerequisites
A component can be restored from a snapshot into the current repository.
Syntax
parseRestoreCommand = OMBRESTORE "restoreSnapshotCommand"
restoreSnapshotCommand = ( SNAPSHOT "QUOTED_STRING" [ CASCADE UP ] [
IGNORE CLASS_DEFINITION ( DIFFERENCES | DIFF ) ] [ FOR (
"UNQUOTED_STRING" "QUOTED_STRING" ) ] )
Keywords And Parameters
parseRestoreCommand
Root production for OMBRESTORE SNAPSHOT.
restoreSnapshotCommand
To restore snapshot components into the repository.
QUOTED_STRING
Name of the snapshot from which components are to be restored.
CASCADE
CASCADE UP - Optional clause for letting the user restore a component even
if its parent does not exist in the current repository.
CLASS_DEFINITION
IGNORE CLASS_DEFINITION DIFF - Optional clause for letting the user restore
a snapshot whether or not the meta-model of the snapshot is different from
that of the current repository.
FOR
Optional component clause for partial restore. This can be used to specify
which components of a snapshot are to be restored.
Examples
OMBRESTORE SNAPSHOT 'S1'
This command restores all components from the snapshot into the repository.
If the corresponding components are not found in the repository, then they
appear as newly recovered components from history.
OMBRESTORE SNAPSHOT 'S1' FOR TABLE '/Project/WH1/T1'
This commands replaces the current definition of the component in the
repository with the snapshot component.
OMBRESTORE SNAPSHOT 'S1' CASCADE UP
This command restores all objects of the snapshot into the repository
whether or not their parents exist in the current repository. If not,
components along with their corresponding parents are restored.
OMBRESTORE SNAPSHOT 'S1' IGNORE CLASS_DEFINITION DIFF
This command restores the snapshot regardless of whether or not the
meta-model of the snapshot is different to that of the current repository.
See Also
OMBCREATE SNAPSHOT, OMBALTER SNAPSHOT, OMBDROP SNAPSHOT, OMBCOMPARE SNAPSHOT, OMBLIST SNAPSHOT, OMBRETRIEVE SNAPSHOT
Purpose
Perform revert action on the repository (all objects are reverted to the last saved state).
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRevertCommand = OMBREVERT
Keywords And Parameters
parseRevertCommand
Specify revert command.
Examples
OMBREVERT
See Also
OMBSAVE
Purpose
To change the default object privilege setting property of a user, basically it will revoke a list of default object
privileges from a list of users or roles. These object privileges will not
be granted to the specified user or role on the new objects whenever the
owner creates them.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRevokeDefObjPrivCommand = OMBREVOKE DEFAULT ( OBJ_PRIV |
OBJECT_PRIVILEGE ) "objPrivNameList" FROM ( USER "userOrRoleNameList"
| ROLE "userOrRoleNameList" ) [ FOR USER "QUOTED_STRING" ]
objPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseRevokeDefObjPrivCommand
This clause changes the default object privilege setting property of a user
through revoking a list of default object privileges from a list of users
or roles.
objPrivNameList
Object privileges. Valid object privileges are: READ, COMPILE, EDIT,
FULL_CONTROL.
Examples
OMBREVOKE DEFAULT OBJ_PRIV EDIT FROM ROLE 'DEVELOPMENT_ROLE'
the current login user revokes default object privilege EDIT from role
DEVELOPMENT_ROLE, thus whenever the current login user creates an object,
the role DEVELOPMENT_ROLE will not be granted EDIT privilege on that object
any more
OMBREVOKE DEFAULT OBJ_PRIV EDIT FROM ROLE 'DEVELOPMENT_ROLE' FOR USER
'USER1'
the current user revokes default object privilege EDIT from role
DEVELOPMENT_ROLE on behalf of user USER1, thus whenever the user USER1
creates an object, the role DEVELOPMENT_ROLE will not be granted EDIT
privilege on that object.Note if the current login user does not change the
default object privilege setting for himself, the FOR USER statement is
required.
See Also
OMBGRANT DEFAULT OBJ_PRIV, OMBLIST DEFAULT OBJ_PRIVS
Purpose
To revoke a list of object privileges on the specified objects from a list of users or roles.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRevokeObjPrivCommand = OMBREVOKE ( OBJ_PRIV | OBJECT_PRIVILEGE )
"objPrivNameList" ON "UNQUOTED_STRING" "QUOTED_STRING" [ CASCADE ]
FROM ( USER "userOrRoleNameList" | ROLE "userOrRoleNameList" )
objPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseRevokeObjPrivCommand
This clause revokes a list of object privileges on the specified objects
from a list of users or roles.
UNQUOTED_STRING
The type of the objects to be listed.Valid object types are: PROJECT,
ORACLE_MODULE, FLAT_FILE_MODULE, PROCESS_FLOW_MODULE, SAP_MODULE,
BUSINESS_DEFINITION_MODULE, BUSINESS_PRESENTATION_MODULE,
TRANSFORMATION_MODULE, PACKAGE, ADVANCED_QUEUE, BUSINESS_AREA, COLLECTION,
CONNECTOR, CUBE, DIMENSION, EXTERNAL_TABLE, FLAT_FILE, FUNCTION,
REGISTERED_FUNCTION, MAPPING, MATERIALIZED_VIEW, OBJECT_TYPE, PROCEDURE,
ITEM_FOLDER, DRILL_PATH, DRILLS_TO_DETAIL, ALTERNATIVE_SORT_ORDER,
LISTS_OF_VALUE, PRESENTATION_TEMPLATE, SEQUENCE, TABLE, PROCESS_FLOW,
PROCESS_FLOW_PACKAGE, LOCATION, CONTROL_CENTER, CONFIGURATION, DEPLOYMENT,
VIEW.
objPrivNameList
Object privileges. Valid object privileges are: READ, COMPILE, EDIT,
FULL_CONTROL.
Examples
OMBREVOKE OBJ_PRIV EDIT ON ORACLE_MODULE '/MY_PROJECT/WH' FROM USER 'USER1'
will revoke EDIT on module WH from user USER1
OMBREVOKE OBJ_PRIV EDIT ON PROJECT 'MY_PROJECT' CASCADE FROM ROLE
'EVERYONE'
will revoke object privilege EDIT from role EVERYONE on project MY_PROJECT
and all its child objects cascade.
OMBREVOKE OBJ_PRIV READ ON TABLE '/MY_PROJECT/WH/EMP*' FROM USER 'USER1'
will revoke READ from user USER1 on all tables under module
/MY_PROJECT/WH whose names match regular expression EMP*.
See Also
OMBGRANT OBJ_PRIV, OMBLIST OBJ_PRIVS
Purpose
To revoke a list of Warehouse Builder roles from a list of Warehouse Builder users.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRevokeRoleCommand = OMBREVOKE ROLE "userOrRoleNameList" FROM USER
"userOrRoleNameList"
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseRevokeRoleCommand
This clause revokes a list of Warehouse Builder roles from a list of
Warehouse Builder users.
Examples
OMBREVOKE ROLE 'DEV' , 'QA' FROM USER 'USER1', 'USER2'
will revoke Warehouse Builder role 'DEV'and 'QA' from user 'USER1' and
'USER2'
See Also
OMBGRANT ROLE, OMBLIST ROLES
Purpose
To revoke a list of system privileges from a list of users or roles.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRevokeSysPrivCommand = OMBREVOKE ( SYS_PRIV | SYSTEM_PRIVILEGE )
"sysPrivNameList" FROM ( USER "userOrRoleNameList" | ROLE
"userOrRoleNameList" )
sysPrivNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
userOrRoleNameList = "QUOTED_STRING" { "," "QUOTED_STRING" }
Keywords And Parameters
parseRevokeSysPrivCommand
This clause revokes a list of system privileges from a list of users or
roles.
sysPrivNameList
List of system privileges. Valid system privileges are:CREATE_PROJECT,
CREATE_MIVDEFINITION,CREATE_EXTENSIONMODEL, CONTROL_CENTER_ADMIN,
CONTROL_CENTER_DEPLOY, CONTROL_CENTER_EXECUTE, CREATE_SNAPSHOT
Examples
OMBREVOKE SYS_PRIV 'CREATE_SNAPSHOT' FROM USER 'USER1', 'USER2'
will revoke system privilege CREATE_SNAPSHOT from user USER1 and USER2.
See Also
OMBGRANT SYS_PRIV, OMBLIST SYS_PRIVS
Purpose
Perform rollback action on the repository.
Prerequisites
Must be connected to a OWB repository.
Syntax
parseRollbackCommand = OMBROLLBACK
Keywords And Parameters
parseRollbackCommand
Specify rollback command.
Examples
OMBROLLBACK
See Also
OMBCOMMIT
Purpose
Perform save action on the repository (all objects are saved).
Prerequisites
Must be connected to a OWB repository.
Syntax
parseSaveCommand = OMBSAVE
Keywords And Parameters
parseSaveCommand
Specify save command.
Examples
OMBSAVE
See Also
OMBREVERT
Purpose
To show the session or system parameter information.
Prerequisites
Need to connect to a repository.
Syntax
parseShowCommand = ( OMBSHOW "UNQUOTED_STRING" )
Keywords And Parameters
parseShowCommand
Show the session or system parameters.The Valid session or system parameter
names are: USER, REPOSITORY, CONNECTION, REPOSITORY_VERSION,
CLIENT_VERSION.
UNQUOTED_STRING
Specify the session or system parameter name.
The Valid session or system parameter names are: USER, REPOSITORY,
CONNECTION, REPOSITORY_VERSION, CLIENT_VERSION.
Examples
OMBSHOW USER
will show the session user name.
Purpose
To execute objects from the Control Center. If the ASYNCHRONOUS keyword is specified then this command will return the Execution Job
Identifier. Note, this can then be passed to the OMBSTOP command.
The 'Best Practice' usage of this command is within the context of a Design
Repository connection. However, advanced users may use this command with a
'Control Center Only' usage. Note, the MAPPING keyword cannot be used in
this mode and you must specify the deployed Mapping type.
If it is required to fully specify the Deployed Mapping type then the
possible values are ABAPFILE, DATAAUDITOR, DATAPROFILE, PLSQLMAP,
PROCESSFLOW, SQLLOADERCONTROLFILE and SCHEDULEDJOB.
The Deployment Location of the object is optional if the name of the
executable object is unique in the Control Center. However, please specify
the 'CONTROL_CENTER' location for types that are deployed to the Control
Center (SQL Loader and SAP Mappings).
The System Parameters that can be overriden are
PLSQL Mapping - BULK_SIZE COMMIT_FREQUENCY DEFAULT_AUDIT_LEVEL
DEFAULT_OPERATING_MODE DEFAULT_PURGE_GROUP MAXIMUM_NUMBER_OF_ERRORS
SQL Loader Mapping - AUDIT BIND_SIZE CONTROL_FILE_LOCATION
CONTROL_FILE_NAME DEFAULT_PURGE_GROUP DIRECT_MODE DISCARD_MAX
ERRORS_ALLOWED LOG_FILE_LOCATION LOG_FILE_NAME PERFORM_PARALLEL_LOAD
READ_SIZE RECORDS_TO_LOAD RECORDS_TO_SKIP ROWS_PER_COMMIT
SKIP_INDEX_MAINTENANCE SKIP_UNUSABLE_INDEXES
SAP Mapping - BACKGROUND CONTROL_FILE_NAME DATA_FILE_NAME
FILE_DELIMITER_FOR_STAGING_FILE LOG_FILE_NAME NESTED_LOOP
PRIMARY_FOREIGN_KEY_FOR_JOIN SAP_LOCATION SQL_JOIN_COLLAPSING
STAGING_FILE_DIRECTORY USE_SELECT_SINGLE
Data Auditor - BULK_SIZE COMMIT_FREQUENCY DEFAULT_AUDIT_LEVEL
DEFAULT_OPERATING_MODE DEFAULT_PURGE_GROUP MAXIMUM_NUMBER_OF_ERRORS
Data Profile - There are no System Parameters defined.
Prerequisites
'Best Practice' usage requires a Design Repository connection and the
context to be set to that of executable object. The 'Control Center Only'
usage does not require a Design Repository connection and therefore no
context.
Syntax
parseExecuteCommand = ( OMBSTART | OMBEXECUTE ) ( ( MAPPING | DATA_AUDITOR
| PROCESS_FLOW | SCHEDULABLE | REAL_TIME_MAPPING | "UNQUOTED_STRING"
) "QUOTED_STRING" [ AS "QUOTED_STRING" ] [ IN "QUOTED_STRING" ] ) [
OVERRIDE SYSTEM_PARAMETER "overideParameters" ] [ OVERRIDE
CUSTOM_PARAMETER "overideParameters" ] [ ASYNCHRONOUS ]
overideParameters = "(" "stringList" ")" VALUES "(" "stringList" ")"
stringList = "stringListValue" { "," "stringListValue" }
stringListValue = ( "QUOTED_STRING" )
Keywords And Parameters
parseExecuteCommand
Specify Execute command.
QUOTED_STRING
The name of the object to be executed or the execution's Audit Name.
AS
The execution's Audit Name.
IN
The deployed object's location.
OVERRIDE
Override an Execution Parameter.
SYSTEM_PARAMETER
Specify to override a System Parameter.
CUSTOM_PARAMETER
Specify to override a Custom Parameter.
ASYNCHRONOUS
Execute in an asynchronous mode.
Examples
Best Practice usage:
OMBSTART MAPPING 'MY_TABLE_MAPPING' IN 'MY_DEPLOYMENT_LOCATION'
OMBSTART MAPPING 'MY_SQLLOADER_MAP' IN 'CONTROL_CENTER'
OMBSTART MAPPING 'MY_SAP_MAP' IN 'CONTROL_CENTER'
Control Center Only:
OMBSTART PLSQLMAP 'MY_TABLE_MAPPING' IN 'MY_DEPLOYMENT_LOCATION'
OMBSTART SQLLOADERCONTROLFILE 'MY_SQLLOADER_MAP' IN 'CONTROL_CENTER'
OMBSTART ABAPFILE 'MY_SAP_MAP' IN 'CONTROL_CENTER'
Purpose
This command will display statistical information about the scripting run, such as memory usage, and elapsed time.
Prerequisites
None.
Syntax
parseStatisticsCommand = OMBSTATS
Examples
OMBSTATS
Purpose
To stop jobs running in the Control Center.
Prerequisites
A Control Center connection. Note, a Design Repository connection is not
required.
Syntax
parseStopCommand = OMBSTOP ( "INTEGER_LITERAL" )
Keywords And Parameters
parseStopCommand
Specify Stop command.
INTEGER_LITERAL
The job id.
Examples
OMBSTOP 123456789
Purpose
To switch the current repository connection back to the previous mode. Valid modes are: SINGLE_USER_MODE (that is, exclusive) and
MULTIPLE_USER_MODE.
Prerequisites
Must be connected to an OWB repository and not have any outstanding/unsaved
work. If not already connected, use OMBCONNECT first. If there exists work
that is not saved, use either OMBSAVE or OMBREVERT first. If the current
mode is the connection mode (that is, there is no previous mode) then the mode
is not switched.
Syntax
parseSwitchBackModeCommand = OMBSWITCHBACKMODE
Keywords And Parameters
parseSwitchBackModeCommand
Specify switch back command.
Examples
OMBSWITCHBACKMODE
See Also
OMBDISPLAYCURRENTMODE, OMBSWITCHMODE, OMBCONNECT, OMBSAVE, OMBREVERT
Purpose
To switch the current repository connection between SINGLE_USER_MODE (that is, exclusive) and MULTIPLE_USER_MODE.
Prerequisites
Must be connected to an OWB repository and not have any outstanding/unsaved
work. If not already connected, use OMBCONNECT first. If there exists work
that is not saved, use either OMBSAVE or OMBREVERT first.
Syntax
parseSwitchModeCommand = OMBSWITCHMODE ( SINGLE_USER_MODE |
MULTIPLE_USER_MODE )
Keywords And Parameters
parseSwitchModeCommand
Specify switch command.
SINGLE_USER_MODE
If specified, the user's current connection will be changed to permit them
to use the repository exclusively.
MULTIPLE_USER_MODE
If specified, the user's current connection will be changed to permit more
than one session to work on the repository at the same time.
Examples
OMBSWITCHMODE SINGLE_USER_MODE
OMBSWITCHMODE MULTIPLE_USER_MODE
See Also
OMBDISPLAYCURRENTMODE, OMBCONNECT, OMBSAVE, OMBREVERT
Purpose
Synchronize the target metadata definition with the source metadata definition.
Prerequisites
1. The current context of scripting must be a project atleast.
2. The target, or source objects, or both should exist in the current project.
3. No concurrent user is operating on the target.
Syntax
ReconcileCommand = ( OMBRECONCILE | OMBSYNCHRONIZE ) ( "parseIOObject" |
"parseSourceFCOSCO" TO "parseTargetFCOSCO" USE "(" "setStrategyClause"
"," "setStrategyClause" ")" )
parseIOObject = ITEM_FOLDER "QUOTED_STRING"
parseSourceFCOSCO = ( ( DATA_AUDITOR "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( MAPPING "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( PLUGGABLE_MAPPING "QUOTED_STRING" [
OPERATOR "QUOTED_STRING" ] ) ) | ( ( REAL_TIME_MAPPING "QUOTED_STRING"
[ OPERATOR "QUOTED_STRING" ] ) ) | ( ( FLAT_FILE "QUOTED_STRING" [
RECORD "QUOTED_STRING" ] ) ) | ( PROCESS_FLOW "QUOTED_STRING" [
ACTIVITY "QUOTED_STRING" ] ) | ( TABLE | EXTERNAL_TABLE | VIEW |
MATERIALIZED_VIEW | SEQUENCE | CUBE | DIMENSION | ADVANCED_QUEUE |
OBJECT_TYPE | VARYING_ARRAY | NESTED_TABLE | ACTIVITY_TEMPLATE |
PACKAGE | FUNCTION | TABLE_FUNCTION | PROCEDURE ) "QUOTED_STRING"
parseTargetFCOSCO = ( ( DATA_AUDITOR "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( MAPPING "QUOTED_STRING" [ OPERATOR
"QUOTED_STRING" ] ) ) | ( ( PLUGGABLE_MAPPING "QUOTED_STRING" [
OPERATOR "QUOTED_STRING" ] ) ) | ( ( REAL_TIME_MAPPING "QUOTED_STRING"
[ OPERATOR "QUOTED_STRING" ] ) ) | ( ( FLAT_FILE "QUOTED_STRING" [
RECORD "QUOTED_STRING" ] ) ) | ( ( PROCESS_FLOW "QUOTED_STRING" [
ACTIVITY "QUOTED_STRING" ] ) ) | ( TABLE | EXTERNAL_TABLE | VIEW |
MATERIALIZED_VIEW | SEQUENCE | ADVANCED_QUEUE | VARYING_ARRAY |
NESTED_TABLE | OBJECT_TYPE | ACTIVITY_TEMPLATE | FUNCTION )
"QUOTED_STRING"
setStrategyClause = ( RECONCILE_STRATEGY | SYNCHRONIZE_STRATEGY )
"retrieveReconcileStrategyClause" | MATCHING_STRATEGY
"retrieveMatchingStrategyClause"
retrieveReconcileStrategyClause = "QUOTED_STRING"
retrieveMatchingStrategyClause = "QUOTED_STRING"
Examples
OMBSYNCHRONIZE EXTERNAL_TABLE 'et1' TO EXTERNAL_TABLE 'et2'
USE (RECONCILE_STRATEGY 'MERGE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_NAME')
OMBSYNCHRONIZE MAPPING 'm1' OPERATOR 'o1' TO TABLE 't1'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY
'MATCH_BY_OBJECT_NAME')
OMBSYNCHRONIZE MAPPING 'm1' OPERATOR 'o1' TO FLAT_FILE 'f1'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY
'MATCH_BY_OBJECT_NAME')
OMBSYNCHRONIZE MAPPING 'm1' OPERATOR 'o1' TO MAPPING 'm1' OPERATOR 'o2'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_ID')
OMBSYNCHRONIZE ITEM_FOLDER 'F1'
OMBSYNCHRONIZE TABLE 't1' TO DATA_AUDITOR 'a1' OPERATOR 'o2'
USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_ID')
For Item Folder synchronization the source is obtained from the repository.
For simple item folders the source
is the table that the item folder is based on. For complex item folders
the source is the dependent folders.
The user does not have to specify the source.
Purpose
Extracts business names and descriptions from a metadata loader file to an XLIFF translation file.
Prerequisites
None.
Syntax
mdlExtractCommand = ( EXTRACT [ FROM ] MDL_FILE "QUOTED_STRING" [ TO ]
"extractTranslateFileClause" [ "setExtractOptions" ] [
"componentsClause" ] [ "extractControlFileClause" ] [
"extractOutputLogClause" ] )
extractTranslateFileClause = TRANSLATE_FILE "QUOTED_STRING"
setExtractOptions = SET OPTIONS "(" "extractOptionNameList" ")" VALUES "("
"extractOptionValueList" ")"
componentsClause = COMPONENTS "(" "componentsList" ")"
extractControlFileClause = CONTROL_FILE "QUOTED_STRING"
extractOutputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
extractOptionNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
extractOptionValueList = "extractOptionValue" { "," "extractOptionValue" }
componentsList = "objectTypeValue" "QUOTED_STRING" { "," "objectTypeValue"
"QUOTED_STRING" }
extractOptionValue = ( "QUOTED_STRING" )
objectTypeValue = ( PROJECT | ORACLE_MODULE | TABLE | VIEW | SEQUENCE |
MATERIALIZED_VIEW | FUNCTION | PROCEDURE | PACKAGE | DIMENSION | CUBE
| ADVANCED_QUEUE | STREAMS_QUEUE | MAPPING | REAL_TIME_MAPPING |
PROCESS_FLOW_MODULE | PROCESS_FLOW_PACKAGE | PROCESS_FLOW | SAP_MODULE
| CMI_MODULE | GATEWAY_MODULE | EXTERNAL_TABLE | FLAT_FILE_MODULE |
FLAT_FILE | BUSINESS_DEFINITION_MODULE | BUSINESS_PRESENTATION_MODULE
| ITEM_FOLDER | LIST_OF_VALUES | DRILL_TO_DETAIL |
ALTERNATIVE_SORT_ORDER | DRILL_PATH | BUSINESS_AREA |
PRESENTATION_TEMPLATE | LOCATION | CONNECTOR | CONTROL_CENTER |
CONFIGURATION | COLLECTION | SNAPSHOT | ROLE | USER | ICONSET |
TRANSFORMATION_MODULE | CALENDAR_MODULE | CALENDAR_FOLDER | CALENDAR |
EXPERT_MODULE | EXPERT | DATA_RULE_MODULE | DATA_RULE | DATA_AUDITOR
| STREAMS_CAPTURE_PROCESS | QUEUE_TABLE | QUEUE_PROPAGATION |
OBJECT_TYPE | NESTED_TABLE | VARYING_ARRAY | DEPLOYMENT | DATA_PROFILE
| PROFILE_REFERENCE | PLSQL_TABLE_TYPE | PLSQL_RECORD_TYPE |
PLSQL_REF_CURSOR_TYPE | PLUGGABLE_MAPPING | PLUGGABLE_MAPPING_FOLDER |
CMI_DEFINITION | ACTIVITY_TEMPLATE | ACTIVITY_TEMPLATE_FOLDER |
TRANSPORTABLE_MODULE )
Keywords And Parameters
mdlExtractCommand
Extract business names and descriptions from a metadata loader file to an
XLIFF translation file.
QUOTED_STRING
Enclose the name of the source metadata loader file in single quotes.
extractTranslateFileClause
Specify the name of the translation file created by extract.
QUOTED_STRING
Enclose the name of the translation file to be created in single quotes.
setExtractOptions
Set options to be used for extract.
componentsClause
List components to be merged.
extractControlFileClause
Specify a control file with options not directly supported by OMBTRANSLATE
EXTRACT command.
QUOTED_STRING
Enclose the control file name in single quotes.
extractOutputLogClause
Extract log file for messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
extractOptionNameList
Comma separated list of extract option names (for example TARGETEQUALSSOURCE,
EXTRACTNULLS).
UNQUOTED_STRING
Valid option names are TARGETEQUALSSOURCE, EXTRACTNULLS, MAPPINGDETAILS,
DTD.
extractOptionValueList
Comma separated list of extract option values (for example 'Y', 'Y').
componentsList
Comma separated list of components to be merged.
QUOTED_STRING
Name of an object (for example 'TABLE_Y').
extractOptionValue
Value for an option in list (for example 'Y').
QUOTED_STRING
Enclose the option value in single quotes.
objectTypeValue
Object type to be merged (for example TABLE, VIEW and so on).
Examples
OMBTRANSLATE EXTRACT FROM MDL_FILE 'd:/mdl/exp1.mdl' TO TRANSLATE_FILE
'd:/mdl/exp1.xlf' OUTPUT LOG TO 'd:/mdl/exp1_extract.log'
OMBTRANSLATE EXTRACT FROM MDL_FILE 'd:/mdl/exp1.mdl' TO TRANSLATE_FILE
'd:/mdl/exp1.xlf' SET OPTIONS(TARGETEQUALSSOURCE, EXTRACTNULLS) VALUES
("Y", "Y")
See Also
OMBTRANSLATE MERGE
Purpose
Merges translated business names and descriptions from an XLIFF translation file into a metadata loader file.
Prerequisites
None.
Syntax
mdlMergeCommand = ( MERGE [ FROM ] MDL_FILE "QUOTED_STRING"
"mergeTranslateFileClause" [ TO ] "mergedMDLFileClause" [
"setMergeOptions" ] [ "componentsClause" ] [ "mergeControlFileClause"
] [ "mergeOutputLogClause" ] )
mergeTranslateFileClause = TRANSLATE_FILE "QUOTED_STRING"
mergedMDLFileClause = MERGED_MDL_FILE "QUOTED_STRING"
setMergeOptions = SET OPTIONS "(" "extractOptionNameList" ")" VALUES "("
"extractOptionValueList" ")"
componentsClause = COMPONENTS "(" "componentsList" ")"
mergeControlFileClause = CONTROL_FILE "QUOTED_STRING"
mergeOutputLogClause = OUTPUT LOG [ TO ] "QUOTED_STRING"
extractOptionNameList = "UNQUOTED_STRING" { "," "UNQUOTED_STRING" }
extractOptionValueList = "extractOptionValue" { "," "extractOptionValue" }
componentsList = "objectTypeValue" "QUOTED_STRING" { "," "objectTypeValue"
"QUOTED_STRING" }
extractOptionValue = ( "QUOTED_STRING" )
objectTypeValue = ( PROJECT | ORACLE_MODULE | TABLE | VIEW | SEQUENCE |
MATERIALIZED_VIEW | FUNCTION | PROCEDURE | PACKAGE | DIMENSION | CUBE
| ADVANCED_QUEUE | STREAMS_QUEUE | MAPPING | REAL_TIME_MAPPING |
PROCESS_FLOW_MODULE | PROCESS_FLOW_PACKAGE | PROCESS_FLOW | SAP_MODULE
| CMI_MODULE | GATEWAY_MODULE | EXTERNAL_TABLE | FLAT_FILE_MODULE |
FLAT_FILE | BUSINESS_DEFINITION_MODULE | BUSINESS_PRESENTATION_MODULE
| ITEM_FOLDER | LIST_OF_VALUES | DRILL_TO_DETAIL |
ALTERNATIVE_SORT_ORDER | DRILL_PATH | BUSINESS_AREA |
PRESENTATION_TEMPLATE | LOCATION | CONNECTOR | CONTROL_CENTER |
CONFIGURATION | COLLECTION | SNAPSHOT | ROLE | USER | ICONSET |
TRANSFORMATION_MODULE | CALENDAR_MODULE | CALENDAR_FOLDER | CALENDAR |
EXPERT_MODULE | EXPERT | DATA_RULE_MODULE | DATA_RULE | DATA_AUDITOR
| STREAMS_CAPTURE_PROCESS | QUEUE_TABLE | QUEUE_PROPAGATION |
OBJECT_TYPE | NESTED_TABLE | VARYING_ARRAY | DEPLOYMENT | DATA_PROFILE
| PROFILE_REFERENCE | PLSQL_TABLE_TYPE | PLSQL_RECORD_TYPE |
PLSQL_REF_CURSOR_TYPE | PLUGGABLE_MAPPING | PLUGGABLE_MAPPING_FOLDER |
CMI_DEFINITION | ACTIVITY_TEMPLATE | ACTIVITY_TEMPLATE_FOLDER |
TRANSPORTABLE_MODULE )
Keywords And Parameters
mdlMergeCommand
Merge business names and descriptions from an XLIFF translation file into a
metadata loader file.
QUOTED_STRING
Enclose the name of the source metadata loader file in single quotes.
mergeTranslateFileClause
Specify the name of the source translation file.
QUOTED_STRING
Enclose the name of the source translation file in single quotes.
mergedMDLFileClause
Specify the name of the merged metadata loader file which will contain the
translation information.
QUOTED_STRING
Enclose the name of the merged metadata loader file in single quotes.
setMergeOptions
Set options to be used for merge.
componentsClause
List components to be merged.
mergeControlFileClause
Specify a control file with merge options not directly supported by
OMBTRANSLATE EXTRACT command.
QUOTED_STRING
Enclose the control file name in single quotes.
mergeOutputLogClause
Merge log file for merge messages and statistics.
QUOTED_STRING
Enclose the log file name in single quotes.
extractOptionNameList
Comma separated list of extract option names (for example TARGETEQUALSSOURCE,
EXTRACTNULLS).
UNQUOTED_STRING
Valid option names are TARGETEQUALSSOURCE, EXTRACTNULLS, MAPPINGDETAILS,
DTD.
extractOptionValueList
Comma separated list of extract option values (for example 'Y', 'Y').
componentsList
Comma separated list of components to be merged.
QUOTED_STRING
Name of an object (for example 'TABLE_Y').
extractOptionValue
Value for an option in list (for example 'Y').
QUOTED_STRING
Enclose the option value in single quotes.
objectTypeValue
Object type to be merged (for example TABLE, VIEW and so on).
Examples
OMBTRANSLATE MERGE FROM MDL_FILE 'd:/mdl/exp1.mdl' TRANSLATE_FILE
'd:/mdl/exp1_de.xlf' TO MERGED_MDL_FILE 'd:/mdl/exp1_de.mdl' OUTPUT LOG TO
'd:/mdl/exp1_de_merge.log'
OMBTRANSLATE MERGE FROM MDL_FILE 'd:/mdl/exp1.mdl' TRANSLATE_FILE
'd:/mdl/exp1_de.xlf' TO MERGED_MDL_FILE 'd:/mdl/exp1_de.mdl'
See Also
OMBTRANSLATE EXTRACT
Purpose
To undefine an association between two classes (types).
Prerequisites
Association definition to be undefined should already exist. This command
can be executed for any association definition regardless of current
context. Only user defined associations can be undefined. User must have
CREATE_EXTENSIONMODEL system privilege and has to be connected in single
user mode to run this command.
Syntax
parseUndefineAssociationCommand = OMBUNDEFINE ASSOCIATION_DEFINITION
"QUOTED_STRING"
Keywords And Parameters
parseUndefineAssociationCommand
Undefine an association.
Examples
OMBUNDEFINE ASSOCIATION_DEFINITION 'UD_ASSOC3'
This will undefine association 'UD_ASSOC3'.
See Also
OMBDEFINE ASSOCIATION_DEFINITION, OMBDESCRIBE ASSOCIATION_DEFINITION
Purpose
To undefine a class.
Prerequisites
Class definition to be undefined should already exist. This command can be
executed for any class definition regardless of current context. Only user
defined classes can be undefined. User must have CREATE_EXTENSIONMODEL
system privilege and has to be connected in single user mode to run this
command.
Syntax
parseUndefineClassCommand = OMBUNDEFINE CLASS_DEFINITION "QUOTED_STRING" [
CASCADE ]
Keywords And Parameters
parseUndefineClassCommand
Undefine a class.
Examples
OMBUNDEFINE CLASS_DEFINITION 'UD_MY_CLASS'
This will undefine class 'UD_MY_CLASS'.
See Also
OMBDEFINE CLASS_DEFINITION, OMBDESCRIBE CLASS_DEFINITION
Purpose
Unlock one or more objects, previously locked by OMBLOCK command. Note that if the object(s) have been modified, save or revert is
also required in order for the lock(s) to be released.
Prerequisites
The object(s) should have been locked previously using OMBLOCK command.
Syntax
parseUnLockCommand = OMBUNLOCK "parseTypeNameList"
parseTypeNameList = "objectType" "QUOTED_STRING" { "," "objectType"
"QUOTED_STRING" }
objectType = ( ADVANCED_QUEUE | STREAMS_QUEUE | BUSINESS_AREA | COLLECTION
| CONNECTOR | CONFIGURATION | DEPLOYMENT | CUBE | DIMENSION | EXPERT
| EXPERT_MODULE | EXTERNAL_TABLE | FLAT_FILE_MODULE | FLAT_FILE |
FUNCTION | TABLE_FUNCTION | GATEWAY_MODULE |
BUSINESS_DEFINITION_MODULE | REGISTERED_FUNCTION | LOCATION | MAPPING
| MATERIALIZED_VIEW | OBJECT_TYPE | VARYING_ARRAY | NESTED_TABLE |
ORACLE_MODULE | PACKAGE | PROCEDURE | PROCESS_FLOW |
PROCESS_FLOW_MODULE | PROCESS_FLOW_PACKAGE | PROJECT | ITEM_FOLDER |
DRILL_PATH | LIST_OF_VALUES | DRILL_TO_DETAIL | ALTERNATIVE_SORT_ORDER
| PRESENTATION_TEMPLATE | BUSINESS_PRESENTATION_MODULE |
CONTROL_CENTER | SAP_MODULE | CMI_MODULE | SEQUENCE | TABLE | VIEW |
CMI_DEFINITION | PLSQL_RECORD_TYPE | "UNQUOTED_STRING" )
Keywords And Parameters
parseUnLockCommand
Specify unlock command.
parseTypeNameList
Specify the object or the list of objects to be unlocked.
QUOTED_STRING
Name of the object to be unlocked. Can be specified as an absolute path or
as a path relative to the current context. However, there is the
restriction that all objects to be unlocked must be in the current project.
objectType
Type of the object to be unlocked.
Examples
OMBUNLOCK TABLE 'T1', VIEW '/MY_PROJECT/ORACLE_1/V1'
will unlock table 'T1' in the current module, and view 'V1' in Oracle
module 'ORACLE_1' from project 'MY_PROJECT'.
See Also
OMBLOCK
Purpose
Un-register a control center.
Prerequisites
Must be logged on as the owner of the repository and connected in a single
user mode.
Syntax
unRegisterControlCenterCommand = OMBUNREGISTER CONTROL_CENTER
"QUOTED_STRING"
Examples
OMBUNREGISTER CONTROL_CENTER 'MY_CONTROL_CENTER'
Purpose
Un-register a location with a Control Center.
Prerequisites
Must be in the context of a project and connected to a Control Center.
Syntax
unRegisterLocationCommand = OMBUNREGISTER LOCATION "QUOTED_STRING"
Examples
OMBUNREGISTER LOCATION 'MY_ORACLE_LOCATION'
Purpose
To unregister a specified Warehouse Builder user. This will not drop the user from database.
Prerequisites
A Warehouse Builder user can be unregistered from any context.
Syntax
parseUnregisterUserCommand = ( OMBUNREGISTER USER "QUOTED_STRING" [
IDENTIFIED BY "QUOTED_STRING" ] )
Keywords And Parameters
parseUnregisterUserCommand
This clause unregister a specified Warehouse user.
Examples
OMBUNREGISTER USER 'USER1'
will unregister user 'USER1'.
OMBUNREGISTER USER 'USER1' IDENTIFIED BY 'passwdOfUser1'
will unregistered user 'USER1'. The password provided from IDENTIFIED BY
clause will be used to clean up the target schema when unregister it if
USER1 is a target schema. If IDENTIFIED BY clause is ommited, Oracle
Warehouse Builder will try to retrieve this information from related
location if available, otherwise there will have some Oracle Warehouse
Builder objects left in the target schema. The IDENTIFIED BY clause is not
necessary if the user USER1 is not used as a target schema.
See Also
OMBREGISTER USER, OMBALTER USER, OMBRETRIEVE USER
Purpose
This command validates an repository object. The results are generated in a file in a user defined directory.
Prerequisites
In the context of a Oracle Module except when validating Project and Oracle
Module. To validate a Project the user needs to be in the Root context. To
validate Oracle Module the user needs to be in Project context.
Syntax
parseValidateCommand = OMBVALIDATE ( ( EXPERT | EXPERT_MODULE | TABLE |
VIEW | SEQUENCE | ORACLE_MODULE | COLLECTION | MATERIALIZED_VIEW |
TRANSPORTABLE_MODULE | BUSINESS_PRESENTATION_MODULE |
BUSINESS_DEFINITION_MODULE | DIMENSION | CUBE | DATA_AUDITOR | MAPPING
| REAL_TIME_MAPPING | PROJECT | OBJECT_TYPE | VARYING_ARRAY |
NESTED_TABLE | PACKAGE | FUNCTION | PROCEDURE | TABLE_FUNCTION |
EXTERNAL_TABLE | FLAT_FILE | FLAT_FILE_MODULE | PRESENTATION_TEMPLATE
| ALTERNATIVE_SORT_ORDER | LIST_OF_VALUES | DRILL_TO_DETAIL |
BUSINESS_AREA | DRILL_PATH | ITEM_FOLDER | REGISTERED_FUNCTION |
LOCATION | CONNECTOR | CONTROL_CENTER | CONFIGURATION | DEPLOYMENT |
PROCESS_FLOW_MODULE | PROCESS_FLOW | PROCESS_FLOW_PACKAGE |
ADVANCED_QUEUE | STREAMS_QUEUE | QUEUE_TABLE | QUEUE_PROPAGATION |
STREAMS_CAPTURE_PROCESS | PLSQL_RECORD_TYPE | PLSQL_TABLE_TYPE |
PLSQL_REF_CURSOR_TYPE | CALENDAR | CALENDAR_MODULE ) "QUOTED_STRING" [
"getOutputValidationResults" ] )
getOutputValidationResults = OUTPUT [ VALIDATION_RESULT ] TO (
"QUOTED_STRING" | ( FILE "QUOTED_STRING" ) ) WRITE ( ( "(" ( ( SUCCESS
| WARNING | ERROR ) [ "," ] )+ ")" ) | ALL | SUCCESS | WARNING |
ERROR )
Keywords And Parameters
parseValidateCommand
This command validates a repository object.
QUOTED_STRING
The name of the object.
getOutputValidationResults
This clause outputs the validation results to one or more files in the
specified folder.
QUOTED_STRING
A directory where validation results are stored.
Examples
OMBVALIDATE TABLE 'T1' OUTPUT VALIDATION_RESULT TO '/tmp' WRITE (SUCCESS,
ERROR)
See Also
OMBCOMPILE
|
 Copyright © 2000, 2006, Oracle. All rights reserved. Legal Notices |
|