This appendix describes messages you might encounter when you run the migration utility.
If objects cannot be migrated, informational messages appear.
If objects are migrated with warnings, warning messages appear.
If the objects cannot be migrated due unexpected errors, error messages appear.
The informational, warning, and error messages are written to the migration utility log in the following formats:
[ERROR|WARN|INFO][Migration][MU-XXXX]: Indicates the message is coming from the migration utility (XXXX is the message ID).
[ERROR|WARN][Migration][ODI]: Indicates the message is coming from ODI.
[ERROR|WARN][Migration][OWB]: Indicates the message is coming from OWB.
For more information about the migration utility log file, see Reviewing Log and Report Files.
Table A-1 provides example OWB and ODI error and warning messages. The message text is as it appears in the message.
Table A-1 Example OWB and ODI Error and Warning Messages
| Message | Cause | Action |
|---|---|---|
|
[ERROR][Migration][OWB] Unable to connect to OWB workspace! Details: {0} |
The connection to the OWB workspace cannot be established. The credential information used to connect to the OWB workspace may be invalid. |
Verify the following parameters in the migration utility configuration file when running the migration utility (
For more information about these parameters, see Configuration File Parameters. Also verify the password for the OWB workspace owner. |
|
[ERROR][Migration][ODI] Unable to connect to ODI repository! Details: {0} |
The connection to the ODI repository cannot be established. The credential information used to connect to the ODI repository may be invalid. |
Verify the following parameters in the migration utility configuration file when running the migration utility (
For more information about these parameters, see Configuration File Parameters. Also verify the passwords for the ODI master repository and the ODI user. |
Table A-2 lists migration utility error and warning messages. Messages are listed in numeric order by message ID. The message text is as it appears in the message.
Table A-2 Migration Utility Informational, Warning, and Error Messages
| Message | Cause | Action |
|---|---|---|
|
[MU-1001] Invalid number of parameters. You have to provide 4 parameters: password for ODI master repository, password for ODI user, password for OWB, full path for settings file. |
Required parameters were not supplied when running the migration utility ( |
Provide the required parameters when running the migration utility ( For more information about the correct syntax, see Migration Utility Syntax and Parameters. |
|
[ERROR] [Migration] [OWB] Unable to connect to OWB workspace! Details: {0} |
The connection to OWB workspace cannot be established. The credential information used to connect to OWB workspace may be invalid. |
Verify the following parameters in the migration utility configuration file when running the migration utility (
|
|
[ERROR] [Migration] [ODI] Unable to connect to ODI repository! Details: {0} |
The connection to ODI repository cannot be established. The credential information used to connect to ODI repository may be invalid. |
Verify the following parameters in the migration utility configuration file when running the migration utility (
|
|
[MU-1004] Unable to load configuration file {0}. Details:{1} |
The migration utility configuration file does not exist or is not readable or accessible. |
Make sure the migration utility configuration file exists and is readable and accessible. Specify the full path to the configuration file and the file name. For more information about the configuration file, see Creating the Migration Utility Configuration File. |
|
[MU-1005] The selected object {0} does not exist or the selection is invalid. It will be skipped. |
An invalid or nonexistent object is specified for the |
Verify the value specified for the For more information about this parameter, see |
|
[MU-1006] Invalid object name {0} in selection {1}, the selection will be skipped. |
An invalid object name is specified for the |
Verify the value specified for the For more information about this parameter, see |
|
[MU-1007] Migration failed. Details: {0} |
As described in the message. |
Review the message to determine the cause of the problem and take appropriate action. |
|
[MU-1008] Unable to write to log or report file {0}. Details:{1} |
The log or report file is not accessible to the migration utility. |
Verify the path specified for the For more information about this parameter, see |
|
[MU-1009] Invalid configuration option {0}. It will be ignored. |
An invalid parameter is specified in the migration utility configuration file. |
Verify the parameters in the migration utility configuration file, make sure they are correct. |
|
[MU-1010] {0} is skipped because it already exists. |
The parameter |
No action. |
|
[MU-2001] Migration of location {0} in platform {1} is not supported. |
The location for this platform is not supported for migration. |
No action. |
|
[MU-2002] Migration of location {0} with no associated platform is not supported. |
The location is not associated with a platform. |
No action. |
|
[MU-3001] Unable to load file {0}. Details: {1}. |
The file |
Verify that the file This file contains the mappings between OWB platforms and ODI technologies. For more information about this file, see OWB Platform to ODI Technology. |
|
[MU-3002] Unable to find ODI technology corresponding to the OWB platform: {0}. |
The mapping of the specified OWB platform to any ODI technology is missing in the file |
Add the mapping of the specified OWB platform to one ODI technology in the file This file contains the mappings between OWB platforms and ODI technologies. For more information about this file, see OWB Platform to ODI Technology. |
|
[MU-3003] Unable to find technology: {0} in ODI. |
The specified technology is not defined in the ODI repository. |
Define the specified technology in ODI, or modify the file This file contains the mappings between OWB platforms and ODI technologies. For more information about this file and these mappings, see OWB Platform to ODI Technology. |
|
[MU-4001] Migration of {0}:{1} is not supported because unsupported data type {3} is used in column {2}. |
The data type used by the specified column is not supported for migration. |
Change the data type in OWB if possible. For more information about data types supported for migration, see Reference to Migration Details. |
|
[MU-4002] {0}:{1} has multiple primary keys. Only one primary key is allowed in ODI, the redundant primary keys will be migrated as alternate keys. |
An OWB table can be defined with several primary keys, but an ODI data store can have just one primary key. Only one of the primary keys in OWB will be migrated as the primary key in ODI. The rest will be migrated as alternate keys. |
No action. |
|
[MU-4003] {0}:{1} is not migrated because it has multiple columns with the same name {2}. |
An OWB table may have duplicate columns due to previous OWB issues. |
Check the OWB table, and rename the columns. Make sure the name of the column is unique in the table. |
|
[MU-5001] Migration of mapping with mapping operator {0}:{1} is not supported. |
The specified mapping operator is not supported for migration. |
No action. |
|
[MU-5002] Migration of mapping with mapping operator {0}:{1} which contains multiple return attributes is not supported. |
Function operators with multiple return attributes are not migrated. |
No action. |
|
[MU-5003] Migration of mapping with mapping operator {0}:{1} which contains OUT parameter {2} is not supported. |
Function operators with |
No action. |
|
[MU-5004]Migration of mapping with mapping operator {0}:{1} which contains INOUT parameter {2} is not supported. |
Function operators with |
No action. |
|
[MU-5005] Migration of mapping with complex data type {2} used in attribute {3} in mapping operator {0}:{1} is not supported}. |
Mapping operators with complex data types used in mapping attributes are not migrated. |
No action. |
|
[MU-5006] Migration of mapping with mapping operator {0}:{1} that does not define return attribute is not supported. |
Function operators with no return attribute are not migrated. |
No action. |
|
[MU-5007] Mapping is not migrated because the function name of the mapping operator {0}:{1} cannot be determined. |
The property |
Set the value for the property |
|
[MU-5008] Unable to set Extract Knowledge Module on physical node {0} in ODI. Details: {1} |
As described in the message. |
Review the message to determine the cause of the problem and take appropriate action. |
|
[MU-5009] Mapping is not migrated because the bound object of the mapping operator {0}:{1} is not being migrated. |
The bound object of a mapping operator is not migrated. |
Check the migration utility log to determine why the bound object was not migrated. |
|
[MU-5010]Mapping is not migrated because the mapping operator{0}:{1} has no output attribute group. |
The Lookup operator has no output attribute group. |
Modify the Lookup operator in OWB, and add the output attribute group for it. |
|
[MU-5011] mapping is not migrated because the output attribute group {1} in Lookup {0} is unbound. Use the configuration option of migration utility "MIGRATE_UNBOUND_OPERATOR" or fix the mapping with unbound output attribute groups. |
The output attribute group of the Lookup operator is unbound. |
Bind the output attribute group of the Lookup operator or set the For more information about this parameter, see |
|
[MU-5012] Mapping is not migrated because the bound object of the mapping operator {0}:{1} for output attribute group {2} is not being migrated. |
The bound object of the output attribute group of the Lookup operator is not migrated. |
Check the migration utility log to determine why the bound object was not migrated. |
|
[MU-5013] Mapping is not migrated because the input attribute group is not defined for output attribute group {1} in Lookup {0}. |
The output attribute group of the Lookup operator has no corresponding input attribute group. |
Modify the Lookup operator, and add the input attribute group for each output attribute group. |
|
[MU-5018] Mapping is not migrated because unsupported data type {3} is used in attribute {2} in mapping operator {0}:{1}. |
Data type {3} set on the mapping attribute is not supported for migration. |
Change the data type of the mapping attribute to a supported data type if possible. For more information about data types supported for migration, see Reference to Migration Details. |
|
[MU-5019] Unable to set expression [{1}] on attribute {0}. Details: {2}. |
As described in the message. |
Review the message to determine the cause of the problem and take appropriate action. |
|
[MU-5020] Unable to split mapping joiner operator {0} into binary joins due to {1}. |
The join condition of the join operator cannot be parsed successfully. |
Check the join condition and modify it if possible. |
|
[MU-5021] The mapping joiner operator {0} will be split into binary joins after migration because some input group(s) have role set to "Outer", even though the mapping property "ANSI SQL Syntax" is set to false or the configuration option for migration utility "SPLIT_JOIN_FOR_ANSI_SYNTAX" is set to false. |
The role is set to For more information about this parameter, see |
No action. |
|
[MU-5022] Unable to find corresponding integration type in ODI according to the loading type {0} in OWB for operator {1}:{2}. Default integration type {3} is used. |
ODI does not support integration types such as delete. |
No action. |
|
[MU-5023] Mapping is not migrated because the mapping operator {0}:{1}. Use the configuration option of migration utility "MIGRATE_UNBOUND_OPERATOR" or fix the mapping with unbound operators. |
A mapping operator is unbound. |
Configure the For more information about this parameter, see |
|
[MU-5024] Migration of mapping operator {0}:{1} with data rules is not supported. |
A mapping operator with data rules set is not supported for migration. |
No action. |
|
[MU-5025] The bound object of mapping operator {0}:{1} is not selected. |
The bound object of the mapping operator is not selected for migration. |
Check whether the bound object is explicitly selected using the For more information about these parameters, see Configuration File Parameters. |
|
[MU-5026] Unable to generate ODI ExternalTable access parameter option for operator {0}:{1}. Details: {2}. |
As described in the message. |
Review the message to determine the cause of the problem and take appropriate action. |
|
[MU-5027] Unable to migrate mapping with operator {0} because no {1} DataStore component hold the generated {2} for it. |
The given mapping has no source data store component to hold the generated The Pre/Post mapping operator is migrated to |
No action. |
|
[MU-5028]Unable to migrate mapping with operator {0} when store generated {1} into {2} DataStore component raised error: {3}. |
Storing the generated |
No action. |