B Reference to Migration Details
This appendix provides reference information about migrating OWB to ODI.
This appendix contains the following topics:
OWB Repositories
OWB Workspace to ODI Work Repository
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 Platform to ODI Technology
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.
Data Type Mapping for OWB GENERIC Platform to ODI Generic SQL Technology
| 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 |
Data Type Mapping for OWB ORACLE Platform to ODI Oracle Technology
| 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 |
Data Type Mapping for OWB DB2UDB Platform to ODI IBM DB2 UDB Technology
| 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 |
Data Type Mapping for OWB SQLSERVER Platform to ODI Microsoft SQL Server Technology
| 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 |
Data Type Mapping for OWB FILE Platform to ODI File Technology
| 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 |
Data Type Mapping for OWB SAP Platform to ODI SAP ABAP Technology
| 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 |
OWB Location to ODI Data Server
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 to Data Server Name
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.
Location Properties to Data Server Properties
The following table shows mapping of properties of OWB Location to properties of ODI Data Server:
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
dataServerId (I_CONNECT) |
NUMBER(10,0) |
This number will be generated. |
||
|
platform |
NUMBER(9) |
technology (I_TECHNO) |
NUMBER(10,0) |
|
|
Name |
VARCHAR2(1000) |
name (CON_NAME) |
VARCHAR2(35 CHAR) |
|
|
Driver Class |
VARCHAR2(4000) |
jdbcDriverName (JAVA_DRIVER) |
VARCHAR2(400 CHAR) |
|
|
Url |
VARCHAR2(4000) |
jdbcUrl (JAVA_URL) |
VARCHAR2(250 CHAR) |
|
|
User Name (CONNECT_AS_USER) |
VARCHAR2(4000) |
username (USER_NAME) |
VARCHAR2(400 CHAR) |
|
|
Batch Update Size (UPDATE_SIZE) |
NUMBER |
batchUpdateSize (BATCH_UPDATE_SIZE) |
NUMBER(10,0) |
|
|
Array Fetch Size (FETCH_SIZE) |
NUMBER |
fetchArraySize (FETCH_ARRAY_SERV) |
NUMBER(10,0) |
|
|
Schema |
VARCHAR2 |
schemaName (SCHEMA_NAME) |
VARCHAR2(128 CHAR) |
|
|
Work Schema |
VARCHAR2 |
workSchemaName (WSCHEMA_NAME) |
VARCHAR2(128 CHAR) |
|
|
Catalog |
VARCHAR2 |
catalogName (CATALOG_NAME) |
VARCHAR2(128 CHAR) |
|
|
Work Catalog |
VARCHAR2 |
workCatalogName (WCATALOG_NAME) |
VARCHAR2(128 CHAR) |
Specific Location
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 to ODI Models
OWB Modules will be migrated to ODI Models.
Module Name to Model Name
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.
Module Properties to Model Properties
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
modelId (I_MOD) |
NUMBER(10,0) |
This number will be generated by the migration utility. |
||
|
Name |
VARCHAR2(1000) |
name (MOD_NAME) |
VARCHAR2(400 CHAR) |
|
|
Platform |
NUMBER(9) |
technology (TECH_INT_NAME) |
VARCHAR2(35 CHAR) |
|
|
logicalSchema (LSCHEMA_NAME) |
VARCHAR2(35 CHAR) |
Will be created according to the OWB module name. |
||
|
Name |
VARCHAR(1000) |
code (COD_MOD) |
VARCHAR2(35 CHAR) |
|
|
Project |
NUMBER(9) |
parentModelFolder (I_MOD_FOLDER) |
NUMBER(10,0) |
|
|
description |
VARCHAR2(4000) |
description (I_TXT_MOD) |
NUMBER(10,0) |
Description |
Additional Migration of OWB Modules to ODI Folders
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 | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (FOLDER_NAME) |
VARCHAR2(400 CHAR) |
Physical Schema and Logical Schema
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 Projects to ODI Projects
OWB Project will be migrated as ODI Project.
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
projectId (I_PROJECT) |
NUMBER(10,0) |
This number will be generated. |
||
|
Name |
VARCHAR2(1000) |
Name (PROJECT_NAME) |
VARCHAR2(400 CHAR) |
|
|
Name |
VARCHAR2(1000) |
code (PROJECT_CODE) |
VARCHAR2(35 CHAR) |
OWB Folders to ODI Folders
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 Data Objects
OWB Table to ODI Datastore
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 as described in Table B-1, "OWB Data Object (Table, View, External Table, File, Materialized View) to ODI Datastore".
Attributes or properties of OWB Table Columns are migrated to ODI Datastore Columns as described in Table B-2, "OWB Table Column to ODI Datastore Column".
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-5, "OWB Key to ODI Key".
-
The attributes/properties of OWB Table Constraints are migrated to ODI Condition as described in Table B-6, "OWB Check Constraint to ODI Condition".
-
The attributes/properties of OWB Table Foreign Keys are migrated to ODI Reference as described in Table B-7, "OWB ForeignKey to ODI Reference".
The attributes/properties of Indexes are migrated to ODI Datastore Key as described in Table B-8, "OWB Index to ODI Key", 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 to ODI Datastore
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 as described in Table B-1, "OWB Data Object (Table, View, External Table, File, Materialized View) to ODI Datastore".
Attributes or properties of OWB View Columns are migrated to ODI Datastore Columns as described in Table B-2, "OWB Table Column to ODI Datastore Column".
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-5, "OWB Key to ODI Key".
-
The attributes/properties of OWB View Constraints are migrated to ODI Condition as described in Table B-6, "OWB Check Constraint to ODI Condition".
-
The attributes/properties of OWB View Foreign Keys are migrated to ODI Reference as described in Table B-7, "OWB ForeignKey to ODI Reference".
OWB Materialized View to ODI Datastore
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 as described in Table B-1, "OWB Data Object (Table, View, External Table, File, Materialized View) to ODI Datastore".
Attributes or properties of OWB Materialized View Columns are migrated to ODI Datastore Columns as described in Table B-2, "OWB Table Column to ODI Datastore Column".
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-5, "OWB Key to ODI Key".
The attributes/properties of OWB Materialized View Constraints are migrated to ODI Condition as described in Table B-6, "OWB Check Constraint to ODI Condition".
The attributes/properties of OWB Materialized View Foreign Keys are migrated to ODI Reference as described in Table B-7, "OWB ForeignKey to ODI Reference".
The attributes/properties of Indexes are migrated to ODI Datastore Key as described in Table B-8, "OWB Index to ODI Key", which lists the mappings between the OWB Index and ODI Key.
OWB External Table to ODI Datastore
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 as described in Table B-1, "OWB Data Object (Table, View, External Table, File, Materialized View) to ODI Datastore".
Attributes or properties of OWB External Table Columns are migrated to ODI Datastore Columns as described in Table B-2, "OWB Table Column to ODI Datastore Column".
OWB External Table has association to OWB FLAT FILE and its access parameters. These associations will not be migrated to ODI.
OWB Flat File to ODI Datastore
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 as described in Table B-1, "OWB Data Object (Table, View, External Table, File, Materialized View) 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-4, "OWB File Record to ODI Datastore Column".
Attributes or properties of OWB File Record Field are migrated to ODI Datastore Columns as described in section Table B-3, "OWB File Record Field to ODI Datastore Column".
OWB Sequence to ODI Sequence
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-10, "OWB Sequence to ODI Sequence".
Property Migration Mapping Tables
Table B-1 OWB Data Object (Table, View, External Table, File, Materialized View) to ODI Datastore
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
defaultAlias (TABLE_ALIAS) |
VARCHAR2(128 CHAR) |
|
|
ClassName |
VARCHAR2(255) |
dataStoreType (TABLE_TYPE) |
VARCHAR2(2 CHAR) |
OWB Table, File, and External Table are mapped to TABLE. OWB View and Materialized view are mapped to VIEW. |
|
Description |
VARCHAR2(4000) |
Description (TABLE_DESC) |
VARCHAR2(250 CHAR) |
|
|
SelectQuery |
CLOB() |
For view. |
||
|
DefaultLocation |
NUMBER(9) |
For External Table. |
||
|
RefersTo |
NUMBER(9) |
For External Table. |
||
|
FixedWidth |
CHAR(1) |
Format (FILE_FORMAT) |
VARCHAR2(1 CHAR) |
For file/record. |
|
FieldDelimiter |
VARCHAR2(40) |
fieldSeparator (FILE_SEP_FIELD) |
VARCHAR2(24 CHAR) |
For file/record. |
|
leftEnclosure and rightEnclosure |
VARCHAR2(40) |
textDelimiter (FILE_ENC_FIELD) |
VARCHAR2(2 CHAR) |
For file/record. |
|
RecordDelimiter |
VARCHAR2(40) |
rowSeparator (FILE_SEP_ROW) |
VARCHAR2(24 CHAR) |
For file/record. |
|
SkipRecords |
NUMBER(9) |
skipHeadingLines (FILE_FIRST_ROW) |
NUMBER(10,0) |
For file/record. |
|
Sourcefrom |
VARCHAR2(255) |
resourceName (RES_NAME) |
VARCHAR2(400 CHAR) |
For file/record. |
Table B-2 OWB Table Column to ODI Datastore Column
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (COL_NAME) |
VARCHAR2(128 CHAR) |
|
|
COL_DESC |
VARCHAR2(250 CHAR) |
Short description. |
||
|
TypeDefinition |
NUMBER(9) Stores an Id which points to a record in another table. |
dataTypeCode (SOURCE_DT) |
VARCHAR2(35 CHAR) |
|
|
Position |
NUMBER(9) |
position (POS) |
NUMBER(10,0) |
|
|
Length |
NUMBER(9) |
length (LONGC) |
NUMBER(10,0) |
|
|
Precision |
NUMBER(9) |
Length (LONGC) |
NUMBER(10,0) |
|
|
Scale |
NUMBER(9) |
scale (SCALEC) |
NUMBER(10,0) |
|
|
Nullable |
CHAR(1) |
mandatory (COL_MANDATORY) |
VARCHAR2(1 CHAR) |
|
|
dafaultValue |
VARCHAR(4000) |
defaultValue (DEF_VALUE) |
VARCHAR2(100 CHAR) |
|
|
scdType (SCD_COL_TYPE) |
VARCHAR2(2 CHAR) |
|||
|
description |
Varchar(4000) |
description (I_TXT_COL_DESC) |
NUMBER(10,0) Stores an Id which points to a record in another table. |
|
|
fractionalsecondsprecision |
NUMBER(9) |
length (LONGC) |
NUMBER(10) |
Table B-3 OWB File Record Field to ODI Datastore Column
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (COL_NAME) |
VARCHAR2(128 CHAR) |
|
|
TypeDefinition |
NUMBER(9) Stores an Id which points to a record in another table. |
dataTypeCode (SOURCE_DT) |
VARCHAR2(35 CHAR) |
|
|
Position |
NUMBER(9) |
position (POS) |
NUMBER(10,0) |
|
|
Sqlprecision |
NUMBER(9) |
NUMBER(10,0) |
||
|
Sqlscale |
NUMBER(9) |
NUMBER(10,0) |
||
|
Precision |
NUMBER(9) |
bytes (BYTES) |
NUMBER(10,0) |
|
|
Scale |
NUMBER(9) |
scale (SCALEC) |
NUMBER(10,0) |
|
|
StartPostion |
NUMBER(9) |
startPosition (FILE_POS) |
NUMBER(10,0) |
Only for file/record. |
|
FieldLength |
NUMBER(9) |
bytes (BYTES) |
NUMBER(10,0) |
Only for file/record. |
|
Nullable |
CHAR(1) |
mandatory (COL_MANDATORY) |
VARCHAR2(1 CHAR) |
|
|
dafaultValue |
VARCHAR(4000) |
defaultValue (DEF_VALUE) |
VARCHAR2(100 CHAR) |
|
|
description |
VARCHAR(4000) |
description (I_TXT_COL_DESC) |
NUMBER(10,0) Stores an Id which points to a record in another table. |
|
|
sqllength |
||||
|
mask |
VARCHAR2(255) |
format (SNP_COL.COL_FORMAT) |
VARCHAR2(35) |
Table B-4 OWB File Record to ODI Datastore Column
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
name (TABLE_NAME) |
|||
|
Name |
VARCHAR2(1000) |
defaultAlias (TABLE_ALIAS) |
VARCHAR2(128 CHAR) |
|
|
classname |
VARCHAR2(255) |
dataStoreType (TABLE_TYPE) |
VARCHAR2(2 CHAR) |
|
|
Description |
VARCHAR2(4000) |
Description (TABLE_DESC) |
VARCHAR2(250 CHAR) |
|
|
Prefix |
VARCHAR2(40) |
|||
|
Position |
NUMBER(9) |
|||
|
RecordClassifierValue |
VARCHAR2(40) |
|||
|
RecordSize |
NUMBER(9) |
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (KEY_NAME) |
VARCHAR2(128 CHAR) |
|
|
Primarykey |
BOOLEAN |
keyType (CONS_TYPE) |
VARCHAR2(2 CHAR) |
keyType: PRIMARY_KEY(PK) ALTERNATE_KEY(AK) |
|
Appslabel |
VARCHAR2(255) |
Table B-6 OWB Check Constraint to ODI Condition
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (KEY_NAME) |
VARCHAR2(128 CHAR) |
|
|
Primarykey |
BOOLEAN |
keyType (CONS_TYPE) |
VARCHAR2(2 CHAR) |
keyType: PRIMARY_KEY(PK) ALTERNATE_KEY(AK) |
|
Appslabel |
VARCHAR2(255) |
Table B-7 OWB ForeignKey to ODI Reference
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
referenceId (I_JOIN) |
NUMBER(10,0) |
This number will be generated. |
||
|
Name |
name (FK_NAME) |
VARCHAR2(128 CHAR) |
||
|
Should map to DB_REFERENCE |
referenceType (FK_TYPE) |
VARCHAR2(1 CHAR) |
referenceType: DB_REFERENCE, ODI_REFERENCE, COMPLEX_REFERENCE |
|
|
primaryDataStore (I_TABLE_PK) |
NUMBER(10,0) |
Find the table by Unique key. |
||
|
module |
primaryModel (PK_I_MOD) |
NUMBER(10,0) |
||
|
primaryDataStoreSchemaName (PK_SCHEMA) |
VARCHAR2(128 CHAR) |
Find the schema based on the model of the primary table. |
||
|
primaryDataStoreName (PK_TABLE_NAME) |
VARCHAR2(128 CHAR) |
Find primary table name by unique key. |
||
|
primaryDataStoreAlias (PK_TABLE_ALIAS) |
VARCHAR2(128 CHAR) |
Find the alias by primary data store. |
||
|
Appslabel |
VARCHAR2(255) |
|||
|
Mandatory |
CHAR(1) |
|||
|
OnetoOne |
CHAR(1) |
Table B-8 OWB Index to ODI Key
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
Name (KEY_NAME) |
VARCHAR2(128 CHAR) |
|
|
Indextype |
keyType (CONS_TYPE) |
VARCHAR2(2 CHAR) |
keyType: ALTERNATE_KEY(AK) INDEX(I) |
|
|
Appslabel |
VARCHAR2(255) |
|||
|
Expression |
CLOB() |
|||
|
LocalIndex |
CHAR(1) |
|||
|
LocalPartitionType |
VARCHAR2(40) |
Table B-9 OWB Partition to ODI Partition
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
Name |
VARCHAR2(1000) |
name (PARTITION_NAME) |
VARCHAR2(400 CHAR) |
|
|
Description |
VARCHAR2(4000) |
Description (PARTITION_DESC) |
VARCHAR2(250 CHAR) |
|
|
classname |
VARCHAR2(255) |
|||
|
Attribute |
VARCHAR2(40) |
|||
|
Autosubpartitionordering |
VARHCAR2(40) |
|||
|
Hashsubpartitioncount |
VARCHAR2(40) |
|||
|
IsDefault |
CHAR(1) |
|||
|
IsSubPartition |
CHAR(1) |
|||
|
PartitionOrder |
VARCHAR2(40) |
Table B-10 OWB Sequence to ODI Sequence
| OWB Property Name | OWB Property Type | ODI Property Name | ODI Property Type | Note |
|---|---|---|---|---|
|
sequenceId (SEQ_ID) |
NUMBER(10,0) |
This number will be generated. |
||
|
Project |
NUMBER(9) |
project (I_PROJECT) |
NUMBER(10,0) |
|
|
Name |
SEQ_NAME |
VARCHAR2(400 CHAR) |
||
|
Increment By |
VARCHAR2(2000) |
incrementValue (INCR) |
NUMBER(10,0) |
Retrieve from active configuration. |
|
seqType (SEQ_TYPE) |
VARCHAR2(1 CHAR) |
OWB sequence is migrated as project sequence. |
||
|
type (IND_STD) |
VARCHAR2(1 CHAR) |
OWB sequence is migrated as native sequence. |
||
|
logicalSchemaName (LSCHEMA_NAME) |
VARCHAR2(35 CHAR) |
Via OWB module, the ODI Model's logical schema is used here. |
||
|
Name |
nativeSequenceName (DB_SEQ_NAME) |
VARCHAR2(128 CHAR) |
||
|
Prefix |
VARCHAR2(40) |
|||
|
ExternalElementName |
VARCHAR2(40) |
|||
|
Proxy |
CHAR(1) |
|||
|
SynonymFor |
VARCHAR2(255) |
|||
|
ValidationResult |
NUMBER(9) |
OWB Mappings
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 Mapping Properties
OWB Mapping Logical Properties
Logical properties of OWB Mapping are migrated to ODI Mapping Properties as follows:
| 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 |
||
|
Icon Object |
|||
|
Last Update Time |
|||
|
Update By |
OWB Mapping Physical Properties
Physical Properties of OWB Mappings are not migrated to ODI.
The following properties are not migrated:
| 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. |
PLSQL Physical Properties
Chunking Options
Properties for Chunking options are not migrated. Those properties are:
- Chunk Method
- Chunk table (NUMCOL_CHUNK_TABLE)
- Chunk column (NUMCOL_CHUNK_COLUMN)
- Chunk size (NUMCOL_CHUNK_SIZE)
- Chunk table (ROWID_CHUNK_TABLE)
- Chunk type (ROWID_CHUNK_TYPE)
- Chunk size (ROWID_CHUNK_SIZE)
- Chunk table (SQL_CHUNK_TABLE)
- SQL statement (SQL_CHUNK_STATEMENT)
- SQL statement chunk type (SQL_CHUNK_TYPE)
Runtime Parameters
Properties for Runtime parameters are not migrated. Those properties are:
- Analyze table sample percentage
- Bulk size
- Chunk execute resume task
- Chunk force resume
- Chunk number of times to retry
- Chunk parallel level
- Commit frequency
- Default audit level
- Default Operating Mode
- Default purge group
- Maximum number of errors
Code Generation Options
Properties for code generation options are migrated as follows:
| 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. |
SQL*LOADER Physical Properties
SQL Loader Settings
Properties for SQL Loader Settings are not migrated. Those properties are:
- Bind Size
- Byte Order Mark
- Column Array Rows
- Continue Load
- Control File Location
- Control File Name
- Database File Name
- Delimited File Record Termination
- Direct Mode
- Endian (Byte Order)
- Errors Allowed
- Load Last Field As Pieced
- Log File Location
- Log File Name
- Multithreading
- Nls Characterset
- Operation Recoverable
- Perform Parallel Load
- Preserver Blanks
- Read Buffers
- Read Size
- Records to Load
- Records to Skip
- Resumable
- Resumable Name
- Resumeable Timeout
- Rows per Commit
- Skip Index Maintenance
- Skip Unusable Indexes
- Stream size
- Suppress discards
- Suppress Errors
- Suppress Feedback
- Suppress Header
- Suppress partitions
ABAP Mapping Physical Properties
Runtime Parameters
Properties for runtime parameters are not migrated, these properties are:
- ABAP Report Name
- Background Job
- Control File Name
- Data File Name
- File Delimiter for Staging File
- Include FTP
- Install only
- Log File Name
- SAP Location
- SAP System Version
- Sql Join Collapsing
- Staging File Directory
- Timeout
SQLPLUS Mapping Physical Properties
KM Mappings Physical Properties
Code Generation Options
Properties for code generation options are migrated as follows:
| 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. |
Multiple Target Mapping Migration
For mappings with multiple targets, target load order and Multiple Target Insert (MTI) are considered for migration.
Target Load Order
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.
Multiple Target Insert (MTI)
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.
Mapping Operator
Logical properties of the OWB Mapping Operator are migrated to ODI Mapping Component Properties as follows:
| 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) |
|
|
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.
Mapping Attribute
General Properties
General properties of OWB Mapping Attribute are migrated to ODI Mapping Attribute properties as follows:
| 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 |
|
|
Icon Object |
Not migrated. |
|
|
Last Update Time |
Not migrated. |
|
|
Update By |
Not migrated. |
Data Type Information
Data type information properties on attribute of OWB Table operator are as follows:
| 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 Technology" for details.
OWB Pluggable Mappings
OWB Pluggable Mapping is migrated to ODI Reusable Mapping.
Also see Pluggable Mapping Operator.
Pluggable Mapping Folder
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.
Properties of Pluggable Mapping
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.
Input Signature and Output Signature
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.
Join Operator in Pluggable Mapping
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.