This appendix contains the following topics:
When invoking the migration utility, the OWB Workspace Owner and its password are needed to connect to the OWB Repository. Each OWB Workspace Owner may have multiple workspaces. Only one workspace will be migrated with each migration. Therefore, one workspace name must be specified for each migration. Each OWB workspace will be migrated to ODI as one ODI Work repository.
If an OWB Workspace owner has multiple OWB Workspaces, each OWB Workspace should be migrated to an ODI Work repository of an ODI Master repository. The migration utility can only migrate at most one OWB Workspace at each time.
OWB Platforms and their associated data types are mapped to ODI Technologies and their associated data types. This platform and data type mapping is stored in a configuration file.
For the predefined platforms in OWB, the mappings to ODI can be found in the file PlatformMappingsForMigration.xml
located in the <ORACLE_HOME for OWB>
/owb/bin/admin
directory.
If a user has defined new or custom Platforms in OWB, the mapping of this platform and its data types to ODI technology and its data types can be defined in the same configuration file. The physical name of the OWB Platform should be specified in the mapping, and the internal name of the ODI technology should be used.
The following table shows the predefined OWB Platform to ODI Technology mappings.
OWB Platform | ODI Technology |
---|---|
GENERIC |
Generic SQL |
ORACLE (including Oracle Workflow, Apps Concurrent manager) |
Oracle |
DB2UDB |
IBM DB2 UDB |
SQLSERVER |
Microsoft SQL Server |
SAP |
SAP ABAP |
FILE |
File |
OBIEE, OBISE, J2EE |
These are not migrated. |
Data type mapping differs for each OWB Platform mapping. The following tables show the data type mappings for each predefined OWB Platform.
If an OWB data type that has no mapping in ODI is used in Data Objects like Table, View, Materialized View, and External Table, the data object is reported as not migrated.
If an OWB data type that has no mapping in ODI is used in a Mapping Attribute, the data type of the mapping attribute is not set.
OWB Data Type (GENERIC) | ODI Data Type (Generic SQL) |
---|---|
BIGINT |
BIGINT |
BINARY |
BINARY |
BINARY_DOUBLE |
BINARY_DOUBLE |
BINARY_FLOAT |
BINARY_FLOAT |
BLOB |
BLOB |
BOOLEAN |
CHAR |
CHAR |
CHAR |
CLOB |
CLOB |
DATE |
DATE |
DATETIME |
DATETIME |
DECIMAL |
DECIMAL |
DOUBLE |
DOUBLE |
FLOAT |
FLOAT |
IMAGE |
BLOB |
INTEGER |
INTEGER |
INTERVAL DAY TO SECOND |
INTERVAL DAY TO SECOND |
INTERVAL YEAR TO MONTH |
INTERVAL YEAR TO MONTH |
LONG |
CLOB |
LONGVARBINARY |
BLOB |
LONGVARCHAR |
CLOB |
MONEY |
MONEY |
NCHAR |
NCHAR |
NCLOB |
NCLOB |
NTEXT |
NCLOB |
NUMERIC |
NUMERIC |
NVARCHAR |
NVARCHAR |
NVARCHAR(MAX) |
NCLOB |
REAL |
REAL |
SMALLINT |
SMALLINT |
TEXT |
CLOB |
TIME |
TIME |
TIMESTAMP |
TIMESTAMP |
TIMESTAMP WITH TIME ZONE |
TIMESTAMP WITH TIME ZONE |
TINYINT |
TINYINT |
VARBINARY |
VARBINARY |
VARBINARY(MAX) |
BLOB |
VARCHAR |
VARCHAR |
VARCHAR(MAX) |
CLOB |
XMLTYPE |
XMLTYPE |
OWB Data Type (ORACLE) | ODI Data Type (Oracle) |
---|---|
BINARY_DOUBLE |
BINARY_DOUBLE |
BINARY_FLOAT |
BINARY_FLOAT |
BLOB |
BLOB |
CHAR |
CHAR |
CLOB |
CLOB |
DATE |
DATE |
FLOAT |
FLOAT |
INTEGER |
NUMBER |
INTERVAL DAY TO SECOND |
INTERVAL DAY TO SECOND |
INTERVAL YEAR TO MONTH |
INTERVAL YEAR TO MONTH |
LONG |
LONG |
LONG RAW |
LONG RAW |
MDSYS.SDOAGGRTYPE |
|
MDSYS.SDO_DIM_ARRAY |
|
MDSYS.SDO_DIM_ELEMENT |
|
MDSYS.SDO_ELEM_INFO_ARRAY |
|
MDSYS.SDO_GEOMETRY |
MDSYS.SDO_GEOMETRY |
MDSYS.SDO_ORDINATE_ARRAY |
|
MDSYS.SDO_POINT_TYPE |
|
NCHAR |
NCHAR |
NCLOB |
NCLOB |
NUMBER |
NUMBER |
NVARCHAR2 |
NVARCHAR2 |
RAW |
RAW |
ROWID |
ROWID |
SYS.ANYDATA |
|
SYS.AQ$_JMS_BYTES_MESSAGE |
|
SYS.AQ$_JMS_MAP_MESSAGE |
|
SYS.AQ$_JMS_MESSAGE |
|
SYS.AQ$_JMS_STREAM_MESSAGE |
|
SYS.AQ$_JMS_TEXT_MESSAGE |
|
SYS.LCR$_ROW_RECORD |
|
TIMESTAMP |
TIMESTAMP |
TIMESTAMP WITH LOCAL TIME ZONE |
TIMESTAMP WITH LOCAL TIME ZONE |
TIMESTAMP WITH TIME ZONE |
TIMESTAMP WITH TIME ZONE |
UROWID |
UROWID |
VARCHAR |
VARCHAR2 |
VARCHAR2 |
VARCHAR2 |
XMLFORMAT |
XMLFORMAT |
XMLTYPE |
XMLTYPE |
OWB Data Type (DB2UDB) | ODI Data Type (IBM DB2 UDB) |
---|---|
BIGINT |
BIGINT |
BLOB |
BLOB |
CHARACTER |
CHAR |
CLOB |
CLOB |
DATE |
DATE |
DBCLOB |
DBCLOB |
DECIMAL |
DECIMAL |
DOUBLE |
DOUBLE |
FLOAT |
FLOAT |
GRAPHIC |
GRAPHIC |
INTEGER |
INTEGER |
LONG VARCHAR |
LONG VARCHAR |
LONG VARGRAPHIC |
LONG VARGRAPHIC |
NUMERIC |
NUMERIC |
REAL |
REAL |
SMALLINT |
SMALLINT |
TIME |
TIME |
TIMESTAMP |
TIMESTAMP |
VARCHAR |
VARCHAR |
VARGRAPHIC |
VARGRAPHIC |
XML |
OWB Data Type (SQLSERVER) | ODI Data Type (Microsoft SQL Server) |
---|---|
BIGINT |
BIGINT |
BINARY |
BINARY |
BIT |
BIT |
CHAR |
CHAR |
DATETIME |
DATETIME |
DECIMAL |
DECIMAL |
FLOAT |
FLOAT |
IMAGE |
IMAGE |
INT |
INT |
MONEY |
MONEY |
NCHAR |
NCHAR |
NTEXT |
NTEXT |
NUMERIC |
NUMERIC |
NVARCHAR |
NVARCHAR |
NVARCHAR(MAX) |
NTEXT |
REAL |
REAL |
SMALLDATETIME |
SMALLDATETIME |
SMALLINT |
SMALLINT |
SMALLMONEY |
SMALLMONEY |
SQL_VARIANT |
SQL_VARIANT |
TEXT |
TEXT |
TIMESTAMP |
TIMESTAMP |
TINYINT |
TINYINT |
UNIQUEIDENTIFIER |
UNIQUEIDENTIFIER |
VARBINARY |
VARBINARY |
VARBINARY(MAX) |
IMAGE |
VARCHAR |
VARCHAR |
VARCHAR(MAX) |
TEXT |
XML |
OWB Data Type (FILE) | ODI Data Type (File) |
---|---|
BYTEINT |
BINARY_SIGNED_BIG_ENDIAN |
CHAR |
STRING |
DECIMAL |
EBCDIC_SIGNED_ZONED_DECIMAL |
DATE |
DATE |
DECIMAL EXTERNAL |
NUMERIC |
DOUBLE |
NUMERIC |
FLOAT |
NUMERIC |
FLOAT EXTERNAL |
NUMERIC |
INTEGER |
BINARY_SIGNED_BIG_ENDIAN |
INTEGER UNSIGNED |
BINARY_UNSIGNED_BIG_ENDIAN |
INTEGER EXTERNAL |
NUMERIC |
INTERVAL DAY TO SECOND |
DATE |
INTERVAL YEAR TO MONTH |
DATE |
SMALLINT |
BINARY_SIGNED_BIG_ENDIAN |
SMALLINT UNSIGNED |
BINARY_UNSIGNED_BIG_ENDIAN |
TIMESTAMP |
DATE |
TIMESTAMP WITH TIME ZONE |
DATE |
TIMESTAMP WITH LOCAL TIME ZONE |
DATE |
VARRAWC |
BINARY_SIGNED_BIG_ENDIAN |
VARCHAR |
STRING |
VARCHARC |
STRING |
ZONED EXTERNAL |
ASCII_SIGNED_ZONED_DECIMAL |
ZONED |
ASCII_SIGNED_ZONED_DECIMAL |
OWB Data Type (SAP) | ODI Data Type (SAP ABAP) |
---|---|
ACCP |
ACCP |
CHAR |
CHAR |
CLNT |
CLNT |
CUKY |
CUKY |
CURR |
CURR |
DATS |
DATS |
DEC |
DEC |
FLTP |
FLTP |
INT1 |
INT1 |
INT2 |
INT2 |
INT4 |
INT4 |
LANG |
LANG |
LCHR |
LCHR |
LRAW |
LRAW |
NUMC |
NUMC |
PREC |
PREC |
QUAN |
QUAN |
RAW |
RAW |
TIMS |
TIMS |
UNIT |
UNIT |
Each OWB Location is associated with an OWB Platform or equivalent ODI technology. Hence OWB location will be migrated to an ODI Data Server under the equivalent ODI technology.
Location Name will be migrated to ODI Data Server Name. Since OWB Location Name is unique within an OWB Workspace, while ODI Data Server Name is unique within the master repository, when there are several OWB workspaces for a Workspace Owner, each OWB Workspace should be migrated to a different ODI Master repository to avoid name conflicts.
The following table shows mapping of properties of OWB Location to properties of ODI Data Server:
OWB Property Name | ODI Property Name | Note |
---|---|---|
- |
dataServerId (I_CONNECT) |
This number will be generated. |
platform |
technology (I_TECHNO) |
- |
Name |
name (CON_NAME) |
- |
Driver Class |
jdbcDriverName (JAVA_DRIVER) |
- |
Url |
jdbcUrl (JAVA_URL) |
- |
User Name (CONNECT_AS_USER) |
username (USER_NAME) |
- |
Batch Update Size (UPDATE_SIZE) |
batchUpdateSize (BATCH_UPDATE_SIZE) |
- |
Array Fetch Size (FETCH_SIZE) |
fetchArraySize (FETCH_ARRAY_SERV) |
- |
Schema |
schemaName (SCHEMA_NAME) |
- |
Work Schema |
workSchemaName (WSCHEMA_NAME) |
- |
Catalog |
catalogName (CATALOG_NAME) |
- |
Work Catalog |
workCatalogName (WCATALOG_NAME) |
- |
For OWB Location using Database Link as the Connection Type, the location will be migrated to a new ODI Data Server, with the location name as the data server name. Other information for the location will not be migrated.
For File Location using FTP as the Connection Type, the location will be migrated to a new ODI Data Server with the location name as the data server name. Other information for the location will not be migrated.
OWB Modules will be migrated to ODI Models.
To create a unique model name, the ODI Model name will be a concatenation of OWB Module Name and OWB Project name. If the resulting name is longer than the allowed length in ODI Model name, the resulting name will be trimmed.
OWB Property Name | ODI Property Name | Note |
---|---|---|
- |
modelId (I_MOD) |
This number will be generated by the migration utility. |
Name |
name (MOD_NAME) |
If the length of the name exceeds the maximum limit, then the name will be truncated. |
Platform |
technology (TECH_INT_NAME) |
- |
- |
logicalSchema (LSCHEMA_NAME) |
Will be created according to the OWB module name. |
Name |
code (COD_MOD) |
If the length of the code exceeds the maximum limit allowed in ODI model code, then the code will be truncated. |
Project |
parentModelFolder (I_MOD_FOLDER) |
- |
description |
description (I_TXT_MOD) |
- |
Some OWB Modules will also be migrated to ODI as ODI Folders, in addition to ODI Models. The following OWB modules will also be migrated as ODI Folders:
Oracle Database Module
Template Mapping Module
OWB Oracle Database Module will be migrated as ODI Model where the OWB Data Objects are migrated to, and also as ODI Folder where OWB mappings are migrated to.
OWB Template Mapping Module and Pluggable Mapping Folder will be migrated as ODI Folder.
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (FOLDER_NAME) |
OWB supported a list of Data Locations for use with a module but only one location is selected to use at a time. This location is called the active location. During migration, only the active location will be migrated to ODI. The location is migrated as ODI Data Server. Corresponding to the location user name, a new ODI Physical Schema will be created in ODI if one does not exist already. The new ODI Physical Schema will be from the Location Schema of OWB Database Location, or the directory path for File Location.
Corresponding to the physical schema, a logical schema will be created in ODI if none with the same name as the Model name exists. The logical schema will set to "LS_" plus model name, and will be associated with the physical schema in the global context.
OWB Project will be migrated as ODI Project.
OWB Property Name | ODI Property Name | Note |
---|---|---|
- |
projectId (I_PROJECT) |
This number will be generated. |
Name |
Name (PROJECT_NAME) |
- |
Name |
code (PROJECT_CODE) |
- |
Two types of OWB Folders will be migrated to ODI:
OWB Pluggable Mapping Folders
OWB Pluggable Mapping Folders are migrated to ODI Folders; the name of the OWB Pluggable Mapping Folder will be the name of the ODI Folder.
OWB Pluggable Mapping Standalone Folders
Pluggable mappings in this OWB folder will be migrated to an ODI Folder named STAND_ALONE.
OWB Table is migrated to ODI Datastore. The following related attributes of tables are migrated:
Columns
Keys
Indexes
Attribute Sets and Data Rules are not migrated.
For Partitions, the partition name and the description are migrated, other properties are not migrated.
Attributes or properties of OWB Table are migrated to ODI Datastore.
Attributes or properties of OWB Table Columns are migrated to ODI Datastore Columns as described in Table B-1.
OWB Table supports these types of keys: Primary Key, Unique Key, Foreign Key, and Constraint.
The attributes/properties of OWB Table Primary Keys and Unique Keys are migrated to ODI Keys as described in Table B-4.
The attributes/properties of OWB Table Constraints are migrated to ODI Condition as described in Table B-5.
The attributes/properties of OWB Table Foreign Keys are migrated to ODI Reference as described in Table B-6.
The attributes/properties of Indexes are migrated to ODI Datastore Key as described in Table B-7, which lists the mappings between the OWB Index and ODI Key.
OWB supports four types of indexes: unique, non-unique, bitmap, and function-based. A unique index will be mapped to OdiKey, and the key type will be set to ALTERNATE_KEY. A non-unique index will be mapped to OdiKey, and the key type will be set to INDEX. Bitmap and function-based keys are not migrated.
OWB View is migrated to ODI Datastore. The following related attributes of OWB View are migrated:
Columns
Keys
Attribute Sets and Data Rules are not migrated.
Attributes or properties of OWB View are migrated to ODI Datastore.
Attributes or properties of OWB View Columns are migrated to ODI Datastore Columns as described in Table B-1.
OWB Table supports these types of keys: Primary Key, Unique Key, Foreign Key, and Constraint.
The attributes/properties of OWB View Primary/Unique Keys are migrated to ODI Keys as described in Table B-4.
The attributes/properties of OWB View Constraints are migrated to ODI Condition as described in Table B-5.
The attributes/properties of OWB View Foreign Keys are migrated to ODI Reference as described in Table B-6.
OWB Materialized View is migrated to ODI Datastore. The following related attributes of Materialized views are migrated:
Columns
Keys
Indexes
Attribute Sets and Data Rules are not migrated.
For Partitions, the partition name and the description are migrated, other properties are not migrated.
Attributes or properties of OWB Materialized View are migrated to ODI Datastore.
Attributes or properties of OWB Materialized View Columns are migrated to ODI Datastore Columns as described in Table B-1.
OWB Materialized View supports these types of keys: Primary Key, Unique Key, Foreign Key, and Constraint.
The attributes/properties of OWB Materialized View Primary Keys and Unique Keys are migrated to ODI Keys as described in Table B-4.
The attributes/properties of OWB Materialized View Constraints are migrated to ODI Condition as described in Table B-5.
The attributes/properties of OWB Materialized View Foreign Keys are migrated to ODI Reference as described in Table B-6.
The attributes/properties of Indexes are migrated to ODI Datastore Key as described in Table B-7, which lists the mappings between the OWB Index and ODI Key.
OWB External Table is migrated to ODI Datastore. The following related attributes of External Table are migrated:
Columns
Data Rules are not migrated. Associated locations will be migrated as ODI Data Server if the migration configuration option MIGRATE_DEPENDENCIES is set to true.
Attributes or properties of OWB External Table are migrated to ODI Datastore.
Attributes or properties of OWB External Table Columns are migrated to ODI Datastore Columns as described in Table B-1.
OWB External Table has association to OWB FLAT FILE and its access parameters. These associations will not be migrated to ODI.
OWB Flat File is migrated to ODI Datastore. The following related attributes of OWB Files are migrated:
Records
Fields
Attributes or properties of OWB Flat File are migrated to ODI Datastore.
OWB Flat File may contain one or more Records. Each Record will be migrated as one ODI Datastore. The naming convention for the ODI Datastore name is <
FlatFileName
>_<
RecordName
>
.
Attributes or properties of OWB File Record are migrated to ODI Datastore Columns as described in Table B-3.
Attributes or properties of OWB File Record Field are migrated to ODI Datastore Columns as described in section Table B-2.
OWB Sequence is migrated to ODI Sequence (Native sequence). OWB Sequence contains Columns, which are not migrated to ODI.
Attributes or properties of OWB Sequence are migrated to ODI Sequence as described in Table B-9.
OWB dimensions are placed under the Oracle database module. ODI dimension objects would be placed under a specific dimensional model. If dimensions or cubes exist in OWB Oracle database module, then that Oracle database module is migrated to an ODI dimension model. To reduce the name conflicts, the naming convention of the migrated ODI dimension model is in the form of <Oracle database module name>_<OWB project name>.
For example, In a project named BI_DEMO
, if there is an Oracle module named SALES_WH
then SALES_WH_BI_DEMO
will be used for the ODI dimension model name after migration. If the length of the name exceeds the maximum length allowed (the maximum length is 35), then the proposed name will be truncated. If the name needs be to unique and it has already been occupied, a unique name suffixed by a digit is generated based on the proposed name. This naming rule is used for all migration objects when the object name needs to be unique and has a maximum length limitation.
Dimension :
OWB dimension will be migrated to ODI dimension.
Cube:
OWB Cube will be migrated to ODI Cube.
Table B-1 OWB Table Column to ODI Datastore Column
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (COL_NAME) |
- |
- |
COL_DESC |
Short description. |
TypeDefinition |
dataTypeCode (SOURCE_DT) |
- |
Position |
position (POS) |
- |
Length |
length (LONGC) |
- |
Precision |
Length (LONGC) |
- |
Scale |
scale (SCALEC) |
- |
Nullable |
mandatory (COL_MANDATORY) |
- |
dafaultValue |
defaultValue (DEF_VALUE) |
If the length of the default value exceeds the maximum length allowed in ODI, then the default value will not be migrated. |
- |
scdType (SCD_COL_TYPE) |
- |
description |
description (I_TXT_COL_DESC) |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
fractionalsecondsprecision |
length (LONGC) |
- |
Table B-2 OWB File Record Field to ODI Datastore Column
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (COL_NAME) |
- |
TypeDefinition |
dataTypeCode (SOURCE_DT) |
- |
Position |
position (POS) |
- |
Sqlprecision |
- |
- |
Sqlscale |
- |
- |
Precision |
bytes (BYTES) |
- |
Scale |
scale (SCALEC) |
- |
StartPostion |
startPosition (FILE_POS) |
Only for file/record. |
FieldLength |
bytes (BYTES) |
Only for file/record. |
Nullable |
mandatory (COL_MANDATORY) |
- |
dafaultValue |
defaultValue (DEF_VALUE) |
- |
description |
description (I_TXT_COL_DESC) |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
sqllength |
- |
- |
mask |
format (SNP_COL.COL_FORMAT) |
- |
Table B-3 OWB File Record to ODI Datastore Column
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
name (TABLE_NAME) |
- |
Name |
defaultAlias (TABLE_ALIAS) |
- |
classname |
dataStoreType (TABLE_TYPE) |
- |
Description |
Description (TABLE_DESC) |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
Prefix |
- |
- |
Position |
- |
- |
RecordClassifierValue |
- |
- |
RecordSize |
- |
- |
Table B-4 OWB Key to ODI Key
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (KEY_NAME) |
- |
Primarykey |
keyType (CONS_TYPE) |
keyType: PRIMARY_KEY(PK) ALTERNATE_KEY(AK) |
Appslabel |
- |
- |
Table B-5 OWB Check Constraint to ODI Condition
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (KEY_NAME) |
- |
Primarykey |
keyType (CONS_TYPE) |
keyType: PRIMARY_KEY(PK) ALTERNATE_KEY(AK) |
Appslabel |
- |
- |
Table B-6 OWB ForeignKey to ODI Reference
OWB Property Name | ODI Property Name | Note |
---|---|---|
- |
referenceId (I_JOIN) |
This number will be generated. |
Name |
name (FK_NAME) |
- |
Should map to DB_REFERENCE |
referenceType (FK_TYPE) |
referenceType: DB_REFERENCE, ODI_REFERENCE, COMPLEX_REFERENCE |
- |
primaryDataStore (I_TABLE_PK) |
Find the table by Unique key. |
module |
primaryModel (PK_I_MOD) |
- |
- |
primaryDataStoreSchemaName (PK_SCHEMA) |
Find the schema based on the model of the primary table. |
- |
primaryDataStoreName (PK_TABLE_NAME) |
Find primary table name by unique key. |
- |
primaryDataStoreAlias (PK_TABLE_ALIAS) |
Find the alias by primary data store. |
Appslabel |
- |
- |
Mandatory |
- |
- |
OnetoOne |
- |
- |
Table B-7 OWB Index to ODI Key
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name (KEY_NAME) |
|
Indextype |
keyType (CONS_TYPE) |
keyType: ALTERNATE_KEY(AK) INDEX(I) |
Appslabel |
- |
- |
Expression |
- |
- |
LocalIndex |
- |
- |
LocalPartitionType |
- |
- |
Table B-8 OWB Partition to ODI Partition
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
name (PARTITION_NAME) |
- |
Description |
Description (PARTITION_DESC) |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
classname |
- |
- |
Attribute |
- |
- |
Autosubpartitionordering |
- |
- |
Hashsubpartitioncount |
- |
- |
IsDefault |
- |
- |
IsSubPartition |
- |
- |
PartitionOrder |
- |
- |
Table B-9 OWB Sequence to ODI Sequence
OWB Property Name | ODI Property Name | Note |
---|---|---|
- |
sequenceId (SEQ_ID) |
This number will be generated. |
Project |
project (I_PROJECT) |
- |
Name |
SEQ_NAME |
- |
Increment By |
incrementValue (INCR) |
Retrieve from active configuration. |
- |
seqType (SEQ_TYPE) |
OWB sequence is migrated as project sequence. |
- |
type (IND_STD) |
OWB sequence is migrated as native sequence. |
- |
logicalSchemaName (LSCHEMA_NAME) |
Via OWB module, the ODI Model's logical schema is used here. |
Name |
nativeSequenceName (DB_SEQ_NAME) |
- |
Prefix |
- |
- |
ExternalElementName |
- |
- |
Proxy |
- |
- |
SynonymFor |
- |
- |
ValidationResult |
- |
- |
1. Dimension
Table B-10 General Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name |
|
Description |
Description |
|
Dimension Role |
Not Migrated |
Table B-11 Storage Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
OWB ROLAP Dimension |
||
Implementation Type |
Implementation Type. It has two types of implementation — Star (for one binding table) Snowflake (for more than one binding tables) |
ODI dimension has no implementation type called Manual. If the OWB dimension is set to Manual implementation, according to the amount of the binding tables on OWB dimension, the implementation type is migrated to Star or Snowflake for ODI dimension. If there is only one binding table for OWB dimension, the implementation type is set to Star for ODI dimension, otherwise the implementation type is set to Snowflake. |
Create composite Unique Key |
Not Migrated |
|
OWB MLOAP Dimensions |
It has no binding tables. User needs to manually set the binding information after migration, if necessary. |
|
AW Name |
Not Migrated |
|
AW table space name |
Not Migrated |
|
Generate surrogate keys in the analytic workspace |
Not Migrated |
|
Use natural keys from data source |
Not Migrated |
All physical properties on OWB Dimension are not migrated.
SCD properties are set directly on ODI dimension level attributes.
Table B-12 Orphan Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Orphan management for loading – Null parent key values |
Load Null Parent |
|
Orphan management for loading – Invalid parent values |
Load Invalid Parent |
|
Orphan management for loading – Default Level Row |
The default values for OWB level attributes in default parent record are migrated as default values for ODI level attributes. |
|
Orphan management for removal |
Not Migrated |
|
Deploy Error Table |
Not Migrated |
2. Level Properties
OWB dimension level will be migrated to ODI dimension level.
Table B-13 Level
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name |
|
Description |
Description |
|
Level Type (time dimension only) |
Description |
Level Type is migrated as a part of the description. |
Used (time dimension only) |
Not Migrated |
3. Dimension Attribute and Level Attribute
As ODI has only level attributes and does not have dimension attributes, ODI level attribute combines all the properties from OWB dimension attribute and OWB level attribute.
Table B-14 General Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Level Attribute Name |
Name |
|
Description |
Description |
|
Surrogate Key |
Surrogate Key |
|
Business Key |
Natural Key Member |
Each business key in OWB dimension is corresponding to an ODI dimension natural key member. Each ODI dimension natural key member is associated with a dimension level attribute. |
Data Type |
Data Type |
ODI level attribute uses Generic data type. Migration utility will convert the data type from Oracle technology to Generic technology. |
Length |
Size |
|
Scale |
Scale |
|
Precision |
Size |
|
Seconds Precision |
Size |
|
Default Value |
Default Value |
Table B-15 SCD2 Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Trigger history |
Trigger history |
|
Effective Date |
Start Date |
|
Expiration Date |
End Date |
Table B-16 SCD3 Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Previous Attribute |
Type 3 Previous Attribute |
|
Effective Date |
Type 3 Start Date |
4. Hierarchy
Table B-17 Hierarchy Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name |
|
Description |
Description |
|
Default |
Default |
|
Hierarchy Type (time dimension only) |
Description |
Hierarchy Type is migrated as part of the description of ODI hierarchy. |
5. Binding Objects
All binding tables/views/sequences are selected to be migrated when the migration option MIGRATE_DEPENDENCY
is set to TRUE
. OWB surrogate key sequence is migrated as ODI surrogate key sequence. If the OWB dimension is of star implementation type, the OWB dimension table is migrated to ODI dimension table. OWB does not have metadata for dimension error table. Migration utility will create the metadata of the error table for ODI dimension when orphan management is enabled. For more details, see Error Table.
6. Stage Table
In OWB, there is no metadata for stage tables (the temp table operator in the extended map of the dimension is unbound). ODI does not allow unbound datastore component. The ODI dimension level needs to be explicitly associated with a stage table. In this case, migration utility creates the metadata of a stage table for each dimension level in ODI based on the structure of the dimension level.
7. Error Table
Error tables behave in the same way as the stage tables. ODI dimension needs to be explicitly bound to an error table if the orphan management feature is enabled. Migration utility will create the metadata of the error tables for dimension when orphan management is enabled. For star implementation dimension, a dimension is associated to an error table. For snowflake implementation dimension, a level is associated to an error table. The structure of the error table is similar to the dimension bound table. The error table should include all the columns from the dimension bound table. More audit columns are added in error table. The audit columns are:
Table B-18 Audit Columns of Error Table
Property Name | Property Type |
---|---|
ODI_ERR_TYPE |
VARCHAR 2 (1 CHAR) NULL |
ODI_ERR_MESS |
VARCHAR 2 (250 CHAR) NULL |
ODI_ORIGIN |
VARCHAR 2 (4000 CHAR) NULL |
ODI_SESS_NO |
VARCHAR 2 (36 CHAR) NULL |
8. Exclusive Check
Before the real migration is performed, exclusive check should be done to check whether the dimension can be migrated or not. The exclusive check includes:
Checking the binding objects (tables/views/sequences) to make sure all the bindings are in the migration selection list and can be migrated. If the bindings are not in the migration selection list, the dimension will be exclusive and so turn on MIGRATE_DEPENDENCY
option or bindings should be explicitly specified in MIGRATION_OBJECTS
present in the configuration file.
If OWB dimension level attributes don't refer to any dimension attribute, then the dimension will be exclusive.
OWB Cube will be migrated to ODI Cube.
1. Cube Properties
Table B-19 General Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name |
|
Description |
Description |
Table B-20 Storage Type Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
For ROLAP Cube,
|
Not Migrated |
|
For MOLAP Cube, the cube is migrated as unbound cube
|
Not Migrated |
Table B-21 Dimensions Properties
OWB Property Name | ODI Property Name | Note |
---|---|---|
Level |
Level |
|
Role |
Role |
Table B-22 Measures
OWB Property Name | ODI Property Name | Note |
---|---|---|
Name |
Name |
|
Description |
Description |
|
Data Type |
Data Type |
OWB measure uses oracle data type, but ODI measure uses Generic technology data type. Data type conversion from oracle data type to Generic data type is handled in migration. |
Length or Precision Or Seconds Precision |
Size |
|
Scale |
Scale |
OWB cube aggregation related properties will not be migrated.
Table B-23 Orphan
OWB Property Name | ODI Property Name | Note |
---|---|---|
Orphan management for loading — Null dimension key values |
Load Null Dimension Key |
|
Orphan management for loading — Invalid dimension key values |
Load Invalid Dimension Key |
|
Deploy Error Table(s) |
Not Migrated. |
ODI does not support this feature. |
Physical Properties
All physical properties on cube are not migrated.
2. Binding Objects
All binding tables/views of cube are selected to be migrated when migration option MIGRATE_DEPENDENCY
is set to true. If the option MIGRATE_DEPENDENCY
is set to false, user should explicitly select the binding table or view together with cube to be migrated. Otherwise cube migration may fail because its bound object is not migrated. The error table is created based on the binding table. If any binding table is not specified to migrate, the corresponding error table will not be migrated.
3. Error Table
In OWB, cube is not explicitly bound to an error table. But in ODI, if the orphan management feature is enabled, then cube should be explicitly bound to an error datastore. Since OWB does not have metadata for cube error table, migration utility will create the error datastore for ODI cube according to the OWB cube bound table when orphan management is enabled. The error datastore should include all the columns from the cube bound table. More audit columns are added in error datastore. The audit columns are:
Table B-24 Audit Columns of Cube
Property Name | Property Type |
---|---|
ODI_ERR_TYPE |
VARCHAR 2 (1 CHAR) NULL |
ODI_ERR_MESS |
VARCHAR 2 (250 CHAR) NULL |
ODI_ORIGIN |
VARCHAR 2 (4000 CHAR) NULL |
ODI_SESS_NO |
VARCHAR 2 (36 CHAR) NULL |
When cube references a dimension with a surrogate key enabled, a natural key column for each dimension reference is assumed to be in the cube error table to load the invalid natural key values from source. Migration utility will create these natural key columns using the naming conversion <dimension_key_bound_column>_NAT
and data type set to VARCHAR2 (4000)
.
4. Exclusive Check
Before the real migration is performed, migration utility will check whether the cube can be migrated or not. It will check the binding objects (tables/views/) of the cube to make sure all the bindings are in the migration selection list and can be migrated. If the bindings are not in the migration selection list, the cube will be exclusive you must turn on MIGRATE_DEPENDENCY
option or bindings should be explicitly specified in MIGRATION_OBJECTS
.
OWB Mapping is migrated to ODI Mapping. OWB Mappings are contained in Oracle module or Template Mapping Module while ODI Mappings are contained in Project Folder. OWB Project is migrated to ODI project, OWB Oracle Module or Template Mapping Module is migrated to ODI Project Folder.
OWB Property Name | Description | ODI Property Name | Note |
---|---|---|---|
Physical Name (NAME) |
Name |
||
Business Name (LOGICAL_NAME) |
|||
Execution Type (EXECUTION_TYPE) |
BATCH, TRICKLE |
TRICKLE mappings are not supported for migration. |
|
Target Load Order (TARGET_LOAD_ORDER) |
TARGET_LOAD_ORDER |
||
Created By |
|||
Creation Time |
|||
Description |
Description |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
|
Icon Object |
|||
Last Update Time |
|||
Update By |
Physical Properties of OWB Mappings are not migrated to ODI.
OWB Property Name | Description | ODI Property Name | Note |
---|---|---|---|
Deployable (DEPLOYABLE) |
Not migrated. |
||
Generation Comments (GENERATION_COMMENTS) |
Not migrated. |
||
Language (GENERATION_LANGUAGE) |
Choices = 'PLSQL, SQLLOADER, ABAP, UNDEFINED' |
Not migrated. |
|
Referred Calendar (REFERRED_CALENDAR) |
Not migrated. Schedules are not supported for migration. |
Properties for Chunking options are not migrated. Those properties are:
Properties for Runtime parameters are not migrated. Those properties are:
Property Name | Description | ODI Property Name | Note |
---|---|---|---|
Analyze table statements |
Generate statistics collection statement if this is true. |
Not migrated. |
|
ANSI SQL Syntax (ANSI_SQL_SYNTAX) |
A switch between ANSI and Oracle SQL syntax. |
ODI has no such property defined on mapping, but ODI Join Component has similar property. |
|
AUTHID Option (AUTHID) |
Generate the map with selected AUTHID option. Package will be executed with the permissions defined by the AUTHID clause rather than the package owner's permissions. |
Not migrated. |
|
Bulk Processing code |
Generate bulk processing code if this is true. |
Not migrated. |
|
Commit Control (COMMIT_CONTROL) |
Choices = 'AUTO_COMMIT, AUTO_CORR_COMMIT, MANUAL_COMMIT' |
Not migrated. |
|
Enable Parallel DML |
Determine if Parallel DML is enabled at runtime. |
Not migrated. |
|
Error trigger (ERROR_TRIGGER) |
Error trigger procedure name |
Not migrated. |
|
Generation Mode |
Choices = 'SET_BASED, ROW_BASED, ROW_BASED_TARGET_ONLY, SET_BASED_FAIL_OVER_TO_ROW_BASED, SET_BASED_FAIL_OVER_TO_ROW_BASED_TARGET_ONLY, ALL_MODES' |
Not migrated. |
|
Optimized Code |
Attempt to generate optimized code if this is true. |
Not migrated. |
|
PL/SQL Compilation Mode |
Specifies the compilation mode for PL/SQL library unit. Choices = 'DEFAULT, INTERPRETED, NATIVE' |
Not migrated. |
|
Use Target Load Ordering (TARGET_LOAD_ORDERING) |
Not migrated. |
Properties for SQL Loader Settings are not migrated. Those properties are:
Properties for Runtime parameters are not migrated. Those properties are:
Properties for runtime parameters are not migrated, these properties are:
The properties for SQL*Plus Settings are not migrated. Those properties are:
Properties for Chunking options are not migrated. (The same as PLSQL mappings.)
OWB Property Name | Description | ODI Property Name | Note |
---|---|---|---|
Analyze table statements |
Generate statistics collection statement if this is true. |
Not migrated. |
|
ANSI SQL Syntax (ANSI_SQL_SYNTAX) |
A switch between ANSI and Oracle SQL syntax. |
ODI has no such property defined on the mapping, but ODI Join Component has a similar property, see migration on Join Operator. |
|
AUTHID Option (AUTHID) |
Generate the map with selected AUTHID option. Package will be executed with the permissions defined by the AUTHID clause rather than the package owner's permissions. |
Not migrated. |
|
Bulk Processing code |
Generate bulk processing code if this is true. |
Not migrated. |
|
Commit Control (COMMIT_CONTROL) |
Choices='AUTO_COMMIT, AUTO_CORR_COMMIT, MANUAL_COMMIT' |
Not migrated. |
|
Enable Parallel DML |
Determine if PDML is enabled at runtime. |
Not migrated. |
|
Error trigger (ERROR_TRIGGER) |
Error trigger procedure name. |
Not migrated. |
|
Generation Mode |
Choices='SET_BASED, ROW_BASED, ROW_BASED_TARGET_ONLY, SET_BASED_FAIL_OVER_TO_ROW_BASED, SET_BASED_FAIL_OVER_TO_ROW_BASED_TARGET_ONLY, ALL_MODES' |
Not migrated. |
|
Optimized Code |
Attempt to generate optimized code if this is true. |
Not migrated. |
|
Use Enclosure Char |
Not migrated. |
||
Use Target Load Ordering (TARGET_LOAD_ORDERING) |
Not migrated. |
Properties for runtime parameters are not migrated. Those properties are:
For mappings with multiple targets, target load order and Multiple Target Insert (MTI) are considered for migration.
The OWB Target Load Order property is migrated to the ODI Target Load Order property.
The OWB Use Target Load Ordering property is not migrated, because this property does not exist in ODI.
When an OWB mapping has multiple targets to insert, the data is coming from the same sources, and the Optimized code option is set to true, during code generation, a single insert statement for all targets may be generated instead of a multi-table insert SQL statement.
Because this property is a physical property and MTI occurs at code generation, MTI is not supported for migration.
OWB Property Name | ODI Property Name | Note |
---|---|---|
Business Name (LOGICAL_NAME) |
Business Name (BUSINESS_NAME) |
|
Create By |
Not migrated. |
|
Create Time |
Not migrated. |
|
Description (Description) |
Description (DESCRIPTION) |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
Icon Object |
Not migrated. |
|
Last Update Time |
Not migrated. |
|
Physical Name (NAME) |
Name (NAME) |
|
Update By |
Not migrated. |
The above properties are common properties for the Mapping operator.
OWB Property Name | ODI Property Name | Note |
---|---|---|
Physical Name (NAME) |
Name |
|
Business Name (LOGICAL_NAME) |
Not migrated. |
|
Created By |
Not migrated. |
|
Creation Time |
Not migrated. |
|
Description |
Description |
If the length of the description exceeds the maximum length allowed in ODI, then the description will be truncated. |
Icon Object |
Not migrated. |
|
Last Update Time |
Not migrated. |
|
Update By |
Not migrated. |
OWB Property Name | ODI Property Name | Note |
---|---|---|
Data Type (DATA_TYPE) |
Data type |
Convert the OWB data type to ODI data type according the data type mappings. |
Fractional Seconds precision (FRACTIONAL_SECONDS_PRECISION) |
Not migrated. |
|
Length (Length) |
Size |
For data type which allows length. |
Precision (Precision) |
Size |
For data type which allows precision. |
Scale (Scale) |
Scale |
Mapping Attributes of OWB Mapping Operator use OWB GENERIC platform data types. OWB GENERIC platform is mapped to ODI Generic SQL technology. See Data Type Mapping for OWB GENERIC Platform to ODI Generic SQL Technologyfor details.
OWB Pluggable Mapping is migrated to ODI Reusable Mapping.
Also see Pluggable Mapping Operator.
The OWB Pluggable Mapping Folder is migrated to an ODI Project Folder. Standalone pluggable mappings are migrated to a Project Folder named STAND_ALONE, which is created automatically during migration if it does not already exist.
Only Physical name and Description are migrated. Physical name of OWB Pluggable Mapping is migrated to name of ODI Reusable Mapping. Description of OWB Pluggable Mapping is migrated to Description of ODI Reusable Mapping.
In OWB, Signature Operator can have unlimited attribute groups (for Input Signature Operator, the attribute groups are output groups; for Output Signature Operator, the attribute groups are input groups). In ODI, Signature Component can have only one connector point, so each attribute group of OWB Signature Operator is migrated to a Signature Component.
For example, the following figure shows a Pluggable Mapping for which the INPUT_SIGNATURE operator has three output groups (INGRP1, INGRP2, and INGPR3).
These OWB output groups are migrated to three Input Signature Components in ODI, as shown in the following figure.
The name of ODI Signature Component is composed of OWB attribute group name of Signature Operator, underscore (_), and Signature Operator name.
The attributes of Signature Operator in OWB are migrated to attributes of Signature Component in ODI. No special properties need to be migrated for signature attributes.
OWB Pluggable Mapping does not have the property ANSI SQL Syntax as does a regular OWB Mapping. Therefore, all Join Operators of a Pluggable Mapping are split into binary joins during migration to ODI unless the migration configuration option SPLIT_JOIN_FOR_ANSI_SYNTAX is set to false in the migration utility configuration file. For information about ordered join, see Join Operator.