1. Error Messages
  2. ODI-1100 to ODI-999999

21 ODI-1100 to ODI-999999

ODI-1100
Agent {0} successfully cleaned up {1} stale sessions from work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1101
Agent {0} successfully completed session {1} ({2}) (for scenario {3}) on {4} using context {5} with statistics: Rows {6} Inserts {7} Updates {8} Deletes {9} Errors {10}.
Category:
Other
Cause:
null
Action:
null
ODI-1102
Agent {0} successfully completed session {1} ({2}) on {3} using context {4} with statistics: Rows {5} Inserts {6} Updates {7} Deletes {8} Errors {9}.
Category:
Other
Cause:
null
Action:
null
ODI-1103
Agent {0} successfully completed step {1} in session {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1104
Agent {0} successfully connected to master repository using {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1105
Agent {0} successfully connected to work repository {1} using {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1106
Agent {0} created load plan {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1107
Agent {0} created session {1} ({2}) in work repository {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1108
Agent {0} created session {1} ({2}) from scenario {3} in work repository {4} using context {5}.
Category:
Other
Cause:
null
Action:
null
ODI-1109
Agent {0} is delegating session {1} on work repository {2} to agent {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1110
Agent {0} successfully retrieved {1} schedules from work repository {2} using {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1111
Agent {0} started. Agent version: {1}. Port: {2}. JMX Port: {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1112
Agent {0} received a request to recalculate its schedule on work repository {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1113
Agent {0} received a data server test request for {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1114
Agent {0} received a request to stop load plan instance {1} on work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1115
Agent {0} received a ping request.
Category:
Other
Cause:
null
Action:
null
ODI-1116
Agent {0} received a request to retrieve its schedule on work repository {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1117
Agent {0} received a request to restart load plan instance ({1}) in work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1118
Agent {0} received a request to start load plan {1} on work repository {2} using context {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1119
Agent {0} received a request to start scenario {1}.{2} on work repository {3} using context {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1120
Agent {0} received a request to restart session {1} on work repository {2} using context {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1121
Agent {0} received a request to stop session {1} on work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1122
Agent {0} successfully restarted {1} queued sessions from work repository {2} using {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1123
Agent {0} sent a request to agent {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1124
Agent {0} started load plan {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1125
Agent {0} started session {1} ({2}) from scenario {3} in work repository {4} using context {5}.
Category:
Other
Cause:
null
Action:
null
ODI-1126
Agent {0} started session {1} ({2}) in work repository {3} using context {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1127
Agent {0} started step {1} in session {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1128
Agent {0} is starting. Container: {1}. Agent Version: {2}. Port: {3}. JMX Port: {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1129
Agent {0} stopped.
Category:
Other
Cause:
null
Action:
null
ODI-1130
Agent {0} is stopping.
Category:
Other
Cause:
null
Action:
null
ODI-1131
Agent {0} encountered an error: {1}
Category:
Other
Cause:
null
Action:
null
ODI-1132
Agent {0} encountered a warning: {1}
Category:
Other
Cause:
null
Action:
null
ODI-1133
Agent {0} detected that the work repository {1} went down.
Category:
Other
Cause:
null
Action:
null
ODI-1134
Agent {0} encountered an error: {1}
Category:
Other
Cause:
null
Action:
null
ODI-1135
Agent {0} detected that the master repository went down.
Category:
Other
Cause:
null
Action:
null
ODI-1136
Starting Schedulers on Agent {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1137
Scheduler started for work repository {0} on Agent {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1138
Migrating Schedulers for Agent {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1139
The current task of the session ({0}) does not support stop immediate. This session will be stopped normally by the Agent ({1}) before next task begins.
Category:
Other
Cause:
null
Action:
null
ODI-1140
Unable to stop session ({0}) immediately. This session will be stopped by the agent ({1}) before next task begins.
Category:
Other
Cause:
null
Action:
null
ODI-1141
Agent {0} started load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1142
Agent {0} successfully completed load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1143
Agent {0} started computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.
Category:
Other
Cause:
null
Action:
null
ODI-1144
Agent {0} completed computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.
Category:
Other
Cause:
null
Action:
null
ODI-1145
Agent {0} not found when trying to stop session with id {1} in work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1146
Agent {0} invocation error when trying to stop session with id {1} in work repository {2}: {3}
Category:
Other
Cause:
null
Action:
null
ODI-1147
Agent {0} stopped load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1148
Agent {0} executing load plan log purge for work repository {1} at {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1151
Agent {0} cannot continue load plan instance {1} ({2}), run {3} in work repository {4}, because the instance has been deleted.
Category:
Other
Cause:
null
Action:
null
ODI-1152
Agent {0} continuing processing for load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1153
An exception occurred while processing scheduled job for scenario {0} and version {1}. The exception message is : {2}
Category:
Other
Cause:
null
Action:
null
ODI-1154
An exception occurred while processing scheduled job for loadplan {0}. The exception message is : {1}
Category:
Other
Cause:
null
Action:
null
ODI-1155
Invalid repetition interval {0} specified in scheduled job for scenario {1} {2}. The schedule would not be repeated.
Category:
Other
Cause:
null
Action:
null
ODI-1156
Invalid repetition interval {0} specified in scheduled job for loadplan {1}. The schedule would not be repeated.
Category:
Other
Cause:
null
Action:
null
ODI-1157
Coherence cluster property {0} is not found in the system properties for Agent {1}. Agent may connect to an unintended coherence cluster.
Category:
Other
Cause:
null
Action:
null
ODI-1158
Agent {0} started invoking load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}. Caused by: step {6}: {7}
Category:
Other
Cause:
null
Action:
null
ODI-1159
Agent {0} completed load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1160
Agent {0} started processing load plan step {5} of load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1161
Agent {0} completed load plan step {5} (status={6}) of load plan instance {1} ({2}), run {3} in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1162
Scheduled task failed with id {0} of work repository {1} on Agent {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1163
The load plan logs purge operation failed on Agent {0}: {1}
Category:
Other
Cause:
null
Action:
null
ODI-1165
Client requires a repository with version {0} but the repository version found is {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1166
Connection to Enterprise Scheduler {0} succeeded with url={1}, factory={2}, JNDI Name={3}, user={4}
Category:
Other
Cause:
null
Action:
null
ODI-1167
Connection to Enterprise Scheduler {0} failed with url={1}, factory={2}, JNDI Name={3}, user={4}
Category:
Other
Cause:
null
Action:
null
ODI-1168
Authentication failed while connection to REST URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1169
Resource not found response for REST URL : {0}. URL not mapped to a REST resource
Category:
Other
Cause:
null
Action:
null
ODI-1170
Bad Request error for REST URL : {0}. Insufficient parameter(s) in the request
Category:
Other
Cause:
null
Action:
null
ODI-1171
Invalid REST base path URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1172
Valid REST base path URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1173
Method not allowed error for OPTIONS call on the URL : {0}. It can be a valid REST path
Category:
Other
Cause:
null
Action:
null
ODI-1174
Unable to determine the validity of URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1175
Allowed Methods : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1176
HTTP Method Used: {0}
Category:
Other
Cause:
null
Action:
null
ODI-1177
Tool Invocation Time : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1178
Request URI : {0} Request Headers : {1}
Category:
Other
Cause:
null
Action:
null
ODI-1179
Response Code : {0} Response Message : {1} Response Family : {2} Response Headers : {3} Response Metadata : {4} Response MediaType : {5} Response Error Message : {6}
Category:
Other
Cause:
null
Action:
null
ODI-1180
Response: not available
Category:
Other
Cause:
null
Action:
null
ODI-1181
System property {0} is not defined
Category:
Other
Cause:
null
Action:
null
ODI-1182
Unable to resolve key {0} to a file. details follow :
Category:
Other
Cause:
null
Action:
null
ODI-1183
Lookup of class for {0} failed
Category:
Other
Cause:
null
Action:
null
ODI-1184
Lookup of key {1} returned class {1}, but class was not found in classpath
Category:
Other
Cause:
null
Action:
null
ODI-1185
Lookup of JAR for {0} failed
Category:
Other
Cause:
null
Action:
null
ODI-1186
Lookup of {0} returned JAR {1}, but JAR was not found
Category:
Other
Cause:
null
Action:
null
ODI-1187
The argument {0}, used as the path ({1}), was not found
Category:
Other
Cause:
null
Action:
null
ODI-1188
One of the System properties {0} or {1} must be defined
Category:
Other
Cause:
null
Action:
null
ODI-1189
Authentication failed while connection to BDC REST URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1190
Resource not found response for BDC REST URL : {0}. URL not mapped to a REST resource
Category:
Other
Cause:
null
Action:
null
ODI-1191
Bad Request error for BDC REST URL : {0}. Insufficient parameter(s) in the request
Category:
Other
Cause:
null
Action:
null
ODI-1192
Invalid BDC REST base path URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1193
Valid BDC REST base path URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1194
Method not allowed error for OPTIONS call on the BDC REST URL : {0}. It can be a valid REST path
Category:
Other
Cause:
null
Action:
null
ODI-1195
Unable to determine the validity of BDC REST URL : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1196
Allowed Methods : {0}
Category:
Other
Cause:
null
Action:
null
ODI-1200
Session start failure: the request is incorrectly formed.
Category:
Other
Cause:
A malformed request was sent to the agent.
Action:
Verify the request format and parameters sent to the agent.
ODI-1201
Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.
Category:
Other
Cause:
An incorrect connection was used for the master repository database, or repository database was down.
Action:
Verify the master repository connection information and the status of the master repository database.
ODI-1202
Session start failure on agent {0}: data source for master repository does not contain a master repository.
Category:
Other
Cause:
The master repository connection information pointed to a database schema that did not contain a master repository.
Action:
Verify the master repository connection information.
ODI-1203
Session start failure on agent {0}: the master repository is in an invalid state.
Category:
Other
Cause:
The master repository was in a state that did not allow connections. This is the case if an upgrade was being performed.
Action:
Verify the state of the master repository.
ODI-1204
Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.
Category:
Other
Cause:
The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.
Action:
Upgrade the master repository version or the agent version.
ODI-1205
Session start failure on agent {0}: an authentication error occurred while connecting to the master repository.
Category:
Other
Cause:
An incorrect ODI user or password was specified for this master repository.
Action:
Verify the ODI user and password used for connecting.
ODI-1206
Session start failure on agent {0}: the agent is not defined in the topology for master repository.
Category:
Other
Cause:
The session was not found in the master repository.
Action:
Verify that a session with this ID exists in the repository.
ODI-1207
Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
Category:
Other
Cause:
An incorrect connection was used for the work repository database, or repository database was down.
Action:
Verify the work repository connection information and the status of the work repository database.
ODI-1208
Session start failure on agent {0}: database schema {1} does not contain a work repository.
Category:
Other
Cause:
The work repository connection information pointed to a database schema that did not contain a work repository.
Action:
Verify the work repository connection information.
ODI-1209
Session start failure on agent {0}: work repository {1} is in an invalid state.
Category:
Other
Cause:
The work repository was in a state that did not allow connections. This is the case if an upgrade was being performed.
Action:
Verify the state of the work repository.
ODI-1210
Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
Category:
Other
Cause:
The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.
Action:
Upgrade the work repository version or the agent version.
ODI-1211
Session start failure on agent {0}: work repository {1} is not bound to the master repository.
Category:
Other
Cause:
The work repository specified in the request was not found in the list of work repositories attached to this master.
Action:
Verify that work repository name matches an existing one.
ODI-1212
Session preparation failure: scenario {0} does not exist in work repository {1}.
Category:
Other
Cause:
The session request was received, but the agent was unable to find the named scenario in the work repository.
Action:
Verify that the scenario name matches an existing scenario name in the work repository.
ODI-1213
Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.
Category:
Other
Cause:
The session request was received, and the scenario existed in the work repository, but not with the specified version.
Action:
Ensure that the scenario version matches an existing scenario version in the work repository.
ODI-1214
Session preparation failure: context {0} does not exist in the master repository.
Category:
Other
Cause:
The session request was received, but the agent was unable to find the context in the master repository.
Action:
Ensure that the context matches an existing context code in the Topology.
ODI-1215
Session preparation failure: privileges are insufficient to run scenario {0}.{1} in repository {2}.
Category:
Other
Cause:
User privileges were not sufficient for running this scenario in this repository.
Action:
Ensure that the user has sufficient privileges for this task.
ODI-1216
Session preparation failure: insufficient privileges to use Context {0} ({1}).
Category:
Other
Cause:
User privileges were not sufficient for using this context.
Action:
Ensure that the user has sufficient privileges for this task.
ODI-1217
Session {0} ({1}) fails with return code {2}.
Category:
Other
Cause:
The session finished in an error state.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1218
Session preparation failure: database error occurs while connecting to the master repository.
Category:
Other
Cause:
The agent received a database error from the master repository while creating the session.
Action:
Verify the state of the master repository database.
ODI-1219
Session preparation failure: database error while connecting to work repository {0}.
Category:
Other
Cause:
The agent received a database error from the work repository while creating the session.
Action:
Verify the state of the work repository database.
ODI-1220
Session preparation failure: an unexpected exception occurred.
Category:
Other
Cause:
The remote agent faced an unexpected error while attempting to create the session.
Action:
Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
ODI-1221
Unable to restart session {0}: session is not found in work repository {1}.
Category:
Other
Cause:
The session to restart did not exist in the repository. This session may have been deleted, or an incorrect session ID or work repository was supplied.
Action:
Verify that a session with this ID exists in the repository.
ODI-1222
Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.
Category:
Other
Cause:
The object to be executed referred to a logical schema not present in the master repository.
Action:
Ensure that the logical schema configuration exists in your master repository.
ODI-1223
Database error while connecting to the master repository.
Category:
Other
Cause:
The connection for the master repository database was incorrect, or the repository database was down.
Action:
Verify the master repository connection information and the status of the master repository database.
ODI-1224
Database error while connecting to work repository {0}
Category:
Other
Cause:
The connection for the work repository database was incorrect, or the repository database was down.
Action:
Verify the work repository connection information and the status of the master repository database.
ODI-1225
An unexpected exception occurred.
Category:
Other
Cause:
The agent faced an unexpected exception.
Action:
Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
ODI-1226
Step {0} fails after {1} attempt(s).
Category:
Other
Cause:
This is an execution warning. The session step failed to execute after the maximum number of retries. If step failure was not handled in the package design, the session finished in an error state.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1227
Task {0} fails on the source connection {1}.
Category:
Other
Cause:
This is an execution warning. The command on the source for this task finished with an error.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1228
Task {0} fails on the target connection {1}.
Category:
Other
Cause:
This is an execution warning. The command on the target for this task finished with an error.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1229
An error occurred while performing a {0} operation on model code {1}.
Category:
Other
Cause:
This is an execution warning. The operation specified failed on the model.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1231
An error occurred while performing a {0} operation on datastore {1}.
Category:
Other
Cause:
This is an execution warning. The operation specified failed on the datastore.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1232
Procedure {0} execution fails.
Category:
Other
Cause:
This is an execution warning. The procedure execution failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1233
Error while evaluating variable the following expression: {0} {1} {2}
Category:
Other
Cause:
This is an execution warning. The variable evaluation failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1235
Error while incrementing variable {0} to value {1}
Category:
Other
Cause:
This is an execution warning. The variable increment failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1236
Error while refreshing variable {0}.
Category:
Other
Cause:
This is an execution warning. The variable refresh failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1237
Error while setting variable {0} to value {1}.
Category:
Other
Cause:
This is an execution warning. The set variable operation failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1238
Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.
Category:
Other
Cause:
This is an execution warning. The interface failed because the number of errors detected in the flow exceeded the value defined in the interface.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
ODI-1239
Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.
Category:
Other
Cause:
This is an execution warning. The interface failed because the percentage of errors detected in the flow exceeded the value defined in the interface.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.
ODI-1240
Flow {0} fails while performing a {1} operation. This flow loads target table {2}.
Category:
Other
Cause:
This is an execution warning. The interface failed because one of the statements returned an error return code.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1241
Oracle Data Integrator tool execution fails.
Category:
Other
Cause:
This is an execution warning. The tool execution failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1242
Operating system command execution fails.
Category:
Other
Cause:
This is an execution warning. Execution of the operating system command failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1243
Session {0} ({1}) fails because work repository {2} went down.
Category:
Other
Cause:
Work repository database went down while session was being executed.
Action:
Verify the state of the work repository database. The session must be restarted.
ODI-1244
Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.
Category:
Other
Cause:
Work repository database went down while session was starting its execution.
Action:
Verify the state of the work repository database. The session must be restarted.
ODI-1245
Session preparation failure: work repository {0} went down during session preparation.
Category:
Other
Cause:
Work repository went down while session was being prepared.
Action:
Verify the state of the work repository database. The session must be restarted.
ODI-1246
The Logical Schema has not been set for {0}.
Category:
Other
Cause:
Because the logical schema had not been set, the object could not be executed.
Action:
Verify the object that you are trying to execute, and set the logical schema for this object.
ODI-1247
Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.
Category:
Other
Cause:
Master repository database went down while session was starting its execution.
Action:
Verify the state of the master repository database. The session must be restarted.
ODI-1248
Session preparation failure by Agent {0}: master repository went down during session preparation.
Category:
Other
Cause:
Master repository went down while session was being prepared.
Action:
Verify the state of the master repository database. The session must be restarted.
ODI-1249
Session {0} ({1}) fails because master repository went down.
Category:
Other
Cause:
Master repository database went down while session was being executed.
Action:
Verify the state of the master repository database. The session must be restarted.
ODI-1250
Session {0} ({1}) could not be stopped by Agent {2} because session {0} {1} already completed execution.
Category:
Other
Cause:
The session has already completed and cannot be stopped.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1251
Session ({0}) could not be stopped by Agent {1} because session ({0}) was not found in work repository {2}.
Category:
Other
Cause:
The session was not found in the work repository.
Action:
Verify that a session with this ID exists in the repository.
ODI-1252
Session ({0}) could not be stopped by Agent {1}: insufficient privileges to access session.
Category:
Other
Cause:
User privileges were not sufficient for accessing this session in this agent.
Action:
Ensure that the user has sufficient privileges for this task.
ODI-1253
Session {0} ({1}) could not be stopped by Agent {2}: an unknown error occurred.
Category:
Other
Cause:
An unexpected Exception occurred.
Action:
Verify your Agent configuration and make sure other operations on Agent are working correctly.
ODI-1254
Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.
Category:
Other
Cause:
The agent had incorrect connection for the work repository database, or repository database was down.
Action:
Verify the work repository connection information and the status of the work repository database.
ODI-1255
Session {0} ({1}) could not be stopped by Agent {2}: insufficient privileges to stop the session.
Category:
Other
Cause:
User privileges were not sufficient for stopping this session in this agent.
Action:
Ensure that the user has sufficient privileges for this task.
ODI-1256
Session {0} ({1}) stopped (Normal) by user {2}.
Category:
Other
Cause:
Session was stopped by the user.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1257
Session {0} ({1}) stopped (Immediate) by user {2}.
Category:
Other
Cause:
Session was stopped by the user.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1258
Session {0} ({1}) stopped (Abort) by user {2}.
Category:
Other
Cause:
Session was aborted by the user.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1259
Session Task {0} stopped (Normal) by user {1}.
Category:
Other
Cause:
Task was stopped by the user.
Action:
Review the task execution details in the Operator Navigator or Repository Explorer.
ODI-1260
Session Task {0} stopped (Immediate) by user {1}.
Category:
Other
Cause:
Task was stopped by the user.
Action:
Review the task execution details in the Operator Navigator or Repository Explorer.
ODI-1261
Session Task {0} stopped (Abort) by user {1}.
Category:
Other
Cause:
Task was aborted by the user.
Action:
Review the task execution details in the Operator Navigator or Repository Explorer.
ODI-1262
Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.
Category:
Other
Cause:
The agent had incorrect connection for the master repository database, or repository database was down.
Action:
Verify the master repository connection information and the status of the master repository database.
ODI-1263
Step {0} stopped (Normal) by user {1}.
Category:
Other
Cause:
Step was stopped by the user.
Action:
Review the step execution details in the Operator Navigator or Repository Explorer.
ODI-1264
Step {0} stopped (Immediate) by user {1}.
Category:
Other
Cause:
Step was stopped by the user.
Action:
Review the step execution details in the Operator Navigator or Repository Explorer.
ODI-1265
Step {0} stopped (Abort) by user {1}.
Category:
Other
Cause:
Step was aborted by the user.
Action:
Review the step execution details in the Operator Navigator or Repository Explorer.
ODI-1266
Agent {0} detected Session as stale session and set to error status.
Category:
Other
Cause:
The agent detected a stale session and the session status was set to error status.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1267
Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.
Category:
Other
Cause:
The agent attempted to stop a session with an invalid stop type.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1268
Agent {0} does not support stopping asynchronous child sessions.
Category:
Other
Cause:
The agent attempted to stop an asynchronous child session and this is not supported.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1269
Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.
Category:
Other
Cause:
The agent attempted to stop a session that is being run by a different agent.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1270
Session {0} ({1}) could not be stopped by Agent {2}: session {0} ({1}) is being run by {3} Agent which is not a listener Agent.
Category:
Other
Cause:
The agent attempted to stop a session that is being run by the internal agent and this is not supported.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1271
The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.
Category:
Other
Cause:
The agent attempted to set the status of the asynchronous ESS job and its jndi name was not set.
Action:
Review the jndi name supplied to the Enterprise Scheduler job.
ODI-1272
The Logical Schema has not been set on {0} for {1}.
Category:
Other
Cause:
The logical schema for this object has not been set.
Action:
Verify that the logical schema has been set in the Topology.
ODI-1273
The selected technology {0} is not supported on source for {1}.
Category:
Other
Cause:
The selected technology is not supported for this object.
Action:
Verify that the object has a valid technology.
ODI-1274
Agent Exception
Category:
Other
Cause:
An error was detected by the agent when performing an operation.
Action:
Review the underlying exception for more details.
ODI-1275
An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.
Category:
Other
Cause:
This is an execution warning. The operation specified failed on the submodel operation.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1276
An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.
Category:
Other
Cause:
An error was occurred while executing the OnConnect command on the JDBC connection created to the data server.
Action:
Review the underlying exception and update the OnConnect command definition configured for the data server.
ODI-1277
An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.
Category:
Other
Cause:
An error was occurred while executing the OnDisconnect command on the JDBC connection created to the data server.
Action:
Review the underlying exception and update the OnDisconnect command definition configured for the data server.
ODI-1278
Load plan instance {0}, run {1} does not exist in work repository {2}.
Category:
Other
Cause:
The Load Plan Instance run does not exist in the repository. This Load Plan Instance run may have been deleted, or an incorrect instance ID/run number or work repository was supplied.
Action:
Verify that a load plan instance run with this instance ID and run number exists in the repository.
ODI-1279
The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
Category:
Other
Cause:
The Logical Schema to Physical Schema Mapping is not defined for the Context used.
Action:
For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
ODI-1280
The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
Category:
Other
Cause:
The Logical Schema to Physical Schema Mapping is not defined for the Context used.
Action:
For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.
ODI-1281
Source Technology {0} of task {1} is not of JDBC Type. When both Source and Target commands are specified, the Source Technology should be of JDBC type.
Category:
Other
Cause:
When Source and Target commands are specified, the Source Technology should always be of JDBC type.
Action:
Make Sure that you modify your Procedure or KM to either use a JDBC Source Technology or edit your step to use only the Target command.
ODI-1282
Invalid log level {0} is specified. A valid log level value is between {1} and {2}.
Category:
Other
Cause:
Invalid log level specified for scenario/session invocation or for session restart.
Action:
Please specify a valid log level.
ODI-1283
Owb preparation failure: Owb object {0} of type {1} in location {2} does not exist in Owb repository {3}.
Category:
Other
Cause:
The session request was received, but the agent was unable to find the named Owb object in the Owb repository.
Action:
Verify that the Owb object name matches an existing Owb object in the location in the Owb repository.
ODI-1284
Session {0} ({1}) with Owb audit Id {2} fails.
Category:
Other
Cause:
The session finished in an error state.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1285
Session {0} ({1}) Retreival of audit for auditId {2} failed in the {3} phase {4}. Please use OWB Design Client or Browser for further information.
Category:
Other
Cause:
An error was raised during the retreival of the Owb audit data.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
ODI-1286
Session {0} ({1}) could not find Owb job for this session.
Category:
Other
Cause:
The session being aborted is not an Owb Job.
Action:
Review the session being aborted in the Operator Navigator or Repository Explorer.
ODI-1287
Session {0} ({1}) with Owb audit Id {2} is in an invalid state to be aborted.
Category:
Other
Cause:
The session being aborted is not in a state that can be aborted.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
ODI-1288
Session {0} ({1}) with Owb audit Id {2} abort fails.
Category:
Other
Cause:
The session abort finished in an error state.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
ODI-1289
Agent {0} detected Session as stale session and set to error status. Please use OWB Design Client or Browser for further information.
Category:
Other
Cause:
The agent detected a stale OWB session and the session status was set to error status.
Action:
Review the session execution details in the OWB Design Client or Browser.
ODI-1290
Session {0} ({1}) Loading of audit for auditId {2} failed in the {3} phase {4}.
Category:
Other
Cause:
An error was raised during the loading of the Owb audit data.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
ODI-1291
Workspace {0} cannot be resolved to a physical workspace using context {1}.
Category:
Other
Cause:
The context does not contain a mapping for the logical workspace.
Action:
Review the mappings defined in the context.
ODI-1292
An execution context cannot be determined for this job.
Category:
Other
Cause:
An execution context cannot be determined for this job.
Action:
Use the Context to provide an explicit context for this execution.
ODI-1293
Exception occurred during spawning of ECID to child session.
Category:
Other
Cause:
Spawning of ECID from parent session to child session failed.
Action:
Review the exception raised to get more detail.
ODI-1294
Unwrapping of a wrapped ECID [{0}] failed.
Category:
Other
Cause:
Unwrapping of ECID failed.
Action:
Review the exception raised and the format of wrapped ECID to get more detail on unwrap failure
ODI-1295
Cleanup of Session {0} ({1}) raised the following {2} messages: {3}
Category:
Other
Cause:
Messages were raised during the Cleanup phase.
Action:
Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
ODI-1296
The Cleanup Tool encountered the following {0} nested errors when executing the Cleanup tasks: {1}
Category:
Other
Cause:
Messages were raised during the Cleanup tool execution.
Action:
Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
ODI-1297
Parallel task "{0}" failed; {1} child task(s) in error; Failed child tasks: {2}
Category:
Other
Cause:
null
Action:
null
ODI-1298
Serial task "{0}" failed because child task "{1}" is in error.
Category:
Other
Cause:
null
Action:
null
ODI-1299
A task "{0}" from one of the parallel branches has failed. Hence aborting the current branch
Category:
Other
Cause:
null
Action:
null
ODI-1300
ASYNC_JNDI_NAME cannot be null for async job.
Category:
Other
Cause:
Action:
ODI-1301
Unable to submit Job Definition: {0}
Category:
Other
Cause:
Action:
ODI-1302
Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}
Category:
Other
Cause:
Action:
ODI-1303
RuntimeSessionfactory must not be null.
Category:
Other
Cause:
Action:
ODI-1304
Unable to find request for ID {0}
Category:
Other
Cause:
Action:
ODI-1305
jobDefinitionId must not be null
Category:
Other
Cause:
Action:
ODI-1306
scheduleDefinitionId must not be null
Category:
Other
Cause:
Action:
ODI-1307
ContextCode is null, cannot lookup physical agent
Category:
Other
Cause:
Action:
ODI-1308
SchedulingService object was created without an EntityManager, cannot lookup physical agent
Category:
Other
Cause:
Action:
ODI-1309
Unable to find logical agent : {0}.
Category:
Other
Cause:
Action:
ODI-1310
Unable to find context : {0}.
Category:
Other
Cause:
Action:
ODI-1311
JobDefinition with name {0} already exists.
Category:
Other
Cause:
JobDefinition already exists.
Action:
Check JobDefinition name.
ODI-1312
Schedule with name {0} already exists.
Category:
Other
Cause:
Schedule already exists.
Action:
Check Schedule name.
ODI-1313
Unable to find job definition for ID {0}.
Category:
Other
Cause:
Wrong ID.
Action:
Check ID.
ODI-1314
Unable to find job definition with name {0}.
Category:
Other
Cause:
Wrong name.
Action:
Check name.
ODI-1315
Unable to update job definition.
Category:
Other
Cause:
Exception during updating.
Action:
Check cause exception details.
ODI-1316
Unable to remove job request.
Category:
Other
Cause:
Exception was thrown.
Action:
Check cause exception details.
ODI-1317
Unable to find scheduler definition with name {0}.
Category:
Other
Cause:
Wrong name.
Action:
Check name.
ODI-1318
jobDefnition is required to have a not null ID.
Category:
Programmatic
Cause:
Metadata Object ID is null.
Action:
Check job definition.
ODI-1319
Error while refreshing variable {0}. Null/Empty refresh query is provided.
Category:
Other
Cause:
This is an execution warning. The variable refresh failed.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-1320
Session start/restart failure on agent {0}: the session {1} is not in status WAITING, ERROR or WARNING
Category:
Other
Cause:
The session cannot be started/restarted because it is not in status WAITING, ERROR or WARNING
Action:
Verify that a session with this ID exists in the repository and status WAITING, ERROR or WARNING.
ODI-1350
Credential map key ''{0}'' not found in credential map ''{1}''.
Category:
Other
Cause:
Action:
ODI-1351
An unexpected error was thrown during execution of the scenario ''{0} - {1}''
Category:
Other
Cause:
Action:
ODI-1352
An unexpected error was thrown during job execution
Category:
Other
Cause:
Action:
ODI-1353
RequestId={0} Scenario={1} : Agent URL must be specified. The Job Definition must include the LocalAgent or the job submission must include a physical agent url ({2}) parameter.
Category:
Other
Cause:
Action:
ODI-1354
Load plan must be asynchronous
Category:
Other
Cause:
Action:
ODI-1355
username ''{0}'' from credential map ''{1}'' does not match currentSubjectName ''{2}''
Category:
Other
Cause:
Action:
ODI-1356
Credential map key parameter ''{0}'' not found.
Category:
Other
Cause:
Action:
ODI-1357
Error resolving ADF connection for connectionId=''{0}''.
Category:
Other
Cause:
Action:
ODI-1400
Agent {0} start failure: JDBC connection error occurs while connecting to the master repository.
Category:
Other
Cause:
The master repository information was incorrect, or the repository database was down.
Action:
Verify the master repository connection information and the status of the master repository database.
ODI-1401
Agent {0} start failure: data source for master repository did not contain a master repository.
Category:
Other
Cause:
The master repository connection information pointed to a database schema that did not contain a master repository.
Action:
Verify the master repository connection information.
ODI-1402
Agent {0} start failure: the master repository is in an invalid state.
Category:
Other
Cause:
The master repository was in a state that did not allow connections. This is the case when an upgrade is being performed.
Action:
Verify the state of the master repository.
ODI-1403
Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.
Category:
Other
Cause:
The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.
Action:
Upgrade the master repository version or the agent version.
ODI-1404
Agent {0} start failure: an authentication error occurred while connecting to the master repository.
Category:
Other
Cause:
An incorrect ODI user or password was specified for this master repository.
Action:
Verify the ODI user and password used for connecting.
ODI-1405
Agent {0} start failure: the agent is not defined in the topology for master repository.
Category:
Other
Cause:
This agent was not declared in the topology.
Action:
Add this physical agent in the list of agents in the ODI topology.
ODI-1406
Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.
Category:
Other
Cause:
The work repository information was incorrect, or the repository database was down.
Action:
Verify the work repository connection information and the status of the work repository database.
ODI-1407
Agent {0} started with warning: connection details of {1} do not contain a work repository.
Category:
Other
Cause:
The work repository connection information pointed to a database schema that did not contain a work repository.
Action:
Review the work repository connection information and revise it as necessary.
ODI-1408
Agent {0} started with warning: work repository {1} is in an invalid state.
Category:
Other
Cause:
The work repository was in a state that did not allow connections. This is the case when an upgrade is being performed.
Action:
Verify the state of the work repository.
ODI-1409
Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.
Category:
Other
Cause:
The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.
Action:
Upgrade the work repository version or the agent version.
ODI-1410
Agent {0} started with warning: work repository {1} is not bound to the master repository.
Category:
Other
Cause:
The work repository specified in the request was not found in the list of work repositories attached to this master.
Action:
Ensure that work repository name matches an existing one.
ODI-1411
Agent {0} started with warning: a database error occurs while cleansing stale sessions.
Category:
Other
Cause:
The agent encountered a database error while attempting to close stale sessions.
Action:
Review the status of the sessions for this agent, and manually remove the stale sessions.
ODI-1412
Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.
Category:
Other
Cause:
The agent encountered an unexpected error while attempting to close stale sessions.
Action:
Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Verify the status of the sessions for this agent, and manually remove the stale sessions.
ODI-1413
Request is incorrectly formed.
Category:
Other
Cause:
A malformed request was sent to the agent.
Action:
Review the request format and parameters sent to the agent.
ODI-1414
Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.
Category:
Other
Cause:
The remote agent had incorrect connection for the master repository database, or repository database was down.
Action:
Verify the master repository connection information and the status of the master repository database.
ODI-1415
Error connecting to agent {0}: data source for master repository did not contain a master repository.
Category:
Other
Cause:
The master repository connection information for the remote agent pointed to a database schema that did not contain a master repository.
Action:
Review the master repository connection information and revise it as necessary.
ODI-1416
Error connecting to agent {0}: the master repository is in an invalid state.
Category:
Other
Cause:
The master repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.
Action:
Verify the state of the master repository.
ODI-1417
Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.
Category:
Other
Cause:
The master repository was upgraded but not the remote agent, or the remote agent was upgraded but not the master repository.
Action:
Upgrade the master repository version or the agent version.
ODI-1418
Error connecting to agent {0}: an authentication error occurs while connecting to the master repository.
Category:
Other
Cause:
An incorrect ODI user or password was specified for this master repository.
Action:
Verify the ODI user and password used for connecting.
ODI-1419
Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
Category:
Other
Cause:
The remote agent had incorrect connection for the work repository database, or the repository database was down.
Action:
Verify the work repository connection information and the status of the work repository database.
ODI-1420
Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.
Category:
Other
Cause:
The work repository connection information for the remote agent pointed to a database schema that did not contain a work repository.
Action:
Verify the work repository connection information.
ODI-1421
Warning connecting to Agent {0}: work repository {1} is in an invalid state.
Category:
Other
Cause:
The work repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.
Action:
Verify the state of the work repository.
ODI-1422
Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
Category:
Other
Cause:
The work repository was upgraded but not the remote agent, or the remote agent was upgraded but not the work repository.
Action:
Upgrade the work repository version or the agent version.
ODI-1423
Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.
Category:
Other
Cause:
The work repository specified in the request was not found in the list of work repositories attached to the master.
Action:
Verify that work repository name matches an existing one.
ODI-1424
Agent host or port cannot be reached using {0}.
Category:
Other
Cause:
Incorrect host or port information was provided, or the agent was not started on the remote host.
Action:
Correct the host or port information or start the agent.
ODI-1425
Agent application cannot be reached using {0}.
Category:
Other
Cause:
An incorrect application name was provided for this agent, or the agent application was not started on the host.
Action:
Correct the application name used in the URL or verify the agent status.
ODI-1426
Agent {0} is not defined in the topology for the master repository.
Category:
Other
Cause:
This agent was not declared in the topology.
Action:
Add this physical agent to the list of agents in the ODI topology.
ODI-1427
invalid parameters
Category:
Other
Cause:
Invalid parameters were supplied in the request.
Action:
Check the parameters that were supplied as part of the request. Ensure that parameter names and cases are correct.
ODI-1428
internal error
Category:
Other
Cause:
An agent internal error occurred.
Action:
Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).
ODI-1429
The user {0} is not authorized to perform request {1} on Agent {2}.
Category:
Other
Cause:
The user had insufficient privileges for performing this request against the remote agent.
Action:
Amend the user privileges.
ODI-1430
Agent {0} cannot clean the stale sessions in work repository {1} due to a database error.
Category:
Other
Cause:
The remote agent faced a database error while attempting to close stale sessions.
Action:
Examine the status of the sessions for this agent, and manually remove the stale sessions.
ODI-1431
Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.
Category:
Other
Cause:
The remote agent was not able to connect to the work repository while attempting to close stale sessions.
Action:
Determine the status of the repository. Once this repository is running, manually remove the stale sessions.
ODI-1432
Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.
Category:
Other
Cause:
The remote agent faced an unexpected error while attempting to close stale sessions.
Action:
Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Determine the status of the sessions for this agent, and manually remove the stale sessions.
ODI-1433
The Internal agent does not support cleaning stale sessions from multiple work repositories.
Category:
Other
Cause:
Empty string value was passed for the work repository name in the Clean Stale Sessions request sent to the Internal Agent.
Action:
Specify a non-empty valid work repository name in the Clean Stale Sessions request sent to the Internal Agent. If you want to clean the stale sessions across the work repositories, perform this operation on a Remote physical Agent.
ODI-1434
Agent {0} start failure: error while trying to use JMX Port {1}.
Category:
Other
Cause:
JMX Registry was unable to use the given port.
Action:
Specify a different port by using the command-line parameter JMXPORT.
ODI-1435
Storage space for the IDs of some object types is low in Repository {0}. When no storage space is available, it will not be possible to create obects of these types. Consider creating a new repository for the following object types (Object Type: Number Remaining) {1}.
Category:
Other
Cause:
Storage space was low for some IDs in this repository.
Action:
Consider creating a new repository.
ODI-1436
Error retrieving ID statistics for repository {0}.
Category:
Other
Cause:
The ID statistics for this repository could not be verified.
Action:
Verify the statistics for this repository manually.
ODI-1437
Error retrieving information from the credential store map.
Category:
Other
Cause:
Could not retrieve information from the credential store map.
Action:
Verify that the credentials have been entered correctly into the credential store map.
ODI-1438
Agent {0} cannot be stopped by user {1}: a JDBC error occurred on master repository {2}.
Category:
Other
Cause:
Some SQL Exception occurred on the Master Repository.
Action:
Verify that other operations on the Agent are working correctly.
ODI-1439
Agent {0} cannot be stopped by user {1}: a JDBC error occurred on work repository {2}.
Category:
Other
Cause:
Some SQL Exception occurred on the Work Repository.
Action:
Verify that other operations on the Agent are working correctly.
ODI-1440
Agent {0} cannot be stopped by user {1}: an unknown error occurred.
Category:
Other
Cause:
An unexpected Exception occurred.
Action:
Verify your Agent configuration and make sure other operations on Agent are working correctly.
ODI-1441
Unable to connect to the master repository at JBDC URL={0} with USER={1}.
Category:
Other
Cause:
An SQLException occurred while creating connection to the master repository with the given parameters.
Action:
Verify your Agent configuration and make sure the master repository connection parameters are correct.
ODI-1442
Unable to load JBDC Driver {0} configured for master repository connection.
Category:
Other
Cause:
ClassNotFoundException occurred while loading the driver class.
Action:
Verify your Agent configuration and make sure the driver specified for master repository connection is correct and the corresponding jar is present under driver folder.
ODI-1443
Error while starting agent : {0}
Category:
Other
Cause:
Error occurred while starting the embedded web container.
Action:
Verify your Agent configuration and make sure that the specified ports are available.
ODI-1444
The master repository signature specified by the client {0} does not match the master repository signature of the agent {1}.
Category:
Other
Cause:
The client and the agent are not using the same master repository
Action:
Verify the client and the agent are using the same master repository. Verify that the client is calling the correct agent.
ODI-1445
Invalid HTTP/S URL retrieved from the JRF utility : {0}
Category:
Other
Cause:
JRF utility has returned an invalid HTTP/S URL for the agent.
Action:
Verify if ODI agent's dependent modules are successfully deployed on the container.
ODI-1446
Agent {0} is already running on port {1}.
Category:
Other
Cause:
This agent is already running.
Action:
Stop the agent before attempting to start it.
ODI-1447
Agent {0} failed to start. {1}.
Category:
Other
Cause:
The agent failed to start.
Action:
See the nodemanager and agent log for further information.
ODI-1448
Failed to execute command {1} for agent {0}.
Category:
Other
Cause:
A command failed to execute on the agent.
Action:
Review the agent log for further information.
ODI-1449
Injection risk detected for command {0}. Command not executed.
Category:
Other
Cause:
The command was not executed because it contained characters that pose an injection risk.
Action:
Adjust the command to eliminate characters that pose an injection risk.
ODI-1450
ODI does not support soft restart.
Category:
Other
Cause:
The process management softRestart method was invoked, but it is not supported.
Action:
Do not invoke the softRestart method.
ODI-1451
Using localhost for hostname because of {0} when trying to get hostname.
Category:
Other
Cause:
An exception was thrown while trying to get the actual host name for the local host.
Action:
No action is required as the exception is caught and the host name is defaulted to localhost.
ODI-1452
Agent {0} cannot be started, {1} is already in use by another agent.
Category:
Other
Cause:
An attempt was made to restart the agent, but it is currently in use.
Action:
Wait for other dependent agents to complete before restarting this agent.
ODI-1453
Agent {0} cannot be started, {1} is already in use by another process.
Category:
Other
Cause:
An attempt was made to restart the agent, but it is currently in use.
Action:
Wait for dependent processes to complete before restarting this agent.
ODI-1454
Agent {0} cannot be started at {1}. Unexpected http response = {2}.
Category:
Other
Cause:
The agent cannot be started. It is possible that another processes is already running on the agent port.
Action:
Review the http response to determine the process running on the agent port.
ODI-1455
System componenent creation failed: instanceName={0}, cause={1}
Category:
Other
Cause:
An exception prevented the ODI component from being created.
Action:
Review the exception to determine the cause.
ODI-1456
getServerConfiguration() failed. domainDir={0}, dirPath={1}, instanceName={2}, cause={3}
Category:
Other
Cause:
An exception was thrown while setting the ODI configuration parameters.
Action:
Review the exception text at the end of the message to determine the cause.
ODI-1457
getDBConfiguration() failed. domainDir={0}, dirPath={1}, datasourceName={2}, cause={3}
Category:
Other
Cause:
An exception was thrown while setting the ODI database configuration parameters.
Action:
Review the exception text at the end of the message to determine the cause.
ODI-1458
ODI configuration files found, but a corresponding instance is not configured. dirPath={0}. Cause={1}
Category:
Other
Cause:
An exception was thrown while retrieving database configuration parameters from a file.
Action:
Review the exception text at the end of the message to determine the file name and exception cause.
ODI-1459
Failed to retrieve master repository name and timestamp for agent {0}. Using the values from instance.properties. Cause={1}
Category:
Other
Cause:
An exception was thrown while attempting to read metadata for the master repository.
Action:
Review the exception text at the end of the message to determine the cause.
ODI-1460
Unable to insert into table {0} for concurrent execution control. Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem. Error message: {1}
Category:
Other
Cause:
An exception was raised when inserting a record into the concurrent execution control table.
Action:
Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem.
ODI-1461
{0} job status has changed unexpectedly from {1} to {2} while waiting for its turn to run under concurrent execution control.
Category:
Other
Cause:
The status of a job was likely changed outside of the control of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.
Action:
The job may have been changed outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
ODI-1462
{0} job [{1}] should be the last one in the following waiting {0} list: {2}
Category:
Other
Cause:
The job may have been changed or deleted outside of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.
Action:
The job may have been changed or deleted outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
ODI-1463
{0} job [{1}] blocked by the following {0} job(s) due to potential concurrent execution condition: {2}{3}
Category:
Other
Cause:
The job was under concurrent execution control with Raise Error violation behavior, and there were existing runnable and/or waiting jobs submitted ahead of the job.
Action:
Start the job when other concurrently running and waiting jobs are completed, or change the job's violation behavior to Wait To Execute before starting the job.
ODI-1464
There is no Hadoop Dataserver selected for PigDataServer- {0} from topology.
Category:
Other
Cause:
Repository Error.
Action:
Verify the dataservers in topology and associate a Hadoop dataserver to Pig dataserver when in Mapreduce mode .
ODI-1465
Error while trying to read values of DataServer- {0} from topology.
Category:
Other
Cause:
Repository Error.
Action:
Verify the dataservers in topology and if needed, associate a Hadoop dataserver to Pig dataserver when in Mapreduce mode.
ODI-1466
Error occurred previewing file on agent {0}
Category:
Other
Cause:
Error previewing file on the agent
Action:
Verify that file configuration is valid. Verify that file is available
ODI-1467
Error occurred trying to find URL of ODI scripting JAR {0}
Category:
Other
Cause:
Error getting the URL of ODI scripting language JAR
Action:
Verify that the path is valid
ODI-1500
SQL Exception when accessing work repository {0} while executing load plan instance {1} - {2}
Category:
Other
Cause:
A SQLException was thrown when trying to update the work repository
Action:
The same set of updates will be attempted later, potentially from a different agent
ODI-1501
Cannot find variable "{0}" in the definition of load plan instance {1}.
Category:
Other
Cause:
The start/restart load plan request contained startup values for variables that are not defined in the load plan
Action:
User error or problem in the IDE invocation code
ODI-1502
Load plan instance {0} is in an inconsistent state: {1}
Category:
Other
Cause:
Indicates a problem in the ODI code, like a wrapped IllegalStateException
Action:
null
ODI-1503
Load plan logs for instance {0}, run {1} are corrupted: {2}
Category:
Other
Cause:
Indicates a problem in the ODI code, it is a wrapped IllegalStateException
Action:
null
ODI-1504
Trying to update variables during execution of step "{0}" (load plan instance {1}, run {2}), as part of the exception handler for step "{3}", but variable updates during exception handlers are not supported.
Category:
Other
Cause:
null
Action:
null
ODI-1505
Current value "{0}" of variable "{1}" (while evaluating When clause "{2}") is not a valid value of type {3} (load plan instance {4}, run {5}).
Category:
Other
Cause:
null
Action:
null
ODI-1506
"Comparison value of step "{2}" ("{0}") is not a valid value of type {3} (load plan instance {4}, variable tested "{1}").
Category:
Other
Cause:
null
Action:
null
ODI-1507
Load Plan Instance restart called for instance {0}, but no previous runs were found.
Category:
Other
Cause:
null
Action:
null
ODI-1508
Load Plan Instance start called for instance {0}, but previous runs have been found.
Category:
Other
Cause:
null
Action:
null
ODI-1509
Load Plan Instance {0} cannot be restarted because the previous run ({1}) status "{2}" is not in "{3}" status.
Category:
Other
Cause:
null
Action:
null
ODI-1510
The same load plan instance {0} simultaneously started by two agents.
Category:
Other
Cause:
null
Action:
null
ODI-1511
Step "{0}" should have already been marked as started before adding value for variable "{1}" (load plan instance {2}, run {3}).
Category:
Other
Cause:
null
Action:
null
ODI-1512
Variable "{0}" is defined as having datatype "{1}" in Load Plan instance {2}, but as having type "{3}" in scenario "{4}" (version {5}), Load Plan instance step "{6}".
Category:
Other
Cause:
null
Action:
null
ODI-1513
Error reading load plan information for session number {0}: "{1}"
Category:
Other
Cause:
null
Action:
null
ODI-1514
Error trying to stop load plan, instance {0} not found.
Category:
Other
Cause:
null
Action:
null
ODI-1515
Load Plan instance {0} could not be stopped by agent {1} because stop type ({2}) provided in the request is invalid.
Category:
Other
Cause:
null
Action:
null
ODI-1516
Can not start load plan: load plan with name "{0}" does not exist in work repository {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1517
Load Plan instance {0}, run {1} could not be stopped because that run is already completed (with status "{2}").
Category:
Other
Cause:
null
Action:
null
ODI-1518
Parallel step "{0}" failed; {1} child step(s) in error, which is more than the maximum number of allowed errors ({3}) defined for the parallel step. Failed child steps: {2}
Category:
Other
Cause:
null
Action:
null
ODI-1519
Serial step "{0}" failed because child step "{1}" is in error.
Category:
Other
Cause:
null
Action:
null
ODI-1520
Case-When/Else step "{0}" failed because child step "{1}" is in error.
Category:
Other
Cause:
null
Action:
null
ODI-1521
Case step "{0}" failed; the selected child "{1}" is in error.
Category:
Other
Cause:
null
Action:
null
ODI-1522
Run Scenario step failed during invocation. Error message was: {0}
Category:
Other
Cause:
null
Action:
null
ODI-1523
Exception handler for step "{0}" failed, because the root exception serial step "{1}" is in error.
Category:
Other
Cause:
null
Action:
null
ODI-1524
Physical agent {0} could not be found.
Category:
Other
Cause:
null
Action:
null
ODI-1525
Physical agent not found for logical agent name "{0}" and context "{1}" while executing step "{2}".
Category:
Other
Cause:
null
Action:
null
ODI-1526
Error encountered while trying to start scenario "{1}{2}" (step "{3}"): {0}
Category:
Other
Cause:
null
Action:
null
ODI-1527
Error refreshing variable "{0}": the associated SQL query returned no results.
Category:
Other
Cause:
null
Action:
null
ODI-1528
Error refreshing variable "{0}": {1}
Category:
Other
Cause:
null
Action:
null
ODI-1529
Refresh of variable "{0}" failed : {1} {2}
Category:
Other
Cause:
null
Action:
null
ODI-1530
Load plan instance was stopped by user request.
Category:
Other
Cause:
null
Action:
null
ODI-1531
Timeout triggered while executing step "{0}".
Category:
Other
Cause:
null
Action:
null
ODI-1532
Timeout triggered on a parent step "{0}" while executing step "{1}".
Category:
Other
Cause:
null
Action:
null
ODI-1533
Error refreshing variable "{0}": could not get a connection to the logical schema "{1}" using context {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1534
Could not get SQL query text for variable "{0}" while trying to refresh it.
Category:
Other
Cause:
null
Action:
null
ODI-1535
Can not continue load plan instance {0}, run {1}, because the instance has been deleted.
Category:
Other
Cause:
null
Action:
null
ODI-1536
Load plan instance {0}, run {1} failed to launch scenario: scenario {2} does not exist in work repository {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1537
Load plan instance {0}, run {1} failed to launch scenario: Version {3} of scenario {2} does not exist in work repository {4}.
Category:
Other
Cause:
null
Action:
null
ODI-1538
Unexpected Exception occurred while executing Load plan instance {0}, run {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1539
Agent {0} cannot continue load plan processing for instance {1}, run {2} on work repository {3}.
Category:
Other
Cause:
null
Action:
null
ODI-1540
Agent {0} start failure: error while trying to use Http Port {1}.
Category:
Other
Cause:
Http service was unable to use the given port.
Action:
Specify a different port by using the command-line parameter PORT.
ODI-1541
Load Plan start failure on agent {0}: ODI User and Password not specified.
Category:
Other
Cause:
ODI user and password are not set.
Action:
Please specify ODI user and password.
ODI-1542
Start Scenario failure on agent {0}: ODI User and Password not specified.
Category:
Other
Cause:
ODI User and password are not set.
Action:
Please specify ODI user and password.
ODI-1543
RuntimeAgent cannot be used inside an opened transaction, it must be used outside a TransactionTemplate
Category:
Other
Cause:
null
Action:
null
ODI-1544
None of the agents in Load Balancing list is able to handle this execution ({0}).
Category:
Other
Cause:
null
Action:
null
ODI-1545
Missing odi supervisor credentials in credential store map [{0}] with key [{1}].
Category:
Other
Cause:
Could not retrieve information from the credential store map.
Action:
Verify that the credentials have been entered correctly into the credential store map.
ODI-1546
The dbms_lock acquisition with lock handle {0} timed out.
Category:
Other
Cause:
null
Action:
null
ODI-1547
The Agent detected deadlock on dbms_lock acquisition with lock handle {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1548
The dbms_lock acquisition failed with illegal lock handle {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1549
The dbms_lock acquisition with lock handle {0} failed with illegal params error. The parameters are {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1550
The dbms_lock acquisition with lock handle {0} failed with unknown return code {1}
Category:
Other
Cause:
null
Action:
null
ODI-1551
The dbms_lock acquisition failed with a sql exception {0}. Please check if the work repository db user {1} has EXECUTE privilege on DBMS_LOCK package.
Category:
Other
Cause:
null
Action:
null
ODI-1552
The dbms_lock release failed with illegal lock handle {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1553
The dbms_lock release for lock handle {0} failed with invalid parameters.
Category:
Other
Cause:
null
Action:
null
ODI-1554
The dbms_lock release for lock handle {0} failed because you do not own the lock.
Category:
Other
Cause:
null
Action:
null
ODI-1555
The dbms_lock release for lock handle {0} failed with an unknown return code {1}.
Category:
Other
Cause:
null
Action:
null
ODI-1556
The lock acquisition failed. The lock is already locked by other connection object.
Category:
Other
Cause:
null
Action:
null
ODI-1557
Error refreshing variable "{0}": the associated SQL query returned a NULL value.
Category:
Other
Cause:
null
Action:
null
ODI-1558
The session {0} corresponding to the load plan step {1} of load plan instance {2}, run {3} is not found. We assume this step to be in error status.
Category:
Other
Cause:
null
Action:
null
ODI-1559
Load Plan Instance {0} cannot be restarted because the context {1} was not found in the work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1560
Load Plan {0} cannot be started because the context {1} was not found in the work repository {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1561
Load Plan {0} cannot be started because the user {1} does not have view privileges to the execution context {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1562
Load Plan Instance {0} cannot be restarted because the user {1} does not have view privileges to the execution context {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1563
Load Plan {0} cannot be started because the user {1} does not have execute privileges to the Load Plan {0}.
Category:
Other
Cause:
null
Action:
null
ODI-1564
Load Plan Instance {0} cannot be restarted because the user {1} does not have restart privileges.
Category:
Other
Cause:
null
Action:
null
ODI-1565
Load Plan {0} cannot be started because an unknown exception occurred.
Category:
Other
Cause:
null
Action:
null
ODI-1566
Load Plan Instance {0} cannot be restarted because an unknown exception occurred.
Category:
Other
Cause:
null
Action:
null
ODI-1567
Load Plan {0} cannot be started because a SQL Exception occurred.
Category:
Other
Cause:
null
Action:
null
ODI-1568
Load Plan Instance {0} cannot be restarted because a SQL Exception occurred.
Category:
Other
Cause:
null
Action:
null
ODI-1569
Error trying to stop load plan, instance {0} run {1} not found.
Category:
Other
Cause:
null
Action:
null
ODI-1570
Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop the Load Plan Instance.
Category:
Other
Cause:
null
Action:
null
ODI-1571
Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop Sessions.
Category:
Other
Cause:
null
Action:
null
ODI-1572
Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because a SQL Exception occurred while accessing the Repository.
Category:
Other
Cause:
null
Action:
null
ODI-1573
Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because an Unknown error has occurred.
Category:
Other
Cause:
null
Action:
null
ODI-1574
Day of week is not specified for the schedule.
Category:
Other
Cause:
null
Action:
null
ODI-1575
Invalid value specified for the excluded days of month filter: {0}
Category:
Other
Cause:
null
Action:
null
ODI-1576
LoadPlan Operation {0} on Agent {1} failed with the exception {2}.
Category:
Other
Cause:
null
Action:
null
ODI-1577
Parallel step error triggered on a parent step "{0}" while executing step "{1}".
Category:
Other
Cause:
null
Action:
null
ODI-1578
Invalid load plan log level value specified: {0}. A valid load plan log value is between {1} and {2}.
Category:
Other
Cause:
Invalid load plan log level value was supplied in the request.
Action:
Check that the load plan log level value supplied was valid (1 - 6) for the request.
ODI-1579
Agent {0} start failure: data source for master repository did not contain a master repository using JDBC URL={1} with USER={2}.
Category:
Other
Cause:
The master repository connection information pointed to a database schema that did not contain a master repository.
Action:
Verify the master repository connection information.
ODI-1580
Unable to set the role OWB_USER for this user.
Category:
Other
Cause:
An attempt was made to set the role OWB_USER for the connected user.
Action:
Check that the role exists and the connected user is an OWB user.
ODI-1581
Unable to set the workspace {0} for this user.
Category:
Other
Cause:
An attempt was made to select the OWB workspace for the connected user.
Action:
Check that the workspace exists and the connected user has got privilege to access it.
ODI-1582
Unexpected error when connecting to Owb workspace {0}.
Category:
Other
Cause:
An unexpected error occurred when connecting to workspace.
Action:
Verify that the Owb repository is up and running.
ODI-1583
Owb workspace {0} does not contain components that enable execution from Odi.
Category:
Other
Cause:
A component that is required by ODI has not been found in this workspace.
Action:
Verify that the Owb repository contains the correct patch for ODI.
ODI-1584
Mandatory parameter {0} is missing for https protocol.
Category:
Other
Cause:
A parameter that is required to start ODI agent to enable https protocol is missing.
Action:
Verify that the parameter is specified in odiparams.[sh|bat].
ODI-1585
A Step with Id {0} does not exist in the Session {1}
Category:
Other
Cause:
null
Action:
null
ODI-1586
A Task with Id {0} does not exist in the step {1} of the Session {2}
Category:
Other
Cause:
null
Action:
null
ODI-1587
An execution context cannot be determined for OGG operation {0}.
Category:
Other
Cause:
An execution context cannot be determined for OGG operation.
Action:
null
ODI-1588
The specified operation {0} provided is not supported by this tool.
Category:
Other
Cause:
The operation provided is not supported by this tool.
Action:
Verify the parameters
ODI-1589
The execution of the OdiOggCommand operation {0} failed.
Category:
Other
Cause:
The execution of the OdiOggCommand operation failed.
Action:
null
ODI-1590
The execution of the script failed. {0}
Category:
Other
Cause:
The execution of the script failed in the BSF Engine.
Action:
null
ODI-1591
The ODI agent name {0} specified in the client request does not match with the ODI agent {1} serving the request.
Category:
Other
Cause:
The client and the agent are not using the same physical agent name.
Action:
Verify the client and the agent are using the same agent name. Verify that the client is calling the correct agent.
ODI-1592
Error occurred testing connection to dataserver with agent {0}
Category:
Other
Cause:
Dataserver connection test failed on the agent
Action:
Verify that dataserver connection configuration is valid. Verify that dataserver is available
ODI-1593
The following bind parameters ({0}) in the task command {1} are not bound to any value. All the bind parameters should be bound for the command to be successful.
Category:
Other
Cause:
Either the source command is not providing values for some of the bind parameters in target command or the Odi Variables and/or Odi Sequence meta-data is not generated for the Scenario.
Action:
Verify that either the source command is correct or the Odi Variables and/or Odi Sequences meta-data is generated in the Scenario.
ODI-1594
The connection to the data server {0} failed.
Category:
Other
Cause:
The data server might be down or the data server connectivity settings are not correct.
Action:
Verify that you are able to test the data server using the Studio successfully.
ODI-1595
The command script failed with trace {0}.
Category:
Other
Cause:
There was a failure in the Ftp or Sftp command script.
Action:
Verify the trace and resolve the error in the command script passed to the tool.
ODI-1596
Failed to execute the pig script.
Category:
Other
Cause:
There was a failure in executing Pig script.
Action:
Verify the trace and resolve the error in the command script passed.
ODI-1597
The submitted pig script is empty.
Category:
Other
Cause:
The command did not contain or generate any pig script.
Action:
Verify the trace and resolve the error in the code generation.
ODI-1598
Failed to call method {0}.
Category:
Other
Cause:
Invocation Error.
Action:
Verify the trace and resolve the error in the runtime pig engine.
ODI-1599
The associated Dataserver with ID- {0} is missing for DataServer- {1} from topology.
Category:
Other
Cause:
Repository Error.
Action:
Verify the dataservers in topology and associate a Dataserver to current Dataserver.
ODI-1600
Unable to update Opmn Xml file.
Category:
Files
Cause:
Action:
ODI-1601
Unable to parse Opmn xml file
Category:
Files
Cause:
Action:
ODI-1602
Please provide all arguments
Category:
Other
Cause:
Action:
ODI-1603
Syntax: java DeleteAgentFromOpmn <Instance Home> <OracleOpmnHome> <Agent Name>
Category:
Other
Cause:
Action:
ODI-1604
Unable to parse Opmns Snippet Xml
Category:
Other
Cause:
Action:
ODI-1605
Component already exists in the file.
Category:
Files
Cause:
Action:
ODI-1606
Please provide the value for {0}
Category:
Other
Cause:
Action:
ODI-1607
Error reading file
Category:
Files
Cause:
Action:
ODI-1608
No of values provided for component name and port number are not equal. Please provide the same no of values for both.
Category:
Other
Cause:
Action:
ODI-1609
No of values provided for component name and JMXport number are not equal. Please provide the same no of values for both.
Category:
Other
Cause:
Action:
ODI-1610
ODI environment variable {0} is not set and ODI Tool startcmd not launched from interactive console.
Category:
Other
Cause:
Action:
ODI-1611
Must provide username for {0} before obtaining password.
Category:
Other
Cause:
Action:
ODI-1612
Unknown parameter ignored: {0}
Category:
Other
Cause:
Action:
ODI-1613
Unknown parameter value pair ignored: {0}={1}
Category:
Other
Cause:
Action:
ODI-1614
{0} is a mandatory parameter
Category:
Other
Cause:
Action:
ODI-1615
DESCRIPTION Resumes an execution session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> [<log_level>] ["-AGENT_URL=<agent_url>" | "-AGENT_NAME=<physical_agent_name>"]
Category:
Other
Cause:
Action:
ODI-1616
DESCRIPTION Starts an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agent.(cmd|sh) -NAME=<agent name> [-PORT=<port>] [-PROTOCOL=<protocol>] [-JMXPORT=<jmxport>] [-ODI_CONNECTION_RETRY_COUNT=<nn>] [-ODI_CONNECTION_RETRY_DELAY=<nn>] PORT represents the listening port. It should match the port value specified against the physical agent defined in Topology. PROTOCOL represents the listening protocol, HTTP or HTTPS. Its default value is HTTP. NAME represents the name of this physical agent. It should match the name of a physical agent defined in Topology. User must have created an agent with this name using configuration wizard. JMXPORT represents the JMX port used for JMX notifications etc. Its default value is calculated as PORT + 1000, or 20810 if the calculated value is greater than 65535 ODI_CONNECTION_RETRY_COUNT represents the number of times a connection to the ODI Repository will be retried. Its default value is 10 ODI_CONNECTION_RETRY_DELAY represents the number of milliseconds between connection retries to the ODI Repository. Its default value is 7000
Category:
Other
Cause:
Action:
ODI-1617
DESCRIPTION Stops an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agentstop.(cmd|sh) "-NAME=<agent name>" ["-AGENT_URL=<agent_url>"] ["-IMMEDIATE=<true(default)|false>" ["-MAX_WAIT=<stop timeout in millis>"]]
Category:
Other
Cause:
Action:
ODI-1618
DESCRIPTION Restarts execution of a load plan instance. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartloadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]
Category:
Other
Cause:
Action:
ODI-1619
DESCRIPTION Starts a Oracle Data Integrator command. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startcmd.(cmd|sh) "-INSTANCE=<instance_name>" <Command Name> ["<command parameter>"]*
Category:
Other
Cause:
Action:
ODI-1620
DESCRIPTION Starts a load plan. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startloadplan.sh "-INSTANCE=<instance_name>" <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*
Category:
Other
Cause:
Action:
ODI-1621
DESCRIPTION Starts a scenario. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startscen.(cmd|sh) "-INSTANCE=<instance_name>" <scenario_name> <scenario_version> <context_code> [<log_level>] ["-SESSION_NAME=<session_name>"] ["-KEYWORDS=<keywords>"] ["-AGENT_URL=<agent_url>"] ["-ASYNC=(no|yes)"] ["-DEBUGGABLE=(no|yes)"] ["-SUSPEND_FIRST_STEP=(no|yes)"] ["-DESCENDANTS_DEBUGGABLE=(no|yes)"] ["-BREAK_ON_ERROR=(no|yes)"] ["<variable>=<value>"]* -ASYNC=no is default; -ASYNC=yes is valid only if -AGENT_URL is specified.
Category:
Other
Cause:
Action:
ODI-1622
DESCRIPTION Stops a load plan instance execution. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stoploadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]
Category:
Other
Cause:
Action:
ODI-1623
DESCRIPTION Stops the execution of a running session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stopsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> ("-AGENT_URL=<agent_url>" | "-AGENT_NAME=<physical_agent_name>") ["-STOP_LEVEL=<normal(default)|immediate>"]
Category:
Other
Cause:
Action:
ODI-1624
DESCRIPTION Encode a password. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX encode.(cmd|sh) "-INSTANCE=<instance_name>" <password>
Category:
Other
Cause:
Action:
ODI-1625
This must be executed from a domain. System property domain.home cannot be null"
Category:
Other
Cause:
Action:
ODI-1626
"Neither parameter {0} nor {1} is specified"
Category:
Other
Cause:
Action:
ODI-1627
"Error getting instance properties"
Category:
Other
Cause:
Action:
ODI-1628
{0} (arg[{1}]) "{2}" should not be blank.
Category:
Other
Cause:
Action:
ODI-1629
{0} (arg[{1}]) "{2}" should specify a valid integer.
Category:
Other
Cause:
Action:
ODI-1630
{0} (arg[{1}]) "{2}" should specify a valid long number.
Category:
Other
Cause:
Action:
ODI-1631
-STOP_LEVEL parameter value must be one of: {0}, {1}
Category:
Other
Cause:
Action:
ODI-1632
Session "{0}" is being stopped ({1})
Category:
Other
Cause:
Action:
ODI-1633
OracleDI: Starting scenario {0} {1} in context {2} ...
Category:
Other
Cause:
Action:
ODI-1634
"Either parameter {0} or {1} should be specified, and they cannot be specified together."
Category:
Other
Cause:
Action:
ODI-1635
"Debug parameters are ignored when -AGENT_NAME parameter is specified."
Category:
Other
Cause:
Action:
ODI-1650
-AGENT_URL=<agent_url> is a mandatory parameter
Category:
Other
Cause:
Action:
ODI-1651
Agent {0} error while executing: {1}
Category:
Other
Cause:
Action:
ODI-1652
Unknown parameter ignored: {0}
Category:
Other
Cause:
Action:
ODI-1653
Unknown parameter value pair ignored: {0}={1}
Category:
Other
Cause:
Action:
ODI-1654
load_plan_instance_id is a mandatory parameter
Category:
Other
Cause:
Action:
ODI-1655
Usage: RestartLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]
Category:
Other
Cause:
Action:
ODI-1656
Load plan instance "{0}", run {1} has restarted
Category:
Other
Cause:
Action:
ODI-1657
load_plan_name and context_code are mandatory parameters
Category:
Other
Cause:
Action:
ODI-1658
Usage: StartLoadPlan -INSTANCE=<instance_name> <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*
Category:
Other
Cause:
Action:
ODI-1659
Load plan "{0}", instance "{1}", run {2} has started
Category:
Other
Cause:
Action:
ODI-1660
load_plan_instance_id is a mandatory parameter
Category:
Other
Cause:
Action:
ODI-1661
Usage: StopLoadPlan -INSTANCE=<instance_name> <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" [-STOP_LEVEL=<normal (default) | immediate>]
Category:
Other
Cause:
Action:
ODI-1662
Load plan instance "{0}", run {1} has stopped ({2})
Category:
Other
Cause:
Action:
ODI-1663
-STOP_LEVEL parameter value must be one of: {0}, {1}
Category:
Other
Cause:
Action:
ODI-1664
Waiting for completion of load plan execution.
Category:
Other
Cause:
Action:
ODI-1665
Load plan execution completed in {0} status.
Category:
Other
Cause:
Action:
ODI-1700
SessionId is not valid
Category:
Other
Cause:
Action:
ODI-1701
The session was not found in the repository: {0}
Category:
Other
Cause:
Action:
ODI-1702
This operation is not supported on this platform
Category:
Other
Cause:
Action:
ODI-1800
Exception {0} has occurred as ESS-EM linking is disabled.
Category:
Configuration
Cause:
Unable to connect to master repository.
Action:
Check if the master repository is accessible and up. This is not mandatory since master repositories can be down.
ODI-1801
Agent target discovery mbean registration has failed due to {0}.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error and take corrective action.
ODI-1802
Agent target discovery mbean unregistration has failed due to {0}.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error and take corrective action.
ODI-1803
Error {0} has occurred during mbean registration.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1804
Error {0} has occurred during mbean deregistration.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1805
Error {0} has occurred during notification listener registration.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1806
Error {0} has occurred during notification listener deregistration.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1807
Error {0} has occurred during deregistration of ODI Service Mbean {1}.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1808
Error {0} has occurred during registration of Agent Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the server and restart the OdiConsole application.
ODI-1809
Error {0} has occurred during registration of Master Repository Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the error and restart the OdiConsole application.
ODI-1810
Error {0} has occurred during registration of Work Repository Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the error and restart the OdiConsole application.
ODI-1811
Error {0} has occurred during registration of Session Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the error and restart the OdiConsole application.
ODI-1812
Error {0} has occurred during registration of Event Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the error and restart the OdiConsole application.
ODI-1813
Error {0} has occurred during registration of Session Search Service Mbean.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the error and restart the OdiConsole application.
ODI-1814
No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.
Category:
Configuration
Cause:
A configuration error has occurred.
Action:
Add the jndi entries for all the work repositories for each of the master repositories in repositories.xml.
ODI-1815
Exception {0} has occurred during Session Search by id.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
No action is required. The session id mentioned for search is not available.
ODI-1816
Session status passed {0} is invalid.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1817
Error {0} has occurred while fetching statistics for agents. Statistics shown might not be complete.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1818
Agent Service Mbean is not initialized. Re-initialization of agents in tree is disabled.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error, fix the same and restart the OdiConsole application.
ODI-1819
Event Service Mbean is not initialized. Re-initialization of event notification listeners is disabled.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check log for details on the error, fix the same and restart the OdiConsole application.
ODI-1820
Agent {0} is not up at {1} for reason {2}.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1821
JMXConnector failed to provide MBean server connection.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-1822
Error occured while closing JMXConnector.
Category:
Programmatic
Cause:
A runtime error has occurred.
Action:
Check the log for details on the error.
ODI-3000
error in creating repository connection {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3001
error in updating repository connection {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3002
error in deleting repository connection {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3003
Failed to connect to the error table {0}. Check the connection details and retry.
Category:
Programmatic
Cause:
The table might no longer exist or the structure of the table might not be correct.
Action:
Check the connection details and retry.
ODI-3016
Creation of Work Repository failed because a previous Work repository was found, and the user had asked not to overwrite any existing repository.
Category:
Data
Cause:
Work repository already exists and overwriting of the repository was not chosen
Action:
Select overwriting of Work Repository
ODI-3017
Exception occurred while creating Work Repository at {0} failed. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3018
Test connection failed due to {0}.
Category:
Data
Cause:
Connection to DB failed
Action:
Check the logs.
ODI-3019
Exception occurred while exporting Master Repository. Failure reason {0}.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3020
Only zip files can be uploaded , the {0} upload was unsuccessful.
Category:
Data
Cause:
A file with extension other than zip was uploaded.
Action:
Make sure file uploaded has zip as extension
ODI-3021
Exception occurred while importing Work Repository. Failure reason {0}.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3022
Attaching of Work Repository failed due to error: {2}
Category:
Programmatic
Cause:
Errored out due to {2} and overwriting of the repository was not chosen
Action:
Check the logs
ODI-3023
Attaching of Work Repository failed
Category:
Programmatic
Cause:
An unexpected error occured and overwriting of the repository was not chosen
Action:
Check the logs
ODI-3024
Exception occurred while attaching Work Repository at {0} failed. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3031
Creation of Master Repository failed at {0}.
Category:
Data
Cause:
Creation of Master Repository Failed
Action:
Check the logs.
ODI-3032
Exception occurred while creating Master Repository at {0} failed. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3033
Supervisor Password and Confirm Supervisor Password fields should match.
Category:
Data
Cause:
Supervisor Password and Confirm Supervisor Password fields must match
Action:
Input same passwords
ODI-3034
Test connection failed due to {0}.
Category:
Data
Cause:
Testing of DB connection failed
Action:
Check the logs
ODI-3035
Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.
Category:
Data
Cause:
Both the password match and zip files to be uploaded conditions failed
Action:
Make sure both the passwords are same and file uploaded is zip file
ODI-3036
Only zip files can be uploaded , the {0} upload was unsuccessful.
Category:
Data
Cause:
zip files to be uploaded condition failed
Action:
Make sure file uploaded is zip file
ODI-3037
Exception occurred while exporting Master Repository. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3038
Exception occurred while exporting Physical Topology. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3039
Exception occurred while Importing Master Repository. Failure reason {1}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3040
Unable to connect to the Repository User. {0}
Category:
Data
Cause:
Testing of DB connection failed
Action:
Check the logs
ODI-3041
Unable to connect to the DBA User. {0}
Category:
Data
Cause:
Testing of DB connection failed
Action:
Check the logs
ODI-3046
unable to find the agent for given logical agent and context code
Category:
Data
Cause:
Physical Agent mapping was not defined for selected logical agent and context.
Action:
A different set of credentials is required or the mapping needs to be defined.
ODI-3047
exception while executing {0}. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3048
Only XML files can be uploaded: the {0} upload fails
Category:
Data
Cause:
File selected for import was not a XML file.
Action:
Provide the XML file.
ODI-3049
exception while importing {0}. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3050
failed to start scenario : {0} ? {1} in debug mode.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3075
Error in purging Load Plans Executions/Sessions {0}
Category:
Programmatic
Cause:
An exception has occurred.
Action:
Check the logs.
ODI-3076
exception while killing {0}. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3077
Selected Session {0} is in {1} State, and therefore cannot be killed.
Category:
Data
Cause:
The selected session was in Done, Error, or Warning state.
Action:
No action is required.
ODI-3078
Selected Session {0} is in {1} State, and therefore cannot be restarted.
Category:
Data
Cause:
The selected session was not in Error state.
Action:
No action is required.
ODI-3079
exception while restarting {0}. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3080
exception while clearing stalesessions. Failure reason {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3081
Error fetching records from error table {0}. The table might no more exist or the format of the table is not correct
Category:
DATA
Cause:
The table might no longer exist or the structure of the table might not be correct
Action:
Upgrade the CKM
ODI-3082
CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.
Category:
Programmatic
Cause:
CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.
Action:
Future release will have the ODI_PK primary key column incorporated in CKM SQL.
ODI-3083
Scenario "{0}" parent not found.
Category:
Data
Cause:
Trying to get the Odi Object which does not exist or has been deleted.
Action:
Check the logs
ODI-3090
failed to restart session : {0} in debug mode.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3101
import of {1} from {0) failed
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3102
export of {1} to {0) failed
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3103
failed to stop a loadplan instance id : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3104
failed to start a loadplan : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3105
failed to start a scenario : {0} ? {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs1
ODI-3106
failed to restart session : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3107
failed to clean stale sessions for repository : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3108
failed to stop session : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3109
Creation of work runtime repository at {0} failed. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3110
Update of work runtime repository at {0} failed. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3111
failed to read config.properties
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3112
shared config dir path is not valid : {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3114
{0} not set
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3115
{0} is not correct
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3116
failed to read
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3117
datasource not located at {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3118
Could not get the service locator. JpsServiceLocator service is not configured.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3119
JPS Exception {0} was thrown. Credential Store might not be configured.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3120
Credential store could not be found.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3121
Not populating any values in credential store
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3122
Exception in purging Session/Load Plan Executions
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3123
Exception occured while inserting usedInContext in Physical Schema
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3124
Exception occured while deleting usedInContext in Physical Schema
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3125
Exception occured while inserting usedInContext in Edit Physical Schema
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3126
Exception in adding an entity
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3127
Odi object not found
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3128
Exception in update
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3129
Unable to find odi object {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3130
Loading of entity failed
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3131
Unauthorized to delete entity of type
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3132
error occurred while executing method
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3133
no repository definition found for alias {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3134
login failed for user {0}=
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3135
version mismatch
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3136
unable to connect to repository with alias {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3137
Error occurred in EMIntegrationServlet.doOperation() - {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3138
failed to init jview diagrammer
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3139
repositories.xml path not set
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3140
{0} file does not exist at {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3141
failed to create RepositoryDefinitionRegistry
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3142
error logging out a user after session expired
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3143
Creation of work dev repository at {0} failed. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3144
Creation of Master Repository failed at {0}. Failure reason {1}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3145
Check the logsPrivilegedActionException {0} was thrown. system-jazn-data.xml might not have the privileges specified.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3146
???
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3147
Delete operation failed
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3148
Maximum number of sessions should be in between 1 and 99999.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3149
Port Number should not be non negative.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3150
Invalid Context code. Context code cannot have lower case characters and white spaces. Though, it can contain '$' and '_' special characters.
Category:
Programmatic
Cause:
A validation error occured
Action:
Context code cannot have lower case characters and white spaces
ODI-3184
Maximum Cache Entries cannot be less than zero.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3185
Unused Blueprint Lifetime cannot be less than zero.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3186
Maximum Threads Number cannot be less than Max Threads Per Session.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3187
Max Threads Per Session cannot be less than zero.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3188
Maximum Threads Number should be greater than zero.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3189
Maximum Threads Number cannot be less than Maximum Session Number.
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3190
Exception fetching connector points. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3191
Exception fetching model. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3192
Exception fetching physical schema. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3193
Exception fetching Data Server. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3194
Exception fetching Catalog. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3195
Exception fetching Constraints. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3196
Exception fetching connector point properties. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3197
Exception during Hadoop Initialization. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3198
Exception during Oozie Initialization. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3199
Failed to initiate Log retriever. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3200
Invalid Deployment Archive. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3201
Exception viewing Deployment Archive. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3202
IO Exception in Deployment Archive. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3203
Exception. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3226
Parameter File could not be Loaded.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3260
Failed to apply settings for agent: {0}
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3261
Exception while applying settings for agent: {0}. Failure reason: {1}
Category:
Programmatic
Cause:
An unexpected error occurred
Action:
Check the logs
ODI-3265
Exception occurred while creating Datasource. Failure reason {0}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3266
Data Source already exists for {0}.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3267
No valid repository alias is found. Click on management link on top right corner to create one.
Category:
Data
Cause:
Either there were no repository connection aliases, or those that were created did not have a valid JNDI name
Action:
Create a new repository connection alias.
ODI-3276
Tab limit reached.Please close at least one tab.
Category:
Data
Cause:
Max limit on the number of tabs that can be open has been met.
Action:
Close at least one tab
ODI-3277
Object cannot be found.
Category:
Data
Cause:
The object might have been deleted.
Action:
Refresh your view.
ODI-3278
View operation fails with the following exception {0}. See the server log for details.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3279
Add operation failed with the following exception {0}. Please see the server log for details.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3280
Edit operation failed with the following exception {0}. Please see the server log for details.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3281
Delete operation failed with the following exception {0}. Please see the server log for details.
Category:
Data
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3290
You are not authorized to add a new entity of this type.
Category:
Data
Cause:
User doesn't have required privileges to add an new entity of a particular type
Action:
No action
ODI-3326
Please specify a valid search text
Category:
Data
Cause:
Invalid search text was specified
Action:
Provide a valid search text
ODI-3327
Please choose at least one model or project type.
Category:
Data
Cause:
No model or project type was selected
Action:
Select at least one model or project type so that search criteria is valid
ODI-3328
Please choose at least one topology type.
Category:
Data
Cause:
No topology type was selected
Action:
Select at least one topology type so that search criteria is valid
ODI-3329
Please choose at least one runtime type.
Category:
Data
Cause:
No runtime type was selected
Action:
Select at least one runtime type so that search criteria is valid
ODI-3330
Exception while importing attrbutes. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3331
Exception while importing properties. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3332
Exception while fetching attributes. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3333
Exception while fetching properties. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3334
Exception while importing propeties and expressions of attributes. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3335
Exception while loading components. Reason: {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3336
Error in persisting user preferences {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3337
UserPref.xml path is not set
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3338
Failed to get User Preferences
Category:
Programmatic
Cause:
An unexpected error occured
Action:
Check the logs
ODI-3339
Error in getting policies. Reason: {0}
Category:
Programmatic
Cause:
Error occurred.
Action:
Check the logs.
ODI-3501
Exception while applying deployment archive. Failure reason {0}
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check the logs.
ODI-3502
Invalid Credential File Password.
Category:
Data
Cause:
The password entered is not correct.
Action:
Re-enter correct credential file password.
ODI-3503
Credential File Not Accessible.
Category:
Data
Cause:
Credential File Permission
Action:
Check permission of Credential file and retry.
ODI-3504
Oracle DB Connection details not found in credential file
Category:
Data
Cause:
Oracle Database connection details not stored in credential file.
Action:
Save oracle database connection details in credential file before using.
ODI-3505
Please select credential file.
Category:
Data
Cause:
Credential file not chosen
Action:
Choose credential file.
ODI-3506
Uploading of File {0} was not successful.
Category:
Data
Cause:
File could not be uploaded.
Action:
Check network connectivity and retry.
ODI-3507
Please enter credential file password.
Category:
Data
Cause:
Credential file password not entered
Action:
Enter credential file password.
ODI-3508
Invalid Credential file.
Category:
Data
Cause:
The file chosen is not a credential file.
Action:
Choose valid credential file.
ODI-5000
Task {0} ({1}) on logical schema {2} with Context Id {3} fails since scripting technology name could not be discovered.
Category:
Other
Cause:
null
Action:
null
ODI-5001
Session {0} ({1}) could not be stopped by Agent {2}: Session run on an 'Internal' agent cannot be stopped from another process.
Category:
Other
Cause:
Stopping a session being run by an internal agent from another process is not possible.
Action:
Review the session execution details in the Operator Navigator or Repository Explorer.
ODI-5002
Pig Script Execution failure: The following {0} Job(s) - [{1}] reported failed. Please check the resource manager logs for these jobs for the failure reason.
Category:
Other
Cause:
There was a failure in executing Pig script in MapReduce Mode. Some Jobs have been reported failed.
Action:
Verify the Resource Manager trace and resolve the error in the command script passed.
ODI-5003
No associated Hadoop dataserver found for given logical schema {0}.
Category:
Other
Cause:
Repository Error.
Action:
Verify given logical schema is Hadoop dataserver or associated with Hadoop dataserver .
ODI-5004
None of the logical schemas {0} and {1} associated with Hadoop dataserver.
Category:
Other
Cause:
Repository Error.
Action:
Verify given logical schema is Hadoop dataserver or associated with Hadoop dataserver .
ODI-5005
Illegal state. Classloader not found for key: {0} for ODI task with name {1}.
Category:
Other
Cause:
ODI Script Engine Error.
Action:
As a workaround try removing classpaths from the Dataserver assocaited with the task and configure them on the agent instead.
ODI-5006
Unrecoverable OdiAgentException occurred during Load Plan execution. Unable to stop and close Load Plan execution due to exception:
Category:
Other
Cause:
null
Action:
null
ODI-5007
Authentication failed. Cannot advance loadplans without authentication. So pending advancing loadplans will be stopped and closed:
Category:
Other
Cause:
null
Action:
null
ODI-5008
Error occurred previewing file on agent {0}, as file {1} is empty
Category:
Other
Cause:
Error previewing file on the agent, as file is empty
Action:
Verify that file is not empty
ODI-5100
Agent {0} cannot read configuration. Cause: {1}.
Category:
Other
Cause:
The agent configuration cannot be read.
Action:
Review the cause and take appropriate action.
ODI-10000
Method setObject class DwgObjectRepresentor does not support object class: {0}.
Category:
Other
Cause:
Java method was not found.
Action:
Contact Oracle Support Services.
ODI-10001
Action unauthorized for this license: {0}
Category:
Security
Cause:
Action was unauthorized for this license.
Action:
Choose another license.
ODI-10002
Only one local repository can be defined; {0} were found.
Category:
Other
Cause:
More than one local repository was found.
Action:
Contact Oracle Support Services.
ODI-10003
No connection set.
Category:
Other
Cause:
No connection was set.
Action:
Set connection.
ODI-10004
File already exists.
Category:
File
Cause:
File already existed.
Action:
Choose another file.
ODI-10005
Repository is expected to be a master repository.
Category:
Other
Cause:
Repository was expected to be a master repository.
Action:
Choose master repository.
ODI-10006
Repository is expected to be enterprise repository.
Category:
Other
Cause:
Repository was expected to be an enterprise repository.
Action:
Choose enterprise repository.
ODI-10007
Object must be in editable state before using set methods.
Category:
Other
Cause:
The object was not in editable state.
Action:
Edit this object.
ODI-10008
Object must be in consult mode before using methods get.
Category:
Other
Cause:
The object was not in consult mode.
Action:
Consult the object.
ODI-10009
Object does not exist in the repository.
Category:
Other
Cause:
The repository did not contains this object.
Action:
Choose another object or create first this one.
ODI-10010
This type of object cannot be updated.
Category:
Other
Cause:
Object could not be updated.
Action:
Do not update this object.
ODI-10011
Invalid object; it has been updated by another user.
Category:
Other
Cause:
Object was updated by another user.
Action:
Refresh the object.
ODI-10012
Object cannot be inserted
Category:
Other
Cause:
Object could not be inserted.
Action:
Check object.
ODI-10013
This import action has been cancelled because it could damage your repository. This is due to an {0} object that has object identifier {1} that is greater than that for the current {0} id sequence. Importing this object would lead to primary key violations in the future.
Category:
Other
Cause:
Import could damage your repository.
Action:
Check identifier sequences.
ODI-10014
Method must be redefined in derived classes. It cannot be called for DwgObject
Category:
Other
Cause:
Method must be redefined in derived classes.
Action:
Call redefined method.
ODI-10015
The work repository {0} is not declared in this master repository, the import process has been cancelled.
Category:
Other
Cause:
Work repository was not declared in this master repository.
Action:
Declare work repository and try again.
ODI-10016
Import aborted.
Category:
Other
Cause:
Import was aborted.
Action:
Check objects and try again.
ODI-10017
This import is forbidden: the text {0} has a different origin in the repository and in the import file.
Category:
Other
Cause:
The text has a different origin in the repository and in the import file.
Action:
Check import file and try again.
ODI-10018
The repository {0} is not coherent between the current repository and the import file.
Category:
Other
Cause:
The repository was not coherent between the current repository and the import file.
Action:
Check import file.
ODI-10019
Impossible to create the directory {0}.
Category:
File
Cause:
I was not possible to create the directory.
Action:
Check your system rights for creating directory; directory's path and name.
ODI-10020
Impossible to replace the file
Category:
File
Cause:
It was not possible to replace the file.
Action:
Check, if you have enough rights for this operation.
ODI-10021
Unspecified save directory.
Category:
Other
Cause:
Directory to save environment information was unspecified.
Action:
Specify the directory for saving the environment information file.
ODI-10022
You must specify all options.
Category:
Other
Cause:
Missed one or more options.
Action:
Specify missed options.
ODI-10023
Invalid license. This license is suitable for {0}.
Category:
Security
Cause:
Invalid license.
Action:
Check license.
ODI-10024
Your installation of Oracle Data Integrator is corrupted.
Category:
Other
Cause:
The technology description file contains errors.
Action:
Reinstall Oracle Data Integrator.
ODI-10025
Your installation of Oracle Data Integrator is corrupted.
Category:
Other
Cause:
The technology description file is missing.
Action:
Reinstall Oracle Data Integrator.
ODI-10026
Error while testing the Master Repository technology.
Category:
Other
Cause:
Error occurred while testing the Master Repository technology.
Action:
Check parameters.
ODI-10027
The import is canceled because at least one object is locked by another user.
Category:
Other
Cause:
At least one object was locked by another user.
Action:
Check objects' locks.
ODI-10028
It is forbidden to import a log into a repository having the same ID.
Category:
Other
Cause:
The log had the same ID as repository.
Action:
Check log and/or repository id.
ODI-10029
Version {0} for object {1} already exists.
Category:
Other
Cause:
Version already existed.
Action:
Choose another version.
ODI-10030
DwgBeanWrapper can only wrap DwgObjects
Category:
Other
Cause:
DwgBeanWrapper can only wrap DwgObjects
Action:
Choose correct type of objects.
ODI-10031
Object {0}: {1} is locked by user {2}
Category:
Other
Cause:
Object was locked by another user.
Action:
Wait until object is unlocked.
ODI-10032
You cannot import this object ({0}). A referenced object ({1}) does not exist in the repository.
Category:
Other
Cause:
A referenced object does not exist in the repository.
Action:
Check import file.
ODI-10033
You cannot delete this object because it is locked by another user ({0}).
Category:
Other
Cause:
This object was locked by another user.
Action:
Wait until object is unlocked.
ODI-10034
The technology hosting your master repository does not support Versioning.
Category:
Other
Cause:
The technology did not support versioning.
Action:
Choose another repository or technology.
ODI-10035
{0} : ''{1}'' (with global id: {5} and internal id: {6}) violates alternate key constraint {2} {3} for values {4}
Category:
Other
Cause:
Object violated alternate key constraint.
Action:
Check object properties and constraint's values.
ODI-10036
Importing object {0} : {1} (with global id: {2} and internal id: {3}) failed.
Category:
Other
Cause:
Import failed.
Action:
Check import file and try again.
ODI-10037
Import-replace for this node is supported for action groups only. The import file is invalid.
Category:
Other
Cause:
Import-replace for this node was supported for action groups only.
Action:
Check import file.
ODI-10038
The interface you are trying to use ({0}) is related to a logical schema ({1}) that no longer exists.
Category:
Other
Cause:
Logical schema was not found.
Action:
Check interface.
ODI-10039
Bad ID for an object representer
Category:
Other
Cause:
Bad ID for an object representer
Action:
Check object`s ID.
ODI-10040
Cannot create directory
Category:
File
Cause:
Directory could not be created.
Action:
Check directory path/name.
ODI-10041
Oracle Data Integrator Remote Object (SnpRemoteObject) must inherit from SnpsFunction.
Category:
Other
Cause:
Oracle Data Integrator Remote Object (SnpRemoteObject) did not inherit from SnpsFunction.
Action:
Use SnpsFunction as parent.
ODI-10042
SnpsQuery must be connected prior to execution
Category:
Other
Cause:
SnpsQuery was not connected.
Action:
Set a connection.
ODI-10043
Security token is a mandatory parameter
Category:
Security
Cause:
Security token was not specified.
Action:
Check security parameters.
ODI-10044
Unable to save the interface. Maximum number of source datastores exceeded.
Category:
Other
Cause:
Maximum number of source datastores was exceeded.
Action:
Contact Oracle Support Services.
ODI-10045
a2.getCargo() not instance of SAPSegment
Category:
Other
Cause:
a2.getCargo() not instance of SAPSegment
Action:
Check SAP Tree.
ODI-10046
No IDoc.
Category:
Other
Cause:
Missed IDoc.
Action:
Check IDoc.
ODI-10047
Repository is not a development work repository
Category:
Other
Cause:
Repository was not a development work repository.
Action:
Choose development work repository.
ODI-10048
No work repository found.
Category:
Other
Cause:
No work repository was found.
Action:
Check your connection settings or database.
ODI-10049
Missing parameter
Category:
Other
Cause:
Parameter was missing.
Action:
Check all parameters.
ODI-10050
Missing parameter at: {0} SQL: {1}
Category:
Other
Cause:
Parameter was missing.
Action:
Check all parameters.
ODI-10051
Some objects cannot be exported because they do not exist in the repository: {0} {1}
Category:
Other
Cause:
Objects did not exist in the repository.
Action:
Check objects state.
ODI-10052
A problem occurred in your repository.
Category:
Other
Cause:
A problem occurred in your repository.
Action:
Contact Oracle Support Services.
ODI-10053
Problem retrieving JCOFunction object. {0}
Category:
Other
Cause:
Problem occurred retrieving JCOFunction object.
Action:
Check JCO Function object.
ODI-10054
Unable to find the XML file corresponding to your technology.
Category:
Other
Cause:
XML file corresponding to your technology was not found.
Action:
Check technology and/or XML file for the technology.
ODI-10055
This ID is already in use in the repository
Category:
Other
Cause:
This ID was already in use in the repository.
Action:
Change ID.
ODI-10056
This repository ID already exists. This repository cannot be created.
Category:
Other
Cause:
Repository ID already existed.
Action:
Change repository ID.
ODI-10057
Unrecognized export type.
Category:
Other
Cause:
Export type was unrecognized.
Action:
Check export type.
ODI-10058
You are trying to import objects from a master repository of an older version into {0} version. This action is forbidden. Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.
Category:
Other
Cause:
You tried to import objects from a master repository of an older version.
Action:
Master repositories must be upgraded using the upgrade assistant, not using the export/import facility.
ODI-10059
Repository is null
Category:
Other
Cause:
Repository was null.
Action:
Check repository.
ODI-10060
Saputil is mandatory.
Category:
Other
Cause:
Saputil was mandatory.
Action:
Check Saputil
ODI-10061
Empty XML Character Set
Category:
Other
Cause:
XML Character Set was empty.
Action:
Fill XML Character Set.
ODI-10062
Unable to find license key {0}. An exception {1} occurred with message: {2}
Category:
Other
Cause:
An exception occurred.
Action:
Check license key.
ODI-10063
Unable to check the license key. An exception {0} occurred with message: {1}
Category:
Other
Cause:
An exception occurred.
Action:
Check license key.
ODI-10064
The interface must have a JMS datastore as a source or target. Another license is required otherwise.
Category:
Other
Cause:
The interface must have a JMS datastore as a source or target.
Action:
Check datastore type and/or license.
ODI-10065
You license does not include these features. Please contact your reseller.
Category:
Other
Cause:
You license does not include these features.
Action:
Please contact your reseller.
ODI-10066
The interface is using a Datastore defined in Model "{0}" which is linked to a logical schema "{1}" that no longer exists.
Category:
Other
Cause:
Logical schema was not found.
Action:
Correct interface.
ODI-10067
Target file already exists.
Category:
File
Cause:
Target file already existed.
Action:
Choose another target file name.
ODI-10068
SnpsConnection: Current Isolation level: {0}. The new Isolation level: {1}, not supported
Category:
Other
Cause:
Isolation level not supported.
Action:
Check isolation level.
ODI-10069
Unsupported XML Character Set: {0}
Category:
Other
Cause:
Unsupported XML Character Set.
Action:
Check XML charset.
ODI-10070
Cannot delete this object. It is being edited or viewed
Category:
Other
Cause:
Object was being edited or viewed.
Action:
Stop edit or view object and try again.
ODI-10071
Cannot delete this object
Category:
Other
Cause:
Could not delete this object.
Action:
Check object state.
ODI-10073
A repository already exists on this data server
Category:
Other
Cause:
A repository already existed on this data server.
Action:
Choose another data server.
ODI-10074
An object with the wrong type was given to an object representative
Category:
Other
Cause:
An object with the wrong type was given to an object representative
Action:
Check object type.
ODI-10075
An object is in an unidentified state {0}
Category:
Other
Cause:
An object is in an unidentified state.
Action:
Check object state.
ODI-10076
A collection object is the wrong class
Category:
Other
Cause:
A collection object is the wrong class.
Action:
Check collection object's class
ODI-10077
Undefined action performed on an object: {0}
Category:
Other
Cause:
An undefined action was performed on an object.
Action:
Check action and object.
ODI-10078
An object will be in an unidentified state (it is in the state "{0}" and "{1}" is currently being performed on it)
Category:
Other
Cause:
An object would have been in an unidentified state.
Action:
Check object state.
ODI-10080
Incorrect License ....
Category:
Other
Cause:
Incorrect License.
Action:
Contact your seller.
ODI-10081
You are not authorized to Insert the Object: {0}: {1} / {2}
Category:
Security
Cause:
You were not authorized to Insert the Object.
Action:
Login with user with right privileges.
ODI-10082
You are not authorized to View the Object: {0}: {1}
Category:
Security
Cause:
You were not authorized to View the Object.
Action:
Login with user with right privileges.
ODI-10083
You are not authorized to Delete the Object: {0}: {1} / {2}
Category:
Security
Cause:
You were not authorized to Delete the Object.
Action:
Login with user with right privileges.
ODI-10084
You are not authorized to Edit the Object: {0}: {1} / {2}
Category:
Security
Cause:
You were not authorized to Edit the Object.
Action:
Login with user with right privileges.
ODI-10085
You cannot consult this object
Category:
Security
Cause:
You could not consult this object.
Action:
Login with user with right privileges.
ODI-10086
You cannot edit this object
Category:
Security
Cause:
You could not edit this object.
Action:
Login with user with right privileges.
ODI-10087
You can only give Supervisor Access Privileges if you are a Supervisor.
Category:
Security
Cause:
You could only give Supervisor Access Privileges if you are a Supervisor.
Action:
Login with user with right privileges.
ODI-10088
Empty Java Character Set.
Category:
Other
Cause:
Java Character Set was empty.
Action:
Fill Java charset.
ODI-10089
You cannot modify another user''s password
Category:
Security
Cause:
You cannot modify another user''s password
Action:
Login with user with right privileges.
ODI-10090
Object {0} {1} is referenced by: {2}. Cannot remove.
Category:
Other
Cause:
Object was referenced by another one.
Action:
Check object''s references.
ODI-10091
not connected
Category:
Other
Cause:
not connected
Action:
Check connection.
ODI-10092
Some objects cannot be exported. They do not exist in the repository.
Category:
Other
Cause:
Objects did not exist in the repository.
Action:
Check objects'' state.
ODI-10093
You are importing an object from another repository with the same identifier. It is forbidden.
Category:
Other
Cause:
You tried to import an object from another repository with the same identifier.
Action:
Change repository ID.
ODI-10094
Problem while computing new name.
Category:
Other
Cause:
A problem occurred while computing new name.
Action:
Try again.
ODI-10095
Exception while getting the children list
Category:
Other
Cause:
Exception while getting the children list.
Action:
Try again.
ODI-10096
Error while parsing fields
Category:
Other
Cause:
Error occurred while parsing fields.
Action:
Check fields value.
ODI-10097
Impossible to find text with ID {0} in text list.
Category:
Other
Cause:
Text was not found.
Action:
Check text ID
ODI-10098
No connection available. Check connection parameters.
Category:
Network
Cause:
No connection was available.
Action:
Check connection parameters.
ODI-10099
Object cannot be exported because the file with name {0} could not be created.
Category:
Other
Cause:
Object could not be exported because the file could not be created.
Action:
Check your system rights to write files and file name.
ODI-10100
Empty XML Version
Category:
Other
Cause:
XML version was empty.
Action:
Fill XML Version.
ODI-10101
Invalid XML Version: {0}
Category:
Other
Cause:
XML Version was invalid.
Action:
Check XML version.
ODI-10102
Alias with the name {0} already exists.
Category:
Other
Cause:
Alias already exists.
Action:
Change alias.
ODI-10103
Alias with the name {0} does not exist.
Category:
Other
Cause:
Alias does not exit.
Action:
Check alias name ant try again.
ODI-10104
File {0} is not a Smart Export file and cannot be imported by Smart Import.
Category:
Other
Cause:
Smart Export file not specified for Smart Import.
Action:
Specify a Smart Export file for importing via Smart Import.
ODI-10105
Smart Import file name cannot be null.
Category:
Other
Cause:
Smart Export file name not specified for Smart Import.
Action:
Specify a Smart Export file for importing via Smart Import.
ODI-10106
Smart Import response file name cannot be null.
Category:
Other
Cause:
Smart import response file name not specified for Smart Import.
Action:
Specify a Smart Import response file.
ODI-10107
Smart Import file {0} not found.
Category:
Other
Cause:
File does not exist.
Action:
Specify an existing Smart Export file for importing via Smart Import.
ODI-10108
Smart Import response file {0} not found.
Category:
Other
Cause:
Response file does not exist.
Action:
Specify an existing Smart Import response file.
ODI-10109
File {0} is not a valid Smart Import Response file.
Category:
Other
Cause:
File is not a valid Smart Import response.
Action:
Specify an existing Smart Import response file.
ODI-10110
{0} with the same {1} exists.
Category:
Other
Cause:
An object with the same alternative key value(s) exists.
Action:
Change the alternative key value to be unique.
ODI-10111
{0} <{1}> referenced by {2} <{3}> is missing.
Category:
Other
Cause:
A referenced object does not exist.
Action:
Either import the missing object or change to reference a different object.
ODI-10112
Project code will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing project code.
Action:
Determine whether the change to project code is desired or not.
ODI-10113
{0} with {1} <{2}> does not exist.
Category:
Other
Cause:
A referenced object does not exist.
Action:
Either import the missing object or change to reference a different object.
ODI-10114
{0} with {1} id <{2}> does not exist.
Category:
Other
Cause:
A referenced object does not exist.
Action:
Either import the missing object or change to reference a different object.
ODI-10115
{0} with the same name <{1}> already exists.
Category:
Other
Cause:
A different object with the same name already exists.
Action:
Either change the name of the object being imported or use match by name to match to the already existing object with the same name.
ODI-10116
Model code will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing model code.
Action:
Determine whether the change to model code is desired or not.
ODI-10117
Sub-model code will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing sub-model code.
Action:
Determine whether the change to sub-model code is desired or not.
ODI-10118
A different Physical Schema is already set as the default physical schema for the same data server.
Category:
Other
Cause:
Action:
ODI-10119
A different Context is already set as the default Context.
Category:
Other
Cause:
Action:
ODI-10120
Context code will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing context code.
Action:
Determine whether the change to context code is desired or not.
ODI-10121
Logical schema name will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing logical schema name.
Action:
Determine whether the change to logical schema name is desired or not.
ODI-10122
Logical agent name will be changed from <{0}> to <{1}>.
Category:
Other
Cause:
The import will make a change to an existing logical agent name.
Action:
Determine whether the change to logical agent name is desired or not.
ODI-10123
{0} with {1} <{2}> and {3} <{4}> does not exist.
Category:
Other
Cause:
A referenced object does not exist.
Action:
Either import the missing object or change to reference a different object.
ODI-10124
Smart import of file {0} cannot be run due to unfixed critical issues.
Category:
Other
Cause:
Critical issues exist for objects in the Smart Import.
Action:
A fix must be provided for all critical issues before the Smart Import can be run.
ODI-10125
Smart Export file name cannot be null.
Category:
Other
Cause:
Smart Export file name not specified for Smart Export.
Action:
Specify a Smart Export file via Smart Export.
ODI-10126
File {0} already exists.
Category:
Other
Cause:
The file already exists.
Action:
Specify another file name.
ODI-10127
Column position {0} is being used by another object <{1}>.
Category:
Other
Cause:
The position value is already in use.
Action:
Specify a unique position value.
ODI-10128
Multiple primary keys found. Only one primary key can be defined per datastore.
Category:
Other
Cause:
Multiple primary keys defined.
Action:
Delete or match primary keys so that only one is defined.
ODI-10129
Object with id {0} and type {1} is not a smart exportable object.
Category:
Other
Cause:
Smart Export does not support the type of object specified.
Action:
Do not export this object.
ODI-10130
Smart Import Response file {0} is not valid for Smart Export file {1}.
Category:
Other
Cause:
Smart Import Response file was not generated for the Smart Export file being imported.
Action:
Specify a Smart Import response file that belongs to the Smart Export file being imported.
ODI-10131
Entity of type {0} cannot be merged.
Category:
Programmatic
Cause:
Wrong entity type.
Action:
Check entity type.
ODI-10132
Entity of type {0} cannot be removed.
Category:
Programmatic
Cause:
Wrong entity type.
Action:
Check entity type.
ODI-10133
Cannot create a transaction against the extended persistent context [{0}].
Category:
Programmatic
Cause:
Another persistence context is already bound to the current thread.
Action:
Unbound persistence context from current thread.
ODI-10134
You do not have READ permission on at least one object from the collection/list.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check your permissions
ODI-10135
Max value ({1}) reached for sequence {0} and reset is not allowed.
Category:
Other
Cause:
Reset is not allowed.
Action:
Check configuration of sequence behaviour.
ODI-10136
Illegal transaction state: transaction synchronization is active but entity manager is not synchronized within the transaction.
Category:
Programmatic
Cause:
Entity manager is not synchronized within the transaction.
Action:
Synchronize entity manager and try again.
ODI-10137
Your program needs to set authentication first.
Category:
Security
Cause:
There is no authentication set.
Action:
Set authentication via odiInstance.getSecurityManager().setGlobalAuthentication(.) or odiInstance.getSecurityManager().setCurrentThreadAuthentication(.), see the SecurityManager API for more detail.
ODI-10138
Unable to create DwgConnectConnection to {0} repository.
Category:
Other
Cause:
Exception during connection.
Action:
Check repository configuration.
ODI-10139
{0} must not be null or empty.
Category:
Configuration
Cause:
Parameter is null or empty.
Action:
Check parameter name.
ODI-10140
{0} must be greater or equal 0.
Category:
Configuration
Cause:
Parameter is negative.
Action:
Check parameter value.
ODI-10141
Unable to create datasource provider from class [{0}].
Category:
Configuration
Cause:
Exception during creation.
Action:
Check configuration.
ODI-10142
Active transaction is required to use the method {0} on the TransactionalOdiEntityManager.
Category:
Programmatic
Cause:
Transaction is not active.
Action:
Check transaction state.
ODI-10143
Error while accessing the {0} repository.
Category:
Network
Cause:
Network problems.
Action:
Check the network connection and the database status.
ODI-10144
OdiInstance is closed.
Category:
Other
Cause:
OdiInstance is closed.
Action:
Check OdiInstance status.
ODI-10145
Limited persistence support.
Category:
Other
Cause:
Limited persistence support.
Action:
Check OdiInstance configuration.
ODI-10146
Cannot create JDBC DataSource for this type of DataServer.
Category:
Programmatic
Cause:
Invalid connection provider.
Action:
Check connection provider.
ODI-10147
Repository type mismatches.
Category:
Configuration
Cause:
Wrong repository type.
Action:
Check repository type.
ODI-10148
Repository is in error install/upgrade state and needs to be repaired. Connection has been disabled.
Category:
Configuration
Cause:
Repository install/upgrade did not complete successfully.
Action:
Check install/upgrade log files and/or ODI user documentation for information on reparation process.
ODI-10149
Local Repository table is empty.
Category:
Configuration
Cause:
Local Repository table is empty.
Action:
Check repository configuration.
ODI-10150
Work repository with ID {0} is not bound to master: Definition in master ID:{0}, Name:{1}, Timestamp:{2} Definition in work ID:{3}, Name:{4}, Timestamp:{5}.
Category:
Configuration
Cause:
Work repository with ID is not bound to master repository.
Action:
Check work and master repositories configuration.
ODI-10151
Unable to get ID for entity {0}.
Category:
Security
Cause:
Wrong entity ID.
Action:
Check entity properties.
ODI-10152
I_OBJECTS for entity class {0} is not found.
Category:
Programmatic
Cause:
Entity type is not mapped to I_OBJECTS.
Action:
Check entity class.
ODI-10153
{0} is denied.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10154
{0} is denied for {1}.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10155
You do not have {0} permission on at least one object from the collection/list.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10156
Impossible to connect to JPS MBean Server.
Category:
Configuration
Cause:
Exception during connection.
Action:
Check configuration.
ODI-10157
{0}: must call preWebLogic() before postWebLogic().
Category:
Programmatic
Cause:
Wrong API usage.
Action:
Call preWebLogic() before postWebLogic().
ODI-10158
The credential with map name {0} and key {1} already exists.
Category:
Programmatic
Cause:
Wrong credential.
Action:
Check credential configuration.
ODI-10159
The user {0} has not required CONNECT profile.
Category:
Security
Cause:
The user has not required profile.
Action:
Grant the user CONNECT profile first.
ODI-10160
Unable to load user.
Category:
Other
Cause:
Exception during user loading.
Action:
Check repository connection.
ODI-10161
Trying to create authentication with Subject parameter which should be applicable when OPSS authentication is used, but ODI shows it is using ODI internal authentication.
Category:
Programmatic
Cause:
ODI internal authentication is used instead of OPSS authentication.
Action:
Check authentication type.
ODI-10162
This OPSS user ''{0}'' is not registered to Oracle Data Integrator.
Category:
Configuration
Cause:
The user is not registered to ODI.
Action:
Check user name.
ODI-10163
This OPSS user ''{0}'' has different GUID than the one found in Oracle Data Integrator repository.
Category:
Security
Cause:
OPSS user differs from ODI user in GUID.
Action:
Check user GUID.
ODI-10164
Only supervisor user can invoke this API.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check user role.
ODI-10165
The RunAsUser {0} is not a valid user from external user identity store.
Category:
Security
Cause:
User is not valid.
Action:
Check user.
ODI-10166
The RunAsUser: {0} has different GUID in ODI repository and external user identity store.
Category:
Security
Cause:
User from external user identity store differs from ODI user in GUID.
Action:
Check user.
ODI-10167
Authentication is missing.
Category:
Security
Cause:
Authentication is missing.
Action:
Check authentication configuration.
ODI-10168
There is already an Authentication bound to this thread.
Category:
Programmatic
Cause:
There is already an Authentication bound to this thread.
Action:
Check authentication configuration.
ODI-10169
Trying to set authentication object which is not created by this security manager.
Category:
Programmatic
Cause:
Authentication object is not created by this security manager.
Action:
Check authentication configuration.
ODI-10170
There is currently no Authentication bound to this thread.
Category:
Security
Cause:
There is currently no Authentication bound to this thread.
Action:
Check authentication configuration.
ODI-10171
There is already an Authentication bound as global Authentication.
Category:
Programmatic
Cause:
There is already an Authentication bound as global Authentication.
Action:
Check authentication configuration.
ODI-10172
There is currently no global Authentication bound to this SecurityManager.
Category:
Security
Cause:
There is currently no global Authentication bound to this SecurityManager.
Action:
Check authentication configuration.
ODI-10173
You are not authorized to change the password for external user ''{0}''.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10174
You are not authorized to change the password for user ''{0}''.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10175
You are not authorized to change the password for external user.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
Check permissions.
ODI-10176
Authentication is needed to change password.
Category:
Security
Cause:
Authentication is missed.
Action:
Authenticate first.
ODI-10177
ODI was not able to load the jdbc driver class "{0}" provided on {1}.
Category:
Other
Cause:
Wrong jdbc driver class.
Action:
Check that the driver class name is correct and that this driver is available to ODI classloader.
ODI-10178
The jdbc URL "{1}" was not accepted by the jdbc driver class "{0}" provided on {2}.
Category:
Other
Cause:
Insufficient jdbc URL.
Action:
Check that the jdbc URL and the driver class name are matching.
ODI-10179
Client requires a repository with version {0} but the repository version found is {1}.
Category:
Other
Cause:
Insufficient repository version.
Action:
Check repository configuration.
ODI-10180
ODI was not able to load the jdbc driver class {0} specified in ODI topology for work repository {1}.
Category:
Other
Cause:
Wrong jdbc driver class.
Action:
Check that the driver class name is correct and that this driver is available to ODI classloader. If the driver class name is incorrect please connect to ODI topology to fix it.
ODI-10181
Uncategorized configuration exception.
Category:
Configuration
Cause:
An unexpected error occurred.
Action:
Check exception cause for details.
ODI-10182
Uncategorized exception during repository access.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Check exception cause for details.
ODI-10183
{0} is an invalid finder class.
Category:
Programmatic
Cause:
Wrong finder class.
Action:
Check finder class.
ODI-10184
Could not get ESS {0}.
Category:
Session
Cause:
Exception during session retrieving.
Action:
Check configuration and try again.
ODI-10185
Operation is not granted.
Category:
Security
Cause:
Current level of permission is not sufficient.
Action:
Check your permissions.
ODI-10186
User {0} is inactive.
Category:
Security
Cause:
There is no GUID defined for this User in ODI repository
Action:
Check user GUID.
ODI-10187
The authentication API is used in wrong way.
Category:
Programmatic
Cause:
The authentication API is used in wrong way.
Action:
Check usage of API.
ODI-10188
Error while login from OPSS.
Category:
Other
Cause:
Exception was thrown during login process.
Action:
Make sure OPSS is configured correctly for this installation.
ODI-10189
The password violates the following rule: "Password policy {0}". Select another password.
Category:
Security
Cause:
Weak password
Action:
Check password policy and correct password.
ODI-10190
The user {0} has its account expired.
Category:
Security
Cause:
Account expired
Action:
Request supervisor for account unlocking.
ODI-10191
Unable to create datasource provider.
Category:
Configuration
Cause:
Exception during creation.
Action:
Check configuration.
ODI-10192
Unable to retrieve user GUID.
Category:
Other
Cause:
Exception during GUID retrieving.
Action:
Check repository connection.
ODI-10193
Unexpected null value in port.
Category:
Programmatic
Cause:
JPS port value is null.
Action:
Check JPS configuration.
ODI-10194
Uncategorized security exception.
Category:
Programmatic
Cause:
An unexpected error occurred.
Action:
Check exception cause for details.
ODI-10195
CsfAccessor is only available for CsfPasswordStorageConfiguration
Category:
Programmatic
Cause:
Password storage configuration is internal.
Action:
Check storage configuration.
ODI-10196
Error while accessing the repository.
Category:
Network
Cause:
Network problems.
Action:
Check the network connection and the database status.
ODI-10197
Instance is not connected to a work repository
Category:
Programmatic
Cause:
Work datasource is null.
Action:
Check work datasource.
ODI-10198
Context with code '{0}' was not found.
Category:
Programmatic
Cause:
Context was not found.
Action:
Check context code.
ODI-10199
Incorrect ODI username or password.
Category:
Security
Cause:
Incorrect ODI username or password.
Action:
Check username and password.
ODI-10200
Work repository {0} was not found.
Category:
Programmatic
Cause:
Wrong repository name or repository is not defined.
Action:
Check repository name.
ODI-10201
The user {0} has its password expired.
Category:
Security
Cause:
Account expired
Action:
Request supervisor for changing password.
ODI-10202
Supervisor privilege is required to setup repository.
Category:
Security
Cause:
Insufficient level of permissions.
Action:
User supervisor account for this operation.
ODI-10203
Transaction state is illegal.
Category:
Programmatic
Cause:
Transaction state is illegal.
Action:
Check transaction state.
ODI-10204
Inappropriate usage of a ODI transaction API.
Category:
Programmatic
Cause:
Inappropriate usage of a ODI transaction API.
Action:
Check ODI transaction API.
ODI-10205
Unexpected rollback.
Category:
Programmatic
Cause:
Attempt to commit a transaction resulted in an unexpected rollback.
Action:
Check transaction.
ODI-10206
Transaction cannot be created.
Category:
Programmatic
Cause:
Exception was thrown during transaction creation.
Action:
Check transaction.
ODI-10207
Uncategorized exception during transaction system usage.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Check exception cause for details.
ODI-10208
Error when changing password for user {0}.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Check exception cause for details.
ODI-10209
Cannot access a closed IOdiEntityManager.
Category:
Programmatic
Cause:
IOdiEntityManager has been closed.
Action:
Check IOdiEntityManager state.
ODI-10210
File {0} does not contain any objects to be imported by Smart Import.
Category:
Other
Cause:
Smart Export file specified for Smart Import is empty.
Action:
Specify a Smart Export file with objects for importing via Smart Import.
ODI-10211
Unsupported Java Character Set: {0}
Category:
Other
Cause:
Unsupported Java Character Set.
Action:
Check Java charset.
ODI-10212
Parent object {0}: ''{1}'' already has child {2}: ''{3}''. Technical details: {2} : ''{3}'' (with global id: {7} and internal id: {8}) violates alternate key constraint {4} {5} for values {6}
Category:
Other
Cause:
Object violated alternate key constraint.
Action:
Check object properties and constraint's values.
ODI-10213
Fixed format file field {0} (starts at {1} ends at {2}) has a file position that overlaps with the file position of field {3} (starts at {4} ends at {5}).
Category:
Other
Cause:
Two fields from a fixed format file have overlapping file positions.
Action:
Modify the file positions or remove a field if the overlapping file positions are not correct.
ODI-10214
Fixed format file fields {0} (starts at {1} ends at {2}) and {3} (starts at {4} ends at {5}) have unused file positions between them.
Category:
Other
Cause:
Two fields from a fixed format file have unused file positions between them.
Action:
Modify the file positions if having unused file positions is not correct.
ODI-10215
It is forbidden to import a log into a repository using any other import mode except "Synonym Mode Insert".
Category:
Other
Cause:
Import mode is not "Synonym Mode Insert".
Action:
Correct import mode.
ODI-10216
Upgrade key cannot be null when importing objects from before ODI 12C.
Category:
Other
Cause:
Upgrade key is not set for import that must upgrade objects to have global ids.
Action:
Specify the upgrade key to be used.
ODI-10217
Permission check failed for instance object {0}.
Category:
Other
Cause:
Permission check failed for instance object.
Action:
Need to grant initial permission for creator on object.
ODI-10218
Invalid WAS_HOME ("{0}") set or WebSphere library jar ({1}) not found under WAS_HOME/plugins.
Category:
Other
Cause:
Wrong WAS_HOME set (or) WebSphere libraries (com.ibm.ws.admin.core.jar, com.ibm.ws.admin.services.jar, com.ibm.ws.runtime.jar) are moved
Action:
Check that the environment-variable WAS_HOME is set properly to point to WebSphere Application Server root. Also, ensure the libraries exist under WAS_HOME/plugins.
ODI-10219
ODI Library for WebSphere access ({0}) not found.
Category:
Other
Cause:
Library could be moved / deleted
Action:
Check that the specified library present
ODI-10220
ODI was unable to find the technology "{0}".
Category:
Other
Cause:
Missing technology.
Action:
Check that this technology is defined in the repository. .
ODI-10221
It is taken {0} second to synchronize Snp_Ent_Principal table content.
Category:
Other
Cause:
Action:
ODI-10222
The compatible Mapping/ReusableMapping {0} can only be modified by 11g SDK.
Category:
Other
Cause:
An attempt was made to modify compatible Mapping using 12c SDK.
Action:
Modify compatible Mapping using 11g Interface SDK.
ODI-10223
A non-legacy compatible import source cannot be imported into a legacy compatible repository.
Category:
Other
Cause:
An attempt was made to import a non-legacy compatible import source into a legacy compatible repository.
Action:
Import a legacy compatible import source or make repository not legacy compatible.
ODI-10224
You are not authorized to create new user.
Category:
Security
Cause:
Only SUPERVISOR could create users.
Action:
Check permissions.
ODI-10225
Invalid wallet password: A valid password must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.
Category:
Security
Cause:
Invalid wallet password.
Action:
Please choose a valid wallet password accordingly.
ODI-10226
Wallet already exists.
Category:
Security
Cause:
Try to create a wallet which already exists.
Action:
Please stop creating a wallet. Instead use the existing one.
ODI-10227
Wallet new password is same as old password.
Category:
Security
Cause:
You provide a new wallet password which is the same as the old one.
Action:
Please choose different wallet password than the old one.
ODI-10228
Repository with id ''{0}'' or with name ''{1}'' has been already used in your master repository.
Category:
Configuration
Cause:
Master repository has already work repository with the same name or id.
Action:
Check your master repository and work repository.
ODI-10229
Repository with id ''{0}'' has been already used in your master repository.
Category:
Configuration
Cause:
Master repository has already work repository with the same id.
Action:
Check your master repository and work repository.
ODI-10230
Repository with name ''{0}'' has been already used in your master repository.
Category:
Configuration
Cause:
Master repository has already work repository with the same name.
Action:
Check your master repository and work repository.
ODI-10231
Interface {0} cannot be imported because source temporary interface / mapping {1} is not found.
Category:
Other
Cause:
An attempt was made to import an interface with a source temporary interface / mapping that cannot be found in the import source or target repository.
Action:
Import the missing source temporary interface / mapping.
ODI-10232
The password violates the following rule: "New password must be different from old one". Select another password.
Category:
Security
Cause:
Weak password
Action:
Check password policy and correct password.
ODI-10234
Object cannot be imported since it contains non XML files
Category:
Other
Cause:
ZipFolder to be imported should not contain non XML files
Action:
Check ZipFolder to be imported
ODI-10235
No Importable files found
Category:
Other
Cause:
None of XML files imported from ZipFolder
Action:
Check XML files to be imported from Zip Folder
ODI-10236
Object must be replaced with an object of same KM type
Category:
Other
Cause:
KM of different type to the existing KM was selected for import replace.
Action:
Import Replace KM with existing KM type
ODI-10237
Object not replaced
Category:
Other
Cause:
A KM was selected for the Import Replace with a different type to the current KM.
Action:
Select a KM of the same type for import replace.
ODI-10238
Object must be replaced with an object of same type
Category:
Other
Cause:
Different ODI object is used to Import Replace KM
Action:
Import Replace KM with Same type
ODI-10239
Importing file "{0}"...
Category:
Files
Cause:
Action:
ODI-10240
Updating dataservers...
Category:
Topology
Cause:
Action:
ODI-10241
Removing Error Tables for Physical Schema with id "{0}"
Category:
Topology
Cause:
Action:
ODI-10242
Removing Error Table "{0}"
Category:
Topology
Cause:
Action:
ODI-10243
Cannot import an export file with parents using regular import and INSERT_UPATE mode. Use smart import instead.
Category:
Other
Cause:
An attempt was made to import an export file created with parent objects using regular import and INSERT_UPATE mode. This would cause all other objects under the parent objects and not in the import file to be deleted.
Action:
Use smart import to import an export file created with parent objects when INSERT_UPDATE functionality is needed.
ODI-10244
Cannot import {0} {1} (with global id: {2} and internal id: {3}) because referenced {4} with global id {5} does not exist.
Category:
Other
Cause:
The referenced object for a foreign key cannot be found in order to set the reference and a missing reference cannot be created.
Action:
Import the missing referenced object before importing the referencing object.
ODI-10245
Cannot import {0} {1} (with global id: {2} and internal id: {3}) belonging to {4} {5} (with global id: {6} and internal id: {7}) because its referenced object is not found in the target repository.
Category:
Other
Cause:
The object was imported in a SYNONYM UPDATE mode and the referenced object was not found in the repository.
Action:
Change the import mode to INSERT_UPDATE or import the file twice first in INSERT MODE and then in UPDATE mode.
ODI-10246
No Exportable objects found in the repository.
Category:
Other
Cause:
No objects are present in the repository for export
Action:
Create repository objects
ODI-10247
Specified project {0} does not exist in the repository.
Category:
Other
Cause:
The repository did not contain the specified project.
Action:
Choose another project or create the project with the specified name.
ODI-10248
{0} : Not an ODI special driver.
Category:
Other
Cause:
Invalid Special driver.
Action:
Check that this technology is part of the special driver list.
ODI-13000
Invalid Directory Path specified - {0}
Category:
Other
Cause:
Invalid directory path. Either the path does not exist or is not a directory
Action:
Provide valid directory path
ODI-13001
Error Fetching Objects From File
Category:
Other
Cause:
Error Fetching Objects From File
Action:
Check The File
ODI-13002
Error Fetching Objects From Version Control System
Category:
Other
Cause:
Error Fetching Objects From Version Control System
Action:
Check The Repository
ODI-13003
Error Fetching Objects From Folder
Category:
Other
Cause:
Error Fetching Objects From Folder
Action:
Check Either the path does not exist or is not a directory
ODI-13005
Error Listing Branches From VCS
Category:
Other
Cause:
Error Listing Branches From VCS
Action:
Check The Repository
ODI-13006
Error Exporting Objects To Memory
Category:
Other
Cause:
Error Exporting Objects To Memory
Action:
Check The Object List
ODI-13007
Error Creating Temp Dir
Category:
Other
Cause:
Error Creating Temp Dir
Action:
Check The Path / Permission
ODI-13008
Error Listing NonEmpty Branches From Version Control System
Category:
Other
Cause:
Error Listing NonEmpty Branches From Version Control System
Action:
Check The Repository
ODI-13009
Error Listing NonEmpty Tags From Version Control System
Category:
Other
Cause:
Error Listing NonEmpty Tags From Version Control System
Action:
Check The Repository
ODI-13010
Error querying merge objects
Category:
Other
Cause:
Error Fetching SnpObjects
Action:
Check The Repository
ODI-13011
An in progress merge already exists. Only one in progress merge is allowed at a time.
Category:
Other
Cause:
A different in progress merge already exists
Action:
Complete the merge that is in progress before attempting to start another merge.
ODI-13012
In progress merge objects still exist for the merge. All merge objects must be complete before merge status can be set to complete.
Category:
Other
Cause:
In progress merge objects still exist for the merge
Action:
Complete the merge for all in progress merge objects in order to complete the merge.
ODI-13013
This operation is supported only when the object is deleted in SOURCE.
Category:
Other
Cause:
This operation is supported only when the object is deleted in SOURCE.
Action:
Perform delete object operation when object is deleted in SOURCE.
ODI-13014
An object ({0} {1}) identified as new for a merge cannot be added due to:
Category:
Other
Cause:
A different object already exists with the same name which causes the adding of the object to fail.
Action:
Delete or rename the conflicting object in the merge target, or rename the object in the merge source.
ODI-13015
This operation is supported only when the object is added in SOURCE.
Category:
Other
Cause:
This operation is supported only when the object is added in SOURCE.
Action:
Perform delete object operation when object is added in SOURCE.
ODI-13700
Unable to set the role OWB_USER for this user.
Category:
Other
Cause:
An attempt was made to set the role OWB_USER for the connected user.
Action:
Check that the role exists and the connected user is an OWB user.
ODI-13701
Unable to set the workspace {0} for this user.
Category:
Other
Cause:
An attempt was made to select the OWB workspace for the connected user.
Action:
Check that the workspace exists and the connected user has got privilege to access it.
ODI-13702
Unexpected error when connecting to OWB workspace {0}.
Category:
Other
Cause:
An unexpected error occurred when connecting to workspace.
Action:
Verify that the Owb repository is up and running.
ODI-13703
Unexpected error when locating object {0} in OWB workspace {1}.
Category:
Other
Cause:
An unexpected error occurred when locating an object in a workspace
Action:
Verify that the Owb repository is up and running and the object exists.
ODI-13704
Could not locate the physical schema associated with OWB workspace {0} in context {1}.
Category:
Other
Cause:
An error occurred when finding the schema related to an OWB workspace in a context.
Action:
Verify that the OWB workspace is related to a physical schema in the context.
ODI-13800
Cannot locate the monitor configuration file: {0} using JVM argument: {1}={2} or the environment variable: {3}={4}.
Category:
Configuration
Cause:
Action:
ODI-13801
Cannot locate the monitor configuration file at: {0}.
Category:
Configuration
Cause:
Action:
ODI-13802
Cannot access the monitor configuration file: {0}.
Category:
Configuration
Cause:
Action:
ODI-13803
The contents of the monitor configuration file: {0} are invalid.
Category:
Configuration
Cause:
Action:
ODI-13804
The runtime performance monitoring has been turned off due to invalid monitor configuration.
Category:
Configuration
Cause:
Action:
ODI-13805
An error occured while updating the monitor status for the Agent:{0}, Master repository external id:{1}
Category:
Other
Cause:
Action:
ODI-13806
An error occurred while starting the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13807
An error occurred while stopping the pre execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13808
An error occurred while starting the request processing monitor for Agent={0}, Master repository external id={1}
Category:
Other
Cause:
Action:
ODI-13809
An error occurred while stopping the request processing monitor for Agent={0}, Master repository external id={1}
Category:
Other
Cause:
Action:
ODI-13810
An error occurred while starting the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13811
An error occurred while stopping the execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13812
An error occurred while starting the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13813
An error occurred while stopping the post execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13814
An error occurred while starting the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13815
An error occurred while stopping the Scenario execution monitor for Agent={0}, Master repository external id={1}, Scenario={2}
Category:
Other
Cause:
Action:
ODI-13816
An error occurred while starting the Step execution monitor for Agent={0}, Scenario={1}, Step={2}
Category:
Other
Cause:
Action:
ODI-13817
An error occurred while stopping the Step execution monitor for Agent={0}, Scenario={1}, Step={2}
Category:
Other
Cause:
Action:
ODI-13818
An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}
Category:
Other
Cause:
Action:
ODI-13819
An unexpected error occurred while updating the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}
Category:
Other
Cause:
Action:
ODI-13820
An unexpected error occurred while starting the entity monitor for entity={0}, agent={1}, master repository external id={2}, session id={3}
Category:
Other
Cause:
Action:
ODI-13821
An error occurred while registering the Agent Discovery Mbean, mbeanName={0}
Category:
Other
Cause:
Action:
ODI-13822
An error occurred while de-registering the Agent Discovery Mbean, mbeanName={0}
Category:
Other
Cause:
Action:
ODI-13823
Could not find the Server MBean for server {0} on platform {1}.
Category:
Other
Cause:
Action:
ODI-14000
Importing Object
Category:
Other
Cause:
Action:
ODI-14001
Importing Profile
Category:
Other
Cause:
Action:
ODI-14002
Importing User
Category:
Other
Cause:
Action:
ODI-14003
Importing InstObj
Category:
Other
Cause:
Action:
ODI-14004
Importing Local Repository
Category:
Other
Cause:
Action:
ODI-14005
Importing Techno
Category:
Other
Cause:
Action:
ODI-14006
Importing Data Types
Category:
Other
Cause:
Action:
ODI-14007
Importing Data Types Conversions
Category:
Other
Cause:
Action:
ODI-14008
Importing Language
Category:
Other
Cause:
Action:
ODI-14009
Importing Open Tools
Category:
Other
Cause:
Action:
ODI-14010
Importing Pwd Policies
Category:
Other
Cause:
Action:
ODI-14011
Importing Pwd Rule
Category:
Other
Cause:
Action:
ODI-14012
Importing Connection
Category:
Other
Cause:
Action:
ODI-14013
Importing Agent
Category:
Other
Cause:
Action:
ODI-14014
Importing LBAgent
Category:
Other
Cause:
Action:
ODI-14015
Importing Logical Agent
Category:
Other
Cause:
Action:
ODI-14016
Importing Context
Category:
Other
Cause:
Action:
ODI-14017
Importing Pschema
Category:
Other
Cause:
Action:
ODI-14018
Importing Lschema
Category:
Other
Cause:
Action:
ODI-14019
Importing Entity
Category:
Other
Cause:
Action:
ODI-14020
Importing Link
Category:
Other
Cause:
Action:
ODI-14021
Importing Field
Category:
Other
Cause:
Action:
ODI-14022
Importing FieldLook Up
Category:
Other
Cause:
Action:
ODI-14023
Importing Look Up
Category:
Other
Cause:
Action:
ODI-14024
Importing Look Up Value
Category:
Other
Cause:
Action:
ODI-14025
Importing Action
Category:
Other
Cause:
Action:
ODI-14026
Importing Action Group
Category:
Other
Cause:
Action:
ODI-14027
Importing Version
Category:
Other
Cause:
Action:
ODI-14028
Importing Solutions
Category:
Other
Cause:
Action:
ODI-14029
Cleaning connections
Category:
Other
Cause:
Action:
ODI-14030
Importing:
Category:
Other{0}
Cause:
Action:
ODI-14031
Importing Session
Category:
Other
Cause:
Action:
ODI-14032
Importing Global Sequences
Category:
Other
Cause:
Action:
ODI-14033
Importing Global Variables
Category:
Other
Cause:
Action:
ODI-14034
Importing Global User Functions
Category:
Other
Cause:
Action:
ODI-14035
Importing Global Group of States
Category:
Other
Cause:
Action:
ODI-14036
Importing Model Folders
Category:
Other
Cause:
Action:
ODI-14037
Importing Models
Category:
Other
Cause:
Action:
ODI-14038
Importing Scenario folders
Category:
Other
Cause:
Action:
ODI-14039
Importing Projects
Category:
Other
Cause:
Action:
ODI-14040
Importing Scenario
Category:
Other
Cause:
Action:
ODI-14041
Importing Folders
Category:
Other
Cause:
Action:
ODI-14042
Importing Packages
Category:
Other
Cause:
Action:
ODI-14043
Importing Interfaces
Category:
Other
Cause:
Action:
ODI-14044
Importing Procedures
Category:
Other
Cause:
Action:
ODI-14045
Importing Knowledge Modules
Category:
Other
Cause:
Action:
ODI-14046
ODI Master Repository Upgrade: Upgrading Repository Structure...
Category:
Upgrade
Cause:
Action:
ODI-14047
ODI Master Repository Upgrade: Upgrading Repository Data...
Category:
Upgrade
Cause:
Action:
ODI-14048
ODI Master Repository Upgrade: Done.
Category:
Upgrade
Cause:
Action:
ODI-14049
Master repository creation is successful.
Category:
Other
Cause:
Action:
ODI-14050
ODI Work Repository Attach: Attaching Repository...
Category:
Other
Cause:
Action:
ODI-14051
ODI Work Repository Attach: Done.
Category:
Other
Cause:
Action:
ODI-14052
ODI Work Repository Upgrade: Upgrading Repository Structure...
Category:
Upgrade
Cause:
Action:
ODI-14053
ODI Work Repository Upgrade: Upgrading Repository Data...
Category:
Upgrade
Cause:
Action:
ODI-14054
ODI Work Repository Upgrade: Done.
Category:
Upgrade
Cause:
Action:
ODI-14055
Work repository creation is successful.
Category:
Other
Cause:
Action:
ODI-14056
Importing SubModels
Category:
Other
Cause:
Action:
ODI-14057
Importing Tables
Category:
Other
Cause:
Action:
ODI-14058
End importing {1}. Import time (milliseconds): {0}.
Category:
Other
Cause:
Action:
ODI-14059
End importing {1}. Import time (hh:mm:ss): {0}.
Category:
Other
Cause:
Action:
ODI-14060
End importing {0}.
Category:
Other
Cause:
Action:
ODI-14061
Master repository already up to date nothing to do.
Category:
Other
Cause:
Action:
ODI-14062
Upgrading master repository from {0} to {1}
Category:
Other
Cause:
Action:
ODI-14063
Applying DDL from file {0}
Category:
Other
Cause:
Action:
ODI-14064
Error while applying DDL from file {0}
Category:
Other
Cause:
Exception during execution of session.
Action:
Check session.
ODI-14065
Work repository already up to date. Nothing to do.
Category:
Upgrade
Cause:
Action:
ODI-14066
upgrade error while executing {0} params = {1}
Category:
Upgrade
Cause:
Wrong parameters at Sql query.
Action:
Check parameters.
ODI-14067
Exporting {0}
Category:
Other
Cause:
Action:
ODI-14068
End exporting {1}. Export time (milliseconds): {0}
Category:
Other
Cause:
Action:
ODI-14069
End exporting {1}. Export time (hh:mm:ss): {0}.
Category:
Other
Cause:
Action:
ODI-14070
Import failed. The parent object was not found in the repository.
Category:
Other
Cause:
The object was imported in a SYNONYM mode and the parent object was not found in the repository.
Action:
Change the import mode or restore the parent object in the repository
ODI-14071
Getting Dependencies
Category:
Other
Cause:
Action:
ODI-14072
End getting dependencies. Time (milliseconds): {0}
Category:
Other
Cause:
Action:
ODI-14073
End getting dependencies. Time (hh:mm:ss): {0}.
Category:
Other
Cause:
Action:
ODI-14074
Parent folder already has the release tag set.
Category:
Other
Cause:
Setting the release tag when the parent already has the release tag set.
Action:
Set the release tag in parent.
ODI-14075
Seed data for property missing.
Category:
Other
Cause:
Seed data for property {0} is missing.
Action:
Contact Oracle Support Services
ODI-14077
Importing Mappings/Reusable Mappings
Category:
Other
Cause:
Action:
ODI-14078
Importing Mapping Component Types
Category:
Other
Cause:
Action:
ODI-14079
Importing Enterprise Scheduler
Category:
Other
Cause:
Action:
ODI-14080
Importing Enterprise Principals
Category:
Other
Cause:
Action:
ODI-14081
User Function syntax is not unique.
Category:
Other
Cause:
Work repository already has User Function with the same syntax.
Action:
Check your user function syntax.
ODI-14085
Object cannot be Imported since it contains non XML file
Category:
Other
Cause:
Folder to be imported should not contain non XML files
Action:
Check Folder to be imported
ODI-14086
Begin importing: {0}
Category:
Other
Cause:
Action:
ODI-14087
Total Time For Import (before Upgrade of Interfaces) : {0} (milliseconds)
Category:
Other
Cause:
Action:
ODI-14088
Total Time For Import (before Upgrade of Interfaces) : {0} (hh:mm:ss)
Category:
Other
Cause:
Action:
ODI-14089
Total Time for Import:{0} (milliseconds)
Category:
Other
Cause:
Action:
ODI-14090
Total Time for Import: {0} (hh:mm:ss)
Category:
Other
Cause:
Action:
ODI-14091
Work repository is already attached to another master repository.
Category:
Other
Cause:
Attempt to attach already attached work repository was made while work repository can be attached to only one master repository at the moment.
Action:
Work repository should be first detached from the master repository it is attached to at the moment.
ODI-14092
Loading Master Repository Info
Category:
Other
Cause:
Action:
ODI-14093
Cannot Connect To Master Repository
Category:
Other
Cause:
Cannot Connect To Master Repository
Action:
Check your connection settings or database
ODI-14094
Master Repository Is In Invalid State.
Category:
Other
Cause:
Action:
ODI-14095
Master Repository Already Up To Date.
Category:
Other
Cause:
Action:
ODI-14096
Error While Upgrading Master Repository {0}
Category:
Other
Cause:
Exception caught while upgrading Master Repository
Action:
Please check the Logs.
ODI-14097
Importing Technology Seed Data
Category:
Other
Cause:
Action:
ODI-14098
Error While Importing Technology Seed Data {0}
Category:
Other
Cause:
Exception caught while importing technology Seed Data
Action:
Please check the logs
ODI-14099
Scanning Export Files
Category:
Other
Cause:
Action:
ODI-14100
Loading Technology
Category:
Other
Cause:
Action:
ODI-14101
Checking for Pre 4.3.3.2 Version
Category:
Other
Cause:
Action:
ODI-14102
Upgrading To Master Repository Till 4.3.3.2 Version
Category:
Other
Cause:
Action:
ODI-14103
Upgrading Master Repository Post 4.3.3.2 Version
Category:
Other
Cause:
Action:
ODI-14104
Reimporting Metadata
Category:
Other
Cause:
Action:
ODI-14105
Reimporting Security Seed Data
Category:
Other
Cause:
Action:
ODI-14106
Getting Work Repositories
Category:
Other
Cause:
Action:
ODI-14107
Found {0} Work Repositories to Upgrade
Category:
Other
Cause:
Action:
ODI-14108
Upgrading {0} Work Repository
Category:
Other
Cause:
Action:
ODI-14109
Cannot Connect To Work Repository
Category:
Other
Cause:
Cannot Connect To Work Repository {0}
Action:
Check your connection settings or database
ODI-14110
Work Repository {0} Is In Invalid State.
Category:
Other
Cause:
Action:
ODI-14111
Work Repository Already Up To Date.
Category:
Other
Cause:
Action:
ODI-14112
Converting All Interface to Mapping
Category:
Other
Cause:
Action:
ODI-14113
Work repository is already attached to the master repository.
Category:
Other
Cause:
Attempt to attach already attached work repository was made.
Action:
Please do not attach the work repository again to the master repository.
ODI-14114
Incorrect wallet password.
Category:
Security
Cause:
Provided wallet password is incorrect.
Action:
Please enter correct wallet password.
ODI-14115
Wallet file {0} is not found at specified location.
Category:
SECURITY
Cause:
Wallet file is not present.
Action:
Please check if wallet file is present at specified location.
ODI-14116
No registry database provided
Category:
Other
Cause:
Registry database not provided.
Action:
Please provide registry database.
ODI-14117
No repository database in URL: {0}
Category:
Other
Cause:
Repository database missing from the jdbc url.
Action:
Please provide repository database in the jdbc url.
ODI-14118
Not a valid jdbc mysql url: {0}
Category:
Other
Cause:
Invalid JDBC mysql url
Action:
Please provide a valid jdbc url.
ODI-14119
The selected database was released after this version of Oracle Fusion Middleware. For the most recent list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14120
The database you are connecting is not a supported version. refer to the certification matrix for supported DB versions.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14121
The selected Oracle Database 11g Release 2 instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 11g Release 2 (11.2.0.3) or higher. For the latest list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14122
The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.5.3.0. Refer to the certification matrix for supported DB versions
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14123
DB Init Param Prerequisite failure for innodb_file_format. Its value should be 'Barracuda'.
Category:
Other
Cause:
INNODB_FILE_FORMAT value is not 'Barracuda'.
Action:
Refer to the certification matrix for supported DB init parameters.
ODI-14124
The selected MySQL instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires MySQL 5.5.14 or higher. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14125
DB Init Param Prerequisite failure for innodb_file_per_table. Its value should be 'ON'
Category:
Other
Cause:
INNODB_FILE_PER_TABLE value is not 'ON'
Action:
Refer to the certification matrix for supported DB init parameters.
ODI-14126
DB Init Param Prerequisite failure for innodb_large_prefix. Its value should be 'ON'.
Category:
Other
Cause:
INNODB_LARGE_PREFIX value is not 'ON'
Action:
Refer to the certification matrix for supported DB init parameters.
ODI-14127
DB Init Param Prerequisite failure for log_bin_trust_function_creators. Its value should be 'ON'.
Category:
Other
Cause:
log_bin_trust_function_creators value is not 'ON'
Action:
Refer to the certification matrix for supported DB init parameters.
ODI-14128
The selected Oracle database is a multitenant container database (CDB). Connecting to a multitenant container database (CDB) is not supported. Instead, connect to a valid pluggble database (PDB).
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14129
The selected Oracle Database 12c instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 12c (12.1.0.1) or higher. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14130
The selected Oracle Database 11g Release 1 or Oracle Database 10g instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires Oracle Database 10g (10.2.0.4) or higher or Oracle Database 11g Release 1 (11.1.0.7) or higher. For the latest list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14131
The database you are connecting is not a supported version. Enter Database with version equal to or higher than 2008 R2. Refer to the certification matrix for supported DB versions.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14132
The selected IBM DB2 instance is not certified with this version of Oracle Fusion Middleware. Oracle Fusion Middleware 12c requires IBM DB2 9.7 or higher in 9 series and IBM DB2 10.1 FP2 or higher in 10 series. For a list of certified databases, refer to the Supported System Configurations information on the Oracle Technology Network.
Category:
Other
Cause:
Database version is not supported
Action:
Refer to the certification matrix for supported DB versions.
ODI-14133
User should have sysdba or dba privilages.
Category:
Other
Cause:
User does not have sysdba or dba privilages
Action:
Grant user sysdba or dba privilages.
ODI-14134
The selected Oracle database is not configured to use the AL32UTF8 character set. Oracle strongly recommends using the AL32UTF8 character set for databases that support Oracle Fusion Middleware.
Category:
Other
Cause:
The database you are connecting is with non-AL32UTF8 character set
Action:
Use AL32UTF8 as the database character set.
ODI-14135
Table schema_version_registry$ already exists. Please use correct database.
Category:
Other
Cause:
Table schema_version_registry$ already exists.
Action:
Use correct database.
ODI-14136
Database does not match the requirement.
Category:
Other
Cause:
Database validation failed
Action:
Refer to the certification matrix for supported DB versions.
ODI-14137
Error occurred while validating database {0}.
Category:
Other
Cause:
Database validation failed
Action:
Refer to the certification matrix for supported DB versions.
ODI-14138
Could not perform validation of the database.Please check the database user privileges.
Category:
Other
Cause:
Database validation failed
Action:
Check if database user has sufficient privileges or required table/view/file exist .
ODI-14139
Encryption Standard is not set in Master Repository.
Category:
Security
Cause:
Master Repository configured with invalid or no Encryption Standard.
Action:
Set the Encryption Standard to be used in the Master Repository, with valid value for algorithm ('AES') and key-length ('128' / '256').
ODI-14140
Master key data is not set in Master Repository
Category:
Security
Cause:
Master Repository does not have the master key data.
Action:
Set the Master key data to be used in the Master Repository.
ODI-14141
The provided key is not matching the key-specification. Key must : be of length 8-100, contain at least one alphabet (lower/uppercase), contain at least one numeric-digit (or) a special-character from: [@ # $ % + / =].
Category:
Security
Cause:
The provided key is not matching the key-specification.
Action:
Provide key that matches the key-specification
ODI-14142
The Security Policy currently in force, does not allow the use of AES-256.
Category:
Security
Cause:
The Security Policy in force does not allow using AES-256 Encryption Standard.
Action:
To use AES-256, please replace the security policy files in JRE_HOME/lib/security, with Unlimited Strength Policy Files available at Java SE downloads at http://www.oracle.com/technetwork/java. Refer Java SE documentation for more information.
ODI-14143
Encryption Standard persisted in master repository is not AES-128 or AES-256.
Category:
Security
Cause:
The Encryption Standard configured in the repository is not supported.
Action:
Edit the master repository configuration to set the Encryption Standard as AES-128 or AES-256.
ODI-14144
An Error occurred while parsing the ODI Tool Command
Category:
Security
Cause:
An error occurred while parsing the ODI Tool Command text.
Action:
Refer to stack trace for more details.
ODI-14145
An Error occurred while setting parameter {0} in ODI Tool Command.
Category:
Security
Cause:
Unable to set parameter in ODI Tool Command.
Action:
Refer to stack trace for more details.
ODI-14146
Incorrect Export Key
Category:
Security
Cause:
The Export Key provided is incorrect for the import source
Action:
Provide a valid Export Key that was used during Export of object
ODI-14147
An error occurred while migrating cipher text in object {0} - ''{1}'' (with Internal ID: {2} and Global ID: {3})
Category:
Security
Cause:
Invalid Cipher content or Invalid Export Key
Action:
If exporting, check if the cipher data present in the object is correct. If importing, check if Export Key is correct.
ODI-14148
An Error occurred while creating Cipher for migration.
Category:
Security
Cause:
An error occurred while creating ODI Cipher.
Action:
Refer to stack trace for more details
ODI-14149
Invalid Encoder/Decoder for Cipher Text Migration.
Category:
Security
Cause:
The ODI Encoder/Decoder is invalid.
Action:
Create valid Encoder/Decoder for Cipher Text Migration.
ODI-14150
An Error occurred while migrating password cipher text
Category:
Security
Cause:
An error occurred while migrating the password cipher text
Action:
Refer to stack trace for more details
ODI-14151
An error occurred while retrieving parameters from ODI Tool Command.
Category:
Security
Cause:
Invalid ODI Tool Command.
Action:
Check ODI Tool Command text.
ODI-14152
Package name is not unique.
Category:
Other
Cause:
Duplicate package name. Package with the same name already exists in this folder.
Action:
Choose another package name.
ODI-14153
Procedure name is not unique.
Category:
Other
Cause:
Duplicate procedure name. Procedure with the same name already exists in this folder.
Action:
Choose another procedure name.
ODI-14154
Context name is not unique.
Category:
Other
Cause:
Context with the same name already exists.
Action:
Check your context name.
ODI-14155
Context code is not unique.
Category:
Other
Cause:
Context with the same code already exists.
Action:
Check your context code.
ODI-14156
KM name is not unique.
Category:
Other
Cause:
Duplicate KM name. KM with the same name already exists.
Action:
Choose another KM name.
ODI-14157
Procedure option name is not unique.
Category:
Other
Cause:
Duplicate procedure option name. Procedure option with the same name already exists.
Action:
Choose another procedure option name.
ODI-14158
A Supervisor user can be updated only by another Supervisor user.
Category:
Security
Cause:
The logged-in user is not a Supervisor user, but trying to update another Supervisor user.
Action:
Login as a user with right privileges.
ODI-14159
An error occurred while validating the Export Key.
Category:
Security
Cause:
An error occurred while validating the export key
Action:
Please check the Logs
ODI-14160
Skipping Data migration on IP Text {0} . Failed with Exception : {1} . Please fix manually.
Category:
Security
Cause:
An error occurred while migrating the password cipher text
Action:
Refer to Error Message for more details
ODI-14161
Duplicate name objects are found in the repository. Please check the upgrade log file.
Category:
Other
Cause:
Some objects with same names are under same parents
Action:
Check the log file for the duplicate name objects. Remove them before upgrade
ODI-14162
User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.
Category:
Security
Cause:
User cannot login ODI with blank password. Please contact SUPERVISOR to reset the password.
Action:
Please contact SUPERVISOR to reset the password.
ODI-14163
User cannot create master repository through import with blank supervisor password.
Category:
Security
Cause:
User cannot create master repository through import with blank supervisor password.
Action:
Please provide valid supervisor password to the API while create master repository thorugh import.
ODI-14164
Work repository name must not be null or empty
Category:
Other
Cause:
Work repository name is null or empty.
Action:
Check Work repository name.
ODI-14165
The repository is currently locked for sync operation and cannot be modified
Category:
Repository
Cause:
User cannot make any changes as repository is locked for sync.
Action:
Please try after some time.
ODI-14166
Importing Project Marker Groups
Category:
Other
Cause:
Action:
ODI-14167
Importing Project Sequences
Category:
Other
Cause:
Action:
ODI-14168
Importing Project Variables
Category:
Other
Cause:
Action:
ODI-14169
Importing Project User Functions
Category:
Other
Cause:
Action:
ODI-14170
Importing Project Knowledge Modules
Category:
Other
Cause:
Action:
ODI-14171
Importing Project Reusable Mappings
Category:
Other
Cause:
Action:
ODI-14172
Importing Project Mappings
Category:
Other
Cause:
Action:
ODI-14173
The repository is for {0} so you cannot connect to this repository from {1}.
Category:
Security
Cause:
Repository is not valid for the invoking application.
Action:
Connect to this repository use the proper application.
ODI-14174
You are using Oracle Golden Gate Studio which only supports internal authentication mode. But the repositgory is in external authentication mode which cannot be used for Oracle Golden Gate Studio.
Category:
Security
Cause:
The repository is in external authentication mode and it is not valid for Oracle Golden Gate Studio since Oracel Golden Gate Studio only supports internal authentication mode. One possibility could be that this repository is for Oracle Data Integrator.
Action:
Connect to a different repository.
ODI-14175
Cannot delete this user since it is the last supervisor user.
Category:
Security
Cause:
You are trying to delete the last supervisor user which cannot deleted.
Action:
Create another user and make it supervisor user and then you can delete this supervisor user.
ODI-14176
Password cannot be empty for accessing the MBean Server, which is used for External Password Storage.
Category:
Security
Cause:
Password is empty for the accessing the MBean Server.
Action:
Provide MBean server password.
ODI-14177
The external user: {0} does not exist in ODI repository and also has no ODI role granted. The GUID of the user : {1}
Category:
Security
Cause:
The specified external user does not exists in ODI repository and has no ODI role granted.
Action:
Add the external user in ODI repository or grant required ODI roles to the user.
ODI-14178
Schema name and Catalog name is not unique for the dataserver {0}
Category:
Other
Cause:
Duplicate physical schema. Physical Schema with the same schema name and catalog name already exists for this dataserver.
Action:
Choose another schema name and/or catalog name.
ODI-14179
For security reasons, you cannot use odiRef.getJDBCConnection("WORKREP"), since your Work Repository and Master Repository use the same database schema. Please contact your Oracle Data Integrator Administrator to grant you <Create JDBC Connection> permission on Master Repository object from Oracle Data Integrator Studio Security Explorer and try again. Please note that the <Create JDBC Connection> permission is located under Master Repository object in the Objects section from Security Explorer. You can give the permission to a user, say User1, by 1) drag and drop it to the user User1 2) then mark the newly granted permission as Generic Privilege: the newly granted permission <Create JDBC Connection> will be under the tree node User1/Objects/Master Repository, open the editor of the granted permission and select the check box named <Generic Privilege>.
Category:
Other
Cause:
The Work Repository and Master Repository use same database schema and you do not have the required permission granted.
Action:
Please contact your Oracle Data Integrator Administrator to grant you <Create JDBC Connection> permission on Master Repository object from Oracle Data Integrator Studio Security Explorer and try again. Or you also can re-create your Master and Work repositories in different database schema. Please note that the <Create JDBC Connection> permission is located under Master Repository object in the Objects section from Security Explorer. You can give the permission to a user, say User1, by 1) drag and drop it to the user User1 2) then mark the newly granted permission as Generic Privilege: the newly granted permission <Create JDBC Connection> will be under the tree node User1/Objects/Master Repository, open the editor of the permission and select the check box named <Generic Privilege>.
ODI-14180
{0}. Data migration is skipped for URL : {1}
Category:
Upgrade
Cause:
The format of the URL is incorrect or the URL contains invalid properties.
Action:
ODI-14181
Upgrading Converson Datatype Global Ids
Category:
Other
Cause:
Action:
ODI-14182
Error While Upgrading Conversion Datatype Global Ids {0}
Category:
Other
Cause:
Exception caught while upgrading conversion datatype (SnpConvDt) Global Ids
Action:
Please check the logs
ODI-14183
The Schema Version Registry Table already exists at {0}.
Category:
Other
Cause:
Schema Version Registry Table already exists.
Action:
Please use correct database.
ODI-14184
Unable to load required classes from {0} Data Server Classpath
Category:
Other
Cause:
Required Classes cannot be loaded from the Classpath specified in the Data Server
Action:
Please specify correct classpath in Data Server
ODI-14185
Unable to load Client: {0}
Category:
Other
Cause:
Client Classes cannot be loaded from the Classpath
Action:
Please check the logs
ODI-14186
Importing Dimension Model
Category:
Other
Cause:
Action:
ODI-14187
Importing Dimension
Category:
Other
Cause:
Action:
ODI-14188
Importing Cube
Category:
Other
Cause:
Action:
ODI-14189
Unable to connect to the Server via broker(s): {0}. Check Connection Settings.
Category:
Other
Cause:
Unable to connect to the Server.
Action:
Please check the connection settings
ODI-14190
Importing OGG Projects
Category:
Other
Cause:
Action:
ODI-14191
Importing OGG Solutions
Category:
Other
Cause:
Action:
ODI-14192
Importing OGG Folders
Category:
Other
Cause:
Action:
ODI-14193
Importing OGG Mappings
Category:
Other
Cause:
Action:
ODI-14194
Objects with null global id's are present in repository. Please check the upgrade log file.
Category:
Other
Cause:
Some objects with NULL global id's are present in repository
Action:
Manually Assign GUID to the objects which got NULL value before upgrade.
ODI-14195
Duplicate name objects and objects with null GUID are found in the repository. Please check the upgrade log file.
Category:
Other
Cause:
Some objects with same names are under same parents and some objects with NULL GOLBAL_ID value
Action:
Remove duplicate named objects and manually assign unique GUID to the objects which got NULL value before upgrade.
ODI-14196
BICS Table Operation File Input Stream cannot be obtained.
Category:
Other
Cause:
BICS Table Operation File Path is not provided by user or invalid, hence input stream cannot be obtained.
Action:
Set valid BICS Table Operation File Pat.
ODI-14197
BICS Dataset Operation File Input Stream cannot be obtained.
Category:
Other
Cause:
BICS Dataset Operation File Path is not provided by user or invalid, hence input stream cannot be obtained.
Action:
Set valid BICS Dataset Operation File Pat.
ODI-14198
BICS Target Type is invalid.
Category:
Other
Cause:
Invalid BICS Target Type is provided by user(it should be table or dataset).
Action:
Set valid BICS Target Type.
ODI-14199
Cannot change BICS Operation property: {0}. Value has already been specified and it is immutable object.
Category:
Other
Cause:
User is trying to set value to immutable member which already has value in it.
Action:
Please do not set value of immutable object.
ODI-14200
You can only grant or retrieve enterprise principal member or ODI internal user member on role object. But this is an user object.
Category:
Security
Cause:
The application invoked some API on an user object, instead the API should be invoked on a role object.
Action:
This is an internal error. Please contact Oracle Support Services with details.
ODI-14201
This method is only applicable to Oracle Golden Gate Studio. But your repository is ODI.
Category:
Security
Cause:
The application invoked some API which is only applicable to Oracle Golden Gate Studio. But your application is configured as ODI.
Action:
This is an internal error. Please contact Oracle Support Services with details.
ODI-14202
Importing KM Template
Category:
Other
Cause:
Action:
ODI-14203
You do not have <Credential Access> permission on data server {0}. Please ask your Oracle Data Integrator Administrator or Security Administrator to grant you the permission. Please note: 1) The administrator first needs to grant you the non-generic <Credential Access> permission by drag-and-drop it to a user from Studio Security Explorer , this non-generic permission is located under Data Server object in the Objects section from Security Explorer; 2) Then the administrator needs to grant you the data server instance permission e.g. drag-and-drop the data server {1} on a user and check method <Credential Access> and save.
Category:
Security
Cause:
You do not have <Credential Access> permission on a data server
Action:
Please ask your Oracle Data Integrator Administrator or Security Administrator to grant you the permission. Please note: 1) The administrator first needs to grant you the non-generic <Credential Access> permission by drag-and-drop it to a user from Studio Security Explorer, this non-generic permission is located under Data Server object in the Objects section from Security Explorer; 2) Then the administrator needs to grant you the data server instance permission e.g. drag-and-drop the data server on a user and check method <Credential Access> and save.
ODI-14204
Method must be redefined in derived class: {0} for Foreign Key: {1}
Category:
Other
Cause:
Method must be redefined in derived class.
Action:
Call redefined method.
ODI-14205
{0} name is not unique.
Category:
Other
Cause:
Another object with the same name exists.
Action:
Choose another name.
ODI-14206
Import failed due to unable to delete unneeded objects in target repository.
Category:
Other
Cause:
Deletion of unneeded target objects failed due to sql constraint violation.
Action:
Contact Oracle Support Services.
ODI-14207
Oracle supplied KM must be imported using DUPLICATION mode cannot be imported using import replace
Category:
Other
Cause:
Oracle supplied KM must be imported by Duplication Mode
Action:
Import Oracle Supplied KM by Duplication mode.
ODI-14208
ImportReplaceKMFromXML API is used to import a KM File
Category:
Other
Cause:
XML File do not contain Procedure object
Action:
XML file must contain an OdiProcedure.
ODI-14209
Argument {0} cannot be null to export Delta artifacts
Category:
Other
Cause:
Argument cannot be null
Action:
Argument cannot be null.
ODI-14210
HDFS directory does not exist : {0}
Category:
Other
Cause:
HDFS directory does not exist.
Action:
HDFS directory must exist.
ODI-14211
Local directory does not exist : {0}
Category:
Other
Cause:
Local directory does not exist.
Action:
Local directory must exist.
ODI-14212
Argument : {0} is mandatory
Category:
Other
Cause:
Argument cannot be null.
Action:
Argument cannot be null.
ODI-14213
Input parameter {0} is not valid. It is either null/empty or invalid.
Category:
Other
Cause:
Input Parameter is invalid.
Action:
Provide valid input.
ODI-14214
Failed to connect to Object Storage.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Verify connection parameters.
ODI-14215
Failed to perform {0} on Object Storage.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services.
ODI-14216
Physical schema {0} is not configured for required field {1}.
Category:
Other
Cause:
Invalid Physical schema value specified.
Action:
Update Physical schema with proper values required for Object Storage.
ODI-14217
Input parameter {0} is not matching for specified users {1}.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14218
{0} should be specified when {1} is specified.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14219
Wallet file {0} is not accessible.
Category:
Security
Cause:
Wallet file is not accesible.
Action:
Please check Wallet file permission.
ODI-14220
{0} directory {1} configured for field {2} for Physical schema {3} does not exists.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14221
Physical schema is not configured for required field {0}.
Category:
Other
Cause:
Empty Physical schema value specified.
Action:
Update Physical schema with proper values required for Object Storage.
ODI-14222
Wallet file {0} does not contain connection information.
Category:
Security
Cause:
Wallet file doesnot have required information.
Action:
Please add connection details to Wallet file.
ODI-14223
Wallet file {0} does not contain credentials for given connection information.
Category:
Security
Cause:
Wallet file doesnot have required credential information.
Action:
Please add credential information to Wallet file for given connection information.
ODI-14224
Service URL {0} has wrong Protocol
Category:
Other
Cause:
Service URL has wrong Protocol
Action:
Please use correct URL to connect to Oracle Storage Cloud Service
ODI-14225
Incorrect UserName, Password or Identity Domain is provided.
Category:
Other
Cause:
Invalid credentials provided to connect to Oracle Storage Cloud Service
Action:
Please provide correct credentials to connect to Oracle Storage Cloud Service
ODI-14226
Invalid Service URL {0} is provided.
Category:
Other
Cause:
Invalid Service URL to connect to Oracle Storage Cloud Service
Action:
Please use correct Service URL to connect to Oracle Storage Cloud Service
ODI-14227
{0} cannot be NULL. Please provide Valid {0} to connect Oracle Storage Cloud Service
Category:
Other
Cause:
{0} Cannot be NULL
Action:
Please use correct {0} to connect to Oracle Storage Cloud Service
ODI-14229
Failed to connect to Oracle Storage Cloud Service
Category:
Other
Cause:
Failed to Download. File Count not matching with Object count in Container to download
Action:
Failed to Download. Please Check valid File Count matching Object count in Container to download
ODI-14230
Failed to {0}.Please use appropriate Storage Container Type to {0} STANDARD or ARCHIVE File Type
Category:
Other
Cause:
Failed to {0}. Invalid Container Storage Type for STANDARD | ARCHIVE type
Action:
Failed to {0}. Please Correct Storage Container Type accordingly to {0} STANDARD or ARCHIVE File type
ODI-14231
Physical schema {0} is not configured for required field {1}.
Category:
Other
Cause:
Invalid Physical schema value specified.
Action:
Update Physical schema with proper values required for Storage CS.
ODI-14232
{0} directory {1} configured for field {2} for Physical schema {3} does not exists.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14233
{0} container {1} configured for field {2} for physical schema {3} does not exist.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14234
{0} bucket {1} configured for field {2} for physical schema {3} does not exist.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14235
Credential zip {0} does not contain required tnsnames.ora.
Category:
Security
Cause:
Credential zip doesnot have required tnsnames.ora.
Action:
Please add required file tnsnames.ora in credential zip.
ODI-14236
Tnsnames file in {0} does not contain connection information.
Category:
Security
Cause:
TnsNames.ora is empty.
Action:
Please add connection information in tnsnames.ora in credential zip.
ODI-14237
Credential zip {0} can not be found.
Category:
Security
Cause:
Credential zip is not found.
Action:
Please check the location. Retry.
ODI-14238
Credential file {0} is not found at specified location {1}
Category:
SECURITY
Cause:
Credential file is not present.
Action:
Please check if credential file is present in Credential zip.
ODI-14240
Service name : {0} cannot contain '-'. Provide valid Service name.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14241
Invalid Service Name. Service : {0} does not exist.
Category:
Other
Cause:
Check Service Name.
Action:
Invalid Service name
ODI-14242
Failed to get list of containers.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services
ODI-14243
Failed to delete the container : {0}.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services
ODI-14244
Failed to create the container : {0}.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services
ODI-14245
Failed to fetch the service : {0}.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14246
Failed to perform {0} on Storage CS.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services
ODI-14247
Credential zip {0} is not accessible.
Category:
Security
Cause:
Credential zip is not accessible.
Action:
Verify permission and path accessibility.
ODI-14248
Unable to unzip Credential zip {0}
Category:
Others
Cause:
Error while trying to unzip credential zip.
Action:
Verify zip uploaded.
ODI-14249
Unable to encrypt files during Upload.
Category:
Other
Cause:
Invalid Encryption key provided.
Action:
Verify Encryption key.
ODI-14250
Invalid decrypt key provided.
Category:
Other
Cause:
Invalid Decryption key provided.
Action:
Verify Decryption key.
ODI-14251
Unable to decrypt files during Download.
Category:
Other
Cause:
Invalid Decryption key provided.
Action:
Verify Decryption key.
ODI-14252
Physical schema is not defined for the logical schema {0}.
Category:
Other
Cause:
Invalid input parameters specified.
Action:
Verify input parameters.
ODI-14253
Provided {0} logical schema {1} is not supported.
Category:
Other
Cause:
Invalid Logical schema value specified.
Action:
Update Logical schema with proper values.
ODI-14254
An error occurred while unzipping the DA file to directory {0}.
Category:
Other
Cause:
An error occurred while unzipping the DA file
Action:
Please check permission.
ODI-14255
Import file has repository version {0} newer than current repository version {1}. This import is not supported.
Category:
Other
Cause:
Import file repository version is greater than current repository version.
Action:
Use supported import file.
ODI-15000
BSF Not Present
Category:
Programmatic
Cause:
Bean Scripting Framework manager cannot be found.
Action:
Ensure that class org.apache.bsf.BSFManager is available in the classpath.
ODI-15001
No End Separator for the following text:
Category:
Programmatic
Cause:
No end delimiter found for a delimited text in the expression.
Action:
Add an end delimiter to the delimited text.
ODI-15002
The string to be transformed cannot be null.
Category:
Programmatic
Cause:
Parsing failed for an expression reference tag.
Action:
Fix the expression.
ODI-15003
Error during Code Interpretor creation
Category:
Programmatic
Cause:
Code generator internal error.
Action:
Contact Oracle support.
ODI-15005
The datatype "{0}" does not exist in technology: {1}.
Category:
Programmatic
Cause:
The datatype for a column is not supported by the technology.
Action:
Change the datatype or the technology of the execution location.
ODI-15006
The source datatype is null for the column: {0}, and the technology: {1}
Category:
Programmatic
Cause:
The datatype for a column is null for the technology.
Action:
Change the datatype or the technology of the execution location.
ODI-15007
Syntax not set for 'Create Table' for the datatype: {0} for the technology: {1}.
Category:
Programmatic
Cause:
The execution location technology does not have any "Create Table" syntax set up.
Action:
Edit the technology definition and add "Create Table" syntax.
ODI-15009
No text for the 'Writable Datatype Syntax' for the datatype: {0} in technology: {1}
Category:
Programmatic
Cause:
The datatype does not have a "Writable Datatype Syntax" property value set up for the execution location technology.
Action:
Edit the datatype in the technology to add a "Writable Datatype Syntax".
ODI-15010
No conversion for the datatype {0}, for the source technology {1} and for the target technology {2}
Category:
Programmatic
Cause:
No conversion is defined for the source technology datatype to the target technology datatype.
Action:
Edit the source or target technology datatype to add a conversion from the source to the target datatype.
ODI-15011
The variable does not exist in the database.
Category:
Programmatic
Cause:
A variable is being referenced but it does not exist in the repository.
Action:
Create the variable in the repository.
ODI-15012
Sequence does not exist in database
Category:
Programmatic
Cause:
A sequence is referenced but does not exist in the repository.
Action:
Create the sequence in the repository.
ODI-15013
The table {0} has fatal errors.
Category:
Programmatic
Cause:
The table cannot be processed.
Action:
Check the table for inconsistencies.
ODI-15014
The referenced text does not exist in the database.
Category:
Programmatic
Cause:
The text reference in the expression does not exist in the repository.
Action:
Repository corruption has occurred, contact Oracle support.
ODI-15015
Too much recursion in this text resolution.
Category:
Programmatic
Cause:
The expression text references other text recursively too many times.
Action:
Review the expression and try to simplify.
ODI-15016
Commands Undefined.
Category:
Programmatic
Cause:
KM is missing a block of lines.
Action:
Check the KM.
ODI-15017
Table not selected (null).
Category:
Programmatic
Cause:
Target table not found.
Action:
Check interface for consistency.
ODI-15018
CKM not selected.
Category:
Programmatic
Cause:
The CKM is not selected for the object.
Action:
Select a CKM.
ODI-15019
Missing context
Category:
Programmatic
Cause:
The context object cannot be found.
Action:
Check the context selection.
ODI-15020
No JKM available
Category:
Programmatic
Cause:
JKM has not been set or is not found.
Action:
Set a valid JKM for the interface.
ODI-15021
Journalizing requires a Primary Key on the Table:
Category:
Programmatic
Cause:
Journalizing is enabled, but the target table has no primary key.
Action:
Add a primary key to the target table.
ODI-15022
No RKM Set.
Category:
Programmatic
Cause:
RKM has not been set or is not found.
Action:
Set a valid RKM for the object.
ODI-15023
Cannot perform standard reverse. Choose customized reverse and set RKM.
Category:
Programmatic
Cause:
Standard reverse engineering is not supported for this object.
Action:
Select customized reverse engineering for the object and select an RKM.
ODI-15025
The interface clause text does not exist.
Category:
Programmatic
Cause:
The interface clause refers to text that does not exist.
Action:
Check interface clauses for (join, filter, etc.) for consistency.
ODI-15026
Interface clauses are missing.
Category:
Programmatic
Cause:
The code generator cannot find the clause collection for the interface.
Action:
Check the interface for consistency.
ODI-15027
Interface source tables are missing.
Category:
Programmatic
Cause:
The code generator cannot find the source table collection for the interface.
Action:
Check the interface for consistency.
ODI-15028
Interface result collection is null.
Category:
Programmatic
Cause:
Interface generation method buildSqlCauses as been called with a null results parameter.
Action:
Ensure that a non null Map is passed for the result parameter.
ODI-15029
Interface error clause collection is missing.
Category:
Programmatic
Cause:
Interface generation method buildSqlCauses as been called with a null error clauses parameter.
Action:
Ensure that a non null collection is passed for the error clauses parameter.
ODI-15030
Interface is missing the integration work table collection.
Category:
Programmatic
Cause:
Interface generation method buildSqlCauses as been called with a null work table collection parameter.
Action:
Ensure that a non null collection is passed for the work table parameter.
ODI-15031
Technology not selected.
Category:
Programmatic
Cause:
No technology is selected for the interface target execution location.
Action:
Check the technology selection for the interface target.
ODI-15032
Unknown object in interface source table collection
Category:
Programmatic
Cause:
Interface generation method buildSqlCauses as been called with a source table collection having a non table item.
Action:
Ensure that only table type items are included in the source table collection.
ODI-15033
The expression: {0} does not have an associated column.
Category:
Programmatic
Cause:
The expression should represent a column, but no column is found for the name.
Action:
Fix the expression.
ODI-15034
A scenario with the same name and the same number already exists. Please select other values.
Category:
Programmatic
Cause:
Cannot create a duplicate scenario with the same name and version number as an existing scenario.
Action:
Give the scenario a different name or version.
ODI-15036
Scenario''s name and/or number are missing.
Category:
Programmatic
Cause:
A scenario must have a name and version, but the name or version is missing.
Action:
Set values for name and version for the scenario.
ODI-15037
The interface {0} has fatal errors.
Category:
Programmatic
Cause:
The interface has fatal errors.
Action:
Check and fix interface issues.
ODI-15038
The scenario name substitution pattern {0} is not supported. Please check the user parameter for the scenario naming convention.
Category:
Programmatic
Cause:
Invalid substitution pattern used for scenario name.
Action:
Change the substitution pattern.
ODI-15039
The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)
Category:
Programmatic
Cause:
Native sequence was used in a sub-select or derived interface.
Action:
Remove the native sequence usage.
ODI-15040
Errors detected when building SQL clauses.
Category:
Programmatic
Cause:
An error occurred when generating code for the SQL clauses.
Action:
Fix the interface clauses.
ODI-15041
An aggregation function may not be used in a join condition. Please use a separate interface for the aggregation and join the result in this interface.
Category:
Programmatic
Cause:
An aggregation function was used inside a join condition expression.
Action:
Change the join condition to remove the aggregation function.
ODI-15042
Unable to regenerate this scenario. It references an package that does not exist.
Category:
Programmatic
Cause:
The scenario must reference a package, but it doesn't.
Action:
Delete the scenario and create a new one.
ODI-15043
Unable to regenerate this scenario from a Runtime repository.
Category:
Programmatic
Cause:
The scenario must cannot be regenerated from the runtime repository.
Action:
Delete the scenario and create a new one.
ODI-15044
Invalid pScenSource type when calling SnpGeneratorSQLCIT.mainGenScenSourceScenario
Category:
Programmatic
Cause:
The scenario generator has been invoked with an invalid scenario source.
Action:
Ensure that only valid scenario source types are used to generate a scenario.
ODI-15045
Invalid value for KM type.
Category:
Programmatic
Cause:
An invalid value was specified for the KM type.
Action:
Specify a valid value.
ODI-15046
The column cache is null during code generation.
Category:
Programmatic
Cause:
The getSnpCol method has been invoked while the SnpColCache member is null;
Action:
Ensure that SnpGeneratorSQLCIT has been properly initialized before invoking getSnpCol.
ODI-15047
The getSnpCol method has been invoked with a null column ID during code generation.
Category:
Programmatic
Cause:
The getSnpCol method has been invoked with a null column ID.
Action:
Ensure that getSnpCol is only called with valid column ID values.
ODI-15050
Flow Control not possible if no key is declared in your target datastore
Category:
Programmatic
Cause:
Flow control is enabled for the interface, but the target datastore has no primary key defined.
Action:
Define a primary key for the target datastore object, and re-add the target datastore.
ODI-15051
Missing mapping instance for interface.
Category:
Programmatic
Cause:
The target column does not have any mapping.
Action:
Add a mapping expression for the target column.
ODI-15052
The interface is missing a dataset.
Category:
Programmatic
Cause:
There is no dataset for the interface source.
Action:
Check the interface for consistency.
ODI-15054
Scenario generation error: Cannot regenerate the scenario. The physical mapping design used to generated the scenario is not found.
Category:
Programmatic
Cause:
The physical mapping design used to generated the scenario is not found.
Action:
Choose to create or replace the scenario.
ODI-15055
Character '']'' missing in: {0}.
Category:
Programmatic
Cause:
A bracketed tag inside a KM line is missing a closing bracket ("]") character.
Action:
Fix the KM line.
ODI-15057
Non-ordered outer join not supported for technology.
Category:
Programmatic
Cause:
Non-ordered outer join syntax disabled for technology.
Action:
Correct join.
ODI-15058
Variable scenario generation error: Logical schema is required.
Category:
Programmatic
Cause:
Variable scenario cannot be generated if logical schema is not set.
Action:
Set the logical schema.
ODI-15059
I_TXT is mandatory.
Category:
Programmatic
Cause:
A call was made to SnpTxtCachedHashMap.getInstance, but the pITxt parameter was null.
Action:
Contact Oracle support.
ODI-15060
The JKM line {0} uses an unsupported execution channel: {1}
Category:
Programmatic
Cause:
A line in the JKM uses an execution channel that is not supported.
Action:
Change the line in the JKM to use a supported channel.
ODI-15061
The JKM line {0} uses an unsupported commit type: {1}
Category:
Programmatic
Cause:
A line in the JKM uses a commit type that is not supported.
Action:
Change the line in the JKM to use a supported commit type.
ODI-15062
Invalid commit type: {0}
Category:
Programmatic
Cause:
An invalid commit type was passed to SnpServiceGenerator.convertCommitType
Action:
Contact Oracle support
ODI-15063
The alternate key {0} is not unique.
Category:
Programmatic
Cause:
An alternate key defined by the repository is found to be non-unique.
Action:
Check the data or the alternate key definitions.
ODI-15064
The primary key {0} is not unique.
Category:
Programmatic
Cause:
A primary key defined by the repository is found to be non-unique.
Action:
Check the data or primary key definitions.
ODI-15065
Join error ({0}) between the table {1} and the table {2}.
Category:
Programmatic
Cause:
A foreign key relationship is not found.
Action:
A foreign key relationship between 2 tables defined in the repository is not valid.
ODI-15066
The column {0} cannot be null.
Category:
Programmatic
Cause:
The column is marked in the repository as not nullable.
Action:
Check the data, or change the not null value.
ODI-15067
The datatype value ''{0}'' is incorrect.
Category:
Programmatic
Cause:
An invalid datatype has been found.
Action:
The repository table contains an invalid datatype.
ODI-15068
Unknown flexfield code {0}.
Category:
Programmatic
Cause:
An undefined flex field code is being referenced
Action:
Check the flex field references in the KM, and the flex field definitions
ODI-15069
{0} Is not valid without session context.
Category:
Programmatic
Cause:
A current session context does not exist.
Action:
Check session definition.
ODI-15070
Unable to find method object: PythonInterpreter.initialize(Properties, Properties, String[]) method
Category:
Other
Cause:
The python method used by the script is not found.
Action:
Check the KM step.
ODI-15071
Error occurred
Category:
Other
Cause:
An exception was thrown while executing a python script in the KM step.
Action:
Check the cause.
ODI-15072
There is no PK constraint
Category:
Programmatic
Cause:
There is a call to "getPK" in the KM, but no PK is found.
Action:
Check the KM and the PK definitions.
ODI-15073
There is no index
Category:
Programmatic
Cause:
There is a call to "getIndex" in the KM, but no index is found.
Action:
Check the KM and the index definitions.
ODI-15076
no dataset
Category:
Programmatic
Cause:
A KM line is calling "getDataSet", but no data set is found.
Action:
Check the KM or the DataSet definitions.
ODI-15077
No Current Model Set
Category:
Programmatic
Cause:
There is a call to "getModel" in the KM, but no model is found.
Action:
Check the KM and the model definitions.
ODI-15078
There is no Not Null column
Category:
Programmatic
Cause:
There is a call to "getNotNullCol" in the KM, but no not null column is found.
Action:
Check the KM and the not null column definitions.
ODI-15079
There is no current Pop.
Category:
Programmatic
Cause:
There is a call to "getPop" in the KM, but no interface is found.
Action:
Check the KM and the interface definitions.
ODI-15080
There is no Step
Category:
Programmatic
Cause:
There is a call to "getStep" in the KM, but no step is found.
Action:
Check the KM and the step definitions.
ODI-15081
There is no Target Table
Category:
Programmatic
Cause:
There is a call to "getTargetTable" in the KM, but no target table is found.
Action:
Check the KM and the interface target table definitions.
ODI-15083
Multiple Primary Keys have been detected for {0} .
Category:
Programmatic
Cause:
A repository table can only have one primary key defined, but multiple primary keys are defined.
Action:
Edit the table's primary key definitions and remove all but one.
ODI-15084
There is no session
Category:
Programmatic
Cause:
There is a call to "getSession" in the KM, but no session is found.
Action:
Check the KM and the session definitions.
ODI-15085
The value : ''({0})'' is unknown.
Category:
Programmatic
Cause:
A KM line has a templated call which contains an unknown bracketed property.
Action:
Fix the KM.
ODI-15086
There is no Temporary Index
Category:
Programmatic
Cause:
There is a call to "getTemporaryIndex" in the KM, but no temporary index is found.
Action:
Check the KM and the temporary index definitions.
ODI-15087
There is no current execution context defined.
Category:
Programmatic
Cause:
There is a call to "getContext" in the KM, but no context is found.
Action:
Check the KM and the context definitions.
ODI-15088
Not in designer mode
Category:
Programmatic
Cause:
A KM line has a call to access design information, but the interpretation location is not set to designer.
Action:
Make sure that the interpretation location is set to designer when this line is executed.
ODI-15089
asked '({0})' and available value are between 0 and ({1}).
Category:
Programmatic
Cause:
A KM line is calling "getDataSet", but the specified index is out of range.
Action:
Fix the KM or the DataSet definitions.
ODI-15090
Table "{0}" not found on model "{1}", schema "{2}"
Category:
Programmatic
Cause:
Attempt to initialize data services from a table that cannot be found
Action:
Change data services reference or make sure that table exists
ODI-15091
Impossible to connect to JPS MBean Server
Category:
Other
Cause:
Cannot connect to JPS MBean server.
Action:
Internal Error.
ODI-15092
Unable to generate data service - the column {0} does not exist in the database.
Category:
Programmatic
Cause:
A data service references a column that does not exist
Action:
Fix the data service reference or make sure that the column exists
ODI-15093
Unable to regenerate this scenario. It references a null package.
Category:
Programmatic
Cause:
The scenario must reference a package, but the package is null.
Action:
Delete the scenario and create a new one.
ODI-15094
You must give a name for the published entity for each datastore.
Category:
Other
Cause:
A web services data store does not have a name.
Action:
Give the data store a name.
ODI-15095
Invalid entity for datastore: {0}
Category:
Other
Cause:
A web services data store has an invalid entity.
Action:
Associate the data store with a valid entity.
ODI-15096
Property name must not be null.
Category:
Programmatic
Cause:
The KM line is calling "isColAttrChanged", but the property value is null.
Action:
Internal error, contact Oracle support.
ODI-15097
Unknown value {0} for property
Category:
Programmatic
Cause:
The KM line is making a templated call, but the property value is unknown.
Action:
Fix the KM.
ODI-15098
You must define a data source for the model.
Category:
Other
Cause:
The model used by a web service does not have any data source.
Action:
Define a data source for the model.
ODI-15099
You must specify a JKM for the model.
Category:
Other
Cause:
The model used by a web service does not have an associated JKM.
Action:
Define a JKM for the model.
ODI-15100
You must define a Java package for the model.
Category:
Other
Cause:
The model used by a web service does not have an associated Java package.
Action:
Define a Java package for the model.
ODI-15101
Invalid Java package format: {0}
Category:
Other
Cause:
The Java package associated with a model has an invalid package format.
Action:
Correct the package format for the model.
ODI-15102
You must specify an XML namespace for the model.
Category:
Other
Cause:
Action:
ODI-15103
Invalid namespace: {0}
Category:
Other
Cause:
A model namespace used by a web service is invalid.
Action:
Correct the namespace for the model.
ODI-15104
You must specify an SKM for the model.
Category:
Other
Cause:
A model used by a web service does not have an associated SKM.
Action:
Add an SKM to the model.
ODI-15105
You must specify which schema the model will be deployed to.
Category:
Other
Cause:
No web service deployment schema is specified for the model.
Action:
Specify a schema to which the model will be deployed.
ODI-15106
You must specify a name for the Data Service for the model.
Category:
Other
Cause:
The data service for the model does not have a name.
Action:
Set a valid name for the data service.
ODI-15107
Invalid model code: {0}. It should follow the Java identifiers naming conventions.
Category:
Other
Cause:
The web service model name does not follow the standard Java identifier naming convention.
Action:
Set a valid name for the model.
ODI-15108
Invalid model Data Service name: {0}. It should follow the Java identifiers naming conventions.
Category:
Other
Cause:
The web service model Data Service name does not follow the standard Java identifier naming convention.
Action:
Set a valid name for the model Data Service.
ODI-15109
Invalid web service name for datastore: {0}
Category:
Other
Cause:
The web service model data store has an invalid name.
Action:
Set a valid name for the model data store.
ODI-15110
SKM is empty
Category:
Other
Cause:
The web service SKM has no valid lines.
Action:
Add some lines to the SKM.
ODI-15111
Problem during deployment
Category:
Deployment
Cause:
Internal error.
Action:
Contact Oracle support.
ODI-15113
Reverse table {0} for model {1} already exists.
Category:
Other
Cause:
An attempt was made to reverse engineer a table, but it already exists in the model.
Action:
Move or rename the data store in the model, or skip reverse engineering for the table.
ODI-15116
There is not enough data in the target file to proceed with the reverse-engineering. Please make sure the file has at least one non-empty line and number of rows to skip is correct.
Category:
Other
Cause:
An attempt was made to reverse engineer a target file that is empty, or the number of skipped rows is larger than the number of rows in the file.
Action:
Set the number of skipped lines to a lower value, or add some data to the file.
ODI-15117
Not allowed (OLD and NEW are involved)
Category:
Programmatic
Cause:
The KM line is calling "getColumn", but the ADH action origin is not ''NEW'' or ''OLD''.
Action:
Change the ADH action origin.
ODI-15118
Invalid FTP URL
Category:
Network
Cause:
The URL given for a web services FTP connection is not correct.
Action:
Check the URL for the FTP connection.
ODI-15119
Column {0} has no Java datatype.
Category:
Programmatic
Cause:
During RDB model validation, no java data type was found for a column.
Action:
Check the model and ensure that a data type has been specified.
ODI-15120
Column {0} has no String datatype.
Category:
Programmatic
Cause:
During RDB model validation, no string data type was found for a column.
Action:
Check the model and ensure that a data type has been specified.
ODI-15121
Selector must be not null
Category:
Programmatic
Cause:
The ADH selector value must not be null when "getColumn" is called from the KM line.
Action:
Change the ADH selector value.
ODI-15122
Exception getPKColList
Category:
Programmatic
Cause:
An exception was found when calling "getPKColList" during KM execution.
Action:
Fix the KM or the PK definitions.
ODI-15123
There is no AK constraint
Category:
Programmatic
Cause:
There is a call to "getAK" in the KM, but no AK is found.
Action:
Check the KM and the AK definitions.
ODI-15124
Unable to regenerate the following scenario:
Category:
Programmatic
Cause:
Cannot regenerate the scenario.
Action:
Delete the scenario and create a new one.
ODI-15125
Missing DataSet.
Category:
Programmatic
Cause:
The interface is missing a dataset.
Action:
Check interface for consistency.
ODI-15126
The sub-model must be set.
Category:
Programmatic
Cause:
The sub-model is not set for the source or target.
Action:
Check the interface for consistency.
ODI-15127
There is no CK constraint
Category:
Programmatic
Cause:
There is a call to "getCK" in the KM, but no CK is found.
Action:
Check the KM and the CK definitions.
ODI-15128
There is no FK constraint
Category:
Programmatic
Cause:
There is a call to "getFK" in the KM, but no FK is found.
Action:
Check the KM and the FK definitions.
ODI-15129
Selector value must be 'OLD' or 'NEW'
Category:
Programmatic
Cause:
The ADH selector value must be 'OLD' or 'NEW' when "getColumn" is called from the KM line.
Action:
Change the ADH selector value.
ODI-15130
Unknown object in interface source table list
Category:
Programmatic
Cause:
An invalid object was found in the SrcTableList member while processing getSrcTablesList.
Action:
Ensure the SrcTableList is only populated with type SnpTable or SnpSourceTab.
ODI-15131
You must define the name of each web service to be generated for each datastore.
Category:
Other
Cause:
A web service associated with a data store has no name.
Action:
Give a name to the web service.
ODI-15132
Exception getPK
Category:
Programmatic
Cause:
An exception was found when calling "getPK" during KM execution.
Action:
Fix the KM or the PK definitions.
ODI-15135
There is no current index.
Category:
Other
Cause:
The current index can not be found for the property name.
Action:
Check the reference.
ODI-15141
Repository is not a development work repository
Category:
Programmatic
Cause:
When getting a connection used to execute the KM, it was determined that the provided connection information does not point to a development work repository
Action:
Fix the connection information
ODI-15142
[PROPERTY: {0} not found.]
Category:
Programmatic
Cause:
The bracketed property in the KM line (e.g. "[COL_NAME]") is not found.
Action:
Fix the KM line to specify a correct property name.
ODI-15143
Invalid isolation level : {0}
Category:
Programmatic
Cause:
An invalid isolation level value was passed to SnpServiceGenerator.convertIsolationLevel
Action:
Contact Oracle support
ODI-15144
KM not encrypted since it is empty.
Category:
Other
Cause:
KM was not encrypted since it is empty.
Action:
Skip encryption.
ODI-15146
Data Type can't be null
Category:
Programmatic
Cause:
null DataType passed.
Action:
Pass non null DataType.
ODI-15147
The changes on this target column will be lost since it is not saved (it has no mapping text)
Category:
Interface Issue
Cause:
Target column will not be saved.
Action:
Enter mapping text if the column requires to be saved.
ODI-15148
The target datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler
Category:
Interface Issue
Cause:
Target datastore is not on Oracle.
Action:
Move target datastore to an Oracle schema.
ODI-15149
The staging area is not on the Oracle Technology: this interface cannot be used with the platform compiler
Category:
Interface Issue
Cause:
Staging Area is not on Oracle.
Action:
Move Staging Area to an Oracle schema.
ODI-15150
The source datastore is not on the Oracle Technology: this interface cannot be used with the platform compiler
Category:
Interface Issue
Cause:
Source DataStore not on Oracle.
Action:
Use only DataStores located on an Oracle technology.
ODI-15151
Non ordered outer joins cannot be used with the platform compiler
Category:
Interface Issue
Cause:
An outer join is not ordered.
Action:
Make the join ordered.
ODI-15152
Unhandled Action {0}
Category:
Programmatic
Cause:
This shouldn't happen. Programmer added an action in the enum and forgot to add it in switch.
Action:
Add action in switch.
ODI-15153
The column is already the first column and cannot be moved up
Category:
Programmatic
Cause:
Column already first and cannot be moved up.
Action:
Do not try to move first column up.
ODI-15154
The column is already the last column and cannot be moved down
Category:
Programmatic
Cause:
Column already last and cannot be moved down.
Action:
Do not try to move last column down.
ODI-15155
Cannot move a target column to a position that is 0 or negative: {0}
Category:
Programmatic
Cause:
Trying to move a column beyond the boundaries of column positions.
Action:
Use a value between 1 and the number of columns.
ODI-15156
Cannot move a target column to a position beyond the size of the column list: {0} is greater than {1}
Category:
Programmatic
Cause:
Trying to move a column beyond the boundaries of column positions.
Action:
Use a value between 1 and the number of columns.
ODI-15157
Cannot remove the only dataset of interface {0}
Category:
Programmatic
Cause:
Trying to remove the last dataset of an interface is not permitted.
Action:
Make sure there are more than one dataset in the interface before deleting it.
ODI-15159
Cannot move target columns on a non temporary DataStore.
Category:
Programmatic
Cause:
Trying to move columns on a non temporary DataStore.
Action:
Make sure that the target DataStore is temporary before attempting to move target columns.
ODI-15160
Native Sequences may not be supported by the target technology after transforming with the Platform Compiler
Category:
Programmatic
Cause:
Using Native Sequence and Platform Compiler Enabled User Param Set
Action:
Make sure that all target technologies will support native sequences
ODI-15162
The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)
Category:
Programmatic
Cause:
Using native sequence in derived sub interface
Action:
Make sure that none sub interface using native sequence
ODI-15200
Tried to retrieve an int with an {0} object
Category:
Programmatic
Cause:
Attempted to read the column from RDB as an integer, but the column type is not integer
Action:
Internal Error: contact Oracle support
ODI-15201
Tried to retrieve a short with an {0} object
Category:
Programmatic
Cause:
Attempted to read the column from RDB as a short type, but the column type is not short
Action:
Internal Error: contact Oracle support
ODI-15202
This resultset accepts only FETCHFORWARD requests
Category:
Programmatic
Cause:
Attempted to set the fetch direction to something other than FETCH_FORWARD for a RDB result set read
Action:
Internal Error: contact Oracle support
ODI-15203
This function is unsupported: the software you are using might not be compatible with this driver.
Category:
Programmatic
Cause:
A jdbc call was made that is not supported by the currently loaded jdbc driver for RDB
Action:
Internal Error: contact Oracle support
ODI-15204
The {0} call is not implemented in this result set class.
Category:
Programmatic
Cause:
A result set call was made that is not implemented by the ODI RDB result set class
Action:
Internal Error: contact Oracle support
ODI-15205
The call is not supported in this result set class.
Category:
Programmatic
Cause:
A result set call was made that is not supported by the ODI RDB result set class
Action:
Internal Error: contact Oracle support
ODI-15206
Unmanaged numeric type {0}
Category:
Programmatic
Cause:
The RDB inserter class was passed a data value of a numeric type that is not handled
Action:
Internal Error: contact Oracle support
ODI-15207
Strange: a PK has multiple lines
Category:
Programmatic
Cause:
When selecting a parent row based on a primary key, multiple rows were returned
Action:
Internal Error: contact Oracle support
ODI-15208
The PK column of the root table has an unknown type: {0}
Category:
Programmatic
Cause:
When unloading data from the RDB, the PK column of the parent table has an unknown type
Action:
Internal Error: contact Oracle support
ODI-15209
Unsupported technology (Driver: {0}, Url: {1})
Category:
Programmatic
Cause:
The jdbc driver is not supported by the ODI RDB
Action:
Internal Error: contact Oracle support
ODI-15210
Unsupported technology: HSQL cannot create FKs after the tables have been created
Category:
Programmatic
Cause:
The Hypersonic SQL engine cannot create FK after the table is already created
Action:
Internal Error: contact Oracle support
ODI-15211
Unsupported technology: HSQL cannot create PKs after the tables have been created
Category:
Programmatic
Cause:
The Hypersonic SQL engine cannot create PK after the table is already created
Action:
Internal Error: contact Oracle support
ODI-15212
Datatype NULL (0) unsupported
Category:
Programmatic
Cause:
The Hypersonic SQL engine does not support the null datatype
Action:
Internal Error: contact Oracle support
ODI-15213
JDBC Datatype '{0}' unsupported
Category:
Programmatic
Cause:
The Hypersonic SQL engine does not support the datatype
Action:
Internal Error: contact Oracle support
ODI-15214
JDBC Datatype '{0}' with length parameter unsupported
Category:
Programmatic
Cause:
The Hypersonic SQL engine does not support the datatype with length
Action:
Internal Error: contact Oracle support
ODI-15215
JDBC Datatype '{0}' with length and scale parameters unsupported
Category:
Programmatic
Cause:
The Hypersonic SQL engine does not support the datatype with scale
Action:
Internal Error: contact Oracle support
ODI-15216
JDBC Datatype '{0}' unsupported
Category:
Programmatic
Cause:
The internal MS Sql Server database does not support the datatype
Action:
Internal Error: contact Oracle support
ODI-15217
JDBC Datatype '{0}' with length parameter unsupported
Category:
Programmatic
Cause:
The internal MS SQL Server database does not support the datatype with length
Action:
Internal Error: contact Oracle support
ODI-15218
JDBC Datatype '{0}' with length and scale parameters unsupported
Category:
Programmatic
Cause:
The internal MS SQL Server database engine does not support the datatype with length and scale
Action:
Internal Error: contact Oracle support
ODI-15219
Please transform your URL into: {0};SelectMethod=cursor
Category:
Programmatic
Cause:
The internal MS SQL Server database engine does not recognize the supplied URL
Action:
Change the format of the connection URL
ODI-15220
need length param
Category:
Programmatic
Cause:
The internal Oracle database does not support the selected type without a length param
Action:
Internal Error: contact Oracle support
ODI-15221
Datatype NULL (0) unsupported
Category:
Programmatic
Cause:
The internal Oracle SQL engine does not support the null datatype
Action:
Internal Error: contact Oracle support
ODI-15222
JDBC Datatype '{0}' unsupported
Category:
Programmatic
Cause:
The internal Oracle database does not support the datatype
Action:
Internal Error: contact Oracle support
ODI-15223
JDBC Datatype '{0}' with length parameter unsupported
Category:
Programmatic
Cause:
The internal Oracle database does not support the datatype with length
Action:
Internal Error: contact Oracle support
ODI-15224
JDBC Datatype '{0}' with length and scale parameters unsupported
Category:
Programmatic
Cause:
The internal Oracle database engine does not support the datatype with length and scale
Action:
Internal Error: contact Oracle support
ODI-15225
No key found on table {0}
Category:
Programmatic
Cause:
The internal database table does not have a key
Action:
Internal Error: contact Oracle support
ODI-15226
The root table {0} has no data
Category:
Programmatic
Cause:
The internal database table does not have any data
Action:
Internal Error: contact Oracle support
ODI-15227
Multiple keys found on table {0}
Category:
Programmatic
Cause:
The internal database table has multiple keys
Action:
Internal Error: contact Oracle support
ODI-15228
*** FATAL *** Table {0} could not be validated
Category:
Programmatic
Cause:
The internal database cannot validate the table
Action:
Internal Error: contact Oracle support
ODI-15229
*** FATAL *** Table {0} could not be found
Category:
Programmatic
Cause:
The internal database cannot find the table
Action:
Internal Error: contact Oracle support
ODI-15230
Could not convert object {0} to a {1}
Category:
Programmatic
Cause:
The internal database cannot convert the datatype of the selected column
Action:
Internal Error: contact Oracle support
ODI-15231
No '=' sign found on line {0} of bundle {1}
Category:
Programmatic
Cause:
The internal database engine encountered a syntax error when reading the property file
Action:
Fix the property file
ODI-15232
The alias {0} for table {1} is already used by another table, when reading bundle {2}
Category:
Programmatic
Cause:
The internal database found a duplicate table alias in a property file
Action:
Fix the property file
ODI-15233
Table {0} is used twice. Make sure that the table names and aliases do not conflict.
Category:
Programmatic
Cause:
The internal database found a duplicate table name in the property bundle
Action:
Fix the property file
ODI-15234
Internal RDB database table {0} not found
Category:
Programmatic
Cause:
The requested table cannot be found in the internal database
Action:
Internal Error: contact Oracle support
ODI-15235
Internal RDB database key {0} not found
Category:
Programmatic
Cause:
The requested key cannot be found in the internal database
Action:
Internal Error: contact Oracle support
ODI-15236
Unknown table {0}
Category:
Programmatic
Cause:
The requested table cannot be found in the internal database
Action:
Correct the model
ODI-15237
Duplicate table
Category:
Programmatic
Cause:
The internal database table is a duplicate table
Action:
Correct the model
ODI-15238
Could not find table although we should have created it!
Category:
Programmatic
Cause:
The newly created table cannot be found
Action:
Internal Error: contact Oracle support
ODI-15239
Only SnpsRDBDiffActionImportDifference are supported for now.
Category:
Programmatic
Cause:
When processing diff actions in a diff operation, an unsupported diff action class was found
Action:
Internal Error: contact Oracle support
ODI-15240
Unknown key {0}
Category:
Programmatic
Cause:
When processing diff actions in a diff operation, a nonexistent key was specified by the diff action
Action:
Internal Error: contact Oracle support
ODI-15241
This type of difference is not managed for now: {0}
Category:
Programmatic
Cause:
When processing diff actions in a diff operation, an unsupported diff action class was found
Action:
Internal Error: contact Oracle support
ODI-15242
Unknown difference type: {0}
Category:
Programmatic
Cause:
When processing diff actions in a diff operation, an unknown diff class was found
Action:
Internal Error: contact Oracle support
ODI-15243
Bad model number: {0}
Category:
Programmatic
Cause:
When processing diff actions in a diff operation, the 2 models that are being compared are internally numbered as model 1 and 2. A model number other than 1 or 2 was used internally in a call to getModel.
Action:
Internal Error: contact Oracle support
ODI-15244
Could not add a key because {0} is not an ID key.
Category:
Programmatic
Cause:
When building a model, the specified key class instance was not an id key
Action:
Internal Error: contact Oracle support
ODI-15245
Unknown key type: {0}
Category:
Programmatic
Cause:
When building a model, an unknown key class was found
Action:
Internal Error: contact Oracle support
ODI-15246
Key {0}.{1} is of unknown type: {2}
Category:
Programmatic
Cause:
When building a model, an unknown key class was found
Action:
Internal Error: contact Oracle support
ODI-15247
The table {0} cannot be found. It is referenced by key: {1}.
Category:
Programmatic
Cause:
When building a model, an table name is referenced by a key, but the table cannot be found
Action:
Check the model
ODI-15248
The column {0} in table {1} cannot be found. It is referenced by key: {2}.
Category:
Programmatic
Cause:
When building a model, an column name is referenced by a key, but the column cannot be found
Action:
Check the model
ODI-15249
An {0} was caught while adding a key which is not an FK. Very strange.
Category:
Programmatic
Cause:
When building a model, an column name is referenced by a key, but the column cannot be found
Action:
Check the model
ODI-15250
The key {0} referenced by table {1} cannot be found.
Category:
Programmatic
Cause:
When building a model, a key name is referenced by a table, but the key cannot be found
Action:
Check the model
ODI-15251
A duplicate key was found: {0}
Category:
Programmatic
Cause:
When dropping a model, a duplicate key was found in the model
Action:
Check the model
ODI-15252
Key already exists: {0}
Category:
Programmatic
Cause:
When updating a model, a duplicate key was found in the model
Action:
Check the model
ODI-15253
Key not found: {0}
Category:
Programmatic
Cause:
When updating a model, the key was not found
Action:
Check the model
ODI-15254
Could not find a constructor with a key name for class {0}
Category:
Programmatic
Cause:
When creating a key class instance, the constructor could not be found
Action:
Internal Error: contact Oracle support
ODI-15255
Could not instantiate an object of class {0}
Category:
Programmatic
Cause:
Could not instantiate the key class
Action:
Internal Error: contact Oracle support
ODI-15256
Could not create an object for class {0} for security reasons
Category:
Programmatic
Cause:
Could not instantiate the key class, due to a security failure
Action:
Check security settings
ODI-15257
Could create an object for class {0} because a {1} occurred saying {2}
Category:
Programmatic
Cause:
Could not instantiate the key class, due to an invocation target exception
Action:
Internal Error: contact Oracle support
ODI-15258
Column {0} not found
Category:
Programmatic
Cause:
The column could not be found
Action:
Internal Error: contact Oracle support
ODI-15259
The key class {0} is not an ID key class.
Category:
Programmatic
Cause:
The specified key class instance was not a SnpsRDBIdKey instance
Action:
Internal Error: contact Oracle support
ODI-15260
Could not add column {0}: Unsupported datatype: {1}
Category:
Programmatic
Cause:
Cannot add the column to the model because the datatype is not supported by the technology
Action:
Correct the model
ODI-15261
Unsupported action: {0}
Category:
Programmatic
Cause:
The action class is not supported by the ODI RDB
Action:
Internal Error: contact Oracle support
ODI-15262
Cannot drop column {0}. It is used in a foreign key!
Category:
Programmatic
Cause:
An attempt was made to drop a column that participates in a foreign key
Action:
Drop the key first, then the column
ODI-15263
Cannot drop column {0}. It is used in a primary key!
Category:
Programmatic
Cause:
An attempt was made to drop a column that participates in a primary key
Action:
Drop the key first, then the column
ODI-15264
Cannot modify this column. It is used in a foreign key!
Category:
Programmatic
Cause:
An attempt was made to modify a column that participates in a foreign key
Action:
Drop the key first, then modify the column
ODI-15265
Cannot modify this column. It is used in a primary key!
Category:
Programmatic
Cause:
An attempt was made to modify a column that participates in a primary key
Action:
Drop the key first, then modify the column
ODI-15268
Table not found: {0}
Category:
Programmatic
Cause:
When attempting to drop a table during an update, the table name is not found
Action:
Check the model
ODI-15270
Key type {0} is not supported here.
Category:
Programmatic
Cause:
The key type is not supported
Action:
Correct the model
ODI-15272
An error occurred while executing a RDB command: {0}
Category:
Programmatic
Cause:
When executing a command action, an exception was thrown
Action:
Check root cause
ODI-15273
{0}: action is not accepted: {1}
Category:
Programmatic
Cause:
Attempt to execute a command action, but it is not accepted
Action:
Check root cause
ODI-15274
Multiple PKs are not allowed on a table
Category:
Programmatic
Cause:
When reverse engineering a primary key, multiple primary keys were found for the table
Action:
Check the model
ODI-15275
An exception ocurred while retrieving a table primary key: {0}
Category:
Programmatic
Cause:
When reverse engineering a table, a primary key could not be retrieved
Action:
Check the model
ODI-15276
An exception occurred while retrieving the indexes of a table: {0}
Category:
Programmatic
Cause:
When reverse engineering a table, the indexes could not be retrieved
Action:
Check the model
ODI-15277
An exception ocurred while retrieving a table foreign keys: {0}
Category:
Programmatic
Cause:
When reverse engineering a table, the foreign keys could not be retrieved
Action:
Check the model
ODI-15278
An exception occurred while retrieving the check constraints of a table: {0}
Category:
Programmatic
Cause:
When reverse engineering a table, the check constraints could not be retrieved
Action:
Check the model
ODI-15279
An exception occurred while retrieving the alternate keys of a table: {0}
Category:
Programmatic
Cause:
When reverse engineering a table, the alternate keys could not be retrieved
Action:
Check the model
ODI-15280
*** FATAL *** Table {0} is duplicate as root
Category:
Programmatic
Cause:
The table is duplicated as the root when determining the root tables of the model
Action:
Check the model
ODI-15281
*** FATAL ** Table {0} is unknown
Category:
Programmatic
Cause:
The root table is unknown
Action:
Check the model
ODI-15282
Table {0} is unknown though it was reversed
Category:
Programmatic
Cause:
The table cannot be found in the ODI model, although it was reversed
Action:
Retry the reverse engineering
ODI-15283
Duplicate declaration for table {0}
Category:
Programmatic
Cause:
The model XML contains a duplicate table declaration
Action:
Fix the XML
ODI-15285
FK {0} references a table with no PK.
Category:
Programmatic
Cause:
The model XML contains a foreign key that references a table with no defined primary key
Action:
Fix the XML
ODI-15286
Unknown PK table for foreign key {0}: please check the name and order of the tables and FK.
Category:
Programmatic
Cause:
The model XML contains a foreign key that references an unknown primary key table
Action:
Fix the XML
ODI-15287
Unknown element: {0}
Category:
Programmatic
Cause:
The model XML contains an unknown element
Action:
Fix the XML
ODI-15288
An {0} error occurred with the following message: {1}
Category:
Programmatic
Cause:
An error occurred when writing the model to a file
Action:
See root cause
ODI-15290
Column {0} was not found in table {1}
Category:
Programmatic
Cause:
The column was not found when building the columns from column names
Action:
Check the model
ODI-15291
*** FATAL *** Could not rename table {0} to {1}
Category:
Programmatic
Cause:
Could not rename table
Action:
Check permissions and security settings
ODI-15292
*** FATAL *** Could not rename table {0} because it was not found in the model!
Category:
Programmatic
Cause:
Could not rename table, because the table to be renamed does not exist
Action:
Check the model
ODI-15293
Unknown FK table for foreign key {0}: please check the name and order of the tables and FK.
Category:
Programmatic
Cause:
The model XML contains a foreign key that references an unknown table
Action:
Fix the XML
ODI-15294
unknown element: {0}
Category:
Programmatic
Cause:
The model XML contains an unknown XML element
Action:
Fix the XML
ODI-15295
Unsupported datatype: {0}
Category:
Programmatic
Cause:
The datatype is unsupported when creating the column from attributes
Action:
Check the model
ODI-15300
A {0} occurred while creating the helper of class {1}. Error message: {2}
Category:
Other
Cause:
INTERNAL ERROR: A helper cannot be created.
Action:
Internal error: contact Oracle support.
ODI-15301
Choose: {0}
Category:
Other
Cause:
Choose one of the displayed options.
Action:
Choose one of the displayed options.
ODI-15302
FK is null: {0}
Category:
Other
Cause:
The FK is null, may indicate repository corruption.
Action:
Internal error: contact Oracle support.
ODI-15303
JDBC Datatype '{0}' with length '{1}' parameter unsupported
Category:
Programmatic
Cause:
MySQL database does not support the datatype with length
Action:
Internal Error: contact Oracle support
ODI-15304
JDBC Datatype '{0}' with length '{1}' and scale '{2}' parameter unsupported
Category:
Programmatic
Cause:
MySQL database does not support the datatype with scale
Action:
Internal Error: contact Oracle support
ODI-15305
JDBC Datatype '{0}' unsupported
Category:
Programmatic
Cause:
MySQL database does not support the datatype
Action:
Internal Error: contact Oracle support
ODI-15306
Column data type "{0}" not supported. Refer documentation for supported types.
Category:
Other
Cause:
Action:
ODI-15307
Metadata format of element with identifier "{0}" is incorrect. Found value "{1}"
Category:
Other
Cause:
Action:
ODI-15308
Error unloading CLOB for column "{0}"
Category:
Other
Cause:
Action:
ODI-15309
Error unloading BLOB for column "{0}"
Category:
Other
Cause:
Action:
ODI-15400
Error in generating data service
Category:
Programmatic
Cause:
Exception thrown when creating the data service used for DDL generation and reverse engineering.
Action:
Check the root cause.
ODI-15401
Unknown key {0}
Category:
Programmatic
Cause:
Unknown key encountered when processing diff class instances during DDL generation.
Action:
Check the model.
ODI-15402
Exception thrown in the DDL generation service: {0}
Category:
Programmatic
Cause:
An exception was thrown while generating DDL.
Action:
Check the root cause.
ODI-15403
The method is not supposed to sort something else than the expected actors. Attempting to sort class instances: {0}, {1}
Category:
Programmatic
Cause:
While sorting action commands, the DDL generator service encountered an unknown class instance type.
Action:
Internal Error: contact Oracle support.
ODI-15404
Scenario generation has not been implemented for this container.
Category:
Programmatic
Cause:
During DDL generation, an attempt was made to generate a scenario for an object that does not support it.
Action:
Internal Error: contact Oracle support.
ODI-15405
Scenario generation exception: {0}
Category:
Programmatic
Cause:
An exception was thrown during scenario generation.
Action:
Check root cause.
ODI-15406
Oozie workflow generation exception: {0}
Category:
Programmatic
Cause:
An exception was thrown during Oozie workflow generation.
Action:
Check root cause.
ODI-15407
Oozie workflow generation exception for Task: {0} - Transactions not supported on Oozie engine with commit mode not set. {1} command Transaction Channel: {2}.
Category:
Programmatic
Cause:
Transactions are not supported on Oozie Engine.
Action:
Please refer to documentation on Oozie Engine Execution.
ODI-15500
Column {0} is executed on the target
Category:
Programmatic
Cause:
Possible Cause
Action:
Suggested Action
ODI-15501
Cannot attach a data store to a target mapping because column {0} is not found.
Category:
Programmatic
Cause:
The specified target column was not found.
Action:
Verify that the correct column has been specified.
ODI-15502
Target mapping not found for column {0}
Category:
Programmatic
Cause:
The specified column is not mapped.
Action:
Map the specified column.
ODI-15503
Cannot set the attached datastore because the mapping is not executed on the SOURCE
Category:
Programmatic
Cause:
The mapping has been configured for execution on the target.
Action:
Configure the mapping for execution on the source.
ODI-15504
Unknown indicator type: {0}
Category:
Programmatic
Cause:
An invalid indicator type has been specified.
Action:
Specify one of the following indicator types from the IndicatorType enumeration: CHECK_NOT_NULL, INSERT, UPDATE, or UPDATE_KEY.
ODI-15505
Invalid UD number: {0}
Category:
Programmatic
Cause:
An invalid UD number has been specified.
Action:
Specify a UD number 1 to 10.
ODI-15506
The specified target column was not found: {0}
Category:
Programmatic
Cause:
The specified target column was not found when attempting to remove a column from a temporary data store.
Action:
Only remove columns which exist in the temporary target datastore.
ODI-15507
Column {0} may not be removed. It is used in other mappings, join clauses, or filter clauses
Category:
Programmatic
Cause:
The specified target column is used in other mappings, filters, or joins. This dependency prevents removal of the column.
Action:
Only remove a column after mapping, filter, or join dependencies have been removed.
ODI-15508
Column {0} may not be removed because it is referenced in interface {1}.
Category:
Programmatic
Cause:
The specified target column is referenced in a filter or join clause in another interface. This dependency prevents removal of the column.
Action:
Only remove a column after other references have been removed.
ODI-15509
The specified target column was not found: {0}
Category:
Programmatic
Cause:
The specified target column was not found.
Action:
Verify the column name.
ODI-15510
A column was not found while updating the key
Category:
Programmatic
Cause:
The update key contains a column that does not exist.
Action:
Check the columns of the update key.
ODI-15511
The join must be attached to the datastore to expand a lookup.
Category:
Programmatic
Cause:
The join is not attached to a datastore, so a valid lookup does not exist.
Action:
Only use the lookup expansion, with a pCreateLookup parameter value of false, on valid lookups.
ODI-15512
Cannot transform a normal datastore into a normal lookup.
Category:
Programmatic
Cause:
The data store is already a non-lookup data store.
Action:
Do not use this transformation on a non-lookup data store. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
ODI-15513
Cannot transform a normal, non-lookup join into a normal join.
Category:
Programmatic
Cause:
The join is already a normal join, not a lookup join, so expansion to a normal, non-lookup join is not possible.
Action:
Do not use this transformation on a normal join. If the datastore and join are non-lookup, use a pCreateLookup parameter value of true to create a lookup from a normal join and normal datastore.
ODI-15514
Cannot transform a lookup datastore into a lookup.
Category:
Programmatic
Cause:
The data store is already designated as a lookup, so transforming to a lookup is not possible.
Action:
Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
ODI-15515
Cannot transform a lookup join into a lookup.
Category:
Programmatic
Cause:
The join is already designated as a lookup, so transforming to a lookup is not possible.
Action:
Do not use this transformation on a lookup. If the datastore and join are designated for lookup, use a pCreateLookup parameter value of false to expand a lookup to a normal join and normal datastore.
ODI-15516
The join must be attached to the datastore to make a lookup.
Category:
Programmatic
Cause:
The join is not properly attached to data sources, so transforming to a lookup is not possible.
Action:
Designate data sources for the join.
ODI-15517
Cannot add a column with the same name as an existing target column: {0}.
Category:
Programmatic
Cause:
The column being added already exists.
Action:
Add a column with a unique name.
ODI-15518
A dataset is already assigned the order: {0}.
Category:
Programmatic
Cause:
Another dataset has already been assigned the order that is being set.
Action:
Assign a unique order to the dataset.
ODI-15519
The target datastore cannot be changed. Interface {0} is used in interface(s) {1} as a source datastore.
Category:
Programmatic
Cause:
The interface is used as a source datastore of another interface, so the target datastore cannot be changed.
Action:
Create a separate interface to avoid the source datastore dependency in the other interface.
ODI-15520
Temporary interface from another project is not allowed.
Category:
Programmatic
Cause:
The interface is used as a source datastore of another interface, so the target datastore cannot be changed.
Action:
Create a separate interface to avoid the source datastore dependency in the other interface.
ODI-15521
A source datastore with alias {0} already exists.
Category:
Programmatic
Cause:
The datastore alias has already been used.
Action:
Specify a unique alias.
ODI-15522
Cannot transform a join into a CrossJoin or natural join if it does not have both attached datastores set.
Category:
Programmatic
Cause:
The join does not have datastores attached yet.
Action:
Attach both join datastores before transforming to a cross join.
ODI-15523
LKM {0} not accepted for source set {1}
Category:
Programmatic
Cause:
The LKM is not compatible with the source set technology or multi-connection setting.
Action:
Select an LKM which matches the source set technology and multi-connection setting.
ODI-15524
LKM {0} not accepted for staging area to target
Category:
Programmatic
Cause:
The LKM is not compatible with the staging area technology or multi-connection setting.
Action:
Select an LKM which matches the staging technology and multi-connection setting.
ODI-15525
CKM {0} not accepted for target technology
Category:
Programmatic
Cause:
The CKM is not compatible with the target technology.
Action:
Select a CKM which matches the target technology.
ODI-15526
IKM {0} not accepted for staging and target technology
Category:
Programmatic
Cause:
The IKM is not compatible with the staging or target technologies or multi-connection setting.
Action:
Select an IKM which matches the staging and target technologies and multi-connection setting.
ODI-15527
IKM {0} not accepted for target technology
Category:
Programmatic
Cause:
The IKM is not compatible with the target technology or multi-connection setting.
Action:
Select an IKM which matches the target technology and multi-connection setting.
ODI-15528
Mapping expression cannot be set because the target column {0} was not found.
Category:
Programmatic
Cause:
The column was not found when setting the expression for a mapping.
Action:
Specify a valid column for the expression.
ODI-15529
Action was not reversible.
Category:
Programmatic
Cause:
The actions causing an impact are not reversible.
Action:
Avoid the sequence of actions causing the impact.
ODI-15530
The interface does not have a source set.
Category:
Programmatic
Cause:
The interface does not have a source set.
Action:
Add a source set to the interface.
ODI-15531
The execution location parameter for the computeExpression method is invalid.
Category:
Programmatic
Cause:
The execution location parameter for the computeExpression method is invalid.
Action:
Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
ODI-15532
The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.
Category:
Programmatic
Cause:
The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.
Action:
Specify an execution location parameter of ExecutionLocation.SOURCE, ExecutionLocation.WORK, or ExecutionLocation.TARGET.
ODI-15533
The physical schema could not be mapped from logical schema {0} and context {1}.
Category:
Programmatic
Cause:
The getPhysicalSchema method failed to map and logical schema and context to a physical schema.
Action:
Ensure that logical to physical schema mappings are created or check the logical schema and context parameters.
ODI-15534
Sub interface must not be null.
Category:
Programmatic
Cause:
The pSubInterface parameter passed to the checkSubInterfaceValid method is null.
Action:
A non-null sub interface parameter is required for the checkSubInterfaceValid method.
ODI-15535
The technology {0} of the source temporary interface {1} used as a derived table does not support derived tables.
Category:
Programmatic
Cause:
The pSubInterface parameter passed to the checkSubInterfaceValid method is null.
Action:
A non-null sub interface parameter is required for the checkSubInterfaceValid method.
ODI-15536
Source temporary interface {0} cannot be used as a derived table. Its source datastore {1} defined in logical schema {2} has no associated physical schema in the optimization context {3}.
Category:
Programmatic
Cause:
The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the source.
Action:
Create a mapping between the logical schema, context, and physical schema for the source data store.
ODI-15537
Source temporary interface {0} cannot be used as a derived table. The logical schema of the target datastore {1} has no associated physical schema in context {2}.
Category:
Programmatic
Cause:
The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the target.
Action:
Create a mapping between the logical schema, context, and physical schema for the target data store.
ODI-15538
Source temporary interface {0} cannot be used as a derived table. The logical schema of the staging area {1} has no associated physical schema in the optimization context {2}.
Category:
Programmatic
Cause:
The temporary interface cannot be used because a physical schema has not been mapped to the logical schema for the staging area.
Action:
Create a mapping between the logical schema, context, and physical schema.
ODI-15539
Source temporary interface {0} cannot be used as a derived table. Source datastore {1} is not on the same data server as the target.
Category:
Programmatic
Cause:
The temporary interface cannot be used because the source data store is not on the same data server as the target.
Action:
Ensure that the source and target datastores are on the same data server.
ODI-15540
Source temporary interface {0} cannot be used as a derived table. Staging area and target datastores are not in the same data server. You may have forced the target context to a different context than the optimization context.
Category:
Programmatic
Cause:
The temporary interface cannot be used because the staging data store is not on the same data server as the target.
Action:
Ensure that the staging and target datastores are on the same data server.
ODI-15541
Source temporary interface {0} uses a journalized datastore and cannot be used as a derived table.
Category:
Programmatic
Cause:
The temporary interface cannot be used because it uses a journalized datastore.
Action:
Use only non journalized data stores in temporary interfaces.
ODI-15542
Source temporary interface {0} cannot be used as a derived table. All source datastores of this interface should be in the same data server as the target and should not be journalized.
Category:
Programmatic
Cause:
The temporary interface cannot be used because it uses a journalized datastore.
Action:
Use only non journalized data stores in temporary interfaces.
ODI-15543
Another interface with the same name already exists in this folder. Please choose a unique interface name.
Category:
Programmatic
Cause:
Another interface with the same name already exists in this folder.
Action:
Specify a unique interface name.
ODI-15544
The interface must have a name.
Category:
Programmatic
Cause:
The interface does not have a name.
Action:
Specify a unique interface name.
ODI-15545
Temporary target datastore has no name.
Category:
Programmatic
Cause:
The temporary target datastore has no name
Action:
Specify a unique datastore name.
ODI-15546
The interface must have a logical schema.
Category:
Programmatic
Cause:
The interface does not have a logical schema.
Action:
Specify a logical schema for the interface.
ODI-15547
Could not fix a missing reference correctly.
Category:
Programmatic
Cause:
The interface is missing one or more references.
Action:
Recheck target expressions for proper source references.
ODI-15548
The source datastore has already been set.
Category:
Programmatic
Cause:
The source datastore has already been set.
Action:
Only invoke setSourceDataStore once.
ODI-15549
Cannot set the source filter because the source datastore is not set.
Category:
Programmatic
Cause:
The source datastore has not been set prior to setting the filter.
Action:
Set the source datastore prior to setting the filter.
ODI-15550
The target datastore has already been set.
Category:
Programmatic
Cause:
The source datastore has already been set.
Action:
Only invoke setSourceDataStore once.
ODI-15552
A source filter requires a source datastore.
Category:
Programmatic
Cause:
The interface cannot be saved because it contains a filter without a source datastore.
Action:
Create a source datastore before creating a source filter.
ODI-15553
The target datastore must be set.
Category:
Programmatic
Cause:
The target datastore for the interface has not been set.
Action:
Set the target datastore before saving the interface.
ODI-15554
An LKM must be set on the source set.
Category:
Programmatic
Cause:
A loading knowledge module has not been assigned to the source set.
Action:
Set the LKM for the source set before saving the interface.
ODI-15555
Target IKM must be set on the target table.
Category:
Programmatic
Cause:
An integration knowledge module has not been assigned to the target table.
Action:
Set the IKM for the target before saving the interface.
ODI-15556
Unknown generic clause type: {0}
Category:
Programmatic
Cause:
An unknown generic clause class was passed to the createSnpPopClauseFromGenericClause method.
Action:
Pass only generic clause classes for join or filter.
ODI-15557
Unknown execution location type: {0}
Category:
Programmatic
Cause:
An unknown execution location enumeration was passed to the getStringExeDbFromExecutionLocation method.
Action:
Pass only location enumerations of ExecutionLocation.SOURCE, ExecutionLocation.WORK, ExecutionLocation.TARGET.
ODI-15558
There is a conflict between physical schemas
Category:
Programmatic
Cause:
There is a conflict between the various physical schemas used to obtain the data, such as multiple data stores in the same source set connected using different physical schemas.
Action:
Ensure that physical schemas of a source set have consistent connection information.
ODI-15559
Unsupported component: {0}
Category:
Programmatic
Cause:
An unsupported component was passed as a parameter to createDataAccessinfo.
Action:
For the pInterfaceSubComponents parameter, supported components are SourceDataStore, ISourceColumn, TargetMapping, and GenericClause.
ODI-15560
Fatal interface condition: {0}
Category:
Programmatic
Cause:
A fatal issue was discovered while saving or verifying an interface.
Action:
Correct the interface issue before saving it.
ODI-15561
Could not find column {0} which choosing a mapping.
Category:
Programmatic
Cause:
The MappingChooserFirst.chooseMapping method was called with an column name that does not exist.
Action:
Check the column name passed to chooseMapping.
ODI-15562
Source sets cannot be computed because one execution area doesn't have a physical schema. Check the errors on the interface.
Category:
Programmatic
Cause:
Source sets cannot be computed because one execution area doesn't have a physical schema.
Action:
Check the errors on the interface.
ODI-15563
Source sets cannot be computed because the staging area is not properly defined. Check your target datastore and the staging area's physical schema in the Definition tab.
Category:
Programmatic
Cause:
Source sets cannot be computed because the staging area is not properly defined.
Action:
Check your target datastore and the staging area's physical schema in the Definition tab.
ODI-15564
There should be one source set on the interface.
Category:
Programmatic
Cause:
The interface has more than one source set.
Action:
Ensure that only one source set is defined.
ODI-15565
Column {0} not found while setting the update key.
Category:
Programmatic
Cause:
A column specified for the update key does not exist.
Action:
Recheck the column names used to define the update key.
ODI-15566
No target column was found while setting the target data store.
Category:
Programmatic
Cause:
No target column was found while setting the target data store.
Action:
Define columns before setting the target datastore.
ODI-15567
Target column {0} was not found.
Category:
Programmatic
Cause:
No specified target column was not found in the target data store.
Action:
Check the column name parameter in the RealBasicInterfaceCreationHelper.getTargetColumn method call.
ODI-15568
Column {0} not found on datastore {1}.
Category:
Programmatic
Cause:
A referenced column was not found in a source data store.
Action:
Check the source datastore columns and references for a mismatch.
ODI-15570
Cannot add a datastore of type {0} as source.
Category:
Programmatic
Cause:
An invalid datastore type has been specified.
Action:
Specify a datastore of type TargetDataStore, SourceDataStore, or OdiDataStore.
ODI-15571
Unexpected join type {0}
Category:
Programmatic
Cause:
An invalid join type has been specified when setting join properties.
Action:
Specify a join type of INNER, CROSS, or NATURAL.
ODI-15572
Unexpected join state.
Category:
Programmatic
Cause:
An invalid join state has been reached. The expected join type is CROSS or NATURAL.
Action:
Review the error details for further information.v
ODI-15573
Failed to create an interface helper instance.
Category:
Programmatic
Cause:
A general exception was encountered while constructing an interface helper.
Action:
This is an internal error with no recommended user action.
ODI-15574
General exception encountered in the interface helper while preparing to persist.
Category:
Programmatic
Cause:
General exception encountered in the interface helper while preparing to persist.
Action:
This is an internal error with no recommended user action.
ODI-15575
Two journalized datastores have been found. There should be only one.
Category:
Programmatic
Cause:
Two journalized datastores have been found. There should be only one.
Action:
Remove jounalizing from one or more datastores.
ODI-15576
Two journalized filters have been found. There should be only one.
Category:
Programmatic
Cause:
Two journalized filters have been found. There should be only one.
Action:
Remove jounalizing from one or more datastores.
ODI-15577
Unmanaged type: {0}
Category:
Programmatic
Cause:
An invalid element type was passed to the prepareSQLStatement method.
Action:
Pass only valid element types such as GenericClause, SourceDataStore, TargetDataStore, ISourceColumn, TargetMapping, SourceSet, DataSet, or TargetColumn.
ODI-15578
No interface was found in the elements.
Category:
Programmatic
Cause:
No interface could be traced to the elements passed to the prepareSQLStatement method.
Action:
Create an interface.
ODI-15579
No dataset was found in the elements.
Category:
Programmatic
Cause:
No data set could be traced to the elements passed to the prepareSQLStatement method.
Action:
Ensure that a dataset has been created first.
ODI-15580
The target is a temporary table.
Category:
Programmatic
Cause:
The target datastore is a temporary target.
Action:
Use a non-temporary target.
ODI-15581
Cannot build the query because the ordered joins are not correct.
Category:
Programmatic
Cause:
The SQL clause cannot be generated because the ordered joins are not correct.
Action:
Ensure that all joins are correct.
ODI-15582
This operation is not supported on joined file datastores.
Category:
Programmatic
Cause:
Multiple source datastores were found.
Action:
Use only a single source datastore.
ODI-15583
This operation is not supported on multiple file datastores.
Category:
Programmatic
Cause:
More than one source datastore was found.
Action:
Use only a single source datastore.
ODI-15584
Elements are from different interfaces.
Category:
Programmatic
Cause:
The components passed to prepareSQLStatement are from different interfaces.
Action:
Only pass components from the same interface when preparing an SQL statement.
ODI-15585
Elements are from different datasets.
Category:
Programmatic
Cause:
The components passed to prepareSQLStatement are from different data sets.
Action:
Only pass components from the same data set when preparing an SQL statement.
ODI-15586
Unsupported component: {0}
Category:
Programmatic
Cause:
An invalid component type was passed to connectionForData.
Action:
Only pass components of type SourceDataStore, ISourceColumn, TargetMapping, TargetColumn, GenericClause, or TargetDataStore.
ODI-15587
Journalization filter not found for the journalized table.
Category:
Programmatic
Cause:
The journalized table does not have a filter.
Action:
Define a journalizing filter for the table.
ODI-15588
The SQL join clause is not valid for a cross join.
Category:
Programmatic
Cause:
A join clause has been specified for a cross join.
Action:
Remove the join condition or change the join type.
ODI-15589
Cannot change the ON_TARGET indicator on a temporary interface.
Category:
Programmatic
Cause:
An attempt was made to set the ON_TARGET indicator for a temporary datastore.
Action:
Do not change the ON_TARGET indicator for a temporary datastore.
ODI-15590
Unknown indicator type: {0}
Category:
Programmatic
Cause:
An unknown value was passed to the constructor for InterfaceActionOnStagingAreaSetIndicator.
Action:
Use valid values of DISTINCT_ROW, ON_TARGET, or ON_USER_DATABASE_SCHEMA for the pIndicatorType parameter.
ODI-15591
Staging Area is on the target and cannot be switched to another logical schema.
Category:
Programmatic
Cause:
The staging area is on the target and uses the target schema. It cannot be switched.
Action:
Do not attempt to switch the schema, or use a separate staging area.
ODI-15592
GenericClause is of unknown type: {0}
Category:
Programmatic
Cause:
InterfaceActionRemoveGenericClause was constructed with an invalid generic clause.
Action:
Use a generic clause type of JOIN or FILTER.
ODI-15593
Could not set LKM for object of type {0}
Category:
Programmatic
Cause:
An LKM is being set for a TargetDataStore or some other invalid type.
Action:
Only set an LKM for a SourceSet or StagingArea.
ODI-15594
Could not set the CKM for a holder of type {0}
Category:
Programmatic
Cause:
A CKM is being set for a SourceSet, StagingArea, or some other invalid type.
Action:
Only set a CKM for a TargetDataStore.
ODI-15595
Could not set the IKM for a holder of type {0}
Category:
Programmatic
Cause:
An IKM is being set for a SourceSet, StagingArea, or some other invalid type.
Action:
Only set an IKM for a TargetDataStore.
ODI-15596
Invalid KM type: {0}
Category:
Programmatic
Cause:
An invalid object type is being used to set a KM.
Action:
Only set a KM of type LKM, CKM, or IKM.
ODI-15597
Could not set the LKM option for a holder of type {0}
Category:
Programmatic
Cause:
An LKM is being set for a TargetDataStore or some other invalid type.
Action:
Only set an LKM option for a SourceSet or StagingArea.
ODI-15598
Could not set the CKM option for a holder of type {0}
Category:
Programmatic
Cause:
A CKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.
Action:
Only set a CKM option for a KM holder of type TagetDataStore.
ODI-15599
Could not set the IKM option for a holder of type {0}
Category:
Programmatic
Cause:
An IKM option is being set for a SourceSet, StagingArea, or some other invalid KM holder type.
Action:
Only set an IKM option for a KM holder of type TagetDataStore.
ODI-15600
Dataset 1 was not found in the list of the interface datasets used with the interface.
Category:
Programmatic
Cause:
The first dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.
Action:
Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
ODI-15601
Dataset 2 was not found in the list of the datasets used with the interface.
Category:
Programmatic
Cause:
The second dataset given as a parameter in the construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.
Action:
Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
ODI-15602
An unimplemented method has been called.
Category:
Programmatic
Cause:
An unimplemented method has been called.
Action:
Review the error details for information on the specific method call. Implement the method or call an alternative method.
ODI-15603
Cannot create an alias for a datastore of type {0}
Category:
Programmatic
Cause:
The method computeAliasForDataStore was called with an invalid datastore type.
Action:
Only call computeAliasForDataStore for datastores of type TargetDataStore or OdiDataStore.
ODI-15604
A non ordered clause was passed to the buildTreeSet method.
Category:
Programmatic
Cause:
A non ordered clause is passed to the construction of ordered joins trees method.
Action:
Use ordered join clauses with this method.
ODI-15605
Multiple ordered joins in this dataset use the same order number.
Category:
Programmatic
Cause:
One or more join clauses uses the same order number in the call to buildTreeSet.
Action:
Ensure that all clauses of an ordered join have unique order numbers.
ODI-15606
Join references the same table twice (directly or indirectly).
Category:
Programmatic
Cause:
A join clause contains two references to the same table.
Action:
Ensure that the join clause only references one table.
ODI-15607
Join references the same table twice through other joins.
Category:
Programmatic
Cause:
A join clause contains two references to the same table.
Action:
Ensure that the join clause only references one table.
ODI-15608
Subcomponent type of {0} is not supported.
Category:
Programmatic
Cause:
An unsupported type was passed to getIssuesComputer.
Action:
Only pass types of OdiInterface, DataSet, SourceDataStore, Filter, Join, StagingArea, TargetDataStore, SourceSet, TargetMapping, or TargetColumn.
ODI-15609
Invalid KM holder type: {0}
Category:
Programmatic
Cause:
An invalid KM holder type was passed to InterfaceKMHolderFactory.getKMHolderFor
Action:
Only pass KM holder types of SOURCE_SET_LKM, STAGING_AREA_LKM, TARGET_CKM, or TARGET_IKM.
ODI-15610
Component must be a source datastore or a source column.
Category:
Programmatic
Cause:
ReferenceManagerAbstract.getReferencesTo was called with an invalid subcomponent.
Action:
Only pass subcomponent types of SourceDataStore or ISourceColumn.
ODI-15611
Column not found from an xref.
Category:
Programmatic
Cause:
A column referenced in an expression was not found in a datastore. It may have been deleted.
Action:
Ensure that all columns referenced in the expression exist.
ODI-15612
Failed to attach an element of type {0} to a source set.
Category:
Programmatic
Cause:
An invalid type of component was found when attaching elements to a source set.
Action:
Elements being attached to a source set must be of type SourceDataStore, Join, Filter, or TargetMapping.
ODI-15613
Interface must have only one dataset.
Category:
Programmatic
Cause:
This sourceset computer can only handle a single dataset, and more than one was found.
Action:
Ensure that the interface uses only one dataset.
ODI-15614
Interface must have only one source table.
Category:
Programmatic
Cause:
This sourceset computer can only handle a single table, and more than one datastore was found.
Action:
Ensure that multiple tables are contained in a sourceset.
ODI-15615
Interface must not have joins.
Category:
Programmatic
Cause:
This sourceset computer can only handle a single table, and the interface contains a join.
Action:
Ensure that joins are contained in a sourceset.
ODI-15616
Source datastore must be a real table
Category:
Programmatic
Cause:
This sourceset computer can only handle a single, real table.
Action:
Ensure that only a single, real table is used in the sourceset.
ODI-15617
Invalid type for a TextHolder: {0}
Category:
Programmatic
Cause:
The method getExecutableTextHolderFor was called with an invalid TextHolder component type.
Action:
Valid types are TargetMapping, TargetColumn, Filter, and Join.
ODI-15618
Cannot set a source set on a target column.
Category:
Programmatic
Cause:
SetSourceSet was called for a target column, which is not a valid usage. This method is specified for the interface, but is not valid for this class.
Action:
SetSourceSet should never be invoked for this class.
ODI-15619
Inconsistent filter with a clauseType of {0}
Category:
Programmatic
Cause:
The Filter.getFilterType method was called, but the clause type was not a filter type.
Action:
Ensure that the filter has a type of SnpPopClause.CLAUSE_TYPE_FILTER or SnpPopClause.CLAUSE_TYPE_JRN_FILTER.
ODI-15620
Execution location is null. Target technology cannot be determined
Category:
Programmatic
Cause:
The execution filter for the location was not set.
Action:
The execution location should be set in the Filter constructor or by invoking setExecutionLocation.
ODI-15621
Attached dataStore is null. Target technology cannot be determined
Category:
Programmatic
Cause:
The attached datastore for the execution location was not set.
Action:
The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
ODI-15622
Staging area does not have a logical schema. Target technology cannot be determined
Category:
Programmatic
Cause:
The attached datastore for the execution location was not set.
Action:
The datastore should be set in the Filter constructor or by invoking setAttachedDataStore.
ODI-15623
Invalid technology for the given index type
Category:
Programmatic
Cause:
The technology of the clause and index type do not match.
Action:
Ensure that the index type technology matches the clause technology.
ODI-15624
Inconsistent join with clauseType = {0} and joinType = {1}
Category:
Programmatic
Cause:
The join clause type is invalid.
Action:
This exception is thrown from a deprecated method. Use isCross or isOrdered methods instead.
ODI-15625
Cannot set OdiDataType on a journalized source column
Category:
Programmatic
Cause:
The setDataType method has been invoked for a journalized source column, but the datatype cannot be set for journalized columns.
Action:
Do not invoke this method for a journalized column.
ODI-15626
Cannot set the length on a journalized source column
Category:
Programmatic
Cause:
The setLength method has been invoked for a journalized source column, but the length cannot be set for journalized columns.
Action:
Do not invoke this method for a journalized column.
ODI-15627
Cannot set the scale on a journalized source column
Category:
Programmatic
Cause:
The setScale method has been invoked for a journalized source column, but the scale cannot be set for journalized columns.
Action:
Do not invoke this method for a journalized column.
ODI-15628
Cannot set the data type on a source column
Category:
Programmatic
Cause:
The setDataType method has been invoked for a source column, but the datatype cannot be set for source columns.
Action:
Do not invoke this method for a source column.
ODI-15629
Cannot set the length on a source column
Category:
Programmatic
Cause:
The setLength method has been invoked for a source column, but the length cannot be set for source columns.
Action:
Do not invoke this method for a source column.
ODI-15630
Cannot set the scale on a source column
Category:
Programmatic
Cause:
The setScale method has been invoked for a source column, but the scale cannot be set for source columns.
Action:
Do not invoke this method for a source column.
ODI-15631
Connection information is not available.
Category:
Programmatic
Cause:
The physical schema has not been set.
Action:
Define physical and logical schemas.
ODI-15632
Column {0} may not be removed because it is mapped in interface {1}.
Category:
Programmatic
Cause:
The specified target column is mapped in another interface. This dependency prevents removal of the column.
Action:
Only remove a column after mapping dependencies have been removed.
ODI-15633
Data Type must be set first.
Category:
Programmatic
Cause:
Data Type is null.
Action:
Set Data Type.
ODI-15634
Length is not allowed for the current Data Type
Category:
Programmatic
Cause:
Data Type doesn't support length.
Action:
Check Data Type.
ODI-15635
Scale is not allowed for the current Data Type.
Category:
Programmatic
Cause:
Data Type doesn't support scale.
Action:
Check Data Type.
ODI-15636
Cannot change the column because it's not a temporary column.
Category:
Programmatic
Cause:
Column isn't temporary.
Action:
Check column state.
ODI-15637
Execution location must be either null or target.
Category:
Programmatic
Cause:
Wrong Execution location state.
Action:
Check Execution location.
ODI-15638
Scenario {0} contains invalid characters. Try {1}.
Category:
Other
Cause:
String contains invalid characters.
Action:
Check scenario name.
ODI-15639
Scenario version is not set.
Category:
Programmatic
Cause:
Scenario version is not set.
Action:
Set scenation version.
ODI-15640
No Scenario was found through the Tag : {0}.
Category:
Other
Cause:
No Scenario was found.
Action:
Check tag.
ODI-15641
The refresh SQL statement of a variable cannot contain sequence references when the variable is added to a load plan.
Category:
Programmatic
Cause:
SQL statement contains sequence references.
Action:
Check refresh SQL statement.
ODI-15642
Scenario name must be {0} characters long max.
Category:
Other
Cause:
Scenario name is too long.
Action:
Check name length.
ODI-15643
No Physical Mapping Design from Mapping: {0}.
Category:
Other
Cause:
Cannot find any Physical Mapping Design from Mapping.
Action:
Check there is valid Physical Mapping Design.
ODI-15644
The physical data server for the source code and for sequqnce(s) {0} is not the same, this may result in the same sequence value being used for each row.
Category:
Other
Cause:
The sequence may be remote so a single nextval is calculated and reused per row.
Action:
Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
ODI-15645
The physical data server for the target code and for sequence(s) {0} is not the same, this may result in the same sequence value being used for each row.
Category:
Other
Cause:
The sequence may be remote so a single nextval is calculated and reused per row.
Action:
Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
ODI-15700
Exception thrown in the Odi shortcut service: {0}
Category:
Programmatic
Cause:
An exception was thrown while materializing a shortcut object.
Action:
Check the root cause.
ODI-16000
Dataset has no sources: {0}
Category:
Programmatic
Cause:
The Dataset has no source or the source is not available.
Action:
Check sources.
ODI-16001
Dataset {0} contains only one source.
Category:
Programmatic
Cause:
The Dataset has only one source.
Action:
Check sources.
ODI-16002
Dataset has added default join condition with cartesian product: {0}
Category:
Programmatic
Cause:
Dataset has added default join condition with cartesian product.
Action:
ODI-16003
Multiple joins in the same dataset have the same order number: {0}
Category:
Programmatic
Cause:
Multiple joins in the same dataset have the same order number.
Action:
Check the order numbers of join components in the dataset.
ODI-16004
ANSI join: {0} has no user-defined order. The default order -1 (meaning "random order") is assigned.
Category:
Programmatic
Cause:
An ANSI join component does not have a join order assigned to it.
Action:
Assign an order number that is not -1.
ODI-16005
Join component inside dataset has no valid source references in the join condition. Join: {0} , condition = {1}.
Category:
Programmatic
Cause:
Join component inside dataset has no valid source references in the join condition.
Action:
Check source references in the join condition.
ODI-16006
Join component inside dataset has only one source references in the join condition, must have at least 2 references. Join: {0}, condition = {1}
Category:
Programmatic
Cause:
Join component inside dataset has only one source references in the join condition, must have at least 2 references.
Action:
Check join condition.
ODI-16008
There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.
Category:
Programmatic
Cause:
There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.
Action:
Check both the join condition references and the user order numbers.
ODI-16009
Lookup component creation is not complete: it misses either driving and/or lookup source information.
Category:
Programmatic
Cause:
Lookup component: {0} in dataset: {1} is incomplete. (Driving source: {2}, lookup source: {3})
Action:
Set the missing driving and/or lookup source on the lookup component.
ODI-16010
Dataset has sources that are not referenced by any join condition. Dataset: {0} , unconnected sources: {1}.
Category:
Programmatic
Cause:
Dataset has sources that are not referenced by any join condition.
Action:
Check sources.
ODI-16011
INTERNAL ERROR: Dataset error when connecting joins in order. Cannot find source for join: {0}, referenced source name: {1}.
Category:
Programmatic
Cause:
Dataset error when connecting joins in order. Cannot find source for join.
Action:
Check sources.
ODI-16012
Cannot find ordered join connection in dataset for: {0}
Category:
Programmatic
Cause:
Cannot find ordered join connection in dataset.
Action:
Check ordered join connection.
ODI-16013
Cannot find a valid pairwise tree of join connections for dataset: {0} unconnected join: {1} ({2})
Category:
Programmatic
Cause:
Cannot find a valid pairwise tree of join connections for dataset.
Action:
Check join connections.
ODI-16014
Cannot find a valid pairwise tree of join connections for dataset: {0}
Category:
Programmatic
Cause:
Cannot find a valid pairwise tree of join connections for dataset.
Action:
Check join connections.
ODI-16015
Missing expression for aggregate component {0}, attribute: {1}
Category:
Programmatic
Cause:
Missing expression for aggregator attribute.
Action:
Check aggregator attribute.
ODI-16016
Could not find an output signature for point: {0}
Category:
Programmatic
Cause:
Could not find an output signature for point.
Action:
Check output signature for the connection point.
ODI-16017
The join component: {0} has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.
Category:
Programmatic
Cause:
The join component has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.
Action:
Check the join component.
ODI-16018
The join condition for component: {0} only references {1} sources, but there are {2} input connector points. Expression text: {3}
Category:
Programmatic
Cause:
The number of references sources is less than the number of input connector points.
Action:
Check the join condition and input connector points.
ODI-16019
Set component output attribute {0} contains {1} expressions, but there are only {2} input connector points.
Category:
Programmatic
Cause:
The number of input expressions is greater than the number of input connector points.
Action:
Check expressions and input connector points.
ODI-16020
Set component output attribute expression for attribute: {0} does not have a scoping input connector point specified. Set component input expressions must have an associated scoping input connector point.
Category:
Programmatic
Cause:
A scoping input connector point need to be specified.
Action:
Check If set component input expressions have an associated scoping input connector point.
ODI-16021
The immediate downstream node {0} of the AP node {1}, which uses a push style LKM, is not a target.
Category:
Programmatic
Cause:
A push style LKM is assigned to an AP node but its immediate downstream node is not a target.
Action:
Either change the LKM to a pull style LKM or move some physical nodes to source execution unit(s).
ODI-16022
Set component output attribute: {0} does not have an expression that references through input: {1}.
Category:
Programmatic
Cause:
Not all input connector points have been referenced by one expression.
Action:
Check input connector points and expressions.
ODI-16023
Expression cross reference object is null: {0}.
Category:
Programmatic
Cause:
Expression cross reference object is null.
Action:
Check expression cross reference object.
ODI-16024
The expression contains unresolved attribute references. {0} Expression: {1} Unresolved identifiers: {2}.
Category:
Programmatic
Cause:
The expression contains identifiers that were not resolved as attribute references.
Action:
Check all identifiers in the expression for accessibility through a valid input connector point.
ODI-16025
An access point (AP) node has been created in the physical graph, but it does not have any columns: {0}.
Category:
Programmatic
Cause:
ERROR: An access point (AP) node has been created in the physical graph, but it does not have any columns.
Action:
Check access points.
ODI-16026
Cannot move an existing physical node to a different physical design! Node: {0}.
Category:
Programmatic
Cause:
Cannot move an existing physical node to a different physical design! .
Action:
The action attempted is not supported.
ODI-16027
No path exists from physical node: {0} to: {1}.
Category:
Programmatic
Cause:
No path exists between physical nodes.
Action:
Check paths between physical nodes.
ODI-16028
Expression push is not allowed because it would push the expression through projector node: {0}.
Category:
Programmatic
Cause:
Expression push is not allowed because it would push the expression through projector node.
Action:
The action attempted is not supported.
ODI-16029
Expression {0} ({1}) owned by: {2} has blank value, but a non-blank value is required.
Category:
Programmatic
Cause:
Expression has blank value, but a non-blank value is required.
Action:
Check the expression text.
ODI-16030
An attribute expression must reference only one projector or joiner source. Attribute: {0}.
Category:
Programmatic
Cause:
An attribute expression must reference only one projector or joiner source.
Action:
Check attribute expressions.
ODI-16031
The lookup component must have a driver and a lookup source input connection.
Category:
Programmatic
Cause:
The lookup component is not properly connected, it must have 2 input connections.
Action:
Connect the lookup component.
ODI-16032
Unsupported component type: {0}: component: {1} in dataset: {2}.
Category:
Programmatic
Cause:
The dataset does not support the component type.
Action:
Remove the component from the dataset.
ODI-16033
Aggregate filter: {0} is not supported in dataset: {1}.
Category:
Programmatic
Cause:
The dataset does not support aggregate filters.
Action:
Remove the aggregate filter.
ODI-16034
A transparent target LKM was picked for: {0}, but the AP node has more than one downstream target component.
Category:
Programmatic
Cause:
An AP node with a transparent target LKM can only have one downstream target.
Action:
Pick a different LKM.
ODI-16035
Target node {0} has assigned IKM {1}. The IKM will be ignored.
Category:
Programmatic
Cause:
A target node that is loaded by an upstream AP node with a transparent target LKM assigned does not need an IKM assigned, since the loading functionality will be handled by the LKM transparent push.
Action:
Set IKM to null.
ODI-16036
No target connected to AP node: {0} with SQL multi-connect LKM assigned.
Category:
Programmatic
Cause:
An AP node with SQL multi-connect LKM assigned has no target.
Action:
Add a target component.
ODI-16037
Only one target allowed for AP node: {0} with SQL multi-connect LKM assigned.
Category:
Programmatic
Cause:
An AP node with multi-connect LKM assigned cannot have multiple targets.
Action:
Pick different LKM, or remove all but one of the targets in the mapping.
ODI-16038
No extra logical components are allowed downstream from AP node: {0} with SQL multi-connect LKM assigned. The AP node must have a direct connection to target.
Category:
Programmatic
Cause:
An AP node with multi-connect LKM assigned must be connected directly to the target, with no intervening nodes.
Action:
Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
ODI-16039
The AP node: {0} has a transparent target LKM assigned, but it is not connected directly to the target.
Category:
Programmatic
Cause:
An AP node with transparent target LKM assigned must be connected directly to the target, with no intervening nodes.
Action:
Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
ODI-16040
Non-ANSI full outer join for component: {0} is not supported.
Category:
Programmatic
Cause:
Full outer join is set to generate non-ANSI syntax.
Action:
Check the box for "Generate ANSI Syntax" under Join properties.
ODI-16041
The manual group by clause is missing a required attribute: {0}
Category:
Programmatic
Cause:
The maual group-by expression is missing one or more attributes required for the SQL group-by clause.
Action:
Edit the manual group-by expression to included the missing attribute.
ODI-16042
The expression for attribute: {0} does not contain an aggregate function, but the group by column setting is NO. Non aggregate attributes should be part of the group-by clause.
Category:
Programmatic
Cause:
The group-by column setting for an attribute is NO, but it should be part of the group-by clause because the expression does not contain an aggregate function.
Action:
If the attribute expression does not contain an aggregate, set the group by column setting to YES.
ODI-16043
The expression for attribute: {0} contains an aggregate function, but the group by column setting is YES. Only non aggregate attributes should be included in the group-by clause.
Category:
Programmatic
Cause:
The group by column setting for an attribute is YES, but it should not be part of the group-by clause because the expression contains an aggregate function.
Action:
If the attribute expression contains an aggregate, set the group by column setting to NO.
ODI-16044
The having clause references aggregate attribute: {0}, but an aggregate function is not specified.
Category:
Programmatic
Cause:
An aggregated attribute is used in a having clause without an aggregate function.
Action:
If the having clause references an aggregated attribute, include the aggregate function used with that attribute.
ODI-16045
Input connector point {0} is not referenced by any attribute expression. That input to the set component is unused.
Category:
Programmatic
Cause:
An input connector point for a set component is unused because no attribute expressions reference attributes scoped through that connector.
Action:
At least one attribute expression should reference an attribute through the input connector in order to use that input to the set.
ODI-16046
Set components must have a minimum of two input connector points.
Category:
Programmatic
Cause:
The set component has less than two input connector points.
Action:
Add an input connector point. Set components must have at least two sources.
ODI-16047
Set component output attribute: {0} must have a non empty expression for input connector point {1}.
Category:
Programmatic
Cause:
The number of input expressions is less than the number of input connector points.
Action:
Specify a non empty expression for each input. Specify null if no attribute reference is used.
ODI-16048
Reusable mapping component: {0} must have a connection for input connector point {1}.
Category:
Programmatic
Cause:
An input connector point is not connected to another map component.
Action:
Connect the input connector point to a source component.
ODI-16049
Reusable mapping component {0} has one or more output connector points, but none are connected or contain target components. DML cannot be generated without a target component connected downstream or within the reusable mapping.
Category:
Programmatic
Cause:
None of the output connector points for the reusable mapping component are connected or contain target components.
Action:
Add a connection for at least one output connector point.
ODI-16050
Native sequence and ORDER BY operation are performed on the same flow. This might not be allowed in some technologies such as Oracle.
Category:
Programmatic
Cause:
Sequence is used before order by, this is now allowed in Oracle.
Action:
Remove sorter component or place sorter in an execution unit different from the sequence expression.
ODI-16051
The Sub select option may not be set for reusable mappings having an input signature.
Category:
Programmatic
Cause:
The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if an input signature is present.
Action:
Avoid calling the setSubSelect method or specify false for the value parameter.
ODI-16052
The Sub select option may not be set for reusable mappings having more than one output signature.
Category:
Programmatic
Cause:
The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if more than one output signature is present.
Action:
Avoid calling the setSubSelect method or specify false for the value parameter.
ODI-16053
Mixed non-ordered (outer) join and ordered join is not supported.
Category:
Programmatic
Cause:
Outer join is set to non-ordered.
Action:
Change the join to ordered join.
ODI-16054
An unparsed identifier, {0}, was found in the aggregate HAVING clause. This identifier was not found in any other aggregate or group by expressions.
Category:
Programmatic
Cause:
An identifier was found in the HAVING clause, but is invalid because it is not present in any aggregation or group by expression.
Action:
Remove this expression from the HAVING clause or use it in one of the aggregate output attribute expressions.
ODI-16055
Reusable mapping {0} for reusable mapping component {1} contains errors or warnings.
Category:
Programmatic
Cause:
A reusable mapping used by this mapping has errors or warnings.
Action:
See following error or warning messages regarding the reusable mapping.
ODI-16056
The driver connection for lookup component {0} is not connected to any source.
Category:
Programmatic
Cause:
A connection has not been made between the source and driving connection of the lookup component.
Action:
Connect a source to the lookup component driver connection.
ODI-16057
The lookup connection for lookup component {0} is not connected to any source.
Category:
Programmatic
Cause:
A connection has not been made between the source and lookup connection of the lookup component.
Action:
Connect a source to the lookup component lookup connection.
ODI-16058
Output signature {0} of reusable mapping {1} is not connected to any input source.
Category:
Programmatic
Cause:
An output signature is not connected to any upstream component.
Action:
Connect the output signature to an upstream component.
ODI-16059
Error adding lines to task container for KM {0}: {1}
Category:
Programmatic
Cause:
Action:
ODI-16060
Error finding helper component KM for AST processing of a node with 11g KM assigned: node={0}, helper KM={1}, error={2}
Category:
Programmatic
Cause:
Action:
ODI-16061
Error when calling generation delegate for component KM {0}: {1}
Category:
Programmatic
Cause:
Action:
ODI-16062
Cannot create node variable binding map for component KM {0}: {1}
Category:
Programmatic
Cause:
Action:
ODI-16063
No target multi-connect IKM found when processing an AP node with a SQL multi-connect LKM assigned.
Category:
Programmatic
Cause:
A multi-connect IKM could not be found for a target.
Action:
Check the target IKM assignment.
ODI-16064
When processing an AP node with SQL multi-connect LKM assigned, the downstream target node does not have a multi-connect IKM assigned.
Category:
Programmatic
Cause:
The IKM assigned to the target is not a multi-connect IKM. If an AP node uses a multi-connect LKM, a multi-connect IKM is required on the target.
Action:
Assign a multi-connect IKM to the target.
ODI-16065
Cannot get an entity manager for the mapping object. The entity manager must be set for the owning mapping or reusable mapping by calling IOdiEntityManager.persist() or Mapping.setEntityManager(), before this operation can be done. Mapping object= {0}
Category:
Programmatic
Cause:
An mapping operation is being performed that requires the mapping to resolve a reference, but the mapping entity manager has not been set.
Action:
Set the entity manager for the mapping, by calling IOdiEntityManager.persist() or Mapping.setEntityManager().
ODI-16066
Target datastore column {0} is a mandatory column and should be mapped.
Category:
Programmatic
Cause:
Missing expression for mandatory target datastore column.
Action:
Check target datastore mandatory column expression.
ODI-16067
The Sub select option may not be set for reusable mappings having no output signature.
Category:
Programmatic
Cause:
The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if no output signature is present.
Action:
Avoid calling the setSubSelect method or specify false for the value parameter.
ODI-16068
A parse error was encountered when parsing the expression: {0}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.
Category:
Programmatic
Cause:
Expression is syntactically incorrect.
Action:
Make sure the expression is well-formed.
ODI-16069
Technology {0} does not support the WHERE clause and cannot process the join.
Category:
Programmatic
Cause:
Technology "Where" indicator is set to false.
Action:
Check the technology setting or remove the join.
ODI-16070
Ordered joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Technology Join Support Ordered indicator is set to false.
Action:
Set join to non-ordered (Generate ANSI syntax = false).
ODI-16071
Cross joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Technology Cross Join indicator is set to false.
Action:
Set join type to non-cross join.
ODI-16072
Natural joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Technology Natural Join indicator is set to false.
Action:
Set join type to non-natural join.
ODI-16073
Non-ordered natural joins are not supported.
Category:
Programmatic
Cause:
Natural Join is set to non-ordered (generate ANSI syntax = false).
Action:
Set 'Generate ANSI syntax' to true.
ODI-16074
Non-ordered joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Join is set to non-ordered (generate ANSI syntax = false).
Action:
Set join to ordered (Generate ANSI syntax = true).
ODI-16075
Non-ordered outer joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Outer Join is set to non-ordered (generate ANSI syntax = false).
Action:
Set 'Generate ANSI syntax' to true.
ODI-16076
Outer joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Join is set to outer join.
Action:
Set join to non-outer join.
ODI-16077
Full outer joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Join is set to full outer join.
Action:
Set join to non-full outer join.
ODI-16078
Inner joins are not supported in technology {0}.
Category:
Programmatic
Cause:
Join is set to inner join.
Action:
Set join to non-inner join.
ODI-16079
Reusable mapping {0} is not compatible with dataset {1}. A reusable mapping within a dataset must have no input signatures and exactly one output signature.
Category:
Programmatic
Cause:
An incompatible reusable mapping is being added to the dataset. The reusable mapping must have no input signatures and exactly one output signature.
Action:
Choose a different compatible reusable mapping or modify the resuable mapping to contain just a single output signature and no input signatures.
ODI-16080
Mapping component type {0} is not supported within a {1}.
Category:
Programmatic
Cause:
An unsupported component is being added to a mapping or composite component.
Action:
Use a supported component.
ODI-16081
Physical Mapping Design {0} cannot be calculated with no optimization context.
Category:
Programmatic
Cause:
The optimization context of the physical design is not set, or it becomes invalid because the referenced context is deleted.
Action:
Check the optimization context of the physical design and specify an appropriate context.
ODI-16082
The physical node {0} cannot be supported by technology {1} on execution unit {2} of mapping {3}.
Category:
Programmatic
Cause:
The physical node cannot be moved to the execution unit because its technology does not support the node.
Action:
Do not move the physical node to this execution unit.
ODI-16083
Input Attribute {0} of reusable mapping component {1} does not have an expression to connect it to any source, but is referenced in the reusable mapping.
Category:
Programmatic
Cause:
An input signature attribute in a reusable mapping is referenced by another component, but the input is not connected in the parent mapping.
Action:
Assign an expression to the reusable mapping component input attribute.
ODI-16084
The proposed connection would create a circular graph.
Category:
Programmatic
Cause:
The proposed connection would create a logical graph which contains a circular path, which connects a source component through some other components and back to itself.
Action:
Fix the connections to get rid of the circular path.
ODI-16085
Cannot set an expression for attribute {0} because the attribute was not found. Available attributes: {1}.
Category:
Programmatic
Cause:
SetAttributeExpressionText was called with an invalid attribute name.
Action:
Specify a valid attribute name.
ODI-16086
Set component {0} input connector point {1}: set operator {2} is not valid for {3} technology.
Category:
Programmatic
Cause:
The set operation chosen for the connector point is not valid for the technology.
Action:
Choose a set operation valid for the technology.
ODI-16087
Generation of set component {0} failed because of an incompatibility with the technology.
Category:
Programmatic
Cause:
The set operation chosen for the connector point is not valid for the technology.
Action:
Choose a set operation valid for the technology.
ODI-16088
Map component {0}, attribute {1} contains an aggregate function. Aggregate functions are only supported by the aggregate component.
Category:
Programmatic
Cause:
An aggregate function is used in the expression of a datastore attribute. The Datastore component does not support aggregate functions and will not generate the required GROUP BY clause.
Action:
Create an aggregate component to contain the aggregate function.
ODI-16089
"Cannot connect to component {0}, no input connector points are available.
Category:
Programmatic
Cause:
An attempt was made to connect to the component, but no input connector points are available.
Action:
Fix the connection graph.
ODI-16090
"Attempt connect a component to itself. from={0}, to= {1}
Category:
Programmatic
Cause:
An attempt was made to connect an output of the component back into an input of the same component.
Action:
Do not connect a component to itself.
ODI-16091
Expression component {0} has no attributes.
Category:
Programmatic
Cause:
An expression has no attributes. Expression components are projectors and must have attributes in order to be referenced by downstream components.
Action:
Add one or more attributes to the expression component.
ODI-16092
Datastore component {0}, attribute {1} is mandatory but not active.
Category:
Programmatic
Cause:
A datastore attribute is mandatory, but has been tagged as non active.
Action:
Set the mandatory attribute to active.
ODI-16093
The subselect option is not valid for reusable mapping component {0} because the reusable mapping contains an expression referencing a native sequence.
Category:
Programmatic
Cause:
The reusable mapping has an expression referencing a native sequence, and the subselect option has been chosen for the reusable mapping component.
Action:
Avoid using the subselect option for reusable mappings having expressions which reference native sequences.
ODI-16094
Physical node {0} is associated with logical schema {1}, but it is not mapped to a physical server in context {2}.
Category:
Programmatic
Cause:
The physical schema of the physical node cannot be resolved, as its logical schema is not mapped in the execution context.
Action:
Associate the logical schema with a physical schema in the context specified.
ODI-16095
"Scenario Generation failed for mapping {0} because no physical design was found.
Category:
Programmatic
Cause:
No physical design was found during scenario generation for a mapping.
Action:
Correct any errors preventing physical design generation.
ODI-16096
A mapping with name {0} already exists in folder {1}.
Category:
Programmatic
Cause:
A mapping with the same name already exist in the same folder.
Action:
Use a different name for the mapping.
ODI-16097
A reusable mapping with name {0} already exists in folder {1}.
Category:
Programmatic
Cause:
A reusable mapping with the same name already exist in the same folder.
Action:
Use a different name for the reusable mapping.
ODI-16098
A reusable mapping with name {0} already exists in global project.
Category:
Programmatic
Cause:
A reusable mapping with the same name already exist in the global project.
Action:
Use a different name for the reusable mapping.
ODI-16099
Name {0} already exists in {1} {2}.
Category:
Programmatic
Cause:
The given name is already used. Object name needs to be unique with the parent object.
Action:
Provide a different name for the object.
ODI-16100
Name cannot be an empty string.
Category:
Programmatic
Cause:
Name of an object cannot be empty.
Action:
Provide a name for the object.
ODI-16101
Name {0} contains invalid characters. Only letters, digits or underscore characters are allowed.
Category:
Programmatic
Cause:
Proposed name contains invalid characters, such as space. Only letters, digits or underscore characters are allowed.
Action:
Provide a different name for the object.
ODI-16102
Name {0} contains invalid characters. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.
Category:
Programmatic
Cause:
Proposed name contains invalid characters, such as space. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.
Action:
Provide a different name for the object.
ODI-16103
Name {0} is longer than {1} characters.
Category:
Programmatic
Cause:
Proposed name is too long.
Action:
Shorten the proposed name.
ODI-16104
The expression for attribute {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.
Category:
Programmatic
Cause:
An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.
Action:
Check all input connector points for correct upstream connections.
ODI-16105
Expression of attribute {0} does not refer to any upstream attribute.
Category:
Programmatic
Cause:
The expression is not set or the input connector point is not properly connected.
Action:
Verify the expression or the connection to the input connector point.
ODI-16106
No columns are set to update column in Target datastore {0}.
Category:
Programmatic
Cause:
The update indicator is not set in target datastore.
Action:
Verify the targetDatastore attribute and set the update indicator.
ODI-16107
The data type for datastore component {0}, attribute {1} is not defined.
Category:
Programmatic
Cause:
The data type of the column to which the datastore attribute is bound is null. This may occur when reverse engineering an unknown data type.
Action:
Add the data type to the technology and set the data type of the column.
ODI-16108
Preset Staging Location explicitly set to target location. This may result in the addition of another execution unit and decreased performance. Consider using the default Preset Staging Location, which is already set to use the target location.
Category:
Programmatic
Cause:
The preset staging location has been explicitly set, instead of using the default value. When an explicit value is set, and execution unit will be created, even if the location is the same as the target location.
Action:
Consider using the default value for the preset staging location.
ODI-16109
Encountered {0} at line {1} column {2}. Was expecting one of: {3}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.
Category:
Programmatic
Cause:
A parser error was encountered when parsing the expression.
Action:
Fix the syntax of the expression.
ODI-16110
Non-ANSI natural join for component: {0} is not supported.
Category:
Programmatic
Cause:
Natural join is set to generate non-ANSI syntax.
Action:
Check the box for "Generate ANSI Syntax" under Join properties.
ODI-16111
Cannot remove {0} connector point for component {1} due to minimum connector point count violation.
Category:
Programmatic
Cause:
Removal of connector point will result in connector point count less than minimum count.
Action:
Do not remove connector point.
ODI-16112
Reusable mapping component {0}, output connector point {1} is not connected.
Category:
Programmatic
Cause:
An output connector point of a reusable mapping component is not connected.
Action:
Check that connections from all output connector points are optional.
ODI-16113
Mapping component {0} has no input or output connections.
Category:
Programmatic
Cause:
An mapping component has not been connected.
Action:
Connect the component to a source and/or target component.
ODI-16114
Error when ordering the components for physical design:{0}, component re-ordering is not valid. A skipped component was not able to be placed in an execution unit because of dependency errors.
Category:
Programmatic
Cause:
When attempting to reorder the component nodes in the physical graph, an eror was found.
Action:
Do not reorder the component.
ODI-16115
Cannot reorder an outer join node around another kind of node.
Category:
Programmatic
Cause:
Cannot reorder an outer join node around another kind of node.
Action:
Cannot reorder an outer join node around another kind of node.
ODI-16116
Cannot reorder a join around another join if one of the joins does not have at least 2 references in its join condition.
Category:
Programmatic
Cause:
Illegal reordering.
Action:
Do not reorder the component.
ODI-16117
Cannot reorder a join around another join if one is generating ANSI and the other is not.
Category:
Programmatic
Cause:
Illegal reordering.
Action:
Do not reorder the component.
ODI-16118
Cannot reorder a join around another join if one is a left or right outer join and the other is not the same type, for non-ANSI joins.
Category:
Programmatic
Cause:
Illegal reordering.
Action:
Do not reorder the component.
ODI-16119
Cannot reorder a join around another join if either one is a left outer or right outer join, for ANSI joins.
Category:
Programmatic
Cause:
Illegal reordering.
Action:
Do not reorder the component.
ODI-16120
Warning: Target Load Order -- Child component is ordered before parent component.
Category:
Programmatic
Cause:
A datastore component with foreign key relationships is ordered before its parent datastore component.
Action:
Change the load order to put parent component before child component or keep the load order knowing that it may result in error in loading due to missing primary record.
ODI-16121
Error: Target Load Order -- Load order is not consistent with processing graph from source to target. Please modify the graph or change the load order.
Category:
Programmatic
Cause:
A target component is ordered before its source component.
Action:
Change the load order to put source component before target component or change the mapping design.
ODI-16122
Cannot create physical design due to mapping validation errors: {0}.
Category:
Programmatic
Cause:
Validation errors.
Action:
Fix the mapping.
ODI-16123
Node pushed upstream causes conflicts due to multiple upstream connections from different execution units. Pushed node={0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16124
Not allowed to reorder node {0}: {1}
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16125
Not allowed to push node {0} past node {1}: {2}
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16126
Physical graph re-ordering is causing a referencing problem for component: {0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16127
Cannot reorder component that is not a selector:{0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16128
Cannot reorder component that does not have at least one input and output connector point: {0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16129
Cannot reorder a component that has multiple downstream targets: {0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16130
Cannot reorder an outer join component: {0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16131
The node will not be moved.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16132
Cannot reorder node {0} downstream of {1}, since {1} has expression references to {0}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16133
Cannot reorder node {0} upstream of {1}, since {0} has expression references to {1}.
Category:
Programmatic
Cause:
Illegal node push.
Action:
Do not push the node to this location.
ODI-16134
Cannot set journalizing for datastore component {0}, since its bound datastore is not journalized.
Category:
Programmatic
Cause:
Cannot set journalizing since the bound datastore is not journalized.
Action:
Make sure the bound datastore is CDC enabled.
ODI-16135
File technology has limited capability to serve as a staging area. Consider switching the staging area to another technology, such as in-memory engine.
Category:
Programmatic
Cause:
File technology unit set as staging area.
Action:
Set staging area to non-file technology.
ODI-16136
{0} {1} should not have a {2}. {2} will be ignored.
Category:
Programmatic
Cause:
With Join Type CROSS or NATURAL, the Join Condition will be ignored.
Action:
Check the Join Type. If correct, set the Join Condition to blank.
ODI-16137
IKM {0} is selected for physical node {1}, but the corresponding logical component {2} of reusable mapping {3} is not marked as derived sub-select.
Category:
Programmatic
Cause:
An IKM is used for extraction of a physical node, but derived sub-select is not enabled.
Action:
Change the KM selected for the physical node, or mark the logical component as derived sub-select.
ODI-16138
Internal error occurred during mapping metadata conversion. Please check the original 11g interface to see if it is complete and valid. Only interfaces that pass validation are supported during the upgrade process. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
Category:
Programmatic
Cause:
Internal error occurred or unexpected exception received during mapping metadata conversion.
Action:
Make sure the original 11g interface is valid. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
ODI-16139
Execution unit {0} does not have a location.
Category:
Programmatic
Cause:
The execution unit does not have a logical schema selected for its location.
Action:
Select a logical schema as the location of the execution unit.
ODI-16140
Mapping component {0} must have a connection for input connector point {1}.
Category:
Programmatic
Cause:
An input connector point is not connected to another map component.
Action:
Connect the input connector point to a source component.
ODI-16141
Mapping component {0} must have a connection for output connector point {1}.
Category:
Programmatic
Cause:
An output connector point is not connected to another map component.
Action:
Connect the output connector point to a downstream component.
ODI-16142
Cannot bind a datastore component to file model datastore {0}, use a file component instead.
Category:
Programmatic
Cause:
Attempt to bind a datastore component to a datastore with file technology.
Action:
Use a file component instead, and bind the file object to it.
ODI-16143
Cannot bind a file component to non-file model datastore {0}, use a datastore component instead.
Category:
Programmatic
Cause:
Attempt to bind a file component to a datastore with non-file technology.
Action:
Use a datastore component instead, and bind the file object to it.
ODI-16144
The expression cannot be pushed to execution unit {0} because its references would be out of scope.
Category:
Programmatic
Cause:
Illegal push-to target execution unit for expression.
Action:
Do not push the expression to this execution unit.
ODI-16145
The lookup match nth rows for lookup component {0} should be positive number.
Category:
Programmatic
Cause:
The match nth row property has not been correctly configured for lookup component.
Action:
Correct the match nth row property for lookup component.
ODI-16146
The join condition for component {0} contains a filter expression that does not reference a different schema on each side of the equality operator: {1}. Filter expressions may not behave as expected in joins.
Category:
Programmatic
Cause:
The join condition contains a filter expression. Filter expressions may not be effective in joins, and are inherently problematic in outer joins.
Action:
Move the extra filter condition to a separate filter component to eliminate interaction with the join.
ODI-16147
The join condition for component {0} does not contain an identifiable equality operator to join the input sources: {1}.
Category:
Programmatic
Cause:
The join condition may be missing an equality operator needed to match rows when joining the input sources.
Action:
Check the join expression for a valid equality operator.
ODI-16148
The size of map attribute {0} ({1}) is greater than the size of attribute {2} ({3}), to which it is mapped. Truncation or runtime errors are possible, depending on the technology.
Category:
Programmatic
Cause:
A map attribute is mapped to an attribute of smaller size. This may result in data truncation or DML errors.
Action:
Verify the size of both attributes and make any adjustments necessary to avoid truncation. Add an expression to explicitely truncate the data if necessary.
ODI-16149
For lookup component {0}, the option {1} for non matching rows may only be selected if option {2} is selected for multiple matching rows.
Category:
Programmatic
Cause:
The no match rows property has not been correctly configured for lookup component. It may only be used if the multiple matching rows option specifies all rows.
Action:
Correct the no match rows property for lookup component.
ODI-16150
Multiple non-ANSI outer joins exist within a dataset for the same datastore {0}.
Category:
Programmatic
Cause:
A datastore is outer joined to more than one datastore. This may result in execution errors.
Action:
Create joins outside of datasets.
ODI-16151
The context value {0} for map component {1} does not map to a physical location.
Category:
Programmatic
Cause:
The forced context value of a data storage component, combined with the model and logical schema, does not map to a physical schema. A map physical design cannot be created.
Action:
Use the logical schema editor or SDK to set a physcial schema for the chosen component context.
ODI-16152
Error processing KM target expression for mapping: {0}, KM line: {1}, KM error: {2}
Category:
Programmatic
Cause:
An exception was thrown during KM processing of the target expression for a particular line.
Action:
Review the KM line and error to determine the cause.
ODI-16153
Error processing KM source expression for mapping: {0}, KM line: {1}, KM error: {2}
Category:
Programmatic
Cause:
An exception was thrown during KM processing of the source expression for a particular line.
Action:
Review the KM line and error to determine the cause.
ODI-16154
No expressions have been defined on the attributes for map component {0}.
Category:
Programmatic
Cause:
A target datastore is connected, but none of its attributes have expressions defined.
Action:
Create expressions to map one or more attributes to a source.
ODI-16155
Join or Lookup component {0} is inactive. Components joining sources must be active.
Category:
Programmatic
Cause:
A join or lookup component has been set to inactive. Components which join sources must be active because all sources will not be in scope without the join.
Action:
Set the component to active.
ODI-16156
Join type {0} in {1} cannot be supported due to circular relationships in Dataset {2}.
Category:
Programmatic
Cause:
If a circle of relationships exist in a Dataset, one of the joinis must be reduced to a filter. The join type defined on it could be lost.
Action:
Examine the logic in the Dataset and try to reduce the number of outer joins if possible as the currently specified logic in Dataset cannot be translated to a SQL query.
ODI-16157
Ambiguous expression reference due to split path. {0} Expression: {1}, Available paths: {2}
Category:
Programmatic
Cause:
The connection path to the referenced attribute is split and the reference does not include a path specifier with a sufficient number of connector names to specify an unambiguous path..
Action:
Add a path specifier qualifier to the expression reference.
ODI-16158
Component in path specifier has multiple output connector points. {0} Expression: {1}, Component={2}
Category:
Programmatic
Cause:
A map component specified in the expression path specifier has multiple output connector points.
Action:
A specific connector point must be specified in the path specifier.
ODI-16159
Path specifier contains nonexistent identifier. {0} Expression: {1}, Identifier={2}
Category:
Programmatic
Cause:
An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.
Action:
Fix the path specifier in the expression.
ODI-16160
Path specifier contains out-of-scope identifier. {0} Expression: {1}, Identifier={2}
Category:
Programmatic
Cause:
An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.
Action:
Fix the path specifier in the expression.
ODI-16161
No matching path can be found. {0} Expression: {1}
Category:
Programmatic
Cause:
A path specifier is included in the expression, but it does not match any actual path in the map.
Action:
Fix the path specifier in the expression.
ODI-16162
Final parsing of {0} command {0} failed with exception {1}.
Category:
Programmatic
Cause:
A final parsing of the command was performed and hit an error.
Action:
Report as an ODI bug.
ODI-16163
Cannot parse identifier "{0}" because there are multiple instances of "{1}" in the mapping.
Category:
Programmatic
Cause:
An identifier in the expression can not be parsed because it refers to multiple components.
Action:
Fix the identifier in the expression.
ODI-16164
Internal Error: Cannot find input query select item with matching path specifier for expression cross reference: {0}
Category:
Programmatic
Cause:
The code generator cannot generate code for the map expression cross reference because the upstream query does not include the referenced object, with a matching path specifier.
Action:
Fix the expression.
ODI-16165
An attribute input expression for a set component must reference upstream attributes through only one input connector point. Attribute: {0}.
Category:
Programmatic
Cause:
An attribute input expression for a set component must reference upstream attributes through only one input connector point.
Action:
Check input expressions for the set component.
ODI-16166
Cannot parse the syntax of user defined function or language element {0}: {1}.
Category:
Programmatic
Cause:
The syntax text of the user defined function or language element cannot be parsed by the code generator.
Action:
Check the syntax text of the user defined function or language element.
ODI-16167
The function call {0} does not match the number of parameters defined for user defined function or language element {1}.
Category:
Programmatic
Cause:
The function call in the expression text does not match the number of parameters of the user defined function or language element.
Action:
Check the function call in the expression.
ODI-16168
Invalid parameter syntax in the syntax text of user defined function or language element {0}: {1}.
Category:
Programmatic
Cause:
One of the parameters in the syntax text contains invalid parameter syntax.
Action:
Check the syntax text of the user defined function or language element.
ODI-16169
Invalid parameter syntax in the implementation text of user defined function or language element {0}: {1}.
Category:
Programmatic
Cause:
One of the parameters in the implementation text contains invalid parameter syntax.
Action:
Check the implementation text of the user defined function or language element.
ODI-16170
Cannot locate calling parameter {0} in implementation text from the syntax text of user defined function or language element {1}.
Category:
Programmatic
Cause:
The calling parameter in the implementation text does not match any parameters that are defined in the syntax of the user defined function or language element.
Action:
Check the implementation text of the user defined function or language element.
ODI-16171
KM {0} is not valid for physical node {1}. The default KM is {2}.
Category:
Programmatic
Cause:
The KM being set is not valid for the physical node.
Action:
Set the KM using the default KM or another compatible KM.
ODI-16172
An expression in map component {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.
Category:
Programmatic
Cause:
An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.
Action:
Check all input connector points for correct upstream connections.
ODI-16173
Map component {0}, attribute {1} contains an expression which references a window function. Window functions are not valid for technology {2}.
Category:
Programmatic
Cause:
An attribute expression references a window or analytical function, but the technology does not support window functions.
Action:
Check the technology editor for window function support, and change the setting if the technology supports window functions. If not, the window function may not be used in the expression.
ODI-16174
Map component {0}, property {1} contains an expression which references a window function. Window functions are not valid for technology {2}.
Category:
Programmatic
Cause:
A property expression references a window or analytical function, but the technology does not support window functions.
Action:
Check the technology editor for window function support, and change the setting if the technology supports window functions. If not, the window function may not be used in the expression.
ODI-16175
Aggregate component {0}, attribute {1} contains an expression which references a window function. Window functions used within an aggregate component may result in errors or unexpected results.
Category:
Programmatic
Cause:
An attribute expression in an aggregate component references a window or analytical function. Due to rowset cardinality differences between window functions and aggregate functions, window functions may be problematic in the context of an aggregation.
Action:
Use window functions within a separate expression component.
ODI-16176
The filter condition for component {0} references a window function. Window function calls are not valid in filter conditions.
Category:
Programmatic
Cause:
A filter condition references a window or analytical function. Window functions are not valid in filter conditions.
Action:
Use window functions within a separate expression component upstream of the filter component.
ODI-16177
The join condition for component {0} references a window function. Window function calls are not valid in join conditions.
Category:
Programmatic
Cause:
A join condition references a window or analytical function. Window functions are not valid in join conditions.
Action:
Use window functions within a separate expression component upstream of the join component.
ODI-16178
The lookup condition for component {0} references a window function. Window function calls are not valid in lookup conditions.
Category:
Programmatic
Cause:
A lookup condition references a window or analytical function. Window functions are not valid in lookup conditions.
Action:
Use window functions within a separate expression component upstream of the lookup component.
ODI-16179
The subquery filter condition for component {0} references a window function. Window function calls are not valid in subquery filter conditions.
Category:
Programmatic
Cause:
A subquery filter condition references a window or analytical function. Window functions are not valid in subquery filter conditions.
Action:
Use window functions within a separate expression component upstream of the subquery filter component.
ODI-16180
The split condition for component {0}, output connector point {1} references a window function. Window function calls are not valid in split conditions.
Category:
Programmatic
Cause:
A split condition references a window or analytical function. Window functions are not valid in split conditions.
Action:
Use window functions within a separate expression component upstream of the split component.
ODI-16181
The expression for attribute {0}, connector point {1}, references a window function. Window functions may not be referenced in the subquery part of a subquery filter.
Category:
Programmatic
Cause:
An expression for an attribute that participates in the subquery part of a subquery filter references a window or analytical function. Window functions are not valid in expressions which are part of the filter in a subquery filter.
Action:
Use window functions within a separate expression component upstream of the subquery filter component.
ODI-16182
The expression for {0} references a native sequence, which is not supported for technology {1}.
Category:
Programmatic
Cause:
An expression for an attribute or property references a native sequence, but the execution technology does not support native sequences.
Action:
Remove the native sequence reference from the expression.
ODI-16183
Lookup component {0} specifies first, last, or nth row matching, but no order-by modifiers have been set on the attributes.
Category:
Programmatic
Cause:
No order by modifiers have been set for the lookup attributes.
Action:
Set an ASC or DESC order by modifier on one of the lookup attributes.
ODI-16184
Unable to fetch data from datastore {0}. The model {1} does not have a reverse-engineering context set.
Category:
Programmatic
Cause:
Context associated with the logical schema does not exist.
Action:
Check the context associated with the logical schema.
ODI-16185
{0} does not support single row selection from multiple matching rows.
Category:
Programmatic
Cause:
The database technology does not support the analytical functions used to select a particular matching row.
Action:
Select a lookup type which does not select a specified single row.
ODI-16186
Input attribute {0} has no expression, and no default value is defined in the corresponding input signature attribute. The input must have either a connected expression or a default value expression.
Category:
Programmatic
Cause:
The input attribute expression is not set and has no default value defined in the input signature attribute.
Action:
Verify the expression or add a default value in the input signature attribute expression.
ODI-16187
Dimension component {0} is not based on any dimension.
Category:
Programmatic
Cause:
Dimension component is not based on any dimension.
Action:
Dimension component should have base dimension.
ODI-16188
Dimension {1}, or its related structures on which component {0} is based, contains errors.
Category:
Programmatic
Cause:
One or more errors were found in the dimension or related structures that this dimension component is based on. These errors must be resolved.
Action:
Review the dimension and its related structures for possible errors.
ODI-16189
Dimension {1}, or its related structures on which component {0} is based, contains warnings.
Category:
Programmatic
Cause:
One or more warnings were found in the dimension or related structures that this dimension component is based on.
Action:
Review the dimension and its related structures for possible warnings.
ODI-16190
In dimension component {0}, the parent natural key attribute {2} of level {1} does not have expression.
Category:
Programmatic
Cause:
Parent natural key attribute does not have expression.
Action:
Set the expressions for parent natural key attributes.
ODI-16191
In dimension component {0}, the natural key attribute {2} of level {1} does not have expression.
Category:
Programmatic
Cause:
Natural key attribute does not have expression.
Action:
Set the expressions for natural key attributes.
ODI-16192
In dimension component {0}, no updatable attributes for level {1} have an expression. An updatable attribute is a non key attribute.
Category:
Programmatic
Cause:
No updatable attribute has an expression.
Action:
Set the expressions for updatable attributes.
ODI-16193
The value {0} for SCD type 2 gap is not valid.
Category:
Programmatic
Cause:
The value for SCD type 2 gap is not valid.
Action:
Set valid value for SCD type 2 gap.
ODI-16194
The value {0} for SCD type 2 gap unit is not valid.
Category:
Programmatic
Cause:
The value for SCD type 2 gap unit is not valid.
Action:
Set valid value for SCD type 2 gap unit.
ODI-16195
Cube component {0} is not based on any cube.
Category:
Programmatic
Cause:
A cube component must be based on a cube to be viable.
Action:
Associate the cube component to a cube.
ODI-16196
Cube {0}, or its related structures on which component {1} is based, contains errors.
Category:
Programmatic
Cause:
One or more errors were found in the cube or related structures (such as measures, dimensions, bound tables, etc.) that this cube component is based on. These errors must be resolved.
Action:
Review the cube and its related structures, such as dimensions and bound datastores, for possible errors.
ODI-16197
Cube {0}, or its related structures on which component {1} is based, contains warnings.
Category:
Programmatic
Cause:
One or more warnings were found in the cube or related structures (such as measures, dimensions, bound tables, etc.) that this cube component is based on.
Action:
Review the cube and its related structures, such as dimensions and bound datastores, for possible warnings.
ODI-16198
The dimension key attribute {0} in cube component {1} does not have an expression.
Category:
Programmatic
Cause:
The dimension key attribute in the cube component must have an expression.
Action:
Set an expression on each dimension key attribute.
ODI-16199
The null or invalid orphan policy for the base cube {0} is set to "default dimension record", but the "enable source aggregation" property on cube component {1} is set to false.
Category:
Programmatic
Cause:
The default dimension record orphan policy is set for the cube object, but source aggregation is not enabled on cube component.
Action:
If the default dimension record orphan policy is set for the cube object then it is recommended that source aggregation also be enabled on cube component. Otherwise the orphan management processing may produce multiple fact rows with the same default dimension references, which will cause an "unstable rowset" execution error in the database, since the dimension references are used as update match attributes for updating the fact table.
ODI-16200
At least one measure attribute in cube component {0} should have an expression.
Category:
Programmatic
Cause:
At least one measure attribute in the cube component should have an expression.
Action:
Set the expressions on the measure attributes.
ODI-16201
Not a known integration type for component {0}.
Category:
Programmatic
Cause:
The integration type for the cube component is invalid.
Action:
Set a valid integration type for the cube component.
ODI-16202
Not a valid attribute of component {0} or the attribute is not a measure.
Category:
Programmatic
Cause:
The specified attribute is not owned by the cube component or the attribute is not a measure.
Action:
Choose a measure attribute of the cube component.
ODI-16203
Not a valid attribute of component {0} or the attribute is not represented as a dimension natural key identifier.
Category:
Programmatic
Cause:
The specified attribute is not owned by the cube component or the attribute is not a dimension natural key identifier.
Action:
Choose a attribute of the cube component which is represented as a dimension natural key identifier.
ODI-16204
Dimension {0}, or its related structures on which component {1} is based, contains errors.
Category:
Programmatic
Cause:
One or more errors were found in the dimension or related structures that this dimension component is based on. These errors must be resolved.
Action:
Review the dimension and its related structures.
ODI-16205
The source aggregation function is not set for measure attribute: {0}, but the source aggregation is enabled on cube component {1}. Measure attribute will be included into GROUP BY clause.
Category:
Programmatic
Cause:
The source aggregation on the cube component is enabled, but no source aggregation function is specified on the measure attribute.
Action:
Specify a source aggregation function on the measure attribute or disable the source aggregation on the cube component.
ODI-16207
Not a known integration type for component {0}.
Category:
Programmatic
Cause:
Referencing a sequence from a different project is invalid.
Action:
Reset the dimension to use a sequence owned by the same project or a global sequence.
ODI-16208
In dimension {0} level {1}, level attribute {2} is defined as surrogate key, but its type is not NUMERIC.
Category:
Programmatic
Cause:
The level attribute is defined as surrogate key,but its datatype is not NUMERIC.
Action:
If the level attribute is defined as surrogate key, its datatype should be NUMERIC.
ODI-16209
Dimension {0} has some levels that use surrogate key but some that do not.
Category:
Programmatic
Cause:
The dimension has some levels that use surrogate key but some that do not.
Action:
Surrogate key usage must be consistent within a dimension. Modify the dimension to ensure all levels have a surrogate key or no levels have a surrogate key.
ODI-16210
In dimension {0}, level {1} does not use surrogate key and the natural key has more attribute defined.This is not supported by the dimension loading pattern.
Category:
Programmatic
Cause:
The level does not use surrogate key and the natural key has more than one attribute defined. This is currently not supported by the dimension loading pattern.
Action:
If no surrogate key is defined, the natural key should have only one attribute defined. Update the level accordingly.
ODI-16211
Dimension {0} uses surrogate key but is not associated with a sequence.
Category:
Programmatic
Cause:
The dimension uses a surrogate key but is not associated with a sequence.
Action:
Associate the dimension with a sequence or do not use a surrogate key.
ODI-16212
In dimension component {0} no SCD2 trigger attributes in level {1} have assignment expressions.
Category:
Programmatic
Cause:
In dimension component {0} no SCD2 trigger attributes in level {1} have assignment expressions.
Action:
Ensure one or more SCD2 trigger attributes have assignment expressions.
ODI-16213
In dimension {0} levels, both SCD2 and SCD3 parameters coexist.
Category:
Programmatic
Cause:
Some dimension attributes are using both SCD2 and SCD3 parameters across all dimension levels, this is not permitted.
Action:
Ensure that either SCD2 or SCD3 parameters are used across all dimension levels attributes, you cannot mix and match SCD2 and SCD3 parameters.
ODI-16222
In dimension {0} level {1}, level attribute {2} set the surrogate key bound column the same with primary key.
Category:
Programmatic
Cause:
The dimension level's surrogate key is bound to the primary key column. For this dimension pattern, that is not allowed.
Action:
For this dimension pattern, a surrogate key cannot be bound to a primary key column.
ODI-17500
Invalid old password.
Category:
Programmatic
Cause:
Old password did not match current password.
Action:
Provide the correct password.
ODI-17501
Temporary table has no column.
Category:
Other
Cause:
No column have been defined for the temporary table.
Action:
Define a column mapping to the temporary table.
ODI-17502
No next value returned.
Category:
Other
Cause:
No sequence next value was found for given context code.
Action:
Verify sequence definition or context code.
ODI-17503
Internal error: object ConnectConnection
Category:
Other
Cause:
Missed connection.
Action:
Try reconnect.
ODI-17504
An ordered join references the same table twice (directly or indirectly).
Category:
Other
Cause:
A same table was referenced twice by a join.
Action:
Check interface definition.
ODI-17505
An ordered join references the same table twice through another join.
Category:
Other
Cause:
A join was referencing the same table twice through another join.
Action:
Check interface definition.
ODI-17506
Variable has no value
Category:
Other
Cause:
Variable had no value.
Action:
Provide value for variable.
ODI-17507
Key does not exist
Category:
Other
Cause:
Key was unknown.
Action:
Provide a known key.
ODI-17508
No conversion for data type "{0}" from source technology "{1}" to destination technology "{2}"
Category:
Other
Cause:
No data type conversion between technology was found.
Action:
Define corresponding data type conversion.
ODI-17509
Query to access value for specific sequence {0} has failed. Query="{1}"
Category:
Other
Cause:
Query for sequence has failed.
Action:
Check sequence definition.
ODI-17510
Driver does not exist.
Category:
Other
Cause:
Driver was not found.
Action:
Check repository.
ODI-17511
No value to be set to variable ''{0}''.
Category:
Other
Cause:
No value was returned to be set to the variable.
Action:
Check variable value.
ODI-17512
Sequence is already locked
Category:
Other
Cause:
The sequence was already locked.
Action:
Unlock the sequence.
ODI-17513
Variable ''{0}'' does not exist.
Category:
Other
Cause:
Variable was not found.
Action:
Check variable.
ODI-17514
Unrecognized Oracle Data Integrator built-in function: {0}
Category:
Other
Cause:
Oracle Data Integrator built-in function was not recognized.
Action:
Check function syntax.
ODI-17515
Invalid loading command (INSERT,UPDATE...).
Category:
Other
Cause:
Loading command was invalid.
Action:
Check loading command.
ODI-17516
Internal error within the connection list
Category:
Other
Cause:
Internal error within the connection list.
Action:
Try again.
ODI-17517
Error during task interpretation. Task: {0} {1} Text: {2}.
Category:
Other
Cause:
A task interpretation error has occured.
Action:
Check tasks and try again.
ODI-17518
Error while interpreting the user name.
Category:
Other
Cause:
User name interpretation has failed.
Action:
Check user name.
ODI-17519
Error while interpreting the URL
Category:
Other
Cause:
URL interpretation has failed
Action:
Check URL.
ODI-17520
Error while interpreting the password
Category:
Other
Cause:
Password interpretation has failed.
Action:
Check password.
ODI-17521
Error while interpreting the driver
Category:
Other
Cause:
Driver interpretation has failed.
Action:
Check driver.
ODI-17522
Empty column name are not allowed
Category:
Other
Cause:
A empty column name was found.
Action:
Fill column name.
ODI-17523
There is no connection for this logical schema / context pair: {0} / {1}.
Category:
Other
Cause:
No connection was found for this logical schema / context pair.
Action:
Check schema and context assignment.
ODI-17524
Cannot set an empty alias for a source table.
Category:
Other
Cause:
Source table''s alias was empty.
Action:
Fill alias of source table.
ODI-17525
Cannot set an empty source set name.
Category:
Other
Cause:
Source set name was empty.
Action:
Fill alias of a source table.
ODI-17526
Cannot set Longc value in a PopCol having a column
Category:
Other
Cause:
Cannot set Longc value in a PopCol having a column.
Action:
Check interface`s columns.
ODI-17527
Cannot set SourceDt value in a PopCol having a column
Category:
Other
Cause:
Cannot set SourceDt value in a PopCol having a column.
Action:
Check interface`s columns.
ODI-17528
Cannot set Scalec value in a PopCol having a column
Category:
Other
Cause:
Cannot set Scalec value in a PopCol having a column.
Action:
Check interface`s columns.
ODI-17529
Reference check failure
Category:
Other
Cause:
Reference check has failed.
Action:
Check control conditions.
ODI-17530
Incomplete join may result in partial cross join
Category:
Other
Cause:
An incomplete join was found.
Action:
Check joins.
ODI-17531
KM already encrypted.
Category:
Other
Cause:
KM has been already encrypted.
Action:
Skip encryption.
ODI-17532
KM not encrypted.
Category:
Other
Cause:
KM was not encrypted.
Action:
Check KM.
ODI-17533
Clause set to cross join on a technology that does not support cross joins.
Category:
Other
Cause:
Technology did not support cross joins.
Action:
Correct joins.
ODI-17534
Clause set to full join on a technology that does not support full joins.
Category:
Other
Cause:
Technology did not support full joins.
Action:
Correct joins.
ODI-17535
Clause set to outer join on a technology that does not support left outer joins or right outer joins.
Category:
Other
Cause:
Technology did not support left outer joins.
Action:
Correct joins.
ODI-17536
Incomplete clause (Missing order number).
Category:
Other
Cause:
Order number was missing.
Action:
Correct clause.
ODI-17537
Incomplete clause (table1 and/or table2 must be set).
Category:
Other
Cause:
Table1 and/or table2 were undefined.
Action:
Set clause''s table1 and/or table2 tables.
ODI-17538
Filter is not properly set (The table must be defined)
Category:
Other
Cause:
The table must have been set.
Action:
Set filter''s table.
ODI-17539
Clause is ordered on a technology that does not support it
Category:
Other
Cause:
Technology did not support ordering.
Action:
Remove ordering.
ODI-17540
Connection is not set for this source set {0}.
Category:
Other
Cause:
Source set''s connection was not set.
Action:
Set connection.
ODI-17541
Method SnpTrt::getAllTrtOfTypeForTechnosAndProject requires not null parameters for technologies
Category:
Other
Cause:
Method requires not null parameters
Action:
Specify correct parameters.
ODI-17542
Sequence must be locked before using this function
Category:
Other
Cause:
Sequence was not locked.
Action:
Lock sequence and try again.
ODI-17543
Technology does not support joins
Category:
Other
Cause:
Technology did not support joins.
Action:
Check technology and/or joins.
ODI-17544
This Technology does not support the WHERE clause
Category:
Other
Cause:
Technology did not support the WHERE clause
Action:
Check technology and/or clause.
ODI-17545
Technology not set for this source set {0}
Category:
Other
Cause:
Source set''s technology was undefined.
Action:
Set technology.
ODI-17546
Specified variable not found in the Repository
Category:
Other
Cause:
Variable was not found in the Repository.
Action:
Define variable and try again.
ODI-17547
Data type "{0}" for the technology "{1}" does not exist.
Category:
Other
Cause:
Data type for the technology did not exist.
Action:
Check data type and/or technology.
ODI-17548
The file reverse-engineering is only possible for delimited files.
Category:
Other
Cause:
The file reverse-engineering was performed against a not delimited file.
Action:
Use delimited files.
ODI-17549
Source data type "{0}" for the technology "{1}" does not exist.
Category:
Other
Cause:
Source data type was not found.
Action:
Check data type and/or technology.
ODI-17550
Missing default Physical Schema for Data Server "{0}"
Category:
Other
Cause:
Default Physical Schema was undefined.
Action:
Specify default Physical Schema.
ODI-17551
Duplicate clause order numbers
Category:
Other
Cause:
Duplicated order numbers were found.
Action:
Check clause definition.
ODI-17552
Duplicate join order numbers
Category:
Other
Cause:
Duplicated join order numbers were found.
Action:
Check join.
ODI-17553
Exceeded the maximum number of errors allowed.
Category:
Other
Cause:
The maximum number of errors allowed were exceeded.
Action:
Check maximum error numbers.
ODI-17554
Agent "{0}" does not exist.
Category:
Other
Cause:
Agent was not found.
Action:
Check agent definition.
ODI-17555
You cannot unlock this object. Only the lock owners and Supervisors can unlock objects.
Category:
Other
Cause:
An attempt was made to unlock objects that were locked by another user.
Action:
Login as Supervisor or as the lock owners and try again.
ODI-17556
Error during decryption of text.
Category:
Other
Cause:
Text decryption has failed.
Action:
Try again.
ODI-17557
No condition defined for this rule.
Category:
Other
Cause:
No condition have been defined for this rule.
Action:
Define conditions.
ODI-17558
The field for this rule is not specified.
Category:
Other
Cause:
The field was unspecified.
Action:
Specify field for this rule.
ODI-17559
The operator for this rule is not specified.
Category:
Other
Cause:
The operator was unspecified.
Action:
Specify operator for this rule.
ODI-17560
The value to test is not defined.
Category:
Other
Cause:
The value to test was not defined.
Action:
Specify value.
ODI-17561
This operator is not supported.
Category:
Other
Cause:
This operator was not supported.
Action:
Correct operator.
ODI-17562
This operator cannot be used with this field.
Category:
Other
Cause:
The operator could not be used with the given field.
Action:
Correct operator.
ODI-17563
There is no work repository matching the name "{0}".
Category:
Other
Cause:
Work repository was not found.
Action:
Check work repository with the given name exists.
ODI-17564
More than one work repository found with the name "{0}" for this master repository.
Category:
Other
Cause:
More than one work repository with the specified name was found for this master repository.
Action:
Contact Oracle Support Services.
ODI-17565
Scenario has been already encrypted. No encryption was performed.
Category:
Other
Cause:
Scenario has been already encrypted.
Action:
Decrypt and try again.
ODI-17566
Scenario is not encrypted. No decryption was performed.
Category:
Other
Cause:
Scenario was not encrypted.
Action:
Check Scenario.
ODI-17567
A Scenario generated from a Variable cannot be encrypted or decrypted.
Category:
Other
Cause:
An attempt was made to encrypte or decrypte a Scenario generated from a Variable.
Action:
Change Scenario'' source component.
ODI-17568
Could not connect to the database referenced by the context and the logical schema
Category:
Network
Cause:
Connection to the database failed.
Action:
Check context and logical schema.
ODI-17569
Unable to update sequence''s next value.
Category:
Other
Cause:
Updating sequence was not possible.
Action:
Check sequence definition.
ODI-17570
Your text is too long. Please shorten it or choose the ''LONG TEXT'' datatype.
Category:
Other
Cause:
Text was too long.
Action:
Shorten the text or choose the LONG TEXT data type.
ODI-17571
Password does not respect the following rule: "{0}".
Category:
Security
Cause:
The password did not respect the rule.
Action:
Choose another password.
ODI-17572
This SnpFfValuee does not exist.
Category:
Other
Cause:
Value was not found.
Action:
Check FlexField value.
ODI-17573
This SnpFfValuem does not exist.
Category:
Other
Cause:
Value was not found.
Action:
Check FlexField value.
ODI-17574
This SnpFfValuew does not exist.
Category:
Other
Cause:
Value was not found.
Action:
Check FlexField value.
ODI-17575
SnpLicense does not exist.
Category:
Other
Cause:
SnpLicense was not found.
Action:
Check License.
ODI-17576
Unknown actual constraint type for an interface constraint.
Category:
Other
Cause:
Interface constraint type was unknown.
Action:
Check constraint type.
ODI-17577
Unknown variable data type.
Category:
Other
Cause:
Variable data type was unknown.
Action:
Check variable data type.
ODI-17578
Name "{0}" is already used.
Category:
Other
Cause:
Name was already used.
Action:
Use another name or change mode of import.
ODI-17579
Type of clause is not set.
Category:
Other
Cause:
Type of clause was not set.
Action:
Set type of clause.
ODI-17580
Type of join is not set.
Category:
Other
Cause:
Type of join was not set.
Action:
Set type of join.
ODI-17581
A non ordered clause is passed to the construction of ordered joins trees method.
Category:
Other
Cause:
A non ordered clause was passed to the construction of ordered joins trees method.
Action:
Check clauses.
ODI-17582
Missing order number for an ordered clause.
Category:
Other
Cause:
Clause order was not set.
Action:
Set the clause order.
ODI-17583
More than one unique constraint associated to an interface constraint.
Category:
Other
Cause:
More than one unique constraint associated to an interface constraint was found.
Action:
Check constraints.
ODI-17584
URL does not exist.
Category:
Other
Cause:
URL was not found.
Action:
Check URL.
ODI-17585
Key cannot be checked.
Category:
Other
Cause:
Key could not be checked.
Action:
Check key definition.
ODI-17586
Field separator is mandatory for a delimited file.
Category:
Other
Cause:
Field separator was missing.
Action:
Check separator and/or file type.
ODI-17587
Object name "{0}" is too long for the technology "{1}" (Logical schema : "{2}" ; Context Code : "{3}")
Category:
Other
Cause:
Object name was too long.
Action:
Correct object name.
ODI-17588
Unable to load work repository info.
Category:
Other
Cause:
Work repository was not found.
Action:
Contact Oracle Support Services.
ODI-17589
Logical schema has not been specified for sequence "{0}"
Category:
Other
Cause:
Logical schema was not specified.
Action:
Specify logical schema.
ODI-17590
Code {0} for model "{1}" is already used by another model.
Category:
Other
Cause:
An already used code was assigned.
Action:
Change code for model.
ODI-17591
Name "{0}" is already used.
Category:
Other
Cause:
A name already used was assigned.
Action:
Change name.
ODI-17592
Object is not in execution work repository.
Category:
Other
Cause:
Object was not in execution work repository.
Action:
Check object and/or repository.
ODI-17593
Maximum number or source/target technologies exceeded. Current limit is {0}.
Category:
Other
Cause:
Maximum number or source/target technologies was exceeded.
Action:
Check limit and number of technologies.
ODI-17594
Cannot encrypte already encrypted action.
Category:
Other
Cause:
This action has been already encrypted.
Action:
Skip encryption.
ODI-17595
This action is not encrypted.
Category:
Other
Cause:
This action was not encrypted.
Action:
Check parameters and try again.
ODI-17596
Query to retrieve value for native sequence "{0}" has failed Query="{1}"
Category:
Other
Cause:
Query has failed.
Action:
Check query.
ODI-17597
Cannot mix ordered and non-ordered join syntax within a dataset for technology.
Category:
Other
Cause:
Mixed join not allowed within a dataset.
Action:
Change all joins in dataset to same join syntax (either ordered or non-ordered).
ODI-17598
Non-ordered natural join is not supported.
Category:
Other
Cause:
Non-ordered natural join is not supported.
Action:
Change natural join to use ordered syntax.
ODI-17599
Ordered inner join is not supported.
Category:
Other
Cause:
Ordered inner join is disabled for technology.
Action:
Change join type.
ODI-17600
Ordered left outer join is not supported.
Category:
Other
Cause:
Ordered left outer join is disabled for technology.
Action:
Change join type.
ODI-17601
Ordered right outer join is not supported.
Category:
Other
Cause:
Ordered right outer join is disabled for technology.
Action:
Change join type.
ODI-17602
Non-ordered full outer join is not supported.
Category:
Other
Cause:
Non-ordered full outer join is not supported.
Action:
Change full outer join to use ordered syntax.
ODI-17603
Sql error checking a condition. {0}
Category:
Other
Cause:
Sql error checking a condition.
Action:
Correct the Sql in the condition.
ODI-17604
Reference column isn't associated with this instance of reference.
Category:
Programmatic
Cause:
Reference column isn't associated with this instance of reference.
Action:
Check reference column.
ODI-17605
Column is not associated to this datastore.
Category:
Programmatic
Cause:
Datastore doesn't have this column.
Action:
Check datastore and column.
ODI-17606
{0} already belongs to another OdiDataStore.
Category:
Programmatic
Cause:
Object belongs to another datastore.
Action:
Check object and datastore.
ODI-17607
Parameter pReference is not an outbound reference for this OdiDataStore.
Category:
Programmatic
Cause:
Parameter is not an outbound reference for OdiDataStore.
Action:
Check parameter.
ODI-17608
Invalid technology for the given data type.
Category:
Other
Cause:
Invalid technology for the given data type.
Action:
Check technology.
ODI-17609
Invalid data type code.
Category:
Programmatic
Cause:
Invalid data type code.
Action:
Check data type code.
ODI-17610
Found NULL in STEP_TYPE.
Category:
Programmatic
Cause:
Step type is null.
Action:
Check step type.
ODI-17611
STEP_TYPE is not valid.
Category:
Programmatic
Cause:
Step type isn't valid.
Action:
Check step type.
ODI-17612
MultiConnectionSupported is not settable for {0}.
Category:
Programmatic
Cause:
MultiConnectionSupported is not settable.
Action:
Check knowledge module.
ODI-17613
Cannot handle {0} of type {1}.
Category:
Programmatic
Cause:
Cannot handle object.
Action:
Check object's type.
ODI-17614
Unknown key type: {0}.
Category:
Programmatic
Cause:
Unknown key type.
Action:
Check key.
ODI-17615
The command is not an ODI Tool command.
Category:
Other
Cause:
Wrong command.
Action:
Check command.
ODI-17616
No WorkTextOrig was found for ID: {0}.
Category:
Other
Cause:
Invalid ID.
Action:
Check ID.
ODI-17617
Class descriptor for WorkTextOrig [ {0} ] is null.
Category:
Programmatic
Cause:
Descriptor is null.
Action:
Check class descriptors.
ODI-17618
Unable to deal with an AliasedColumnCrossRef with type {0}.
Category:
Programmatic
Cause:
Incorrect column type.
Action:
Check column type.
ODI-17619
Unexpected CrossRef {0} type.
Category:
Programmatic
Cause:
Incorrect CrossRef type.
Action:
Check CrossRef.
ODI-17620
Object type is not valid.
Category:
Programmatic
Cause:
Object type is not valid.
Action:
Check object type.
ODI-17621
Unable to manage crossRef for object from class [ {0} ].
Category:
Programmatic
Cause:
Illegal object type.
Action:
Check object type.
ODI-17622
pSqlIndGroup is not a valid group type.
Category:
Programmatic
Cause:
Invalid group type.
Action:
Check type.
ODI-17623
Too many parameters for function {0}, Object {1}, Language {2}.
Category:
Other
Cause:
Too many parameters.
Action:
Check parameters count.
ODI-17624
Missing parameter for function {0}, Object {1}, Language {2}.
Category:
Other
Cause:
Missing parameter.
Action:
Check parameters count.
ODI-17625
Only OdiColumns are currently supported for SnpsExpressionTag.
Category:
Programmatic
Cause:
Wrong column type.
Action:
Check column type.
ODI-17626
Cannot reassign a DataType.
Category:
Programmatic
Cause:
Technology has been assigned yet.
Action:
Check DataType
ODI-17627
Inconsistent connection settings.
Category:
Programmatic
Cause:
Inconsistent connection settings.
Action:
Check connection settings type.
ODI-17628
Unknown IConnectionSettings implementation.
Category:
Programmatic
Cause:
Unknown IConnectionSettings implementation.
Action:
Check settings type.
ODI-17629
Connection Settings for repository server must be instanceof JdbcSettings.
Category:
Programmatic
Cause:
Wrong settings type.
Action:
Check settings type.
ODI-17630
Unknown OptionType.
Category:
Programmatic
Cause:
Unknown OptionType.
Action:
Check option type.
ODI-17631
The given class has no matching OverridenOptionOrig.
Category:
Programmatic
Cause:
The given class has no matching OverridenOptionOrig.
Action:
Check class.
ODI-17632
Unexpected variable type.
Category:
Programmatic
Cause:
Unexpected variable type.
Action:
Check variable type.
ODI-17633
{0} datatype is expected.
Category:
Programmatic
Cause:
Wrong value datatype.
Action:
Check value datatype.
ODI-17634
Parameter must have text; it must not be null or empty.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17635
Parameter must have text; it must not be null, empty, or blank.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17636
Parameter {0} must be false.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17637
Parameter must not be null.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17638
Parameter {0} must be null.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17639
Parameter must be null.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17640
Parameter {0} must have text; it must not be null or empty.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17641
No {0} matches this IObject: {1}.
Category:
Programmatic
Cause:
IObject is not matched.
Action:
Check class.
ODI-17642
No Entity Class matches this Snp Class: {0}.
Category:
Programmatic
Cause:
No Entity Class matches Snp Class.
Action:
Check Entity Class.
ODI-17643
No Snp Class matches this Entity Class: {0}.
Category:
Programmatic
Cause:
No Snp Class matches Entity Class.
Action:
Check Snp Class.
ODI-17644
Unknown FlexFieldType.
Category:
Programmatic
Cause:
Unknown FlexFieldType.
Action:
Check FlexFieldType type.
ODI-17645
Parameter must be instance of {0}.
Category:
Programmatic
Cause:
Wrong parameter type.
Action:
Check parameter.
ODI-17646
It is forbidden to use a variable of one project in a package of another project.
Category:
Other
Cause:
Variable and package have different parents.
Action:
Check variable and package.
ODI-17647
Unable to create the expression element, Object {0}, Language {1}.
Category:
Other
Cause:
Unable to create the expression element.
Action:
Check expression parameters.
ODI-17648
A mapping cannot be on the target.
Category:
Other
Cause:
A mapping cannot be on the target.
Action:
Check execution location.
ODI-17649
Can't create join between 2 source datastore from different DataSet.
Category:
Other
Cause:
Source datastores are from different DataSet.
Action:
Correct join.
ODI-17650
A {0} was expected as value since {1} is {2}.
Category:
Other
Cause:
Wrong type.
Action:
Check type.
ODI-17651
Parameter {0} must be instance of [{1}].
Category:
Programmatic
Cause:
Wrong parameter class.
Action:
Check parameter class.
ODI-17652
Class {0} is not assignable to {1}.
Category:
Programmatic
Cause:
Inconsistent classes.
Action:
Check classes.
ODI-17653
{0} line isn't found.
Category:
Other
Cause:
Missed line.
Action:
Check line count.
ODI-17654
Parameter {0} must not be null.
Category:
Programmatic
Cause:
Parameter must be not null.
Action:
Check parameter.
ODI-17655
Parameter {0} must be {1} characters long max.
Category:
Programmatic
Cause:
Parameter length is too long.
Action:
Check parameter length.
ODI-17656
Can't define variable override for steps in exception tree.
Category:
Other
Cause:
Step is in exception tree.
Action:
Check step and variable for consistency.
ODI-17657
Cannot add a reference column to an OdiReference with type [{0}].
Category:
Other
Cause:
Reference type isn't ReferenceType.COMPLEX_REFERENCE.
Action:
Check reference type.
ODI-17658
Cannot change the target table because it's not a temporary datastore.
Category:
Other
Cause:
Datastore isn't temporary.
Action:
Check target table and datastore.
ODI-17659
Cannot get the journalized columns of a non-journalized datastore.
Category:
Programmatic
Cause:
Datastore isn't journalized.
Action:
Check datastore.
ODI-17660
Cannot set a clause on the target.
Category:
Other
Cause:
Wrong execution location.
Action:
Check execution location.
ODI-17661
{0} is not supported for this Technology.
Category:
Other
Cause:
Object is not supported for this Technology.
Action:
Check topology.
ODI-17662
Parameter {0} must have text; it must not be null, empty, or blank.
Category:
Programmatic
Cause:
Incorrect parameter.
Action:
Check parameter.
ODI-17663
Parameter {0} must be uppercase.
Category:
Programmatic
Cause:
Parameter is lower case.
Action:
Check parameter case.
ODI-17664
Parameter {0} must not contain whitespaces.
Category:
Programmatic
Cause:
Parameter contains whitespaces.
Action:
Consider to replace whitespace with another symbold (e.g. underscore)
ODI-17665
Column is not associated with this instance of OdiKey.
Category:
Other
Cause:
Column is not associated with instance of OdiKey.
Action:
Check column and OdiKey.
ODI-17666
Column is not present in the key.
Category:
Other
Cause:
Column is not present in the key.
Action:
Check column and key.
ODI-17667
Data type should be set before accessing value.
Category:
Programmatic
Cause:
Illegal method usage.
Action:
Set Data type.
ODI-17668
Datastore already has a Primary Key.
Category:
Other
Cause:
Datastore already has a Primary Key.
Action:
Remove the current primary key before adding a new one.
ODI-17669
{0} must be set before calling method {1}.
Category:
Programmatic
Cause:
Illegal method usage.
Action:
Set actual value.
ODI-17670
Default implementation already exists.
Category:
Programmatic
Cause:
Default implementation already exists.
Action:
Check function implementation.
ODI-17671
{0} must not be negative.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Set value to 0 or greater.
ODI-17672
FlexFields isn''t initialized.
Category:
Programmatic
Cause:
FlexFields isn''t initialized.
Action:
Call initFlexFields method first.
ODI-17673
Foreign key column''s datastore must be equals to this reference''s foreign datastore.
Category:
Other
Cause:
Inconsistent datastores.
Action:
Check datastore.
ODI-17674
IncrementValue is not set.
Category:
Programmatic
Cause:
IncrementValue is not set.
Action:
Set IncrementValue with setVariable method.
ODI-17675
Invalid step log's status.
Category:
Other
Cause:
Step status is not RUNNING.
Action:
Check step status.
ODI-17676
Invalid value type.
Category:
Programmatic
Cause:
Invalid value type.
Action:
Check value type.
ODI-17677
Cycle could be defined in {0} hierarchy.
Category:
Other
Cause:
It is forbidden to define cycle in {0} hierarchy.
Action:
Check hierarchy.
ODI-17678
It is forbidden to fill a key with columns from another datastore.
Category:
Other
Cause:
It is forbidden to fill a key with columns from another datastore.
Action:
Check datastore.
ODI-17679
It is forbidden to link two steps from different packages.
Category:
Other
Cause:
Steps are from different packages.
Action:
Check steps and packages.
ODI-17680
Line wasn't found.
Category:
Other
Cause:
Line wasn't found.
Action:
Check procedure lines.
ODI-17681
Maximum number of sessions must be positive.
Category:
Other
Cause:
Wrong value.
Action:
Check maximum number.
ODI-17682
Method is not valid unless MultiConnectionSupported.
Category:
Programmatic
Cause:
MultiConnectionSupported is true.
Action:
Check procedure.
ODI-17683
Model must be in Customized mode.
Category:
Other
Cause:
Wrong model mode.
Action:
Call setReverseType(ReverseType.CUSTOMIZED).
ODI-17684
Name can't be set.
Category:
Other
Cause:
Name is computed.
Action:
Check name.
ODI-17685
No {0} is defined for this model.
Category:
Other
Cause:
Missed definition.
Action:
Define CKM for model.
ODI-17686
No valid {0} name was found from this qualified name.
Category:
Other
Cause:
Valid name wasn't found.
Action:
Check qualified name.
ODI-17687
No valid qualified name was provided.
Category:
Other
Cause:
Name is invalid.
Action:
Check qualified name.
ODI-17688
OdiScenario is undefined.
Category:
Other
Cause:
OdiScenario is undefined.
Action:
Check OdiScenario definition.
ODI-17689
Option must be in the same procedure as line.
Category:
Other
Cause:
Option procedure is inconsistent.
Action:
Check option procedure.
ODI-17690
Package and procedure must be owned by the same project.
Category:
Other
Cause:
Procedure parent is inconsistent.
Action:
Check procedure parent.
ODI-17691
Primary key column's datastore must be equals to this reference's primary datastore.
Category:
Other
Cause:
Column datastore is inconsistent.
Action:
Check datastores.
ODI-17692
Reference column doesn't belong to this reference.
Category:
Programmatic
Cause:
Column is inconsistent.
Action:
Check column.
ODI-17693
Reference's foreign datastore is not equal to this datastore.
Category:
Programmatic
Cause:
Datastores are inconsistent.
Action:
Check datastores.
ODI-17694
Steps can't be moved from one package to another.
Category:
Other
Cause:
Steps can't be moved from one package to another.
Action:
Conside not to move steps.
ODI-17695
The new position is not valid.
Category:
Other
Cause:
The new position is not valid.
Action:
Check new position.
ODI-17696
The option already exists.
Category:
Other
Cause:
The option already exists.
Action:
Check option.
ODI-17697
The option owner has already been set.
Category:
Other
Cause:
The option owner has already been set.
Action:
Check option owner.
ODI-17698
The reference type must be [ {0} ] in order to define a complex SQL expression.
Category:
Programmatic
Cause:
Wrong reference type.
Action:
Check reference type.
ODI-17699
The reference type must be [ {0} ] in order to obtain the complex SQL expression.
Category:
Programmatic
Cause:
Wrong reference type.
Action:
Check reference type.
ODI-17700
The string value length should not exceed MAX_SHORT_TEXT_LENGTH since FlexFieldType is SHORT_TEXT.
Category:
Other
Cause:
FlexFieldType is SHORT_TEXT.
Action:
Check FlexFieldType and string value length.
ODI-17701
This OdiLoadPlanInstanceRun is not ESS Job related.
Category:
Other
Cause:
OdiLoadPlanInstanceRun is not ESS Job related.
Action:
Check OdiLoadPlanInstanceRun.
ODI-17702
This session is not ESS Job related.
Category:
Other
Cause:
Session is not ESS Job related.
Action:
Check session.
ODI-17703
This OdiReference must be from type [{0}] in order to access the primary DataStore alias.
Category:
Programmatic
Cause:
Wrong OdiReference type.
Action:
Check OdiReference type.
ODI-17704
This OdiReference must be from type [{0}] in order to set the primary DataStore alias.
Category:
Programmatic
Cause:
Wrong OdiReference type.
Action:
Check OdiReference type.
ODI-17705
This file descriptor is not consistent with the parent model's technology.
Category:
Other
Cause:
File descriptor is not consistent.
Action:
Check file descriptor and parent technology.
ODI-17706
This setVariable is used for increment.
Category:
Programmatic
Cause:
Increment value is set.
Action:
Use method getIncrementValue().
ODI-17707
Unable to add an alien main partition.
Category:
Other
Cause:
Main partition datastore is inconsistent.
Action:
Check main partition.
ODI-17708
Unable to compute name.
Category:
Programmatic
Cause:
Name has been set on this physical schema.
Action:
Do not compute name.
ODI-17709
Parameter must be false.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17710
Parameter {0} must be true.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17711
Undefined ODI work repository name.
Category:
Other
Cause:
Undefined repository name.
Action:
Check repository name.
ODI-17712
Variable and Step should be defined in the same Load Plan.
Category:
Other
Cause:
Variable and Step have different parent Load Plans.
Action:
Define variable and step in the same Load Plan.
ODI-17713
VariableDataType should be set before accessing DefaultValue.
Category:
Programmatic
Cause:
VariableDataType is undefined.
Action:
Set VariableDataType.
ODI-17714
You can only set KMs contained in the OdiProject containing of the OdiInterface.
Category:
Other
Cause:
KM has different parent project than OdiInterface.
Action:
Check KM.
ODI-17715
Can't add a null variable to load plan.
Category:
Programmatic
Cause:
Variable is null.
Action:
Check variable value.
ODI-17716
DataTypes must be consistent.
Category:
Other
Cause:
DataTypes is inconsistent.
Action:
Check DataTypes.
ODI-17717
Constraint is not a condition.
Category:
Programmatic
Cause:
Inconsistent constraint type.
Action:
Check parameter.
ODI-17718
Constraint is not a key.
Category:
Programmatic
Cause:
Inconsistent constraint type.
Action:
Check constraint.
ODI-17719
Option is not associated to this procedure.
Category:
Other
Cause:
Option is not associated to this procedure.
Action:
Check option and procedure.
ODI-17720
Constraint is not a reference.
Category:
Programmatic
Cause:
Inconsistent constraint type.
Action:
Check parameter.
ODI-17721
Parameter {0} already belongs to {1}.
Category:
Programmatic
Cause:
Parameter has parent.
Action:
Check parameter.
ODI-17722
Parameter {0} does not belong to this instance of {1}.
Category:
Programmatic
Cause:
Parameter has different parent.
Action:
Check parameter.
ODI-17723
Parameter {0} must belong to this {1}.
Category:
Programmatic
Cause:
Parameter parent is inconsistent.
Action:
Check parameter.
ODI-17724
Parameter {0} can't be moved to an other {1}.
Category:
Other
Cause:
Parameter can't be moved.
Action:
Do not move parameter.
ODI-17725
Parameter {0} must start with {1} prefix.
Category:
Other
Cause:
Parameter has wrong prefix.
Action:
Check parameter prefix.
ODI-17726
Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}.
Category:
Other
Cause:
Agent is null.
Action:
Check agents.
ODI-17727
pDataServiceContainer is not a data service.
Category:
Programmatic
Cause:
pDataServiceContainer is not a data service.
Action:
Check pDataServiceContainer.
ODI-17728
Package and interface must be owned by the same project.
Category:
Other
Cause:
Package and interface have different parents.
Action:
Check package and interface.
ODI-17729
Parameter must be true.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17730
Not legal for shortcut.
Category:
Programmatic
Cause:
Object is shortcut.
Action:
Use getShortcutBaseObject() to access the real object.
ODI-17731
Not legal to construct a shortcut from a datastore in a model with a different technology.
Category:
Programmatic
Cause:
Inconsistent technologies.
Action:
Check model and datastore.
ODI-17732
Odi object Must be shortcut after materialize.
Category:
Programmatic
Cause:
Object isn't shortcut.
Action:
Check object.
ODI-17733
Reference's primary datastore must be not null in order to define a ReferenceColumn.
Category:
Programmatic
Cause:
Primary DataStore is null.
Action:
Check DataStore.
ODI-17734
pDataServiceContainer {0} has no technology defined.
Category:
Programmatic
Cause:
Data Service Container has no technology defined.
Action:
Define technology.
ODI-17735
Reference's foreign datastore is not equals to this datastore.
Category:
Programmatic
Cause:
Reference's foreign datastore is not equals to this datastore.
Action:
Check DataStores.
ODI-17736
You can only set global KMs or KMs contained in the OdiProject containing the OdiInterface.
Category:
Programmatic
Cause:
Wrong KM.
Action:
Check KM and project.
ODI-17737
StepLog and Variable don't belong to the same session.
Category:
Programmatic
Cause:
Inconsistent session.
Action:
Check Session value for StepLog and Variable.
ODI-17738
Unable to find '{0}' as variable used by the scenario '{1}' in version '{2}'.
Category:
Programmatic
Cause:
Variable is null.
Action:
Check variable name.
ODI-17739
Unable to override '{0}' variable for execution. It is marked as read-only for scenario '{1}' in version '{2}'.
Category:
Programmatic
Cause:
Variable is read-only.
Action:
Check variable.
ODI-17740
Error while connecting to the Application Server at URL {0}.
Category:
Network
Cause:
Exception was thrown during connection.
Action:
Ensure that the Application Server is running and accepting requests.
ODI-17741
Datastore isn't used as a lookup source.
Category:
Programmatic
Cause:
Datastore isn't used as a lookup source.
Action:
Check Datastore.
ODI-17742
Parameter {0} must be greater or equal than {1} and less or equal than {2}.
Category:
Programmatic
Cause:
Wrong parameter value
Action:
Check parameter.
ODI-17743
Variable should be related to the same {0}.
Category:
Programmatic
Cause:
Wrong parent for variable.
Action:
Check variable.
ODI-17744
The status can only be switched from ERROR to DONE or from DONE to ERROR.
Category:
Programmatic
Cause:
Wrong status
Action:
Check status.
ODI-17745
Parameter {0} must be greater or equal than {1}.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17746
Parameter {0} must be greater than {1}.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter.
ODI-17747
Array {0} must not be empty.
Category:
Programmatic
Cause:
Array length is 0.
Action:
Check array.
ODI-17748
Parameter {0} is not relevant to this schedule.
Category:
Programmatic
Cause:
Wrong parameter.
Action:
Check parameter.
ODI-17749
Invalid value was specified. Cannot create {0} with the value {1}.
Category:
Programmatic
Cause:
Invalid value was specified.
Action:
Check value.
ODI-17750
Parent folder already has the release tag set.
Category:
Programmatic
Cause:
Setting the release tag when the parent already has the release tag set.
Action:
Set the release tag in parent.
ODI-17751
Shortcut and the base object are under same folder.
Category:
Programmatic
Cause:
Cannot create shortcut {0} with the base object under same folder {1}.
Action:
Create shortcut in different folder.
ODI-17752
Shortcut and the base object are in different projects.
Category:
Programmatic
Cause:
Cannot create shortcut {0} in project {1} which is different from the project of the base object.
Action:
Create shortcut in same project as the base object.
ODI-17753
Shortcut with same reference object in same folder.
Category:
Programmatic
Cause:
There is other shortcut object with same reference object as {0} in the same folder.
Action:
Create shortcut in different folder.
ODI-17754
Shortcut and the base object are under same model.
Category:
Programmatic
Cause:
Cannot create shortcut {0} with the base object under same model {1}.
Action:
Create shortcut in different model.
ODI-17755
Shortcut with same reference object in same model.
Category:
Programmatic
Cause:
There is other shortcut object with same reference object as {0} in the same model.
Action:
Create shortcut in different model.
ODI-17756
Scenario "{0}", which is referenced by RunScenario step "{1}", has variable "{2}" but LoadPlan does not have variable with the same name.
Category:
Programmatic
Cause:
Missed variable in Load Plan
Action:
Check Load Plan''s variables.
ODI-17757
Scenario "{0}", which is referenced by RunScenario step "{1}", has a newer version "{2}" in the repository
Category:
Programmatic
Cause:
Scenario has newer version.
Action:
Consider to use latest version.
ODI-17758
LoadPlan Variable "{0}" SQL is different than the design repository Variable "{1}" SQL.
Category:
Programmatic
Cause:
Variable's SQL was redefined.
Action:
Check LoadPlan's variable.
ODI-17759
LoadPlan Variable "{0}" LogicalSchema "{1}" is different than the design repository Variable "{2}" LogicalSchema "{3}".
Category:
Programmatic
Cause:
Variable's Logical Schema was redefined.
Action:
Check LoadPlan's variable.
ODI-17760
Exception "{0}" is not used in the Load Plan.
Category:
Programmatic
Cause:
Exception is not used.
Action:
Consider to delete or disable unused exception.
ODI-17761
LoadPlan Variable "{0}" is refreshed at step "{1}", but it has no SQL.
Category:
Programmatic
Cause:
LoadPlan Variable doesn't have refresh SQL.
Action:
Check variable''s SQL or disable variable refreshing.
ODI-17762
Context is specified on a step "{0}", but it''s no longer present in the topology.
Category:
Programmatic
Cause:
Context was removed.
Action:
Check step's context.
ODI-17763
Logical Agent is specified on a step "{0}", but it is no longer present in the topology
Category:
Programmatic
Cause:
Logical Agent was removed.
Action:
Check step's Logical Agent.
ODI-17764
Context "{0}" and Logical agent "{1}" on a step "{2}" does not map to any physical agent.
Category:
Programmatic
Cause:
Physical Agent doesn''t exist.
Action:
Check agents'' mapping.
ODI-17765
Scenario variable "{0}" type and LoadPlan variable "{1}" type mismatch.
Category:
Programmatic
Cause:
Variables have different datatype.
Action:
Check variables.
ODI-17766
Scenario "{0}" wasn''t found.
Category:
Programmatic
Cause:
Scenario doesn''t exist
Action:
Check scenario and Load Plan step.
ODI-17767
LoadPlan has variable "{0}", but repository doesn't have variable with the same name.
Category:
Programmatic
Cause:
Variable was deleted.
Action:
Check variables.
ODI-17768
LoadPlan Variable "{0}" has SQL, which could not be validated.
Category:
Programmatic
Cause:
OdiVariableTextGeneratorException during validation.
Action:
Check variable and variable text generator.
ODI-17769
OdiRef: Internal ID {0} of IObjects {1} should not be used when the repository is 12c mode.
Category:
Programmatic
Cause:
Internal ID is used in 12c mode.
Action:
Use Global Id instead of internal id.
ODI-17770
Profile {0} is not assigned to role {1}.
Category:
Security
Cause:
Profile is not assigned to role.
Action:
Check role's profiles.
ODI-17771
Enterprise principal with unique ID/name {0} is not mapped to role {1}.
Category:
Security
Cause:
Enterprise principal is not mapped to role.
Action:
Check role's mapped enterprise principals.
ODI-17772
Parameter {0} should be {1} or {2}.
Category:
Programmatic
Cause:
Wrong parameter value.
Action:
Check parameter value.
ODI-17773
Enterprise User or Role {0} does not exist.
Category:
Security
Cause:
Enterprise principla with such name could be found at LDAP server.
Action:
Check principal name and LDAP server.
ODI-17774
Maximum number of concurrent threads must be positive.
Category:
Other
Cause:
Wrong value.
Action:
Check maximum number provided.
ODI-17775
Maximum number of threads per session can not be negative.
Category:
Other
Cause:
Wrong value.
Action:
Check maximum number provided.
ODI-17776
Maximum number of concurrent threads must not be less than maximum session count.
Category:
Other
Cause:
Wrong value.
Action:
Check maximum numbers provided.
ODI-17777
Maximum number of threads per session must be not greater than maximum number of threads.
Category:
Other
Cause:
Wrong value.
Action:
Check maximum numbers provided.
ODI-17778
Maximum number of cache entries in Session Blueprint queue cannot be negative.
Category:
Other
Cause:
Wrong value.
Action:
Check value.
ODI-17779
Maximum idle time for Session Blueprint in cache cannot be negative.
Category:
Other
Cause:
Wrong value.
Action:
Check value.
ODI-17780
Package and mapping must be owned by the same project.
Category:
Other
Cause:
Package and mapping have different parents.
Action:
Check package and mapping.
ODI-17781
Physical Mapping Design must be owned by the mapping.
Category:
Other
Cause:
Physical Mapping Design is not owned by mapping.
Action:
Check mapping and physical design.
ODI-17782
OdiRef: Internal ID is retrieved in method {0}.{1} for 12c repository.
Category:
Programmatic
Cause:
Internal ID is retrieved in 12c mode.
Action:
Retrieve Global Id instead of internal id.
ODI-17783
Mapping metadata version mismatch. Expected {0}, but was {1}.
Category:
Other
Cause:
Mapping metadata version mismatch.
Action:
Check the expected and actual Mapping metadata version.
ODI-17784
Reusable Mapping metadata version mismatch. Expected {0}, but was {1}.
Category:
Other
Cause:
Reusable Mapping metadata version mismatch.
Action:
Check the expected and actual Reusable Mapping metadata version.
ODI-17785
Option positions in knowledge module must be unique.
Category:
Programmatic
Cause:
Option position undefined or multiple option in knowledge module has same position.
Action:
Modify the position of options to be unique and not null.
ODI-17786
JKM is not Oracle Golden Gate JKM.
Category:
Programmatic
Cause:
Model doesn't have JKM set or JKM is not Oracle Golden Gate JKM.
Action:
Set Oracle Golden Gate JKM for the model.
ODI-17787
Extract and initial extract processes cannot be the same.
Category:
Programmatic
Cause:
Extract and inital extract processes are the same.
Action:
Choose another extract or initial expract process.
ODI-17788
Replicat and initial replicat processes cannot be the same.
Category:
Programmatic
Cause:
Replicat and initial replicat processes are the same.
Action:
Choose another replicat or initial replicat process.
ODI-17789
Positions must be set positive.
Category:
Programmatic
Cause:
Position is not a positive integer.
Action:
Set the position to be a positive integer.
ODI-17790
{0} should be {1}
Category:
Programmatic
Cause:
Type is not correct
Action:
Set the correct type.
ODI-17791
The option group already exists.
Category:
Other
Cause:
The option group already exists.
Action:
Check option group.
ODI-17792
Option group is not associated to the same procedure
Category:
Other
Cause:
Group is not associated to the same procedure
Action:
Check option group.
ODI-17794
Count is larger than permissible value of Integer. Use method : {0}
Category:
Programmatic
Cause:
Return value is larger than permissible value of Integer
Action:
Use method : {0}
ODI-17795
{0} parameter is not valid
Category:
Programmatic
Cause:
Parameter is not correct
Action:
Set the correct parameter.
ODI-17796
{0} is not a valid technology.
Category:
Programmatic
Cause:
Technology is not correct.
Action:
Set the correct technology.
ODI-17797
Logical Agent "{0}" type and Physical Agent "{1}" type mismatch.
Category:
Programmatic
Cause:
Logical Agent and Physical Agent are of different type.
Action:
Check the type of Logical and Physical Agents.
ODI-17798
{0} parameter format is not valid.
Category:
Programmatic
Cause:
Parameter format is not correct.
Action:
Set the parameter with correct format.
ODI-17799
Level attribute {0} bound column: {1} is owned by table {2}, but the level is bound to table {3}
Category:
Programmatic
Cause:
The bound column parent table does not match the bound table for the level or dimension
Action:
Reset the column binding to a column of the bound level table.
ODI-17800
Level attribute {0} bound error column: {1} is owned by table {2}, but the level is bound to error table {3}
Category:
Programmatic
Cause:
The bound error column parent table does not match the bound error table for the level or dimension
Action:
Reset the error column binding to a column of the bound level error table.
ODI-17801
Level attribute {0} bound staging column: {1} is owned by table {2}, but the level is bound to staging table {3}
Category:
Programmatic
Cause:
The bound staging column parent table does not match the bound staging table for the level or dimension
Action:
Reset the staging column binding to a column of the bound level staging table.
ODI-17803
The dimension has an invalid cyclical parent/child level relationship involving {0}.
Category:
Programmatic
Cause:
One of the parent/child relationships reverses the order of another parent/child relationship, this is not allowed.
Action:
Fix the parent/child relationships for the dimension.
ODI-17804
The dimension hierarchy member uses parent ref {0}, which points to a level that is not included in the hierarchy.
Category:
Programmatic
Cause:
A dimension hierarchy must use parent references that allow navigation of the levels that are included in the hierarchy.
Action:
Fix the hierarchy member to use a different parent ref, or add a level to the hierarchy.
ODI-17805
An invalid dimension key for this key reference.
Category:
Programmatic
Cause:
The key reference must point to a dimension key which is belonged to the referenced dimension.
Action:
Use the dimension key belonged to the referenced dimension.
ODI-17806
The dimension key is already used by another key reference.
Category:
Programmatic
Cause:
Each dimension key can only be used by one key reference.
Action:
Set another dimension key that has not been used by any key reference.
ODI-17807
A non-transparent LKM must have a processing type of BOTH.
Category:
Programmatic
Cause:
The setProcessingType method was called for a LKM, and specified and incorrect type. A non-transparent LKM must have processing type of BOTH.
Action:
Change the call to set the correct type.
ODI-17808
Sql join parameter combination is not correct for technology {0}.
Category:
Programmatic
Cause:
Sql Join parameters combination is not correct.
Action:
Set the correct sql join parameter combination.
ODI-17809
When data server contains multiple schemas with same table and column names, physical schema must specify a schema name.
Category:
Other
Cause:
Schema name is not specified while creating the physical schema.
Action:
Please specify the schema name in corresponding physical schema.
ODI-17810
Error during BeanShell evaluation: {0}, Pre-execution code: {1}
Category:
Other
Cause:
Error occurs during BeanShell evaluation of procedure or KM task code.
Action:
Please check the procedure or KM task code in the error message.
ODI-17811
Supplied value {1} for flex field {0} is not a valid format.
Category:
Other
Cause:
Flex field value is not a valid format
Action:
Please provide the correct format.
ODI-17900
Cube {0} does not reference any dimensions.
Category:
Programmatic
Cause:
A cube must reference at least one dimension to be viable.
Action:
Add dimension references to the cube.
ODI-17901
Cube {0} does not have any measures.
Category:
Programmatic
Cause:
A cube must have at least one measure to be viable.
Action:
Define measures for this cube.
ODI-17902
A dimension reference of cube {0} is not associated with a level.
Category:
Programmatic
Cause:
A cube reference to a dimension must be associated with a level to be viable.
Action:
Ensure each dimension reference of the cube is associated with a level.
ODI-17903
Dimension {1} referenced by cube {0} is invalid.
Category:
Programmatic
Cause:
The cube references an invalid dimension.
Action:
Validate the dimensions which are referenced by this cube.
ODI-17904
Cube {0} has multiple references to dimension {1} with no unique role qualifiers.
Category:
Programmatic
Cause:
Role qualifiers are missing or not unique when a cube has multiple references to a dimension.
Action:
Set role qualifiers on the dimension references of the cube and ensure role qualifiers are unique.
ODI-17905
Cube {0} is not bound to a datastore.
Category:
Programmatic
Cause:
A cube must be bound to a datastore to be viable.
Action:
Bind the cube to a datastore.
ODI-17906
Cube {0} with orphan management enabled is not bound to an error datastore.
Category:
Programmatic
Cause:
A cube must be bound to an error datastore to be viable when orphan management is enabled.
Action:
Bind the cube to an error datastore.
ODI-17907
In cube {0}, measure {1} is not bound to a column of the cube bound datastore.
Category:
Programmatic
Cause:
The measure must be bound to a column of the cube bound datastore.
Action:
Bind each measure to a column of the cube bound datastore.
ODI-17908
In cube {0}, measure {1} is not bound to an error column of the cube bound error datastore when orphan management is enabled.
Category:
Programmatic
Cause:
The measure must be bound to an error column of the cube bound error datastore when orphan management is enabled.
Action:
Bind each measure to an error column of the cube bound error datastore.
ODI-17909
Cube {0} is bound to datastore {1}, but measure {2} is bound to column {3} which is owned by datastore {4}.
Category:
Programmatic
Cause:
The measure is bound to a column which is owned by a different datastore to the one bound to the cube.
Action:
Bind each measure to a column which is owned by the cube bound datastore.
ODI-17910
Cube {0} is bound to error datastore {1}, but measure {2} is bound to error column {3} which is owned by datastore {4}.
Category:
Programmatic
Cause:
The measure is bound to an error column which is owned by a different error datastore to the one bound to the cube.
Action:
Bind each measure to an error column which is owned by the cube bound error datastore.
ODI-17911
Cube {0} reference to dimension {1} does not have a key reference.
Category:
Programmatic
Cause:
The cube is missing a key reference for one of the dimensions.
Action:
Ensure the cube references the key for each dimension.
ODI-17912
Cube {0} reference to dimension {1}, level {2} has a surrogate key, but the key reference does not point to this surrogate key.
Category:
Programmatic
Cause:
The cube has a key reference that does not point to the surrogate key of the dimension level.
Action:
Ensure the cube references the surrogate key if the dimension level has a surrogate key.
ODI-17913
In cube {0}, the key reference for dimension {1} is not bound to a column of the cube bound datastore.
Category:
Programmatic
Cause:
The key reference for a dimension must be bound to a column of the cube bound datastore.
Action:
Bind each key reference to a column of the cube bound datastore.
ODI-17914
In cube {0}, the key reference for dimension {1} is not bound to an error column of the cube bound error datastore when orphan management is enabled.
Category:
Programmatic
Cause:
The key reference for a dimension must be bound to an error column of the cube bound error datastore when orphan management is enabled.
Action:
Bind each key reference to an error column of the cube bound error datastore.
ODI-17915
Cube {0} is bound to datastore {1}, but key reference for dimension {2} is bound to column {3} which is owned by datastore {4}.
Category:
Programmatic
Cause:
The key reference for a dimension is bound to a column which is owned by a different datastore to the one bound to the cube.
Action:
Ensure each key reference is bound to a column of the cube bound datastore.
ODI-17916
Cube {0} is bound to an error datastore {1}, but key reference for dimension {2} is bound to an error column {3} which is owned by datastore {4}.
Category:
Programmatic
Cause:
The key reference for a dimension is bound to an error column which is owned by a different datastore to the one bound to the cube.
Action:
Ensure each key reference is bound to an error column of the cube error bound datastore.
ODI-17917
In cube {0}, multiple dimension key references or measures are bound to the same column {1} of the cube bound datastore.
Category:
Programmatic
Cause:
Multiple dimension key references or measures of the cube are bound to a same column of the cube bound datastore.
Action:
Ensure each dimension key reference and each measure is bound to a separate column of the cube bound datastore.
ODI-17918
In cube {0}, multiple dimension key references or measures are bound to the same error column {1} of the cube bound error datastore.
Category:
Programmatic
Cause:
Multiple dimension key references or measures of the cube are bound to a same error column of the cube bound error datastore.
Action:
Ensure each dimension key reference and each measure is bound to a separate error column of the cube bound error datastore.
ODI-17919
There is no primary key to foreign key constraint defined in ODI between the cube table {0} and the dimension table {1}.
Category:
Programmatic
Cause:
ODI looks for primary key and foreign key references between dimension tables and cube tables. For cube table there is no foreign key to the dimension table.
Action:
Define a foreign key on the cube table that references the primary key on the dimension table.
ODI-17920
Dimension {0} does not have any levels.
Category:
Programmatic
Cause:
The dimension does not have any levels.
Action:
Create one or more levels for this dimension.
ODI-17921
In Dimension {0}, level {1} does not have any level attributes.
Category:
Programmatic
Cause:
The level does not have level attributes.
Action:
Create one or more level attributes for this level.
ODI-17922
In datastore {0}, attribute {1} is bound by more than one level attribute or parent reference members: {2}.
Category:
Programmatic
Cause:
One datastore attribute is bound by multiple level attributes or parent reference members; it should only be bound once.
Action:
Rebind the other level attributes or parent reference members to other datastore attributes.
ODI-17923
In Dimension {0}, hierarchy {1} contains either only one level or no levels.
Category:
Programmatic
Cause:
The hierarchy contains only one level or no levels.
Action:
The hierarchy should contain two or more levels.
ODI-17924
Dimension {0} has more than one level but no hierarchy defined.
Category:
Programmatic
Cause:
The dimension has more than one level but no hierarchy defined.
Action:
The dimension can have a single level with no hierarchies or all levels must be contained in at least one hierarchy.
ODI-17925
In dimension {0}, level {1} does not have any natural key.
Category:
Programmatic
Cause:
The level does not have any natural key.
Action:
Create a natural key for this level.
ODI-17927
In dimension {0}, level {1} does not have any updatable attributes. An updatable attribute is defined as level attribute that is not surrogate key or natural key.
Category:
Programmatic
Cause:
The level does not have any updatable attributes.
Action:
Define one or more updatable attributes for this level.
ODI-17929
Dimension {0} flagged as a star implementation is not bound to a datastore.
Category:
Programmatic
Cause:
The dimension flagged as a star implementation must be bound to a datastore.
Action:
Bind the dimension to a datastore.
ODI-17930
Dimension {0} is flagged as a snowflake implementation, but level {1} is not bound to a datastore.
Category:
Programmatic
Cause:
The dimension is flagged as a snowflake implementation, but the level is not bound to a datastore.
Action:
Bind the level to a datastore.
ODI-17931
In dimension {0}, level {1} is not bound to a staging datastore.
Category:
Programmatic
Cause:
The dimension level is not bound to a staging datastore.
Action:
Bind the level to a staging datastore.
ODI-17932
Dimension {0} is flagged as a star implementation and the orphan management is enabled, but the dimension is not bound to an error datastore.
Category:
Programmatic
Cause:
The dimension is flagged as a star implementation and the orphan management is enabled, but the dimension is not bound to an error datastore.
Action:
Bind the dimension to an error datastore.
ODI-17933
Dimension {0} is flagged as a snowflake implementation and the orphan management is enabled, but level {1} is not bound to an error datastore.
Category:
Programmatic
Cause:
The dimension is flagged as a snowflake implementation and the orphan management is enabled, but the level is not bound to an error datastore.
Action:
Bind the level to an error datastore.
ODI-17934
In dimension {0} level {1}, level attribute {2} is not bound to a column of the bound datastore.
Category:
Programmatic
Cause:
The level attribute is not bound to a column of the bound datastore.
Action:
Bind the level attribute to a column of the bound datastore.
ODI-17935
In dimension {0} level {1}, level attribute {2} is not bound to a staging column of the bound staging datastore.
Category:
Programmatic
Cause:
The level attribute is not bound to a staging column of the bound stating datastore.
Action:
Bind the level attribute to a staging column of the bound staging datastore.
ODI-17936
In dimension {0} level {1}, level attribute {2} is not bound to an error column of the bound error datastore.
Category:
Programmatic
Cause:
The level attribute is not bound to an error column of the bound error datastore.
Action:
Bind the level attribute to an error column of the bound error datastore.
ODI-17937
In dimension {0}, level {1} is bound to datastore {2}, but level attribute {3} is bound to column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to a datastore, but a level attribute is bound to a column which is owned by another datastore.
Action:
Bind the level attribute to a column which is owned by the datastore that is bound to the level.
ODI-17938
In dimension {0}, level {1} is bound to staging datastore {2}, but level attribute {3} is bound to staging column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to a staging datastore, but a level attribute is bound to a staging column which is owned by another datastore.
Action:
Bind the level attribute to a staging column which is owned by the staging datastore that is bound to the level.
ODI-17939
In dimension {0}, level {1} is bound to error datastore {2}, but level attribute {3} is bound to error column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to an error datastore, but a level attribute is bound to an error column which is owned by another datastore.
Action:
Bind the level attribute to an error column which is owned by the error datastore that is bound to the level.
ODI-17941
Dimension {0} uses surrogate key but bound datastore {1} does not have primary key constraint.
Category:
Programmatic
Cause:
The dimension uses a surrogate key, but the datastore that is bound to the dimension does not have a primary key constraint.
Action:
Define a primary key constraint for the datastore that is bound to the dimension.
ODI-17942
Dimension {0} uses surrogate key but bound datastore {1} of level {2} does not have primary key constraint.
Category:
Programmatic
Cause:
The dimension uses a surrogate key, but the datastore that is bound to the level does not have a primary key constraint.
Action:
Define a primary key constraint for the datastore that is bound to the level.
ODI-17943
In dimension {0} level {1}, parent reference member {2} is not bound to a column.
Category:
Programmatic
Cause:
In the dimension, the parent ref member is not bound to a column.
Action:
Bind the parent reference member to a column.
ODI-17944
In dimension {0} level {1}, parent reference member {2} is not bound to a staging column.
Category:
Programmatic
Cause:
In dimension, the parent ref member is not bound to a staging column.
Action:
Bind the parent reference member to a staging column.
ODI-17945
In dimension {0} level {1}, parent reference member {2} is not bound to an error column.
Category:
Programmatic
Cause:
In dimension, the parent ref member is not bound to an error column.
Action:
Bind the parent reference member to an error column.
ODI-17946
In dimension {0} level {1} is bound to datastore {2}, but parent reference member {3} is bound to staging column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to a datastore, but a parent reference member is bound to a column which is owned by another datastore.
Action:
Bind the parent reference member to a column which is owned by the datastore that is bound to the level.
ODI-17947
In dimension {0} level {1} is bound to staging datastore {2}, but parent reference member {3} is bound to column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to a staging datastore, but a parent reference member is bound to a staging column which is owned by another datastore.
Action:
Bind the parent reference member to a staging column which is owned by the staging datastore that is bound to the level.
ODI-17948
In dimension {0} level {1} is bound to error datastore {2}, but parent reference member {3} is bound to error column {4} which is owned by datastore {5}.
Category:
Programmatic
Cause:
The level is bound to an error datastore, but a parent reference member is bound to an error column which is owned by another datastore.
Action:
Bind the parent reference member to an error column which is owned by the error datastore that is bound to the level.
ODI-17949
Dimension {0} is flagged as a snowflake implementation, in level {1}, the bound column of parent reference member {2} does not have foreign key constraint.
Category:
Programmatic
Cause:
The dimension is flagged as a snowflake implementation, in the level, the bound column of a parent reference member {2} does not have a foreign key constraint.
Action:
Define foreign key constraints for the columns that are bound to the parent reference members.
ODI-17950
In dimension {0} parent reference member {1}, the datatype of {3} of referenced level attribute {2} does not match with the datatype {5} of bound column {4}.
Category:
Programmatic
Cause:
For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound column.
Action:
The datatype of the referenced level attribute should match with that of the bound datastore column.
ODI-17953
In dimension {0} parent reference member {1}, the datatype {3} of referenced level attribute {2} does not match with the datatype {5} of bound staging column {4}.
Category:
Programmatic
Cause:
For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound staging column.
Action:
The datatype of the referenced level attribute should match with that of the bound staging datastore column.
ODI-17956
In dimension {0} parent reference member {1}, the datatype {3} of referenced level attribute {2} does not match with the datatype {5} of bound error column {4}.
Category:
Programmatic
Cause:
For the parent reference member, the datatype of the referenced level attribute does not match with that of the bound error column.
Action:
The datatype of the referenced level attribute should match with that of the bound error datastore column.
ODI-17959
Dimension {0} has an invalid cyclical parent/child level relationship involving parent reference {1}.
Category:
Programmatic
Cause:
One of the parent/child relationships reverses the order of another parent/child relationship, this is not allowed.
Action:
Fix the parent/child relationships for the dimension.
ODI-17960
In dimension {0} hierarchy {1}, the hierarchy member for level {2} uses parent reference {3}, which points to level {4} that is not included in this hierarchy.
Category:
Programmatic
Cause:
The hierarchy member uses the parent reference which points to the level that is not included in hierarchy.
Action:
Fix the hierarchy member to use a different parent reference or add a level to the hierarchy.
ODI-17961
In dimension {0} level {1}, the datatype {3} of level attribute {2} is does not match with the datatype {5} of bound column {4}.
Category:
Programmatic
Cause:
The datatype of the level attribute does not match with that of the bound column.
Action:
The datatype of the level attribute should match with that of the bound datastore column.
ODI-17964
In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of bound staging column {4}.
Category:
Programmatic
Cause:
The datatype of the level attribute does not match with that of the bound staging column.
Action:
The datatype of the level attribute should match with that of the bound staging datastore column.
ODI-17967
In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of bound error column {4}.
Category:
Programmatic
Cause:
The datatype of the level attribute does not match with that of the bound error column.
Action:
The datatype of the level attribute should match with that of the bound error datastore column.
ODI-17970
Dimension {0} is flagged as a star implementation, but parent reference {1} member {2} is not bound to the same column {3} as the matching parent level key attribute {4}.
Category:
Programmatic
Cause:
The dimension is star implementation, but one or more parent reference members is not bound to the same column as the matching parent level key attribute.
Action:
Bind the parent reference member to the column which is also bound to the matching parent level key attribute.
ODI-17971
In dimension {0} level {1}, attribute {2} is defined as a surrogate or natural key but is also flagged as having an SCD2 role (e.g. start date or trigger, etc.). This is not allowed.
Category:
Programmatic
Cause:
In SCD type 2, a key attribute cannot be flagged as a date or trigger attribute.
Action:
Do not define a key attribute as an SCD2 flag(e.g. date or trigger).
ODI-17972
In dimension {0}, if any of SCD2 trigger history, SCD2 effective time or SCD2 expiration time is set for a level {1}, then all of them must be set.
Category:
Programmatic
Cause:
In the dimension, if any of SCD2 trigger history, SCD2 effective time or SCD2 expiration time is set for a level, then all of them must be set.
Action:
Set SCD2 trigger history, SCD2 effective time and SCD2 expiration time for the level.
ODI-17973
In dimension {0}, SCD2 is enabled, but surrogate key is not used.
Category:
Programmatic
Cause:
In the dimension, SCD2 is enabled, but surrogate key is not used.
Action:
The dimension should use surrogate key if SCD2 is enabled.
ODI-17974
In dimension {0}, SCD2 is enabled for non-leaf level {1}, but hierarchy versioning is not enabled between level {1} and {2}. The versioning of non-leaf level {1} will not result in the versioning of its corresponding child records in level {2}.
Category:
Programmatic
Cause:
In the dimension, SCD2 is enabled for non-leaf level, but hierarchy versioning is not enabled.
Action:
Enable hierarchy versioning, otherwise the versioning of non-leaf level will not result in the versioning of its corresponding child records.
ODI-17975
In dimension {0} level {1}, a key attribute {2} is flagged as role playing(date or trigger, etc.). This is not allowed.
Category:
Programmatic
Cause:
In SCD type 3, a key attribute cannot be flagged as a date or trigger attribute.
Action:
Do not define a key attribute as an SCD3 flag(e.g. date or trigger).
ODI-17976
In dimension {0} level {1}, the datatype {3} of level attribute {2} does not match with the datatype {5} of SCD3 previous attribute {4}.
Category:
Programmatic
Cause:
In the dimension, the datatype of the level attribute does not match with that of the SCD3 previous attribute.
Action:
The datatype of the level attribute should match with that of the SCD3 previous attribute.
ODI-17979
Parameter {0} already exists
Category:
Programmatic
Cause:
Parameter {0} already exists
Action:
Use setValue() method to update the existing Parameter
ODI-17980
An operation with the name ''{0}'' already exists in ''{1}''.
Category:
Programmatic
Cause:
REST operation with same name.
Action:
Check REST operation name.
ODI-17981
REST operation with the name ''{0}'' does not exists in ''{1}''.
Category:
Programmatic
Cause:
REST operation does not exist.
Action:
Check REST operation name.
ODI-17982
Base KM type is incorrect.
Category:
Programmatic
Cause:
Base KM type is incorrect.
Action:
Set the Base KM with the correct type.
ODI-17983
It is not allowed for line defined in {0} referencing {1} line.
Category:
Programmatic
Cause:
Either line type is not same or the lines are self referencing.
Action:
Set the correct line.
ODI-17984
Line type is null.
Category:
Programmatic
Cause:
KM line type is null.
Action:
Set the correct line type.
ODI-17985
In dimension {0} level {1}, the attribute {2} is defined as part of the natural key, it cannot also be of type SCD3 at the same time.
Category:
Programmatic
Cause:
In the dimension, a level attribute is set as both natural key and SCD3 at the same time.
Action:
Either remove the SCD3 setting or remove this attribute from the natural key.
ODI-17986
In dimension {0} level {1}, level attribute {2} can not be flagged as an SCD3 previous value for more than one attribute nor as both a previous value and an effective date.
Category:
Programmatic
Cause:
In the dimension, a level attribute is set as an SCD3 previous value for more than one attribute or as both a previous value and as an effective date.
Action:
Correct the multiple SCD3 role uses of this attribute.
ODI-17987
In dimension {0} level {1}, level attribute {2} can not have both a SCD2 setting (date or trigger, etc.) and be used in an SCD3 role (previous value or effective date).
Category:
Programmatic
Cause:
In the dimension, a level attribute has both an SCD2 setting and is used in an SCD3 role.
Action:
Either remove this attribute's SCD2 setting or its uses as an SCD3 role.
ODI-17988
In dimension {0} level {1}, level attribute {2} can not have an SCD2 setting (date or trigger, etc.) and have SCD3 type attributes (previous value or effective date) set for it.
Category:
Programmatic
Cause:
In the dimension, a level attribute has an SCD2 setting and has SCD3 type attributes set for it.
Action:
Either remove this attributes SCD3 type attributes or remove its SCD2 setting.
ODI-17989
In dimension {0} level {1}, level attribute {2} can not be used as an SCD3 role attribute (previous value or effective date) and have SCD3 type attributes at the same time.
Category:
Programmatic
Cause:
In the dimension, a level attribute is used as an SCD3 role attribute and has SCD3 type attributes at the same time.
Action:
Either remove this attribute's SCD3 role usages or the SCD3 type attributes.
ODI-17990
In dimension {0}, level {1}, for level attribute {2} if the SCD3 effective date is set, the previous value must also be set.
Category:
Programmatic
Cause:
In the dimension, a level attribute has the SCD3 effective date set but has no previous value set.
Action:
Either remove this attribute's SCD3 effective date or add the SCD3 previous value.
ODI-17991
In dimension {0} level {1}, level attribute {2} is set as both the surrogate key and the natural key.
Category:
Programmatic
Cause:
In the dimension, can not set one attribute to surrogate key and natrual key both.
Action:
Reset either the surrogate key or the natural key.
ODI-17992
Model {0} is not a Generic Model
Category:
Programmatic
Cause:
Cannot map a Non-Generic Model to a Non-Generic Model
Action:
Provide a Generic Model to map
ODI-17993
Model {0} is not a Non-Generic Model
Category:
Programmatic
Cause:
Cannot map a Generic Model to a Generic Model
Action:
Provide a Non-Generic Model to map
ODI-17994
Invalid Sort by Position value: {0}
Category:
Programmatic
Cause:
Invalid value was provided for Hive Sort By Position
Action:
Provide a value >=1 or null
ODI-17995
This operation is not supported on {0} Technology
Category:
Programmatic
Cause:
This operation is not supported on the Technology of the Data Store
Action:
Please refer to documentation for supported Technologies
ODI-17996
Qualified Knowledge Module name {0} is invalid.
Category:
Programmatic
Cause:
KM qualified name is invalid
Action:
Provide a valid qualified KM Name
ODI-17997
Knowledge Module not found {0}
Category:
Programmatic
Cause:
KM with the given name not found
Action:
Provide a valid KM name
ODI-17998
Knowledge Module Line not found {0}
Category:
Programmatic
Cause:
KM Line with the given name not found
Action:
Provide a valid KM Line name
ODI-17999
Invalid language name or {0} Technology not set for KM.
Category:
Programmatic
Cause:
Language name is invalid or Technology not set for the KM.
Action:
Set valid language name and set KM source or target technology.
ODI-18000
In dimension {0} level {1}, the attribute {2} is defined as the surrogate key, it cannot also be of type SCD3.
Category:
Programmatic
Cause:
In the dimension, a level attribute is set as both surrogate key and SCD3 at the same time.
Action:
Remove the SCD3 setting from the surrogate key
ODI-18001
Cannot add new operation to BICS Physical Schema.
Category:
Programmatic
Cause:
User is trying to add new operation to BICS Physical Schema.
Action:
Adding new operation is not supported, please Contact Oracle support
ODI-18002
Cannot remove operation from BICS Physical Schema.
Category:
Programmatic
Cause:
User is trying to remove existing operation from BICS Physical Schema.
Action:
Removing operation is not supported, please Contact Oracle support
ODI-18003
Cannot delete mandatory property [{0}] from Data Server
Category:
Programmatic
Cause:
User is trying to delete a mandatory property from the Data Server
Action:
Mandatory properties cannot be deleted
ODI-18004
Invalid value specified for Data Server Property [{0}]. Permitted Values are: {1}
Category:
Programmatic
Cause:
User is trying to specify an invalid value for the Data Server property
Action:
Specify valid property value
ODI-18005
Language is not supported by the technology of this KM template or technology is not set for this KM template.
Category:
Programmatic
Cause:
Language is invalid for the technology set or technology not set for this KM template.
Action:
Set a language which is supported by the technology of this KM template.
ODI-18006
There are no unused levels remaining.
Category:
Programmatic
Cause:
No remaining levels to add to the hierarchy.
Action:
All levels are already part of this hierarchy.
ODI-18007
This level has no remaining parent references.
Category:
Programmatic
Cause:
All parent references for this level are already in use.
Action:
An unused parent reference is required in order to define a skip level.
ODI-18008
All attributes available for use in the natural key have already been set as members.
Category:
Programmatic
Cause:
There are no attributes remaining to participate in the natural key.
Action:
An unused attribute is required in order to add a natural key member.
ODI-18009
The line cannot be moved because the "before" or "after" line does not belong to this KM. A resolved base line is passed to the method.
Category:
Other
Cause:
Wrong KM line.
Action:
Check which KM owns the line.
ODI-18010
The "before" or "after" line has been deleted or is null. An invalid 'before' or 'after' line was passed to the move method.
Category:
Other
Cause:
Invalid line.
Action:
Check whether the line is not deleted or null
ODI-18011
Template Name "{0}" is already used with same combination of Technology and Language
Category:
Other
Cause:
A name already used with combination of same technology and Language
Action:
Change name.
ODI-18012
Failed to persist property {0} while persisting data server for Object Storage.
Category:
Other
Cause:
Contact Oracle support.
Action:
Contact Oracle support.
ODI-18013
Failed to retrieve credential information from Wallet for given connection information while creating Data Server
Category:
Security
Cause:
Contact Oracle support.
Action:
Contact Oracle support.
ODI-18014
Wallet file {0} is not found at specified location.
Category:
Security
Cause:
Wallet file is not present.
Action:
Please check Wallet file is present at specified location.
ODI-18015
Incorrect Wallet password.
Category:
Security
Cause:
Provided Wallet password is incorrect.
Action:
Please enter correct Wallet password.
ODI-18016
Wallet file {0} is not accessible .
Category:
Security
Cause:
Wallet file is not accesible.
Action:
Please check Wallet file permission.
ODI-18017
Invalid Credential file type : {0}. Please upload valid Credential file.
Category:
Security
Cause:
Credential file is not valid.
Action:
Please upload valid Credential file.
ODI-18018
Wallet file {0} does not contain credentials for given connection information.
Category:
Security
Cause:
Wallet file doesnot have required information.
Action:
Please add credential information to Wallet file for given connection information.
ODI-18019
Credential file {0} does not contain connection information.
Category:
Security
Cause:
tnsnames.ora file doesnot have required information.
Action:
Please add required connection information.
ODI-18020
Credential file {0} is not accessible.
Category:
Security
Cause:
Credential file doesnot have required permission.
Action:
Please add required permission.
ODI-18021
Failed to perform {0} on Storage CS.
Category:
Other
Cause:
Contact Oracle Support Services.
Action:
Contact Oracle Support Services.
ODI-18022
Regeneration failed. User does not have Regenerate privilege.
Category:
Other
Cause:
User does not have regenerate privilege
Action:
Please grant regenerate privilege.
ODI-20001
ODI-20001: Cannot check the key because the Datastore does not exist in the database.
Category:
Other
Cause:
The Datastore referenced by this key did not exist in the database.
Action:
Ensure the Datastore refers to an existing database table.
ODI-20002
ODI-20002: The selected file is not a valid key file.
Category:
Other
Cause:
An invalid encryption key file was selected.
Action:
Select a valid encryption key file.
ODI-20003
ODI-20003: Cannot edit the condition
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20004
ODI-20004: Cannot edit the reference
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20005
ODI-20005: Cannot edit the variable
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20006
ODI-20006: Cannot display table's data. Data is probably already displayed.
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20007
ODI-20007: Cannot display table's data.
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20008
ODI-20008: You cannot Display this Attribute Data. Data is probably already displayed
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20009
ODI-20009: Cannot display data. The datastore resource name is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.
Category:
Other
Cause:
The datastore resource name exceeded the limit allowed by its technology.
Action:
Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing the datastore resource name to comply.
ODI-20010
ODI-20010: Cannot display this Attribute Data
Category:
Other
Cause:
General Exception invoking editor.
Action:
This is an internal error with no recommended user action.
ODI-20011
ODI-20011: Cannot perform this action: a Column of this Datastore is currently being edited
Category:
Other
Cause:
Another user may be editing this datastore.
Action:
Wait for the other editing session to be committed.
ODI-20012
ODI-20012: Cannot perform this action: the Datastore containing this Column is currently being modified
Category:
Other
Cause:
Another user may be editing this datastore.
Action:
Wait for the other editing session to be committed.
ODI-20013
ODI-20013: Unable to perform the action because the package is currently being modified
Category:
Other
Cause:
Another user may be editing this package.
Action:
Wait for the other editing session to be committed.
ODI-20014
ODI-20014: Cannot encrypt the Procedure: it is currently being modified
Category:
Other
Cause:
Another user may be editing this procedure.
Action:
Wait for the other editing session to be committed.
ODI-20015
ODI-20015: Cannot initialize the Flexfields values
Category:
Other
Cause:
Another user may be editing the flexfield values.
Action:
Wait for the other editing session to be committed.
ODI-20016
ODI-20016: Unable to add project user functions
Category:
Other
Cause:
An unsupported action was attempted.
Action:
No action required as Project user functions are not a valid selection to be added to a label.
ODI-20017
ODI-20017: Unable to add project sequences
Category:
Other
Cause:
An unsupported action was attempted.
Action:
No action required as Project sequences are not a valid selection to be added to a label.
ODI-20018
ODI-20018: Unable to add project variables
Category:
Other
Cause:
An unsupported action was attempted.
Action:
No action required as Project variables are not a valid selection to be added to a label.
ODI-20019
ODI-20019: Unable to get GBO object
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20020
ODI-20020: Cannot change CKM
Category:
Other
Cause:
Only one CKM is available.
Action:
Import additional CKMs.
ODI-20021
ODI-20021: Cannot change the order of this Command because you do not have 'Edit' privileges on this Object
Category:
Other
Cause:
Insufficient privileges to edit the object.
Action:
Assign additional privileges to edit the object.
ODI-20022
ODI-20022: Could not change the KM
Category:
Other
Cause:
Additional KMs may not be available or installed for the current technology.
Action:
Import additional KMs.
ODI-20024
ODI-20024: Cannot create the cross reference for the condition
Category:
Other
Cause:
Internal error creating cross references for a condition.
Action:
No action required.
ODI-20025
ODI-20025: Cannot create the cross references for the reference
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20026
ODI-20026: Cannot view this Datastore: one of its Columns is currently being edited
Category:
Other
Cause:
The data store is being edited in another session.
Action:
Wait for the other editing session to end.
ODI-20027
ODI-20027: Cannot view this Column: its Datastore is currently being edited
Category:
Other
Cause:
A package step is being edited in another session.
Action:
Wait for the other session to end.
ODI-20028
ODI-20028: Cannot start execution.
Category:
Other
Cause:
Execution cannot be started due to an internal error.
Action:
No required action.
ODI-20029
ODI-20029: Cannot move a line
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20030
ODI-20030: Cannot start the generation. The file is probably already open.
Category:
Other
Cause:
Attempt to open report file for output failed.
Action:
Ensure the specified file is not currently open and the file permissions allow for write access before retrying the operation. Consider choosing a different file for output.
ODI-20031
ODI-20031: Cannot Delete a Command being Edited.
Category:
Other
Cause:
An attempt was made to delete a command being edited.
Action:
Save the edit before deleting.
ODI-20032
ODI-20032: Cannot Delete a Command
Category:
Other
Cause:
Internal error.
Action:
No required action
ODI-20033
ODI-20033: Cannot find the KM description
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20034
ODI-20034: Cannot find the Options list for a Command
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20035
ODI-20035: Could not find a description for the KM
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20036
ODI-20036: Impossible to find the technology name, please check your privileges.
Category:
Other
Cause:
The ODI security permissions were insufficient to allow access to the specified technology.
Action:
Ensure the ODI user security permissions are correct.
ODI-20037
ODI-20037: Cannot find data transferred by the Drag'n'Drop
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20038
ODI-20038: Could not connect
Category:
Other
Cause:
A connection was not established to the selected Logical Schema.
Action:
Ensure the connection data for the Physical Schema of the selected Logical Schema is valid.
ODI-20039
ODI-20039: Incorrect context
Category:
Other
Cause:
A context was not chosen for execution.
Action:
Select an execution context.
ODI-20040
ODI-20040: Problem encountered when determining the context
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20041
ODI-20041: No candidate datastore was found. Please create a mapping which loads data into this datastore.
Category:
Other
Cause:
There were no datastores in the current model usable as candidates for generating OUT mappings.
Action:
Consider creating an mapping to load data into a datastore of the current model.
ODI-20042
ODI-20042: Property key is empty
Category:
Other
Cause:
The Property key for one of the specified Data Server's properties was not specified.
Action:
Ensure a non-empty key value is supplied or remove the property with this key.
ODI-20043
ODI-20043: Invalid property key entered. Property key maximum length is 250 characters
Category:
Other
Cause:
The Property key for one of the specified Data Server's properties had a length greater than 250 characters.
Action:
Ensure a key value with the valid length is supplied or remove the property with this key.
ODI-20044
ODI-20044: Invalid property value entered. Property value maximum length is 250 characters
Category:
Other
Cause:
The Property value for one of this Data Server's properties had a length greater than 250 characters.
Action:
Ensure a value with the valid length is supplied or remove the property with this value.
ODI-20046
ODI-20046: Unable to change an open object
Category:
Other
Cause:
An object is already open in another editor and cannot be modified.
Action:
Close any other editors which may be locking the object.
ODI-20047
ODI-20047: Unable to change Value
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20048
ODI-20048: Invalid Value entered. Value maximum length is 250 characters
Category:
Other
Cause:
The Value for one of this object's Flexfields had a length greater than 250 characters.
Action:
Ensure the value supplied has a valid length.
ODI-20049
ODI-20049: You cannot copy a folder into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Folders cannot be copied into hierarchy of another projects.
ODI-20050
ODI-20050: You cannot copy a knowledge module into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be copied into hierarchy of another projects.
ODI-20051
ODI-20051: You cannot copy a package into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Packages cannot be copied into hierarchy of another projects.
ODI-20052
ODI-20052: You cannot copy an interface into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be copied into hierarchy of another projects.
ODI-20053
ODI-20053: You cannot copy a procedure into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be copied into hierarchy of another projects.
ODI-20054
ODI-20054: You cannot move a folder into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Folders cannot be moved into hierarchy of another projects.
ODI-20055
ODI-20055: You cannot move a knowledge module into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be moved into hierarchy of another projects.
ODI-20056
ODI-20056: You cannot move a package into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Packages cannot be moved into hierarchy of another projects.
ODI-20057
ODI-20057: You cannot move an interface into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be moved into hierarchy of another projects.
ODI-20058
ODI-20058: You cannot move a procedure into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be moved into hierarchy of another projects.
ODI-20059
ODI-20059: You cannot copy a knowledge module into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be copied into packages from another projects.
ODI-20060
ODI-20060: You cannot copy an interface into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be copied into packages from another projects.
ODI-20061
ODI-20061: You cannot copy a procedure into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be copied into packages from another projects.
ODI-20062
ODI-20062: You cannot move a knowledge module into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be moved into packages from another projects.
ODI-20063
ODI-20063: You cannot move an interface into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be moved into packages from another projects.
ODI-20064
ODI-20064: You cannot move a step into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Package steps cannot be moved into packages from another projects.
ODI-20065
ODI-20065: You cannot move a procedure into a package belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be moved into packages from another projects.
ODI-20066
ODI-20066: You cannot copy a folder into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Folders cannot be copied into hierarchy of another projects.
ODI-20067
ODI-20067: You cannot copy a procedure into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be copied into hierarchy of another projects.
ODI-20068
ODI-20068: You cannot copy a variable into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Variables cannot be copied into hierarchy of another projects.
ODI-20069
ODI-20069: You cannot move a folder into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Folders cannot be moved into hierarchy of another projects.
ODI-20070
ODI-20070: You cannot move a sequence into another project. Copy the sequence instead.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Sequences cannot be moved into hierarchy of another projects.
ODI-20071
ODI-20071: You cannot move a procedure into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be moved into hierarchy of another projects.
ODI-20072
ODI-20072: You cannot move a variable into another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Variables cannot be moved into hierarchy of another projects.
ODI-20073
ODI-20073: You cannot copy a schedule into a scenario belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Schedules cannot be copied into hierarchy of another projects.
ODI-20074
ODI-20074: You cannot move a schedule into a scenario belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Schedules cannot be moved into hierarchy of another projects.
ODI-20075
ODI-20075: You cannot move a folder into one of its subfolders.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Folders cannot be moved into their subfolders.
ODI-20076
ODI-20076: You cannot copy a knowledge module into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be copied into package steps from another projects.
ODI-20077
ODI-20077: You cannot copy an interface into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be copied into package steps from another projects.
ODI-20078
ODI-20078: You cannot copy a procedure into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be copied into package steps from another projects.
ODI-20079
ODI-20079: You cannot move a knowledge module into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Knowledge modules cannot be moved into package steps from another projects.
ODI-20080
ODI-20080: You cannot move an interface into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Interfaces cannot be moved into package steps from another projects.
ODI-20081
ODI-20081: You cannot move a step into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Steps cannot be moved into package steps from another projects.
ODI-20082
ODI-20082: You cannot move a procedure into a package step belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures cannot be moved into package steps from another projects.
ODI-20083
ODI-20083: Unable to perform the operation. {0} is being edited.
Category:
Other
Cause:
An object is being edited, preventing other operations.
Action:
Save or cancel editing of the object.
ODI-20084
ODI-20084: Only variables from the same project can be placed in a package.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Variables from another projects cannot be placed in packages.
ODI-20085
ODI-20085: Only mappings from the same project can be placed in a package.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Mappings from another project cannot be placed in packages.
ODI-20086
ODI-20086: Only procedures from the same project can be placed in a package.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Procedures from another projects cannot be placed in packages.
ODI-20087
ODI-20087: Error while duplicating
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20088
ODI-20088: Error while generating the scenario
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20089
ODI-20089: Error during parameter initialization
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20090
ODI-20090: Error while duplicating
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20091
ODI-20091: An unexpected error occurred.
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20092
ODI-20092: An error occurred while replacing the version.
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20093
ODI-20093: Scenario generation is not allowed for non-saved object
Category:
Other
Cause:
Scenario generation could not be performed because the source object was not saved.
Action:
Ensure the source object is saved before attempting scenario generation for it.
ODI-20094
ODI-20094: Specify the object name to generate Scenario
Category:
Other
Cause:
Scenario generation could not be performed because the source object's name was not specified.
Action:
Ensure the source object's name is specified before attempting scenario generation for it.
ODI-20095
ODI-20095: Marker Group save was cancelled
Category:
Other
Cause:
Marker group save was cancelled by a user.
Action:
No action required.
ODI-20096
ODI-20096: Unable to edit the action line.
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20097
ODI-20097: The line Name is mandatory
Category:
Other
Cause:
A value for the Action Line Name field was not specified.
Action:
Enter a non-empty value for the Action Line Name field.
ODI-20098
ODI-20098: Some Datatype Conversions between current and new Technologies are absent
Category:
Other
Cause:
Changing the selected Model's Technology failed because the Physical Architecture did not provide datatype conversion rules for datatypes used by attributes of datastores belonging to the selected model.
Action:
Ensure datatype conversion rules exist for all datatypes used by attributes of datastores belonging to the selected model or do not use datatypes that cannot be converted.
ODI-20099
ODI-20099: Unable to create execution window
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20100
ODI-20100: Unable to access a join or a filter
Category:
Other
Cause:
Access to a join or filter failed due to insufficient ODI security permissions.
Action:
Ensure the ODI user security permissions are correct for the join or filter object.
ODI-20101
ODI-20101: Unable to find mapping alias
Category:
Other
Cause:
Access to the target mapping failed due to insufficient ODI security permissions.
Action:
Ensure the ODI user security permissions are correct for the target mapping.
ODI-20102
ODI-20102: Unable to find source table alias
Category:
Other
Cause:
Access to the source table failed due to insufficient ODI security permissions.
Action:
Ensure the ODI user security permissions are correct for the source table.
ODI-20103
ODI-20103: Unable to access a target column
Category:
Other
Cause:
Access to the target column failed due to insufficient ODI security permissions.
Action:
Ensure the ODI user security permissions are correct for the target column.
ODI-20105
ODI-20105: "Schema", "Table", "Column" and "Filter" are mandatory fields.
Category:
Other
Cause:
Values for the mandatory "Schema", "Table", "Column" and "Filter" fields were not supplied.
Action:
Ensure values are supplied for these mandatory fields.
ODI-20106
ODI-20106: Schema and Native sequence name are mandatory fields
Category:
Other
Cause:
Values for the mandatory Schema and Native sequence name fields were not supplied.
Action:
Ensure values are supplied for these mandatory fields.
ODI-20107
ODI-20107: A project sequence with the name "{0}" already exists in the project "{1}"
Category:
Other
Cause:
Saving the project sequence failed because the Sequence name was not unique within the Project.
Action:
Ensure the sequence name entered is unique.
ODI-20108
ODI-20108: A global sequence with the name "{0}" already exists
Category:
Other
Cause:
Saving the Global sequence failed because the Global Sequence name was not unique.
Action:
Ensure the sequence name entered is unique.
ODI-20109
ODI-20109: Error while restoring the version
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-20110
ODI-20110: No version of this element exist.
Category:
Other
Cause:
The selected version of this object was not found in version repository.
Action:
Create or restore the selected version of the object.
ODI-20111
ODI-20111: Sub-model code cannot be empty.
Category:
Other
Cause:
A value of the mandatory Sub-model code field was not supplied.
Action:
Enter a non-empty value for the Sub-model code field.
ODI-20112
ODI-20112: The path defined in the logical schema is incorrect.
Category:
Other
Cause:
Incorrect path was specified in physical schema which is linked to the logical schema of this datastore in the current context.
Action:
Ensure the path specified in physical schema is correct.
ODI-20113
ODI-20113: The GUID that was supplied does not match the GUID for this user in the external identity store. Please retrieve the correct GUID before saving.
Category:
Other
Cause:
The supplied GUID did not match GUID from external identity store.
Action:
Provide a valid GUID.
ODI-20114
ODI-20114: Error while subscribing
Category:
Other
Cause:
An unexpected error occurred while trying to subscribe a datastore for CDC.
Action:
Review the error details for further information.
ODI-20115
ODI-20115: Error while stopping journalizing
Category:
Other
Cause:
An unexpected error occurred while trying to stop journalizing.
Action:
Review the error details for further information.
ODI-20116
ODI-20116: Aliases are specified and are not unique.
Category:
Other
Cause:
Duplicate Alises were detected.
Action:
Change the name of the join key alias.
ODI-20117
ODI-20117: Error while executing command line.
Category:
Other
Cause:
An unexpected error occurred while trying to open the Report.
Action:
Review the error details for further information.
ODI-20118
ODI-20118: Error while building the menu.
Category:
Other
Cause:
An unexpected error occurred while building a menu.
Action:
Review the error details for further information.
ODI-20119
ODI-20119: Error during generation.
Category:
Other
Cause:
An unexpected error occurred during the report generation.
Action:
Review the error details for further information.
ODI-20120
ODI-20120: Error while journalizing
Category:
Other
Cause:
An unexpected error occurred during journalizing.
Action:
Review the error details for further information.
ODI-20121
ODI-20121: Error while saving the diagram
Category:
Other
Cause:
An unexpected error occurred during the saving the diagram.
Action:
Review the error details for further information.
ODI-20122
ODI-20122: Error while unsubscribing
Category:
Other
Cause:
An unexpected error occurred during the unsubscribing action.
Action:
Review the error details for further information.
ODI-20123
ODI-20123: Error while executing query
Category:
Other
Cause:
An unexpected error occurred during query execution.
Action:
Check the error details for further actions.
ODI-20124
ODI-20124: Operation cancelled by user.
Category:
Other
Cause:
Operation cancelled by user
Action:
Review the other messages for further actions.
ODI-20126
ODI-20126: TreeTableColumn cannot be added
Category:
Other
Cause:
TreeTableColumn with this order number already exists
Action:
Contact Oracle Support Services.
ODI-20127
ODI-20127: This TreeTableColumn cannot be removed.
Category:
Other
Cause:
TreeTableColumn does not exist.
Action:
Contact Oracle Support Services.
ODI-20128
ODI-20128: Could not rollback.
Category:
Other
Cause:
An error occurred during rollback operation.
Action:
Review other messages for further information.
ODI-20129
ODI-20129: Exception occurred.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Review the error details for further information.
ODI-20130
ODI-20130: You must select a folder.
Category:
Other
Cause:
A folder was not selected.
Action:
Select a folder before attempting this action.
ODI-20131
ODI-20131: Cannot retrieve the table list
Category:
Other
Cause:
An error occured while trying to retrieve a list of tables.
Action:
Review the message log for more information. If problem persists contact Oracle Support Services.
ODI-20132
ODI-20132: An interface cannot be moved to another project
Category:
Other
Cause:
An unsupported drag and drop operation was attempted.
Action:
No action required.
ODI-20133
ODI-20133: A procedure cannot be moved to another project
Category:
Other
Cause:
An unsupported drag and drop operation was attempted.
Action:
No action required.
ODI-20134
ODI-20134: A variable cannot be moved to another project
Category:
Other
Cause:
An unsupported drag and drop operation was attempted.
Action:
No action required
ODI-20135
ODI-20135: A step cannot be moved to another package
Category:
Other
Cause:
An unsupported drag and drop operation was attempted.
Action:
No action required
ODI-20138
ODI-20138: An error occured during: dragGesture
Category:
Other
Cause:
An unexpected error occurred while dragging an object.
Action:
Review the message log for more information. If problem persists contact Oracle Support Services.
ODI-20139
ODI-20139: An error occured during: dragEnter
Category:
Other
Cause:
An unexpected error occurred during a drag operation.
Action:
Review the error details for further information.
ODI-20140
ODI-20140: An error occured during: Drop
Category:
Other
Cause:
An unexpected error occurred while dropping an object.
Action:
Review the message log for more information. If problem persists contact Oracle Support Services.
ODI-20141
ODI-20141: Login Creation Error
Category:
Other
Cause:
An unexpected error occurred while creating a new Login.
Action:
Review the error details for further information.
ODI-20142
ODI-20142: Popup Menu Creation Error
Category:
Other
Cause:
An unexpected error occurred while creating a popup menu.
Action:
Review the error details for further information.
ODI-20144
ODI-20144: Error while Deleting
Category:
Other
Cause:
An unexpected error occurred while deleting a tree object.
Action:
Review the error details for further information.
ODI-20145
ODI-20145: Error while Opening splitframe.
Category:
Other
Cause:
An unexpected error occurred opening a frame.
Action:
Review the error details for further information.
ODI-20146
ODI-20146: Error occured during duplication
Category:
Other
Cause:
An unexpected error occurred while duplicating an object.
Action:
Review the error details and message log for more information.
ODI-20148
ODI-20148: An error occured during: drag over the object
Category:
Other
Cause:
An unexpected error occurred while dragging an object over another object.
Action:
Review the error details and message log for more information.
ODI-20149
ODI-20149: Logical schema can't be undefined
Category:
Other
Cause:
A Logical schema was not defined.
Action:
Define a Logical schema.
ODI-20150
ODI-20150: KM or Procedure already encrypted. No encryption was performed.
Category:
Other
Cause:
The requested object has already been encrypted.
Action:
No action required.
ODI-20151
ODI-20151: File is not found. Invalid file location
Category:
Other
Cause:
The specified file could not be located in the file system.
Action:
Ensure file location specified is valid and accessible.
ODI-20152
ODI-20152: Object cannot be deleted
Category:
Other
Cause:
The specified object could not be deleted.
Action:
Ensure the specified object exists and the security permissions permit deletion.
ODI-20153
ODI-20153: The following field is missing: Syntax
Category:
Other
Cause:
User function syntax has not been specified.
Action:
Specify the function syntax.
ODI-20155
ODI-20155: Changing the Logical Schema may require a re-generation of your Mappings. It may be better to modify the Topology information instead.
Category:
Other
Cause:
Action:
ODI-20158
ODI-20158: Datastores distribution failed.
Category:
Other
Cause:
An error occured during the datastore distribution process.
Action:
Review the message details and message log for more information. If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
ODI-20159
ODI-20159: The Attribute {0} is used as a Reference
Category:
Other
Cause:
An attempt was made to delete an attribute referenced by another object.
Action:
Delete the object which references this attribute then retry deleting this attribute.
ODI-20160
ODI-20160: The table {0} does not exist.
Category:
Other
Cause:
An error occured while executing the SQL request
Action:
Review the message details for more information. If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
ODI-20161
ODI-20161: Standard reverse-engineering failed.
Category:
Other
Cause:
An error occured during the standard reverse-engineering process.
Action:
Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
ODI-20162
ODI-20162: The context is not valid.
Category:
Other
Cause:
A Context was not specified.
Action:
Specify a Context.
ODI-20163
ODI-20163: Unable to add object
Category:
Other
Cause:
An error occurred while dragging and dropping an object.
Action:
Review the message details and message log for more information.
ODI-20164
ODI-20164: The line Name is mandatory
Category:
Other
Cause:
A name was not specified.
Action:
Specify a Line name.
ODI-20165
ODI-20165: The project name {0} is a reserved word.
Category:
Other
Cause:
A reserved word was used as the name of a project.
Action:
Enter a different project name.
ODI-20166
ODI-20166: The project code {0} is a reserved word.
Category:
Other
Cause:
A reserved word was used as the project code.
Action:
Enter a different project code.
ODI-20167
ODI-20167: Logical schema is not set for the current context
Category:
Other
Cause:
A Logical schema was not set for the current context.
Action:
Ensure the Logical Schema is not set to "Undefined" in the Context editor.
ODI-20168
ODI-20168: Logical schema is not set for the current context
Category:
Other
Cause:
A Logical schema was not set for the current context.
Action:
Ensure the Logical Schema is not set to "Undefined" in the Context editor.
ODI-20169
ODI-20169: The field {0} is mandatory.
Category:
Other
Cause:
A mandatory field was not specified.
Action:
Enter a value for this field.
ODI-20170
ODI-20170: You are trying to insert this versioned object but the version was deleted. Please re-create a version for this object.
Category:
Other
Cause:
The requested version of the object did not exist in the repository.
Action:
Recreate the required version of this object.
ODI-20171
ODI-20171: The label already contains a child of {0}. To add {1} to the label, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the label's coherence.
Category:
Other
Cause:
The label already contained the specified object as a child.
Action:
Delete the child object from the label before retrying the addition. Consider using the synchronize option to verify the label's coherence.
ODI-20172
ODI-20172: The label already contains a parent of {0}. To add {1} to the label, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the label's coherence.
Category:
Other
Cause:
The label has already contained the specified object as a parent of {0}.
Action:
Delete the parent object from the label before retrying the addition. Consider using the synchronize option to verify the label's coherence.
ODI-20173
ODI-20173: An error occurred while generating the procedure
Category:
Other
Cause:
An unexpected error occurred while generating a procedure.
Action:
Review the error details for further information.
ODI-20174
ODI-20174: Folder {0} already contains an mapping named {1}
Category:
Other
Cause:
An mapping of the same name already existed in the specified folder.
Action:
Specify another name for the mapping.
ODI-20175
ODI-20175: You cannot give an empty name to an mapping
Category:
Other
Cause:
The Mapping's name was not specified.
Action:
Enter a non-empty value for the mapping's name.
ODI-20176
ODI-20176: You cannot create multiple mappings with the same name
Category:
Other
Cause:
An mapping of the same name already existed.
Action:
Specify a different name for the mapping.
ODI-20177
ODI-20177: You must select a generation folder
Category:
Other
Cause:
The Generation folder was not selected.
Action:
Select a generation folder.
ODI-20180
ODI-20180: You cannot choose an expiration date in the past.
Category:
Other
Cause:
Entered expiration date was in the past.
Action:
Enter valid expiration date.
ODI-20181
ODI-20181: You cannot set an expiration date if there is no password.
Category:
Other
Cause:
No password was entered.
Action:
Enter a password before setting an expiration date.
ODI-20182
ODI-20182: Error while opening window
Category:
Other
Cause:
An unexpected error occurred while opening a window.
Action:
Review the error details for further information.
ODI-20183
ODI-20183: Error while refreshing Label
Category:
Other
Cause:
An unexpected error occurred while refreshing a label.
Action:
Review the error details for further information.
ODI-20184
ODI-20184: The request to retrieve the sequence list has not been defined on the technology.
Category:
Other
Cause:
The query for retrieving sequences has not been defined for the technology.
Action:
Update the technology with the sequence query syntax.
ODI-20185
ODI-20185: Error while opening window
Category:
Other
Cause:
An unexpected error occurred while opening a window.
Action:
Review the error details for further information.
ODI-20186
ODI-20186: Error while saving
Category:
Other
Cause:
An unexpected error occurred while saving an object.
Action:
Review the error details for further information.
ODI-20187
ODI-20187: Error while adding the marker
Category:
Other
Cause:
An unexpected error occurred while adding a marker.
Action:
Review the error details for further information.
ODI-20188
ODI-20188: This object is locked by another user. You cannot edit its markers.
Category:
Other
Cause:
The object was locked by another user.
Action:
Wait until the object is unlocked. Consider contacting the user who has the object locked.
ODI-20189
ODI-20189: You do not have the sufficient privileges to reverse-engineer a model
Category:
Other
Cause:
The model could not be reverse-engineered due to insufficient privileges.
Action:
Ensure the SUPERVISOR or owner of model grants the appropriate permissions.
ODI-20190
ODI-20190: You cannot reverse engineer a model in 'Standard' mode: the model technology assumes RKM to be selected.
Category:
Other
Cause:
No RKM was specified for this model.
Action:
Select an RKM for this model.
ODI-20191
ODI-20191: The model you want to reverse-engineer references a logical schema that no longer exists.
Category:
Other
Cause:
The referenced Logical Schema for the Model was not found.
Action:
Ensure a valid Logical Schema is assigned for the Model.
ODI-20192
ODI-20192: Error while replacing versioned object
Category:
Other
Cause:
An unexpected error occurred while replacing a versioned object.
Action:
Review the error details for further information.
ODI-20193
ODI-20193: An error occurred during the versioning operation.
Category:
Other
Cause:
An unexpected error occurred during versioning.
Action:
Review the error details for further information.
ODI-20194
ODI-20194: Your license does not allow Versioning operations.
Category:
Other
Cause:
The license does not include versioning.
Action:
Upgrade the license.
ODI-20195
ODI-20195: Unable to unlock this object
Category:
Other
Cause:
An unexpected error occurred while unlocking an object.
Action:
Review the error details for further information.
ODI-20196
ODI-20196: You must select an object version
Category:
Other
Cause:
No version selected for checkout.
Action:
Select version for checkout.
ODI-20197
ODI-20197: Your license does not allow Versioning operations.
Category:
Other
Cause:
The current license does not inlude versioning.
Action:
Upgrade the license to include versioning.
ODI-20198
ODI-20198: Error while creating the version.
Category:
Other
Cause:
An unexpected error occurred while creating a version.
Action:
Review the error details for further information.
ODI-20199
ODI-20199: Your license does not allow Versioning operations.
Category:
Other
Cause:
The license does not include versioning.
Action:
Upgrade your license.
ODI-20200
ODI-20200: An error happened while comparing the versions
Category:
Other
Cause:
An unexpected error occurred while comparing versions.
Action:
Review the error details for further information.
ODI-20201
ODI-20201: Error while refreshing.
Category:
Other
Cause:
An unexpected error occurred while refreshing.
Action:
Review the error details for further information.
ODI-20202
ODI-20202: Synchronisation was stopped by the user.
Category:
Other
Cause:
Synchronization was stopped by the user.
Action:
No action is required.
ODI-20203
ODI-20203: The current version for this object no longer exists. Please create a new version for this object.
Category:
Other
Cause:
The current version for this object was not found in the repository.
Action:
Create a new version for this object.
ODI-20205
ODI-20205: Could not delete object. This object is being used.
Category:
Other
Cause:
The object deletion failed because it was already in use.
Action:
Remove the usage of the selected object before retrying the deletion.
ODI-20206
ODI-20206: Could not delete object. This object is being displayed.
Category:
Other
Cause:
The object deletion failed because it was being displayed.
Action:
Close object before retrying the deletion.
ODI-20208
ODI-20208: A code was duplicated:
Category:
Other
Cause:
A Flex field with the same code already existed.
Action:
Enter another Flex field code.
ODI-20209
ODI-20209: An error occurred.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Review the error details for further information.
ODI-20210
ODI-20210: Error When Printing...
Category:
Other
Cause:
An unexpected error occurred while printing.
Action:
Review the error details for further information.
ODI-20211
ODI-20211: Error When Displaying Node...
Category:
Other
Cause:
An unexpected error occurred while displaying a node.
Action:
Review the error details for further information.
ODI-20212
ODI-20212: An error occurred while checking errors
Category:
Other
Cause:
An unexpected error occurred while checking errors.
Action:
Review the error details for further information.
ODI-20213
ODI-20213: An error occurred while recovering an object in a node
Category:
Other
Cause:
An unexpected error occurred while recovering an object in a node.
Action:
Review the error details for further information.
ODI-20214
ODI-20214: An error occurred while deleting
Category:
Other
Cause:
An unexpected error occurred while deleting an object.
Action:
Review the error details for further information.
ODI-20216
ODI-20216: Error while deleting
Category:
Other
Cause:
An unexpected error occurred while deleting an object.
Action:
Review the error details for further information.
ODI-20217
ODI-20217: Error while executing the reverse-engineering
Category:
Other
Cause:
An unexpected error occurred while reverse engineering.
Action:
Review the error details for further information.
ODI-20218
ODI-20218: Error during duplication ...
Category:
Other
Cause:
An unexpected error occurred during duplication.
Action:
Review the error details for further information.
ODI-20219
ODI-20219: Error while opening
Category:
Other
Cause:
An unexpected error occurred while opening an object.
Action:
Review the error details for further information.
ODI-20220
ODI-20220: Error during data loading ....
Category:
Other
Cause:
An unexpected error occurred while loading data.
Action:
Review the error details for further information.
ODI-20221
ODI-20221: Error during execution ...
Category:
Other
Cause:
An unexpected error occurred during execution.
Action:
Review the error details for further information.
ODI-20222
ODI-20222: Error during scenario creation ...
Category:
Other
Cause:
An unexpected error occurred during scenario generation.
Action:
Review the error details for further information.
ODI-20223
ODI-20223: Error When Purging Log
Category:
Other
Cause:
An unexpected error occurred while purging the log.
Action:
Review the error details for further information.
ODI-20224
ODI-20224: An interface with the same name already exists in this folder. Please change the name of the new interface.
Category:
Other
Cause:
An interface with the same name already existed in this folder.
Action:
Specify another name for the interface.
ODI-20225
ODI-20225: Error while creating the popup menu
Category:
Other
Cause:
An unexpected error occurred while creating a popup menu.
Action:
Review the error details for further information.
ODI-20226
ODI-20226: Error while applying the changes
Category:
Other
Cause:
An unexpected error occurred while saving changes.
Action:
Review the error details for further information.
ODI-20227
ODI-20227: You cannot copy this attribute. Attribute name already in use.
Category:
Other
Cause:
Attribute copy failed because the Datastore already contained an attribute with the same name.
Action:
Select another attribute to drop to datastore.
ODI-20228
ODI-20228: Error while creating the popup menu
Category:
Other
Cause:
Retrieval of the Available Methods for the column failed.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20229
ODI-20229: Unable to create condition.
Category:
Other
Cause:
The editor for the Condition could not be opened.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20230
ODI-20230: Error while creating the popup menu
Category:
Other
Cause:
Retrieval of the Available Methods for the Condition failed.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20231
ODI-20231: Unable to create a synonym for this table.
Category:
Other
Cause:
An unexpected error occurred while creating a synonym.
Action:
Review the error details for further information.
ODI-20232
ODI-20232: Error while deleting attributes
Category:
Other
Cause:
An unexpected error occurred while deleting attributes.
Action:
Review the error details for further information.
ODI-20233
ODI-20233: Error during the drag-and-drop operation
Category:
Other
Cause:
An unexpected error occurred during a drag and drop operation.
Action:
Review the error details for further information.
ODI-20234
ODI-20234: You do not have the sufficient privileges to add this object.
Category:
Other
Cause:
The operation failed due to insufficient ODI security on Attribute.
Action:
Ensure the ODI user security permissions are correct specifically the Attribute Duplication setting.
ODI-20235
ODI-20235: Error during the drag-and-drop operation
Category:
Other
Cause:
An unexpected error occurred during a drag and drop operation
Action:
Review the error details for further information.
ODI-20236
ODI-20236: You do not have the sufficient privileges to add this object.
Category:
Other
Cause:
The operation failed due to insufficient ODI security on Datastore.
Action:
Ensure the ODI user security permissions are correct.
ODI-20237
ODI-20237: Unable to duplicate the attribute.
Category:
Other
Cause:
An unexpected error occurred while duplicating an attribute.
Action:
Review the error details for further information. Ensure that the repository connection is still valid.
ODI-20238
ODI-20238: Unable to duplicate the table.
Category:
Other
Cause:
An unexpected error occurred while duplicating a table.
Action:
Review the error details for further information. Ensure that the repository connection is still valid.
ODI-20239
Error during the action
Category:
Other
Cause:
An unexpected error occurred during a user action.
Action:
Review the error details for further information.
ODI-20240
ODI-20240: Error while deleting
Category:
Other
Cause:
An unexpected error occurred during a delete operation.
Action:
Review the error details for further information. Ensure that the repository connection is valid.
ODI-20241
ODI-20241: Unable to apply changes.
Category:
Other
Cause:
The changes to the filter could not be applied.
Action:
Save the object before retrying to apply the filter.
ODI-20242
ODI-20242: Error while creating the popup menu
Category:
Other
Cause:
Retrieval of the Available Methods for the filter failed.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20243
ODI-20243: Unable to add an attribute.
Category:
Other
Cause:
An unexpected error occurred while adding an attribute.
Action:
Review the error details for further information. Ensure that the repository connection is open.
ODI-20244
ODI-20244: Unable to add reference
Category:
Other
Cause:
An unexpected error occurred while adding a reference.
Action:
Review the error details for further information. Ensure that the repository connection is open.
ODI-20245
ODI-20245: Unable to add table
Category:
Other
Cause:
An unexpected error occurred while adding a table.
Action:
Review the error details for further information. Ensure that the repository connection is open.
ODI-20246
ODI-20246: Error while applying the changes
Category:
Other
Cause:
The reference to the Model could not be created.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20247
ODI-20247: Unable to add key.
Category:
Other
Cause:
An unexpected error occurred while adding a key.
Action:
Review the error details for further information.
ODI-20248
ODI-20248: Error while opening window
Category:
Other
Cause:
The editor could not be opened.
Action:
Save the object before retrying the edit.
ODI-20249
ODI-20249: Error while creating the popup menu
Category:
Other
Cause:
An unexpected error occurred while creating a popup menu.
Action:
Review the error details for further information.
ODI-20250
ODI-20250: Error while
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-20251
ODI-20251: An unexpected error has occurred
Category:
Other
Cause:
Unable to acess the Security Authorization settings.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20252
ODI-20252: Unable to apply changes.
Category:
Other
Cause:
Saving the model condition failed.
Action:
Ensure the repository database connection is not broken and the ODI Security permissions are correct.
ODI-20253
ODI-20253: The object was deleted by another user
Category:
Other
Cause:
The operation could not be performed because the specified object could not found.
Action:
Refresh the view and retry the operation.
ODI-20254
ODI-20254: The marker was deleted by another user
Category:
Other
Cause:
The operation could not be performed because the specified Marker object was in an Inconsistent state.
Action:
Refresh the view and retry the operation.
ODI-20255
ODI-20255: Marker name is mandatory
Category:
Other
Cause:
Marker could not be saved because the mandatory Name field was not entered.
Action:
Enter a value in the Marker name field.
ODI-20256
ODI-20256: You do not have the sufficient privileges to change the marker
Category:
Other
Cause:
Modification of the Marker failed due to insufficient ODI security privileges.
Action:
Ensure the ODI user security permissions are correct.
ODI-20257
ODI-20257: The Where text is mandatory when the Filter is active for a static control.
Category:
Other
Cause:
The WHERE clause was null or empty.
Action:
Ensure the WHERE clause is valid.
ODI-20258
ODI-20258: It is not possible to check the expression due to DBMS connection failure
Category:
Other
Cause:
Connection to the DBMS failed.
Action:
Ensure the DBMS is available and the connection information to it is correctly specified.
ODI-20259
ODI-20259: cannot show the data since the join points to different connections
Category:
Other
Cause:
Unable to retrieve data due to a conflict between the physical schemas involved.
Action:
Ensure the Topology or Context settings are correct and multiple data stores in the same Source Set are not connected using different Physical Schemas.
ODI-20260
ODI-20260: Name and Code columns of the FlexField cannot be empty.
Category:
Other
Cause:
FlexField name or code were found to be empty or null.
Action:
Enter a name and a code for the FlexField.
ODI-20261
ODI-20261: The "Procedure Name" is mandatory.
Category:
Other
Cause:
The "Procedure Name" field value was not specified.
Action:
Enter a value for the "Procedure Name" field.
ODI-20262
ODI-20262: Logical Schema is not selected.
Category:
Other
Cause:
There is no Logical Schema selected for this variable.
Action:
Select a Logical Schema.
ODI-20263
ODI-20263: Please enter the duration in a format such as 5s (seconds), 10m (minutes), 1d (days), 1y (years).
Category:
Other
Cause:
Duration is specified in an invalid format
Action:
Please change duration such that it comprises an integer followed by a time indicator, for example 10s, 30d, 1y
ODI-20300
ODI-20300: Error while printing the diagram
Category:
Other
Cause:
An unexpected condition has occurred in the print system.
Action:
Check the printer settings and physical printer.
ODI-20301
ODI-20301: Error while saving the diagram
Category:
Other
Cause:
The save file could not be created.
Action:
Check the destination folder is writable and that their is sufficient disk space.
ODI-20310
Unsupported Flavor
Category:
Other
Cause:
An attempt was made to drag and drop an object into an unsupported area of the canvas.
Action:
Drag a different object type or drop the object into a valid area.
ODI-20311
ODI-20311: An unexpected exception occurred while reading or writing a text in a business object.
Category:
Other
Cause:
An unexpected exception occurred while reading or writing text.
Action:
Review the console output or logs for additional information.
ODI-20312
ODI-20312: An error occurred while printing.
Category:
Other
Cause:
An error occurred while printing.
Action:
Ensure that the printer is configured properly.
ODI-20313
ODI-20313: Could not double click
Category:
Other
Cause:
An unexpected error has occured.
Action:
Contact Oracle Support Services.
ODI-20315
ODI-20315: Invalid Password
Category:
Other
Cause:
The Password is incorrect.
Action:
Correct the password and try again.
ODI-20316
ODI-20316: A timeout occurred while trying to establish a connection.
Category:
Other
Cause:
A timeout error occurred while connecting to the database.
Action:
Verify that the Database Connection details are correct and the database is available.
ODI-20317
ODI-20317: The field "{0}" is mandatory.
Category:
Other
Cause:
A value has not been provided for a required field.
Action:
Enter a value for the named field.
ODI-20318
ODI-20318: The icon {0} cannot be found.
Category:
Other
Cause:
An unexpected error has occured.
Action:
Contact Oracle Support Services.
ODI-20319
ODI-20319: {0} is not a valid date for field {1}. The format is: {2}
Category:
Other
Cause:
The format of the date does not match the required format.
Action:
Enter a valid date using the correct date format.
ODI-20320
ODI-20320: Error when applying changes.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20321
ODI-20321: Error when initializing the panel.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20322
ODI-20322: Unable to add a Step.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20323
ODI-20323: Unable to execute the step
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20324
ODI-20324: Cannot execute the Package
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20325
ODI-20325: Unable to open the linked object.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20326
ODI-20326: Unable to edit the text
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20327
ODI-20327: Unable to modify the value.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20328
ODI-20328: Unable to define the next Step.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20329
ODI-20329: Unable to delete Steps(s). You do not have Edit privileges.
Category:
Other
Cause:
An error occurred while attempting to delete one or more package steps.
Action:
Update security settings to allow step editing privileges.
ODI-20330
ODI-20330: Unable to delete Link(s). You do not have Edit privileges.
Category:
Other
Cause:
You must have Edit privilege on each steps of the link.
Action:
Review the Security settings for the steps and ensure that you have the correct permissions.
ODI-20331
ODI-20331: The Step diagram is not be accessible.
Category:
Other
Cause:
You do not have permission to access this step.
Action:
Check the diagram security settings and verify that you have permission to access the diagram.
ODI-20332
ODI-20332: Cannot change the position of this object
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20333
ODI-20333: Cannot view this Step because the Package is being edited
Category:
Other
Cause:
A package step cannot be viewed while the parent package is being edited.
Action:
Close the package editor.
ODI-20335
ODI-20335: Printing Options not accessible.
Category:
Other
Cause:
An unexpected error occurred while printing a package.
Action:
Review the log file for additional info about the exception.
ODI-20336
ODI-20336: Unknown event sent to the Package event manager.
Category:
Other
Cause:
An unexpected error has occurred.
Action:
Contact Oracle Support Services.
ODI-20337
ODI-20337: A Knowledge Module cannot be added as a Step.
Category:
Other
Cause:
Only a DataStore,Model,Sub Model,Interface,Procedure or Variable can be added as a Step.
Action:
Use a valid object type for your step creation.
ODI-20338
ODI-20338: A starting Step must be defined.
Category:
Other
Cause:
A Starting step has been defined.
Action:
Select the first step in the package and mark is the starting step.
ODI-20339
ODI-20339: One or more Steps are not linked.
Category:
Other
Cause:
All steps must be linked.
Action:
Ensure that all steps are linked .
ODI-20340
ODI-20340: Only one starting Step can be defined.
Category:
Other
Cause:
A package must have one and only one starting steps.
Action:
Ensure that you have only one starting step defined .
ODI-20341
ODI-20341: You do not have the appropriate privileges to edit a package step.
Category:
Other
Cause:
An attempt was made to edit or view a package step, but the user does not have privileges to access the step.
Action:
Update security settings for the user to allow package and step access.
ODI-20342
ODI-20342: Cannot open the Expression Editor
Category:
Other
Cause:
An unexpected error has occured.
Action:
Contact Oracle Support Services.
ODI-20343
ODI-20343: There are errors in your diagram
Category:
Other
Cause:
The diagram may contain objects that are not connected, or objects that are not completely defined.
Action:
Check the diagram and ensure that all objects are connected and fully defined.
ODI-20344
ODI-20344: Cannot launch the editor for this expression
Category:
Other
Cause:
An error occured while retrieving the language for the expression. This may be due to an unexpected exception, or the language may not be available for the schema's technology.
Action:
Review the message log for additional errors. Ensure that the schema has a valid technology for which the language is set.
ODI-20345
ODI-20345: Cannot change the clause position
Category:
Other
Cause:
An unexpected internal exception has occured.
Action:
Contact Oracle Support Services.
ODI-20346
ODI-20346: Cannot get the boolean value of an option
Category:
Other
Cause:
The boolean value of the option could not be retrieved due to a security error.
Action:
Review the message log and contact Oracle Support Services for further assistance.
ODI-20347
ODI-20347: Error during data transfer for drag and drop
Category:
Other
Cause:
An internal error occured while dropping the object into the diagram.
Action:
Review the message log for additional information and contact Oracle Support Services for further assistance.
ODI-20348
ODI-20348: An interface with the same name already exists in this folder. Please change the name of the new interface.
Category:
Other
Cause:
An interface with the specified name exists in the folder. The interface name must be unique within a folder.
Action:
Enter a new interface name that is unique within the folder.
ODI-20349
ODI-20349: Unknown event detected by the event manager. Please contact Oracle Support Services.
Category:
Other
Cause:
The Package Event Manager was called to action an unknown event.
Action:
Contact Oracle Support Services for further assistance.
ODI-20350
ODI-20350: Your diagram contains one or more FATAL/CRITICAL errors preventing display of the Flow Editor
Category:
Other
Cause:
The diagram is incomplete or contains errors that prevent the Flow Editor being displayed.
Action:
Return to the diagram tab and review the error messages using the errors and warnings button in the toolbar. Fix the errors in order to access the Flow Editor.
ODI-20351
ODI-20351: Error adding source to Quick Edit source table.
Category:
Other
Cause:
An internal error occured which prevented the source being added.
Action:
Contact Oracle Support Services for further assistance.
ODI-20352
ODI-20352: Error adding target datastore to Quick Edit mapping table.
Category:
Other
Cause:
An internal error occured which prevented the target being added.
Action:
Contact Oracle Support Services for further assistance.
ODI-20353
ODI-20353: Only a single column may be pasted into a Quick Edit table.
Category:
Other
Cause:
The clipboard contains multiple columns. Quick Edit only supports pasting a single cell into a table.
Action:
Select the cells to be copied and paste them one at a time.
ODI-20354
ODI-20354: Paste targets must be in the same column as the previous copy. This does not apply to Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).
Category:
Other
Cause:
You have selected a value from one column, and tried to paste it into a different column. This is only supported for Expression Columns.
Action:
Please enter the values into the cell manually.
ODI-20355
ODI-20355: Duplicate value is not supported on this column.
Category:
Other
Cause:
The paste operation is not permitted in the Alias and Target Column Name fields as these fields must contain a unique value.
Action:
Please enter the Alias or Name field manually.
ODI-20356
ODI-20356: Can not perform paste into a read-only column.
Category:
Other
Cause:
The Paste operation is not permitted on read-only columns.
Action:
You may not update this value in the table.
ODI-20357
ODI-20357: Can not perform deletion because the target datastore is not temporary.
Category:
Other
Cause:
An attempt was made to delete a row in the target, but the target datastore is not a temporary table. Only rows in a temporary target table may be deleted.
Action:
You cannot delete the row.
ODI-20358
ODI-20358: Interface cannot be saved because it has a fatal error: {0}.
Category:
Other
Cause:
The Interface could not be saved because it contains a fatal error which must be resolved.
Action:
Review the errors in the Diagram tab and resolve the fatal errors.
ODI-20359
ODI-20359: Only one cell can be copied one at a time.
Category:
Other
Cause:
More than one cell was selected. Quick Edit only supports copying a single cell.
Action:
Select and copy a single cell.
ODI-20360
ODI-20360: Only Expression columns support Copy and Paste from other applications. For all other columns, please perform a copy first on that column before pasting.
Category:
Other
Cause:
Only values from other applications may be copied into Expression columns.
Action:
For all other columns, perform a copy first on that column before pasting.
ODI-20361
ODI-20361: Can not perform Copy and Paste across tables, except for Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).
Category:
Other
Cause:
Values may not be copied between tables in Quick Edit, apart from between Expression columns.
Action:
Please enter the values manually.
ODI-20362
ODI-20362: Couldn't connect to Web Service
Category:
Other
Cause:
An error occured while creating a connection to the Web Service.
Action:
Ensure that the Web Service is accessible and WSDL URL is correct.
ODI-20363
ODI-20363: Error while exporting request
Category:
Other
Cause:
The request could not be exported
Action:
Check that there is sufficient disk space and that the target directory is accessible.
ODI-20364
ODI-20364: Error while parsing the XML file
Category:
Other
Cause:
An error occured while parsing the XML file
Action:
Ensure that the correct XML file is specified and that it is correctly structured
ODI-20365
ODI-20365: There is no port with SOAP binding defined on this service
Category:
Other
Cause:
The referenced service does not support the specified port
Action:
Specify a valid port for the service
ODI-20366
ODI-20366: The timeout must be an integer value.
Category:
Other
Cause:
The value entered for the timeout is not a valid integer
Action:
Enter a valid integer value
ODI-20367
ODI-20367: Export directory {0} does not exist.
Category:
Other
Cause:
The specified directory does not exist
Action:
Create the directory and repeat the operation
ODI-20368
ODI-20368: WSDL URL is null or empty, ODI can not initialize the current request.
Category:
Other
Cause:
WSDL URL is null
Action:
Set the WSDL URL or remove the soap request.
ODI-20370
ODI-20370 : Shortcuts within a project can only refer to objects that belong to that same project
Category:
Other
Cause:
Shortcuts within a project can only refer to objects that belong to that same project
Action:
=Try another folder destination
ODI-20371
ODI-20371 : No two shortcut objects within a folder may refer to the same base object
Category:
Other
Cause:
No two shortcut objects within a folder may refer to the same base object
Action:
Try another folder destination or fix folder contents
ODI-20372
ODI-20372 : The source and destination models must be defined with the same Technology
Category:
Other
Cause:
The source and destination models must be defined with the same Technology
Action:
Try another model destination or fix model properties.
ODI-20373
ODI-20373 : No two shortcuts within a model may contain the same base object
Category:
Other
Cause:
No two shortcuts within a model may contain the same base object
Action:
Try another folder destination or fix model contents.
ODI-20374
ODI-20374 : A model cannot contain a datastore and a datastore shortcut to another datastore with the same datastore name
Category:
Other
Cause:
A model cannot contain a datastore and a shortcut to another datastore with the same datastore name
Action:
Try another folder destination or fix model contents.
ODI-20701
ODI-20701: The Name field is mandatory.
Category:
Other
Cause:
The Name field was not entered.
Action:
Enter a name for the Load Plan.
ODI-20702
ODI-20702: The name given for the Load Plan is already used by another load plan. Please provide another name.
Category:
Other
Cause:
The name provided for the Load Plan was not unique.
Action:
Enter a unique name for the Load Plan.
ODI-20703
ODI-20703: Variable "{0}" is not found.
Category:
Other
Cause:
The variable could not be found.
Action:
Provide another name for the variable.
ODI-20704
ODI-20704: Datatype of variable "{0}" has been changed.
Category:
Other
Cause:
The datatype of the original variable is different to the datatype of the load plan variable.
Action:
Verify the datatype of the variable and ensure that the types of the original and load plan variables match.
ODI-20705
ODI-20705: This variable is used in one or more case steps. Removing it will trigger deletion of those case steps, and all of their child steps. Do you want to continue?
Category:
Other
Cause:
An attempt was made to remove a variable which is used in one or more case steps.
Action:
To remove the variable and its associated case steps, click Yes. Otherwise, click No, and nothing will be removed.
ODI-20706
ODI-20706: The Step Name is mandatory.
Category:
Other
Cause:
The Step Name field was not entered.
Action:
Enter a name for the Step.
ODI-20707
ODI-20707: The Variable is mandatory.
Category:
Other
Cause:
A Variable was not selected.
Action:
Select a variable.
ODI-20708
ODI-20708: The Scenario is mandatory.
Category:
Other
Cause:
A Scenario was not selected.
Action:
Select a Scenario.
ODI-20709
ODI-20709: The Value is mandatory.
Category:
Other
Cause:
A Value was not provided.
Action:
Enter a Value.
ODI-20710
ODI-20710: The Value format is not valid.
Category:
Other
Cause:
An incorrect format was given for the Value.
Action:
Check the format of the Value and correct it.
ODI-20711
ODI-20711: The Step Name is mandatory.
Category:
Other
Cause:
The Step Name field was not entered.
Action:
Provide the name of the Step.
ODI-20712
ODI-20712: The Variable is mandatory.
Category:
Other
Cause:
A Variable was not selected.
Action:
Select a Variable.
ODI-20713
ODI-20713: The Scenario is mandatory.
Category:
Other
Cause:
A Scenario was not selected.
Action:
Select a Scenario.
ODI-20714
ODI-20714: The Context is mandatory.
Category:
Other
Cause:
A Context was not selected for execution.
Action:
Select an execution Context.
ODI-20715
ODI-20715: The Logical Agent is mandatory.
Category:
Other
Cause:
A Logical Agent was not selected for execution.
Action:
Select a Logical Agent.
ODI-20716
ODI-20716: No Physical Agent is defined for the selected Logical Agent and Context. Edit Logical Agent "{0}", and define a Physical Agent for Context "{1}".
Category:
Other
Cause:
There was no Physical Agent associated with this Logical Agent in the specified context.
Action:
Associate a Physical Agent with the Logical Agent in the selected context.
ODI-20717
ODI-20717: No Physical Agents are running. A Physical Agent must be running in order to Restart a Load Plan.
Category:
Other
Cause:
There were no Physical Agents running.
Action:
Start a Physical Agent before restarting the Load Plan.
ODI-20718
ODI-20718: No Physical Agents are running. A Physical Agent must be running in order to Stop a Load Plan.
Category:
Other
Cause:
There were no Physical Agents running.
Action:
Start the Agent before executing the Load Plan.
ODI-20719
ODI-20719: Scenario "{0}" is not found.
Category:
Other
Cause:
The scenario was not found.
Action:
Specify an existing scenario.
ODI-20720
ODI-20720: Physical Agent "{0}" - which is defined in Logical Agent "{1}" to be used for Context "{2}" - is not responding. Verify that Physical Agent "{0}" has been started.
Category:
Other
Cause:
The Physical Agent was not reachable.
Action:
Check the Physical Agent and start it.
ODI-20721
ODI-20721: Interface contains one or more errors. You should correct the errors before attempting to execute it
Category:
Other
Cause:
The interface contains errors which prevent it from being executed.
Action:
Review the errors shown in the interface editor and update the interface to fix the problems.
ODI-20722
ODI-20722: Cannot display data. Source alias is {0} characters long which is longer than allowed by the technology ({1}). Please review the technology settings in Topology.
Category:
Other
Cause:
Source alias exceeded the limit allowed by its technology.
Action:
Ensure the maximum table name length setting in the corresponding technology is correct. Consider changing source alias to comply.
ODI-20723
ODI-20723: There is no any version of scenario {0} found. A scenario of the step {1} cannot be refreshed.
Category:
Other
Cause:
The scenario of step was not found.
Action:
Check if specified scenario for this step is correct.
ODI-20724
ODI-20724: Journalized data not found. Journal data view: {0}
Category:
Other
Cause:
Journal is not started or is stopped.
Action:
Ensure the journal is started: select Changed Data Capture > Journal Data.
ODI-20726
ODI-20726: The Step Name is mandatory.
Category:
Other
Cause:
The Step Name field was not entered.
Action:
Enter a name for the Step.
ODI-20727
ODI-20727: Scenario "{0}" parent is not found.
Category:
Other
Cause:
The Scenario source object does not exist.
Action:
Check if the source object, from which the Scenario was generated, does exist.
ODI-20728
ODI-20728: The attribute name is mandatory
Category:
Other
Cause:
The datastore attribute could not be saved because the mandatory Name field was not entered.
Action:
Enter a value in the attribute name field.
ODI-20729
ODI-20729: {0} is a dependant object of the following object(s) {1} and cannot be removed
Category:
Other
Cause:
Selected object for removal is a dependent object.
Action:
Remove the dependent object first.
ODI-20731
ODI-20731: The parent from which this scenario is generated does not exist anymore so the editor couldn't show the parent related information.
Category:
Other
Cause:
The editor couldn't show the parent related information because the scenario parent does not exist anymore. This could happen, for example, if you imported the scenario, but didn't import it's parent object.
Action:
Try to figure out, why the scenario parent object does not exist. Try to restore the parent.
ODI-20732
ODI-20732: You cannot move a submodel into another model.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Submodels cannot be moved into hierarchy of another models.
ODI-20733
ODI-20733: You cannot copy a submodel into another model.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Submodels cannot be copied into hierarchy of another models.
ODI-20734
ODI-20734: Changing the name of a user function only impacts the user function itself; Users need to manually change object(s) which reference the old user function name.
Category:
Other
Cause:
The user function name has been updated
Action:
It is the user's responsibility to determine where the user function is referenced and to manually change the name of the user function in those places
ODI-20735
ODI-20735: The name given for the Physical Agent is already used by another agent. Please provide another name
Category:
Other
Cause:
The name provided for the Physical Agent was not unique.
Action:
Enter a unique name for the Physical Agent.
ODI-20736
ODI-20736: The Name field is mandatory.
Category:
Other
Cause:
The value for the Name field was not specified.
Action:
Enter a name for the Object.
ODI-20737
Could not build WSDL Model.
Category:
Other
Cause:
An unexpected error occurred while building a WSDL model.
Action:
Review the error details for further information.
ODI-20741
ODI-20741: This is not a valid Cobol Copybook.
Category:
Other
Cause:
The file chosen in the Reverse Engineering Cobol Copybook process is not a valid Cobol Copybook.
Action:
Ensure the file is a valid Cobol Copybook.
ODI-20742
ODI-20742: You cannot copy a mapping into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Mappings cannot be copied into hierarchy of another projects.
ODI-20743
ODI-20743: You cannot copy a reusable mapping into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Reusable mappings cannot be copied into hierarchy of another projects.
ODI-20744
ODI-20744: You cannot move a mapping into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Mappings cannot be moved into hierarchy of another projects.
ODI-20745
ODI-20745: You cannot move a reusable mapping into a folder belonging to another project.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Reusable mappings cannot be moved into hierarchy of another projects.
ODI-20746
ODI-20746: You cannot move a global reusable mapping into a folder.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Global Reusable mappings cannot be moved into a folder.
ODI-20747
ODI-20747: You cannot copy a global reusable mapping into a folder.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Global Reusable mappings cannot be copied into a folder.
ODI-20748
ODI-20748: Open is not valid for this node.
Category:
Other
Cause:
The editor is not applicable for this node.
Action:
Editor cannot be opened for this node.
ODI-20749
ODI-20749: Selected Capture/Initial Load Capture process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.
Category:
Other
Cause:
Selected Goldengate Capture/Initial Load Capture process is used in a different model.
Action:
Select a different set of process instances for this model.
ODI-20750
ODI-20750: Selected Delivery/Initial Load Delivery process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.
Category:
Other
Cause:
Selected Goldengate Delivery/Initial Load Delivery process is used in a different model.
Action:
Select a different set of process instances for this model.
ODI-20751
ODI-20751: Load Plan Debugging is not supported: {0}.
Category:
Other
Cause:
An unsupported operation was attempted.
Action:
Load Plan can't be debug.
ODI-20752
ODI-20752: Format can not be empty for File datastore's Date type column
Category:
Other
Cause:
Column added for the File datastore has Date as type but Format is not given
Action:
Ensure the Format is entered for File datatsore's column of type Date.
ODI-20753
ODI-20753 : Shortcuts in a Model can not be moved
Category:
Other
Cause:
Shortcuts in a Model can not be moved to another Model
Action:
Please get the base object of the shortcut first and then try to move
ODI-20754
ODI-20754 : Driver name cannot be empty
Category:
Other
Cause:
Driver is not assigned for the Data Server
Action:
Please choose the appropriate driver for the datastore.
ODI-20755
ODI-20755: A Data Server with the name {0} already exists. Please provide another name.
Category:
Other
Cause:
The name provided for the Data Server is not unique.
Action:
Enter a unique name for the Data Server.
ODI-20756
ODI-20756: A Logical Schema with the name {0} already exists. Please provide another name.
Category:
Other
Cause:
The name provided for the Logical Schema is not unique.
Action:
Enter a unique name for the Data Server.
ODI-20757
ODI-20757: If logical schema is specified, WSDL URL can not differ from physical schema's WSDL URL.
Category:
Other
Cause:
You have specified different WSDL URL compared to physical schema WSDL URL.
Action:
WSDL URL and physical schema WSDL URL should be same when logical schema is specified.
ODI-20758
ODI-20758: If logical schema is specified, HTTP User can not differ from physical schema's/data server's HTTP User.
Category:
Other
Cause:
You have specified different user compared to physical schema/data server HTTP user.
Action:
User and physical schema/data server HTTP user should be same when logical schema is specified.
ODI-20759
ODI-20759: If logical schema is specified, Port Type can not differ from physical schema's port type.
Category:
Other
Cause:
You have specified different port type compared to physical schema port type.
Action:
Port type and physical schema port type should be same when logical schema is specified.
ODI-20760
ODI-20760: Choice names should be unique.
Category:
Other
Cause:
You have added duplicate choice names.
Action:
Ensure only unique choice names are used.
ODI-20761
ODI-20761: An Option Group with the name {0} already exists. Please provide another name.
Category:
Other
Cause:
The name provided for the Option Group is not unique.
Action:
Enter a unique name for the Option Group.
ODI-20763
ODI-20763: Maximum number of login attempts reached. ODI User will be locked.
Category:
Other
Cause:
You have exceeded the maximum number of login attempts.
Action:
A Supervisor user must unlock this user.
ODI-20764
ODI-20764: Error occurred while creating version for regenerated Scenario.
Category:
Other
Cause:
Auto versioning failed for the regenerated Scenario
Action:
Please check log for more information
ODI-20765
ODI-20765: Agent Invocation Failed.
Category:
Other
Cause:
ODI Agent request invocation failed.
Action:
Ensure Agent is in correct state.
ODI-20766
ODI-20766: ODI does not support View Data for Non-JDBC datastore
Category:
Other
Cause:
ODI does not support View Data for Non-JDBC datastore
Action:
View Data for Non-JDBC datastore is not supported
ODI-23001
ODI-23001: The import process failed
Category:
Other
Cause:
The work repository export file specified could not be imported.
Action:
Ensure the specified file is readable and is a valid work repository export file.
ODI-23006
ODI-23006: Agent Test failed
Category:
Other
Cause:
Agent could not be contacted using the specified connection details.
Action:
Ensure the Agent connection details are correct and the Agent is running.
ODI-23007
ODI-23007: Data Source already exists for "{0}".
Category:
Other
Cause:
The Data Source has already been associated with this Agent.
Action:
No action is necessary as the Data Source is already associated with this Agent. Consider removing the Data Source from this Agent and retrying this action.
ODI-23010
ODI-23010: Please enter first a name, an expression and a help text for this language element.
Category:
Other
Cause:
The Name, Expression or Help Text parameter values for this Language Element were not entered in the Definition panel. These are mandatory parameters.
Action:
Return to the Definition panel and ensure the Name, Expression and Help Text parameters have valid values.
ODI-23011
ODI-23011: Name is empty
Category:
Other
Cause:
A value for the Name parameter of the Language Element Implementation was not entered. This is a mandatory parameter.
Action:
Enter a valid value for the Name parameter before saving this Language Element.
ODI-23012
ODI-23012: Expression is empty
Category:
Other
Cause:
A value for the Expression parameter of the Language Element Implementation was not entered. This is a mandatory parameter.
Action:
Enter a valid value for the Expression parameter before saving this Language Element.
ODI-23013
ODI-23013: Help is undefined
Category:
Other
Cause:
A value for the Help Text parameter of the Language Element Implementation was not entered. This is a mandatory parameter.
Action:
Enter a value for the Help Text parameter before saving this Language Element.
ODI-23014
ODI-23014: Technology is undefined
Category:
Other
Cause:
A value for the Technology parameter of the Language Element Implementation was not entered. This is a mandatory parameter.
Action:
Enter a value for the Technology parameter before saving this Language Element.
ODI-23015
ODI-23015: Logical Schema {0} is already linked to a physical schema in context {1}.
Category:
Other
Cause:
A Physical Schema has already been defined for this Context and Logical Schema combination.
Action:
Remove the Context and Logical Schema combination from the Context editor, then retry saving the Physical Schema.
ODI-23016
ODI-23016: The context is either invalid or no longer exists in the database.
Category:
Other
Cause:
One of the Contexts used by the Physical Schema is invalid or no longer exists in the Master Repository.
Action:
Ensure the Context for the Physical Schema is correct by either selecting a valid Context for the Physical Schema or recreating the missing Context.
ODI-23017
ODI-23017: This Physical Schema already exists for this data server.
Category:
Other
Cause:
A Physical Schema referencing this Data Server has already been defined in the Master Repository.
Action:
Specify the correct Physical Schema for this Data Server to use.
ODI-23018
ODI-23018: Unable to connect to Work Repository.Repository host or database is not available.
Category:
Other
Cause:
The Work Repository could not be accessed using the connection details defined for it. This may be due to the database or host not being available, or the password could have changed.
Action:
Ensure the Work Repository host and database are active. Using the Work Repository editor, ensure the connection details for it are correct.
ODI-23019
ODI-23019: Error Detected during Repository Installation. Invalid connection parameters.
Category:
Other
Cause:
The repository installation process was unable to connect to the repository database.
Action:
Correct any errors identified in the installation log and retry the installation. If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
ODI-23020
ODI-23020: Error Detected during Repository Installation. Invalid External Authentication credentials.
Category:
Other
Cause:
The ODI Supervisor credentials supplied did not match the credentials held in the External Password Store.
Action:
Retry the installation, ensuring the Supervisor user name and password match those held in the external store.
ODI-23021
ODI-23021: Error Detected during Repository Installation. Invalid External Authentication configuration.
Category:
Other
Cause:
A connection to the External Authentication Store could not be established.
Action:
Ensure the External Authentication Store is available and the connection details specified in the JPS configuration file are valid.
ODI-23022
ODI-23022: An error occurred during the generation of the Data Service.
Category:
Other
Cause:
An unexpected error occurred while generating data services.
Action:
Review the error details for further information.
ODI-23023
ODI-23023: The Schema path ({0}) is not supported
Category:
Other
Cause:
The Model's Physical Schema attempted to define the Schema path using an unsupported protocol (ftp, http or file).
Action:
Change the Physical Schema to not use ftp, http or file protocol to reference the file.
ODI-23024
ODI-23024: The URL is mandatory.
Category:
Other
Cause:
The URL field has not been entered and is a mandatory parameter.
Action:
Enter the URL parameter. A template chosen from the drop down list may help to ensure the syntax is correct.
ODI-23025
ODI-23025: The ID is mandatory.
Category:
Other
Cause:
The Repository ID parameter has not been entered and is a mandatory parameter.
Action:
Enter an integer value for the Repository ID parameter.
ODI-23026
ODI-23026: The ID must be an integer value.
Category:
Other
Cause:
The value entered for the Repository ID is not a valid integer.
Action:
Enter an integer value for the Repository ID parameter.
ODI-23027
ODI-23027: The driver is mandatory.
Category:
Other
Cause:
A JDBC Driver was not specified and is a mandatory parameter.
Action:
Select a JDBC Driver from the list of values.
ODI-23028
ODI-23028: The password is mandatory.
Category:
Other
Cause:
The Supervisor user's Password parameter was not specified.
Action:
Enter the Supervisor password.
ODI-23029
ODI-23029: The confirm password is mandatory.
Category:
Other
Cause:
The Supervisor user's Confirm Password parameter was not specified.
Action:
Enter the Supervisor user's password in the Confirm Password parameter.
ODI-23030
ODI-23030: Password and Confirm Password are different
Category:
Other
Cause:
The Password and Confirm Password parameters are not the same.
Action:
Ensure the same value is entered for both the Password and Confirm Password parameters.
ODI-23031
ODI-23031: The Supervisor username is mandatory.
Category:
Other
Cause:
The Supervisor User parameter was not entered.
Action:
Enter a value for the Supervisor User parameter ensuring it matches a user in the external enterprise identify store, or switch to ODI Authentication.
ODI-23032
ODI-23032: Maximum number of sessions cannot be less or equal to 0.
Category:
Other
Cause:
The Maximum Number of Sessions parameter value was specified as 0.
Action:
Change the Maximum Number of Sessions parameter in the Agent Definition tab to a value greater than 0.
ODI-23033
ODI-23033: The file reverse-engineering is only possible for delimited files.
Category:
Other
Cause:
The file format for the specified file was not delimited.
Action:
Select a delimited format file and retry the reverse-engineering action.
ODI-23035
ODI-23035: Can not update the scheduling - This agent may not be running
Category:
Other
Cause:
The Update Scheduling action could not be performed because the ODI Client could not connect to the Agent.
Action:
Check that the Agent connection details are correct and that the agent is running. Use the Agent Test button to check the connection details.
ODI-23036
ODI-23036: Logical Schema not set for Context
Category:
Other
Cause:
A Logical Schema entry in the Physical Schema's Context was specified as <Undefined>.
Action:
Ensure none of the Logical Schemas on the Physical Schema's Context tab are set to <Undefined>.
ODI-23037
ODI-23037: To use scheduling please associate a Logical Agent to a Physical Agent via the Logical Architecture Accordion in the Topology Navigator
Category:
Other
Cause:
There are no logical agents available to use for scheduling.
Action:
Associate a logical agent with a physical agent using the Topology Navigator and then resubmit your schedule request.
ODI-23038
ODI-23038: Cannot resolve the table name. Check the masks defined for this physical schema.
Category:
Other
Cause:
The table and schema format could not be calculated. This is because the object mask has not been set for the Physical Schema that contains this table.
Action:
From the Topology Navigator edit the Physical Schema containing this table and ensure the Masks parameter value is valid for the schema based on its technology (for example "%SCHEMA.%OBJECT").
ODI-23039
ODI-23039: You cannot carry out this type of export.
Category:
Other
Cause:
The export type specified is not supported.
Action:
Retry the export. If the problem persists then contact Oracle Support Services.
ODI-23040
ODI-23040: Import file "{0}" error
Category:
Other
Cause:
An error occured during the import file process.
Action:
Correct any errors identified in the error log and retry the import process. If the problem persists then contact Oracle Support Services.
ODI-23042
ODI-23042: An error occurred while changing the repository number.
Category:
Other
Cause:
An error occured while changing the repository number.
Action:
Correct any errors identified in the message log and retry the action. If the problem persists then contact Oracle Support Services.
ODI-23043
ODI-23043: The Repository ID must be numeric.
Category:
Other
Cause:
The value specified for the Repository ID parameter was not a valid numeric value.
Action:
Enter a valid numeric value for the Repository ID parameter.
ODI-23044
ODI-23044: The new ID you have chosen is already in use as a table "{0}" primary key. The renumbering has been aborted. No changes have been made.
Category:
Other
Cause:
The Repository ID specified is already used by an existing object.
Action:
Enter a different value for the Repository ID parameter ensuring it is unique within the repository.
ODI-23045
ODI-23045: You may not renumber a repository before version 11. Please upgrade your repository first.
Category:
Other
Cause:
The renumber functionality is not supported for ODI Repository versions prior to version 11.
Action:
Upgrade the repository to version 11 (or higher) and then renumber it.
ODI-23046
ODI-23046: An error was encountered during the test.
Category:
Other
Cause:
An attempt to connect a Work Repository failed.
Action:
Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
ODI-23047
ODI-23047: Could not connect to the work repository. The renumbering process has been aborted. No changes have been made.
Category:
Other
Cause:
An attempt to connect a Work Repository failed.
Action:
Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
ODI-23048
ODI-23048: Import report generation error
Category:
Other
Cause:
The import was performed, but there was an unexpected error while opening the Import Report.
Action:
Contact Oracle Support Services.
ODI-23049
ODI-23049: Error Detected during Repository Installation
Category:
Other
Cause:
An error occured during the creation or import of the Master Repository.
Action:
Correct any errors described in the message log and retry the installation process. If this is caused by an external application, then fix the related code; otherwise, contact My Oracle Support.
ODI-23050
ODI-23050: The password you entered doesn't match the actual password
Category:
Other
Cause:
The password you entered doesn't match the actual password
Action:
Ensure that the password entered matches the actual password
ODI-23051
ODI-23051: Maximum number of threads must be greater than zero.
Category:
Other
Cause:
Values for maximum number of threads is not valid
Action:
Enter valid value for maximum number of threads
ODI-23052
ODI-23052: Maximum number of thread per session cannot be less than 0.
Category:
Other
Cause:
Values for maximum number of thread per session is not valid
Action:
Enter valid value for maximum number of threads per session
ODI-23053
ODI-23053: Maximum number of threads cannot be less than maximum number of threads per session.
Category:
Other
Cause:
Maximum number of threads less than maximum number of threads per session
Action:
Enter valid values for maximum number of threads and maximum number of threads per session
ODI-23054
ODI-23054: Maximum number of cache entries cannot be less than zero.
Category:
Other
Cause:
Values for maximum number of cache entries is not valid
Action:
Enter valid values for maximum number of cache entries
ODI-23055
ODI-23055: Session Blueprint Lifetime cannot be less than zero.
Category:
Other
Cause:
Value for session blueprint lifetime is not valid
Action:
Enter valid values forsession blueprint lifetime
ODI-23056
ODI-23056: Syntax of condition "{0}" is not valid.
Category:
Other
Cause:
The entered condition has invalid syntax.
Action:
Specify the valid condition expression.
ODI-23057
ODI-23057: The Registry Database is mandatory for MySQL Technology.
Category:
Other
Cause:
The Registry Database was not specified for MySQL Technology.
Action:
Enter the Registry Database for MySQL Technology.
ODI-23058
ODI-23058: This Technology does not support multiple schemas.
Category:
Other
Cause:
Attempt to create multiple Physical Schemas for Technologies that support only one Schema.
Action:
The solution for Technologies that do not support multiple Physical Schemas is to create separate Data Dervers from the Physical Schemas.
ODI-23059
ODI-23059: No Agent selected
Category:
Other
Cause:
No Agent has been selected for the selected DataSource.
Action:
Make sure an Agent is selected for the DataSource.
ODI-23060
ODI-23060: Update Import Modes are not valid for Interfaces
Category:
Other
Cause:
An invalid import mode of Update is selected for an Interface export file.
Action:
Use an import mode other than Update or alternatively only import Mapping export files
ODI-23061
ODI-23061: Syntax of expression "{0}" is not valid.
Category:
Other
Cause:
The entered expression has invalid syntax.
Action:
Specify the valid expression.
ODI-23062
ODI-23062: Maximum number of threads cannot be less then the maximum number of sessions.
Category:
Other
Cause:
Value for maximum number of threads is less than the maximum number of sessions
Action:
Ensure that maximum number of threads is equal to or greater than the maximum number of sessions
ODI-23064
ODI-23064 Language Name must be specified
Category:
Other
Cause:
Language name is not specified.
Action:
Enter Language name on the Languages table.
ODI-23065
ODI-23065 Parameter Key names not unique
Category:
Other
Cause:
Invalid values.
Action:
Parameter values need to be valid including uniquenames for keys.
ODI-23066
ODI-23066: Letter used in the icon input "{0}" is not valid. No Special Characters are allowed to be entered.
Category:
Other
Cause:
The entered input is invalid.
Action:
Enter the valid value.
ODI-23068
ODI-23068 : Degree Of Parallelism For Target has to be in the range of 1 to 99.
Category:
Other
Cause:
Value entered for Degree Of Parallelism is not in the range 1-99.
Action:
Please choose the appropriate Degree Of Parallelism For Target.
ODI-23069
ODI-23069 : Web Application Context must be provided
Category:
Other
Cause:
No value entered for the Web Application Context.
Action:
Please enter value for the Web Application Context.
ODI-23070
ODI-23070: Port number must be an integer between 0 and 65535.
Category:
Other
Cause:
The value for the Port Number was not valid.
Action:
Enter a valid integer value between 0 and 65535 for the Port Number.
ODI-23071
ODI-23071: Invalid Override Endpoint URL.
Category:
Other
Cause:
Override Endpoint URL enterred is invalid.
Action:
Please enter a valid Override Endpoint URL.
ODI-23072
ODI-23072: Invalid WSDL URL.
Category:
Other
Cause:
WSDL URL enterred is invalid.
Action:
Please enter a valid WSDL URL.
ODI-23073
ODI-23073: Duplicate Operation Names exist.
Category:
Other
Cause:
Duplicate Operation Names exist
Action:
Please ensure that operation names are unique.
ODI-23074
ODI-23074: The JNDI driver is mandatory.
Category:
Other
Cause:
A JNDI Driver was not specified and is a mandatory parameter.
Action:
A JNDI Protocol chosen from the drop down list may help to ensure the syntax is correct.
ODI-23075
ODI-23075: The JNDI URL is mandatory.
Category:
Other
Cause:
The JNDI URL field has not been entered and is a mandatory parameter.
Action:
Enter the URL parameter. A template chosen from the drop down list may help to ensure the syntax is correct.
ODI-23076
ODI-23076: The JNDI Resource is mandatory.
Category:
Other
Cause:
The JNDI Resource field has not been entered and is a mandatory parameter.
Action:
Enter the Resource parameter.
ODI-23077
ODI-23077: Please enter Credential file password.
Category:
Other
Cause:
Credential file password is a mandatory parameter for ewallet.p12.
Action:
Enter the credential file password.
ODI-23078
ODI-23078: Could not fetch details from Credential file. Please check logs for further details.
Category:
Other
Cause:
Error occurred while fetching details from Credential file.
Action:
Please check logs.
ODI-23079
ODI-23079: Invalid Credential file.
Category:
Other
Cause:
Valid credential file not found.
Action:
Please provide valid credential file path.
ODI-23080
ODI-23080: Credential file is not accessible.
Category:
Other
Cause:
Credential file does not have required permissions.
Action:
Please provide required permissions to Credential file.
ODI-23081
ODI-23081: Credential file could not be found at given path.
Category:
Other
Cause:
Credential file is not found in given path.
Action:
Please provide correct Credential file path.
ODI-23082
ODI-23082: Unable to retrieve credentials, the connection information does not match with any of the entries in Credential file.
Category:
Other
Cause:
Connection information does not match with any of the entries in Credential file.
Action:
Verify Credential file.
ODI-23083
ODI-23083: No connection information found in Credential file.
Category:
Other
Cause:
Credential file is empty.
Action:
Verify Credential file.
ODI-23084
ODI-23084: Please select an Oracle database connection.
Category:
Other
Cause:
No selection made.
Action:
Select Oracle database connection.
ODI-23085
ODI-23085: Entered password does not match Credential file password.
Category:
Other
Cause:
Credential file password is not valid.
Action:
Please try again.
ODI-24004
ODI-24004: There are no supervisor accounts in the ODI repository with matching entries in the identity store. Please provide a suitable supervisor account. Or you may also want to double check your JPS configuration file e.g. jps-config-jse.xml regarding the identity store configuration on properties such as {0}.
Category:
Other
Cause:
The ODI repository does not have any supervisor account that matches the entries in the identity store based on the identity store configuration from JPS configuration file.
Action:
Create a supervisor account in the ODI repository that matches an entry in the identify store. Or you may also want to double check your JPS configuration file e.g. jps-config-jse.xml file regarding the identity store configuration on properties such as username.attr, groupname.attr, user.search.bases, group.search.bases.
ODI-24005
ODI-24005: An error occurred while checking the status of the master repository.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
ODI-24006
ODI-24006: An error occurred while switching the authentication mode for the master repository.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
ODI-24007
ODI-24007: Rules should not have empty conditions.
Category:
Other
Cause:
Rules associated with policy have empty conditions.
Action:
Create rules with conditions associated with them.
ODI-25001
ODI-25001: Unable to input a larger element
Category:
Other
Cause:
The total length of all keywords exceeds the maximum length.
Action:
Remove one or more of the keywords, or decrease their lengths.
ODI-25002
ODI-25002: The end date cannot be before the start date.
Category:
Other
Cause:
The end date is before the start date.
Action:
Set the end date to be after the start date.
ODI-25003
ODI-25003: Error while starting session
Category:
Other
Cause:
An unexpected error occured while starting the session.
Action:
Check the error details for further information and contact Oracle Support Services for further assistance.
ODI-25004
ODI-25004: Date Format Not Valid
Category:
Other
Cause:
One of the Date fields is invalid. This may be the From or To Date.
Action:
Click the button to the right of the field to invoke a dialog for entering a valid Time and Date.
ODI-25005
ODI-25005: Incorrect date format . The format is {0}.
Category:
Other
Cause:
The date format is incorrect.
Action:
Use the format that is presented in the error message.
ODI-25006
ODI-25006: At least one agent must be selected.
Category:
Other
Cause:
Agent selection is mandatory.
Action:
Select at least one agent to clean stale sessions.
ODI-25007
ODI-25007: At least one work repository must be selected.
Category:
Other
Cause:
Work repository selection is mandatory.
Action:
Select at least one work repository to clean stale sessions.
ODI-25008
ODI-25008: You are not allowed to delete session variable.
Category:
Other
Cause:
User attempt to delete session variable.
Action:
Cancel deleting session variable.
ODI-25009
ODI-25009: You are not allowed to delete scenario variable.
Category:
Other
Cause:
User attempt to delete scenario variable.
Action:
Cancel deleting scenario variable.
ODI-26001
ODI-26001: Boolean does not correspond to the Field Update Object Layer.
Category:
Other
Cause:
The repository contained an invalid value of the Field Update property for a checkbox or radio group.
Action:
Ensure the repository value is a boolean for checkbox or a valid action command for a radio group.
ODI-26002
ODI-26002: This object is referenced by another object. View the details for more information. You may also see where this object is used in the hierarchy.
Category:
Other
Cause:
The specified object could not be used because it is referenced by another object.
Action:
Remove references to this object. The "Uses" hierarchy may be useful in finding objects references.
ODI-26003
ODI-26003: This object cannot be removed: it is referenced by another object.
Category:
Other
Cause:
The specified object could not be deleted because it is referenced by another object.
Action:
Remove references to this object before deleting it. The "Uses" hierarchy may be useful in finding objects references.
ODI-26004
ODI-26004: Action denied:
Category:
Other
Cause:
The current license may not allow use of the designer.
Action:
Review the error details for further information.
ODI-26005
ODI-26005: You are importing an object from another repository with the same identifier. It is forbidden.
Category:
Other
Cause:
An object in the import file has an identifier which already exists in the repository.
Action:
Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
ODI-26006
ODI-26006: The specified encryption key is invalid.
Category:
Other
Cause:
The encryption key specified was found to be invalid during the decrypting phase.
Action:
Ensure a valid encryption key is utilized.
ODI-26007
ODI-26007: KM or Procedure not encrypted. No decryption was performed.
Category:
Other
Cause:
Decryption was requested for a non-encypted KM or Procedure.
Action:
Do not attempt to decrypt a non-encrypted KM or Procedure.
ODI-26008
ODI-26008: Scenario not encrypted. No decryption was performed.
Category:
Other
Cause:
Decryption was requested for a non-encypted Scenario.
Action:
Do not attempt to decrypt a non-encrypted Scenario.
ODI-26009
ODI-26009: Action not encrypted. No decryption was performed.
Category:
Other
Cause:
Decryption was requested for a non-encypted Action.
Action:
Do not attempt to decrypt a non-encrypted Action.
ODI-26010
ODI-26010: Decryption failed due to incompatible key.
Category:
Other
Cause:
The key provided to decrypt was an invalid key.
Action:
Ensure the decryption key is correctly specified.
ODI-26011
ODI-26011: unable to find specified encryption API
Category:
Other
Cause:
The specified cryptographic algorithm requested was not available in the environment.
Action:
Ensure the environment can access the DES/ECB/PKCS5Padding algorithms and padding.
ODI-26012
ODI-26012: invalid encrypted data.
Category:
Other
Cause:
The BASE64 content may be invalid or the zip file contents may be corrupted.
Action:
Ensure the encrypted data is correct and the decryption key is correctly specified.
ODI-26013
ODI-26013: Your security parameters are insufficient to perform this action.
Category:
Other
Cause:
The ODI user security parameters do not specifically permit the user to perform this particular action.
Action:
Ensure this ODI user is granted the security access to perform this action.
ODI-26014
ODI-26014: The code of your {0} is already used by another {1}. Please give another code to save this {2}.
Category:
Other
Cause:
The value entered for code must be unique for the entire work repository.
Action:
Ensure the a unique value is entered.
ODI-26015
ODI-26015: You do not have sufficient privileges to perform this operation.
Category:
Security
Cause:
The ODI user security parameters do not specifically permit the user to perform this particular operation.
Action:
Ensure this ODI user is granted the security access to perform this operation.
ODI-26016
ODI-26016: The requested operation cannot succeed. The object no longer exists.
Category:
Other
Cause:
The specified ODI object cannot be accessed because it no longer exists in the repository (it may have been deleted by another ODI user).
Action:
Recreate the specified ODI object. Consider importing the object from a backup.
ODI-26017
ODI-26017: Error.
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-26018
ODI-26018: Key Error.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Review the error details for further information.
ODI-26019
ODI-26019: Action Denied.
Category:
Other
Cause:
An unexpected error occurred.
Action:
Review the error details for further information.
ODI-26020
ODI-26020: Retrieve method incorrect.
Category:
Other
Cause:
Retrieve method is incorrect. Must be "set" or "get".
Action:
Please change the retrieve method to "set" or "get".
ODI-26021
ODI-26021: Object initialization denied.
Category:
Other
Cause:
A component could not be initialized.
Action:
Ensure that the user has security permissions to create the object.
ODI-26022
ODI-26022: Unrecoverable error during object saving.
Category:
Other
Cause:
The object could not be saved. This is possibly due to a repository connection error, or inconsistent data values supplied. It's also possible that the object was modified by another user.
Action:
Ensure the repository database is available and the data values supplied are valid. Try to save changed data, then refresh edited object and apply changed data again.
ODI-26023
ODI-26023: Cannot create object.
Category:
Other
Cause:
An unexpected error occured during the object creation process.
Action:
Contact Oracle Support Services.
ODI-26024
ODI-26024: Cannot stop update operation.
Category:
Other
Cause:
An unexpected error occured during the update operation.
Action:
Contact Oracle Support Services.
ODI-26025
ODI-26025: Display Initialization denied.
Category:
Other
Cause:
An unexpected error occured during the display initialization process.
Action:
Contact Oracle Support Services.
ODI-26026
ODI-26026: Cannot refresh.
Category:
Other
Cause:
An unexpected error occured during the refresh process.
Action:
Contact Oracle Support Services.
ODI-26027
ODI-26027: Security not set for the instance. The instance will not be added to the tree.
Category:
Security
Cause:
Instance security permissions "By repository" were choosen but a concrete repository is not specified.
Action:
Ensure a repository is specified.
ODI-26028
ODI-26028: Cannot save your modifications.
Category:
Other
Cause:
Internal error.
Action:
No action required.
ODI-26029
ODI-26029: Could not deploy the datasource automatically.
Category:
Other
Cause:
Weblogic Administration server is not up and running, the server connection parameters are wrong.
Action:
Please check Weblogic Administration server connection parameters and the server state.
ODI-26030
ODI-26030: The new password does not meet the password policy. Your change could not be saved.
Category:
Other
Cause:
The new password does not meet the password policy.
Action:
Please verify that the new password meets the password policy (go to the "Security Navigator -> Password policies...").
ODI-26031
ODI-26031: You may not delete work repository {0} because you are connected to it. To delete this repository, reconnect to a different work repository or use a master repository only connection.
Category:
Other
Cause:
Deletion of a work repository which is currently connected is not supported.
Action:
Disconnect from the repository and then connect utilizing a Master Repository Only connection or a different work repository before attempting to delete the specified work repository.
ODI-26032
ODI-26032: This object was modified by {0} on {1} at {2}. Your changes cannot be saved.
Category:
Other
Cause:
The object was changed in the repository after the editor was opened for this object.
Action:
Close the editor without saving changes. Open the editor again and reapply the edits and save. Note: consider using the lock object facility to disallow current modifications to an object.
ODI-26033
ODI-26033: You cannot edit this object because it is locked by another user ({0}). You can only view it.
Category:
Other
Cause:
The ODI object opened for editing is locked by another user. Other ODI users can only view such objects.
Action:
Try to edit the object later.
ODI-26034
ODI-26034: An error occurred while deleting executions.
Category:
Other
Cause:
The specified executions could not be deleted. This is possibly caused by the repository database connection problems.
Action:
Retry to delete the executions. If problem persists, contact Oracle Support Services.
ODI-26035
ODI-26035: Error.
Category:
Other
Cause:
Internal error.
Action:
Review the error details for further information.
ODI-26036
ODI-26036: Error while encrypting.
Category:
Other
Cause:
A general error occured during the ecrypting process, possibly caused by caused by repository database access problems, lack of security permissions, or encryption engine failures,
Action:
Retry the encrypt action again.
ODI-26037
ODI-26037: Encryption key is not valid.
Category:
Other
Cause:
An invalid encryption key was entered causing an encryption engine failure.
Action:
Enter a valid encryption key and retry the action.
ODI-26038
ODI-26038: Unable to execute, the selected Logical Agent is not associated to a Physical Agent in the desired Context.
Category:
Other
Cause:
A Logical Agent was not associated with this Physical Agent in this Context.
Action:
Ensure a valid "Logical Agent - Physical Agent" association exists in the desired Context.
ODI-26039
ODI-26039: Connection failed.
Category:
Other
Cause:
The attempt to connect to the repository failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.
Action:
Ensure the repository database is available and acceccesible and the repository connection parameters are correct.
ODI-26040
ODI-26040: error while updating
Category:
Other
Cause:
Failed to update the ODI logins file: snps_login_work.xml.
Action:
Ensure write-access is granted to the ODI logins file: snps_login_work.xml.
ODI-26041
ODI-26041: Error while attempting to get FieldData from ObjectDisplay.
Category:
Other
Cause:
An unexpected error occured obtaining FieldData from ObjectDisplay.
Action:
Contact Oracle Support Services.
ODI-26042
ODI-26042: Error while attempting to set FieldUpdate from ObjectUpdate.
Category:
Other
Cause:
An unexpected error occured updating FieldUpdate from ObjectUpdate.
Action:
Contact Oracle Support Services.
ODI-26043
ODI-26043: Window closing cancelled by the User.
Category:
Other
Cause:
User asked to close the parent window where child lines were modified.
Action:
No action performed on that.
ODI-26044
ODI-26044: Host Variable Not Found.
Category:
Other
Cause:
An unexpected error occurred searching for a host variable.
Action:
Review the error details for further information.
ODI-26045
ODI-26045: Unable to perform the drop operation.
Category:
Other
Cause:
Dropped entity is invalid.
Action:
Check whether the dropped entity is valid and perform the drag-n-drop action again.
ODI-26046
ODI-26046: MethodGetter was not found
Category:
Other
Cause:
An unexpected error occured obtaining the getter method.
Action:
Contact Oracle Support Services.
ODI-26047
ODI-26047: Object on method setObjectDisplay(Object pObjectDisplay) is not an array.
Category:
Other
Cause:
This is caused by programmatic error.
Action:
ODI users should normally never see this message.
ODI-26048
ODI-26048: Object on method setObjectDisplay(Object pObjectDisplay) is not a vector.
Category:
Other
Cause:
This is caused by programmatic error.
Action:
ODI users should normally never see this message.
ODI-26049
ODI-26049: Parameters not valid.
Category:
Other
Cause:
An unexpected error occured due to an invalid parameter value.
Action:
Contact Oracle Support Services.
ODI-26050
ODI-26050: Master repository not installed on this connection.
Category:
Other
Cause:
This is caused by programmatic error.
Action:
ODI users should normally never see this message.
ODI-26051
ODI-26051: XML Export Error.
Category:
Other
Cause:
An error occured during the creation of the XML Export file.
Action:
Ensure the repository is accessible and the export file and its directory are writable.
ODI-26052
ODI-26052: XML Import Error.
Category:
Other
Cause:
An unexpected error occurred while importing an XML document.
Action:
Review the error details for further information.
ODI-26053
ODI-26053: An error occurred during initialization.
Category:
Other
Cause:
Initialization failed possibly due a repository access failure or insufficient ODI security permissions.
Action:
Ensure the repository database is available, and the ODI user security permissions permit connection.
ODI-26054
ODI-26054: Page not available.
Category:
Other
Cause:
The selected page number was invalid.
Action:
Ensure the page number entered is greater than 0 and less than the total number of pages.
ODI-26056
ODI-26056: Error while disconnecting.
Category:
Other
Cause:
This error is occured while closing the repository database connection after "Test query" action completed.
Action:
This error may be ignored.
ODI-26057
ODI-26057: Unable to connect the agent. The agent is probably not started.
Category:
Other
Cause:
The connection request to the agent failed.
Action:
Ensure the agent is started and available. Ensure the connection information is valid.
ODI-26058
ODI-26058: Unable to connect the agent. The agent URL cannot be found.
Category:
Other
Cause:
The connection request to the agent failed using the given URL.
Action:
Ensure the agent is started and available. Ensure the connection URL information is valid.
ODI-26059
ODI-26059: Object on method setObjectDisplay(Object pObjectDisplay) is not a List.
Category:
Other
Cause:
An unexpected error occured setting ObjectData.
Action:
Contact Oracle Support Services.
ODI-26060
ODI-26060: The Password and Confirmation Password do not match.
Category:
Other
Cause:
The values entered for Password and Confirmation Password did not match.
Action:
Enter the same value for Password and Confirmation Password.
ODI-26061
ODI-26061: The minimum password length is {0} characters.
Category:
Other
Cause:
The length of the Password entered is less than specified in password policy rule.
Action:
Enter a Password whose length is greater than or equal to the specified minimum length.
ODI-26062
ODI-26062: The password violates the following rule: "{0}". Select another password.
Category:
Other
Cause:
The password supplied was invalid.
Action:
Enter a valid password.
ODI-26063
ODI-26063: Invalid password.
Category:
Other
Cause:
The password supplied was invalid.
Action:
Enter a valid password.
ODI-26064
ODI-26064: Error while exporting.
Category:
Other
Cause:
An error occured during the creation of the Export file.
Action:
Ensure the repository is accessible and the export file and its directory are writable.
ODI-26065
ODI-26065: You must specify all the options.
Category:
Other
Cause:
This is caused by programmatic error.
Action:
ODI users should normally never see this message.
ODI-26066
ODI-26066: An unexpected error has occurred.
Category:
Other
Cause:
An unexpected error occured this process.
Action:
Retry action. If problem persists then contact Oracle Support Services.
ODI-26067
ODI-26067: mandatory field "Java charset" not entered
Category:
Other
Cause:
A value for the "Java character set" field was not entered.
Action:
Enter a value for the "Java character set" field.
ODI-26068
ODI-26068: unable to load export list in the module: {0}
Category:
Other
Cause:
The contents of the export file list was not formatted correctly.
Action:
Correct the format of the export list file specified.
ODI-26069
ODI-26069: The specified export directory does not exist.
Category:
Other
Cause:
The specified export directory is invalid.
Action:
Ensure the specified export directory exists and is writable.
ODI-26070
ODI-26070: The Open Tool class name must not begin with "Snp" or "Odi".
Category:
Other
Cause:
The Open Tool class name begins with "Snp" or "Odi".
Action:
Ensure the Open Tool class name does not begin with "Snp" or "Odi".
ODI-26071
ODI-26071: Open Tool not activated. Your Open Tool references a class which not found.
Category:
Other
Cause:
The class name specified in this Open Tool was not found.
Action:
Ensure the Open Tool class name specified is valid and available in the class path.
ODI-26072
ODI-26072: Your Open Tool has been installed. You can now use it in a procedure or package.
Category:
Other
Cause:
Installation of the Open Tool has been completed.
Action:
No action is required.
ODI-26073
ODI-26073: Could not activate Open Tool. Check that it is in the "oracledi/userlib" directory.
Category:
Other
Cause:
The Open Tool references a class which was not found.
Action:
Ensure the Open Tool class exists in the "oracledi/userlib" directory.
ODI-26074
ODI-26074: Policy "Name" is a mandatory field.
Category:
Other
Cause:
A value for the Policy "Name" field value was not entered.
Action:
Enter a value for the Policy "Name" field.
ODI-26075
ODI-26075: Policy "Name" must be unique.
Category:
Other
Cause:
A Policy with the same name already exists.
Action:
Enter a unique value in Policy "Name" field.
ODI-26076
ODI-26076: You do not have enough memory to generate this report. Increase the maximum Java heap size value (-Xmx).
Category:
Other
Cause:
There was not enough memory allocated to generate the report.
Action:
Increase the maximum Java heap size value by using the "-Xmx" JVM option.
ODI-26077
ODI-26077: Target file name is not specified.
Category:
Other
Cause:
The Target file name is mandatory and was not specified.
Action:
Enter a value for the target file name.
ODI-26078
ODI-26078: Error while creating the version
Category:
Other
Cause:
An unexpected error occurred while versioning an object.
Action:
Review the error details for further information.
ODI-26079
ODI-26079: Version already exists, versioning aborted.
Category:
Other
Cause:
A version with the specified version number already exists.
Action:
Enter a unique version number.
ODI-26080
ODI-26080: Unable to delete version {0} for {1} {2}. It is referenced by label {3}
Category:
Other
Cause:
Deletion of a version of an object referenced by a Solution was attempted.
Action:
Delete the label referencing the object version. Then retry deleting the object version.
ODI-26081
ODI-26081: Unable to delete version {0} for {1} {2}. It is referenced by version {3} of label {4}
Category:
Other
Cause:
An object version cannot be deleted because it is referenced.
Action:
If an object version must be deleted, remove all references first.
ODI-26082
ODI-26082: No difference found
Category:
Other
Cause:
No difference was found between two object versions.
Action:
No action is required.
ODI-26083
ODI-26083: No difference found.
Category:
Other
Cause:
No difference was found between object versions.
Action:
No action is required.
ODI-26084
ODI-26084: Could not compare versions of different objects.
Category:
Other
Cause:
Objects of different types were selected for comparison.
Action:
Select objects of the same type before performing comparison.
ODI-26085
ODI-26085: You cannot restore several versions of the same object.
Category:
Other
Cause:
Multiple versions were selected for restoring.
Action:
Select a single version when performing this action.
ODI-26086
ODI-26086: You cannot select more than one version at the same time.
Category:
Other
Cause:
Multiple version were selected for this action.
Action:
Select a single version when performing this action.
ODI-26087
ODI-26087: You must select a version.
Category:
Other
Cause:
A version was not selected.
Action:
Select a version before performing this action.
ODI-26088
ODI-26088: You must select the version to restore.
Category:
Other
Cause:
A version to restore was not selected.
Action:
Select a version to restore.
ODI-26089
ODI-26089: This object is currently locked by user: {0}. Version restoration cancelled.
Category:
Other
Cause:
The object selected for restoration was locked by another user.
Action:
Ensure the selected object is not locked by another user before retrying the operation.
ODI-26090
ODI-26090: Object version list is empty.
Category:
Other
Cause:
The object selected was not versioned.
Action:
Select a versioned object before retrying the operation.
ODI-26091
ODI-26091: An array with an invalid size was passed to SnpsObjectTableColumnTextIntrospectMapper.createMapFromArrayOfArrays.
Category:
Other
Cause:
An array with an invalid size was passed to SnpsObjectTableColumnTextIntrospectMapper.createMapFromArrayOfArrays.
Action:
Review the error details for further information.
ODI-26092
ODI-26092: Table Model must have at least one Column.
Category:
Other
Cause:
The Model for this Table did not contain any Columns.
Action:
Add at least one Column to the Table's Model.
ODI-26093
ODI-26093: Unable to open window.
Category:
Other
Cause:
An unexpected error occurred while opening a window.
Action:
Review the error details for further information.
ODI-26094
ODI-26094: Your license does not allow Changed Data Capture operations.
Category:
Other
Cause:
The current license does not include change data capture.
Action:
Upgrade the license to include change data capture.
ODI-26095
ODI-26095: This object is locked by {0}. You cannot edit it unless it is unlocked.
Category:
Other
Cause:
Object could not be opened for write access because it was already locked by another user.
Action:
Ensure the selected object is not locked by another user before retrying the operation.
ODI-26096
ODI-26096: Replacement of object failed.
Category:
Other
Cause:
The file specified did not contain correctly formed XML.
Action:
Ensure the XML in the specified file is valid before retrying the operation.
ODI-26097
ODI-26097: Replace failed due to an SQL exception.
Category:
Other
Cause:
The file used to replace this object is not a valid XML format.
Action:
Select a valid XML file format before performing this replace object action.
ODI-26098
ODI-26098: You must specify an Export Path or File.
Category:
Other
Cause:
Either the Export Path or File was not specified.
Action:
Specify a value for either the Export Path or File.
ODI-26099
ODI-26099: You don't have the appropriate license to use this KM
Category:
Other
Cause:
The current license does not include usage of the specified KM.
Action:
Select another compatible KM or upgrade the license.
ODI-26100
ODI-26100: You don't have the appropriate privileges on Step objects.
Category:
Other
Cause:
Package Steps operation failed due to insufficient ODI security permissions.
Action:
Ensure the ODI user security permissions are correct for the Package Steps object.
ODI-26101
ODI-26101: The Data Check cannot be performed. A CKM is not selected on the Model.
Category:
Other
Cause:
No CKM was assigned to the Model.
Action:
Enter a CKM for the Model before performing the Data Check. Consider using the Model editor to make this entry.
ODI-26102
ODI-26102: The Service cannot be generated. An Application Server is not selected on the Model.
Category:
Other
Cause:
No Application Server was assigned to the Model.
Action:
Enter an Application Server for the Model before performing Generate Service. Consider using the Model editor to make entry.
ODI-26103
ODI-26103: You must specify a connection parameter
Category:
Other
Cause:
Repository connection parameters have not been specified.
Action:
Enter all required repository connection parameters.
ODI-26104
ODI-26104: You must specify a query parameter
Category:
Other
Cause:
A query parameter is missing for retrieving a level.
Action:
Supply the missing parameter.
ODI-26105
ODI-26105: Test failed
Category:
Other
Cause:
The value of Schema, Table, Column or Filter was invalid.
Action:
Ensure the Schema, Table, Column and Filter are valid. Consult the details for additional information.
ODI-26106
ODI-26106: Decryption failed. Data has been restored.
Category:
Other
Cause:
The Decryption process failed.
Action:
Consult the details for additional information.
ODI-26107
ODI-26107: Cannot find this {0} icon
Category:
Other
Cause:
An unexpected error occurred while searching for an icon.
Action:
Review the error details for further information.
ODI-26108
ODI-26108: The specified path is not valid.
Category:
Other
Cause:
The specified path was invalid or was not found on the file system.
Action:
Ensure a valid file system path is entered.
ODI-26109
ODI-26109: Error while reading the search criteria. Invalid file
Category:
Other
Cause:
The selected file did not contain search criteria in a valid format.
Action:
Ensure the selected file is one exported from the ODI search UI and contains correctly formatted search criteria information.
ODI-26110
ODI-26110: An error occurred while saving.
Category:
Other
Cause:
An unexpected error occurred during a save operation.
Action:
Review the error details for further information. Ensure that the repository connection is open.
ODI-26111
ODI-26111: Error while accessing the file
Category:
Other
Cause:
The specified file could not be opened.
Action:
Ensure the specified file exists and is accessible.
ODI-26112
ODI-26112: Error while performing the search
Category:
Other
Cause:
An unexpected error occurred while searching for an object.
Action:
Review the error details for additional information.
ODI-26113
ODI-26113: XML parser configuration error
Category:
Other
Cause:
The selected file is not a valid search criteria file format.
Action:
Select a valid search criteria file exported from the ODI search UI.
ODI-26114
ODI-26114: Host cannot be empty.
Category:
Other
Cause:
The Host field is mandatory and was not specified.
Action:
Enter a valid Host name.
ODI-26115
ODI-26115: Port number must be an integer between 1024 and 65535.
Category:
Other
Cause:
The value for Port Number was not valid.
Action:
Enter a valid integer value between 1024 and 65535 for Port Number.
ODI-26116
ODI-26116: User cannot be empty.
Category:
Other
Cause:
The User field is mandatory and was not supplied.
Action:
Enter a valid User Name.
ODI-26117
ODI-26117: Connection failed. Reason:
Category:
Other
Cause:
Could not connect to a repository with the specified connection details.
Action:
Ensure the repository database is available and valid connection details are supplied.
ODI-26118
ODI-26118: External password storage connection test failed.
Category:
Other
Cause:
Could not connect to the external password storage with the specified connection details.
Action:
Ensure the external password storage is available and valid connection details are supplied.
ODI-26119
ODI-26119: Exception when computing the value
Category:
Other
Cause:
An unexpected error occurred while comparing tables.
Action:
Review the error details for further information.
ODI-26120
ODI-26120: Fields compared are not the same
Category:
Other
Cause:
An unexpected error occurred while comparing fields.
Action:
Review the error details for further information.
ODI-26121
ODI-26121: Error while exploring version
Category:
Other
Cause:
An unexpected error occurred while checking the version.
Action:
Review the error details for further information.
ODI-26122
ODI-26122: Exception when getting the children list
Category:
Other
Cause:
An unexpected error occurred while getting a list of child elements.
Action:
Review the error details for further information.
ODI-26123
ODI-26123: Cannot connect to the repository with the provided login information.
Category:
Other
Cause:
Could not connect to a repository with the specified connection details.
Action:
Ensure the repository database is available and valid connection details are supplied.
ODI-26124
ODI-26124: Exception during connection to the repository with the provided login information:
Category:
Other
Cause:
Could not connect to a repository with the specified connection details.
Action:
Ensure the repository database is available and valid connection details are supplied.
ODI-26125
ODI-26125: The configured external password storage is still accessible. Instead, use the Password Storage Switch service to change the configuration.
Category:
Other
Cause:
Could not connect to the external password storage with the specified connection details.
Action:
Ensure the external password storage is available and valid connection details are supplied. Consider using the Password Storage Switch service to change the configuration.
ODI-26126
ODI-26126: Error while opening window.
Category:
Other
Cause:
An unexpected error occured while opening window.
Action:
Contact Oracle Support Services.
ODI-26127
ODI-26127: The selected master repository configured to use internal password storage. Recovery is possible only for external storages.
Category:
Other
Cause:
Recovery was attempted for a master repository configured to use internal password storage.
Action:
Select a master repository not configured to use internal password storage.
ODI-26128
ODI-26128: Unable to open Editor
Category:
Other
Cause:
An unexpected error occurred while opening an editor.
Action:
Review the error details for further information.
ODI-26129
ODI-26129: Unable to open Editor: Technology could not be opened twice
Category:
Other
Cause:
Technology editor is already open.
Action:
Close the other editor before opening a new technology editor.
ODI-26130
ODI-26130: Could not connect to repository
Category:
Other
Cause:
Could not connect to a repository with the specified connection details.
Action:
Ensure the repository database is available and valid connection details are supplied.
ODI-26131
ODI-26131: Specify Import Path
Category:
Other
Cause:
A value for Import Path is a mandatory and it was not supplied.
Action:
Enter the correct value for the Import Path.
ODI-26132
ODI-26132: Repository id {0} or Repository name {1} is already used in your master repository.
Category:
Other
Cause:
The ID or Name specified for the master repository were already used.
Action:
Enter valid unique values for Repository ID and Repository name.
ODI-26134
ODI-26134: Invalid number format for port number.
Category:
Other
Cause:
The value specified for Port Number was not in a valid format and number range.
Action:
Enter a valid Port Number. See SQL*Net documentation for additional information regarding format and range.
ODI-26135
ODI-26135: The Network Adapter could not establish the connection.
Category:
Other
Cause:
Connection via the Network Adapter could not be established.
Action:
Ensure the network resource is available and the connection details in the Network Adapter are correct..
ODI-26136
ODI-26136: The specified character set is not supported.
Category:
Other
Cause:
The specified character set was not supported.
Action:
Select a supported character set.
ODI-26137
ODI-26137: The context or type are incorrect.
Category:
Other
Cause:
The selected ODI context is invalid: it was probably removed from the repository database.
Action:
Reopen Execution dialog again so that the list of ODI contexts will be reloaded.
ODI-26138
ODI-26138: Server initialization failed.
Category:
Other
Cause:
The attempt to initialize the server failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.
Action:
Ensure the server is available and acceccesible and the connection parameters are correct.
ODI-26139
ODI-26139: Oozie Engine initialization failed.
Category:
Other
Cause:
The attempt to initialize the Oozie engine failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.
Action:
Ensure the Oozie engine is available and acceccesible and the connection parameters are correct.
ODI-26140
ODI-26140: Oozie Engine test failed.
Category:
Other
Cause:
The attempt to initialize the Oozie engine failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.
Action:
Ensure the Oozie engine is available and acceccesible and the connection parameters are correct.
ODI-26150
ODI-26150: Incorrect Context.
Category:
Other
Cause:
A valid Context was not specified.
Action:
Select a Context from the list. If none are available then create one from the Topology Navigator.
ODI-26153
ODI-26153: Connection failed; JDBC Error
Category:
Other
Cause:
An unexpected JDBC error was encountered during the connection process.
Action:
Ensure the resource referenced is available and the connection information is correct.
ODI-26155
ODI-26155: No Master Repository on this connection
Category:
Other
Cause:
A connection to the Master Repository could not be established.
Action:
Ensure the Master Repository is available and valid connection details are provided.
ODI-26156
ODI-26156: Designer cannot connect to an Execution repository. The operation will be canceled.
Category:
Other
Cause:
Unable to establish a connection to the Execution repository.
Action:
Ensure the Execution repository is available and the connection details are correct.
ODI-26157
ODI-26157: Connection Error
Category:
Other
Cause:
A connection to the Master Repository could not be established.
Action:
Ensure the Master Repository is available and valid connection details are provided.
ODI-26158
ODI-26158: Work Repository Attachment Error
Category:
Other
Cause:
A connection to the Work Repository could not be established.
Action:
Ensure the Work Repository is available and valid connection details are provided.
ODI-26159
ODI-26159: Error while creating Work Repository
Category:
Other
Cause:
An unexpected error occurred while creating the Work Repository.
Action:
Correct any issues described in the error details.
ODI-26160
ODI-26160: URL not referenced in the list.
Category:
Other
Cause:
The URL is not valid for the driver.
Action:
Ensure that the URL parameters are correct and in the proper format.
ODI-26161
ODI-26161: File Not Found
Category:
Other
Cause:
The XML file for the driver or URL format list is missing.
Action:
Review the exception for the missing file. Those files should be included with the installation.
ODI-26162
ODI-26162: Connection failure
Category:
Other
Cause:
A connection to the repository could not be established.
Action:
Ensure the repository is available and valid connection details are provided.
ODI-26163
ODI-26163: Access Denied
Category:
Other
Cause:
A connection to the repository could not be established because of insufficient user privilege.
Action:
Ensure the ODI user has sufficient privilege to connect to the specified repository.
ODI-26164
ODI-26164: The reverse cannot be executed. Your Model will be created.
Category:
Other
Cause:
The specified technology or driver did not support standard reverse-engineering.
Action:
Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
ODI-26165
ODI-26165: This driver has no match in the URL list
Category:
Other
Cause:
A match could not be made between the driver and the list of URLs.
Action:
Ensure that the correct driver has been selected.
ODI-26166
ODI-26166: The template was not generated: {0}
Category:
Other
Cause:
The WLS Template could not be generated.
Action:
Correct any errors identified in the error log and retry the operation.
ODI-26167
ODI-26167: File System Error: {0}
Category:
Other
Cause:
Creation of the Server Template file failed due to an error detected by the file system.
Action:
Correct any errors identified in the error log. Ensure the file system location is accessible and retry the operation.
ODI-26168
ODI-26168: Client requires a repository with version {0} but the repository version found is {1}
Category:
Other
Cause:
Could not connect to the repository due to the old repository version.
Action:
Update repository to the latest version.
ODI-26169
ODI-26169: JDBC driver is mandatory.
Category:
Other
Cause:
JDBC driver was not entered.
Action:
Provide JDBC driver for database connection.
ODI-26170
ODI-26170: JDBC URL is mandatory.
Category:
Other
Cause:
JDBC URL was not entered.
Action:
Provide JDBC URL for database connection.
ODI-26171
ODI-26171: User is mandatory.
Category:
Other
Cause:
User was not entered.
Action:
Provide user for database connection.
ODI-26172
ODI-26172: Id is mandatory.
Category:
Other
Cause:
Id was not entered.
Action:
Provide work repository ID.
ODI-26173
ODI-26173: Name is mandatory.
Category:
Other
Cause:
Name was not entered.
Action:
Provide work repository name.
ODI-26174
ODI-26174: Database connection is not available.
Category:
Other
Cause:
Connection error occurred while connecting to the database.
Action:
Verify that the Database Connection details are correct and the database is available.
ODI-26175
ODI-26175: Import folder does not exist or not a valid folder.
Category:
Other
Cause:
Non-existing or invalid folder was specified.
Action:
Ensure the specified folder path is correct and refers to an existing folder.
ODI-26176
ODI-26176: Import file does not exist or not a valid file.
Category:
Other
Cause:
Non-existing or invalid file was specified.
Action:
Ensure the specified file path is correct and refers to an existing file.
ODI-26177
ODI-26177: Unable to connect to the DBA user.
Category:
Other
Cause:
Unable to connect to the DBA account.
Action:
Check that the DBA username and password are correct.
ODI-26178
ODI-26178: Unable to connect to the Repository user.
Category:
Other
Cause:
Unable to connect to the Repository account.
Action:
Check that the Repository connection details are correct.
ODI-26179
ODI-26179: Invalid Date Format
Category:
Other
Cause:
An Invalid Date format was entered in the date filter.
Action:
Ensure the date entered is of the required format.
ODI-26180
ODI-26180: Changing the name of a sequence only impacts the sequence itself; Users need to manually change object(s) which reference the old sequence name.
Category:
Other
Cause:
Action:
ODI-26181
ODI-26181: Unable to add a Project knowledge module
Category:
Other
Cause:
An unsupported action was attempted.
Action:
No action required as Project knowledge modules are not a valid selection to be added to a solution.
ODI-26182
ODI-26182: Object was modified by another user and cannot be saved.
Category:
Other
Cause:
The object could not be saved. It's possible that the object was modified by another user.
Action:
Try to save changed data, then refresh edited object and apply changed data again.
ODI-26183
ODI-26183: The maximum password length is {0} characters.
Category:
Other
Cause:
The entered work repository password length is greater than allowed.
Action:
Provide a shorter password.
ODI-26184
ODI-26184: SQL error occurred. See error details for more information.
Category:
Other
Cause:
SQL error occurred while performing UI action.
Action:
If this error is not expected, contact Oracle Support Services.
ODI-26185
ODI-26185: File does not exist or cannot be created. See error details for more information.
Category:
Other
Cause:
UI action tried to open a file which did not exist, or create a file which could not be created due to some reasons.
Action:
Make sure the file path is typed correctly. Make sure application has enough file system permissions in order to create a file at the specified path.
ODI-26186
ODI-26186: Character set is not supported. See error details for more information.
Category:
Other
Cause:
UI action tried to use character encoding which is not supported.
Action:
Make sure character set is typed correctly.
ODI-26187
ODI-26187: Unexpected I/O error occurred. See error details for more information.
Category:
Other
Cause:
UI action caused unexpected I/O error.
Action:
Contact Oracle Support Services.
ODI-26188
ODI-26188: There is no enough memory to perform this UI action. Increase the maximum Java heap size value (-Xmx).
Category:
Other
Cause:
UI action requires more memory than available at the current moment.
Action:
Increase the maximum Java heap size value by using the "-Xmx" JVM option.
ODI-26189
ODI-26189: Unexpected report generation error occurred. See error details for more information.
Category:
Other
Cause:
UI action caused unexpected report generation error.
Action:
Contact Oracle Support Services.
ODI-26190
ODI-26190: A user with same name {0} already exists in ODI. Note: LDAP user name is case insensitive. You have to first drop that user prior to registering or changing this one.
Category:
Other
Cause:
Due to LDAP user name is case insensitive so ODI will follow same rule in external authenticaiton mode.
Action:
Please drop the existing user with same name(ingoring case) first prior to registering this one.
ODI-26191
ODI-26191: You cannot move this object because it is locked by another user ({0}).
Category:
Other
Cause:
This object was locked by another user.
Action:
Wait until object is unlocked.
ODI-26192
ODI-26192: You cannot drag & drop this object because it is locked by another user ({0}).
Category:
Other
Cause:
This object was locked by another user.
Action:
Wait until object is unlocked .
ODI-26193
ODI-26193: You are not allowed to delete master repository.
Category:
Other
Cause:
User attempt to delete master repository.
Action:
Cancel deleting master repository.
ODI-26194
ODI-26194: Database Connection User is mandatory.
Category:
Other
Cause:
Database Connection User was not entered.
Action:
Provide Database Connection User.
ODI-26195
ODI-26195: Database Connection Password is mandatory.
Category:
Other
Cause:
Database Connection Password was not entered.
Action:
Provide Database Connection Password.
ODI-26196
ODI-26196: Failed to migrate login information to new format.
Category:
Other
Cause:
ODI was not able to migrate login information from old format into the new format.
Action:
Make sure that directory %ODI_HOME%/oracledi has write permissions. Try manually copying %ODI_HOME%/oracledi/snps_login_work.xml into %ODI_HOME%/oracledi/snps_login_work_12.xml file.
ODI-26197
ODI-26197: Failed to delete old login information.
Category:
Other
Cause:
ODI was not able to delete old login information after migration from old format into the new format.
Action:
Make sure that directory %ODI_HOME%/oracledi and file %ODI_HOME%/oracledi/snps_login_work.xml have write permissions. Try manually removing %ODI_HOME%/oracledi/snps_login_work.xml file.
ODI-26198
ODI-26198: Passwords do not match.
Category:
Other
Cause:
Password confirmation doesn't match the entered password.
Action:
Make sure that password and password confirmation are the same.
ODI-26199
ODI-26199: User {0} is not authorized to grant object {1}.
Category:
Security
Cause:
Current user is not authorized to grant generic object privileges
Action:
Assign generic object privileges to user.
ODI-26200
ODI-26200: User {0} is not authorized to grant method {1}.
Category:
Security
Cause:
Current user is not authorized to grant generic method privileges
Action:
Assign generic method privileges to user.
ODI-26201
ODI-26201: Invalid Export Key. Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).
Category:
Other
Cause:
Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).
Action:
Provide a valid Export Key
ODI-26202
ODI-26202: The Export Key and the confirmed Export Key are not the same.
Category:
Other
Cause:
Export Key confirmation doesn't match the entered Export Key.
Action:
Make sure that the Export Key and confirmed Export Key are the same.
ODI-26203
ODI-26203: The provided Export Key is not correct for the selected file.
Category:
Other
Cause:
The provided Export Key is not the same as the Export Key of this selected file.
Action:
Provide a correct Export Key
ODI-26204
ODI-26204: The incorrect Export Key is entered three times. The Export Key field will be disabled now. You can Import this file without an Export Key (the cipher data will not be imported) or Cancel import.
Category:
Other
Cause:
The incorrect Export Key entered 3 times.
Action:
Continue import this file without importing cipher data or Cancel import.
ODI-26205
ODI-26205: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or Cancel import.
Category:
Other
Cause:
The incorrect Export Key entered 3 times.
Action:
Continue import this file or all files without importing cipher data, or Skip the file, or Cancel import.
ODI-26206
ODI-26206: Unable to connect Registry Database to the DBA user.
Category:
Other
Cause:
Unable to connect Registry Database by DBA Account.
Action:
Check Registry Database and the DBA username and password are correct.
ODI-26207
ODI-26207: An Option with the name {0} already exists. Please provide another name.
Category:
Other
Cause:
The name provided for the Option is not unique.
Action:
Enter a unique name for the Option.
ODI-26208
ODI-26208: Unable to perform move because {0} already exists in folder {1}.
Category:
Other
Cause:
A folder already consists a such type of object with the same name as a moving object.
Action:
Rename an object, which you want to move, or rename, or delete an existing object from a folder.
ODI-26209
ODI-26209: Repository Seeding Version Mismatch: A client of an older version is used to connect to a repository that already contains newer map component and KM definitions. Continuing login will not update any seeded objects. Continue login?
Category:
Other
Cause:
A client of an older version is used to connect to a repository that already contains newer map component and KM definitions.
Action:
Update the current client by downloading and installing the latest patch. Insure other clients that connect to the same repository are also at the same patch version.
ODI-26210
ODI-26210: The repository contains map component and KM definitions that are older than the ones supported by the current client version. Clicking Yes will continue the login and the map component definitions will be updated. Clicking No will disconnect from the repository without updating. Do you want to continue?
Category:
Other
Cause:
The current client contains map component and KM definitions that are newer than the ones recorded in the repository.
Action:
Continuing the connection will update the repository with map component and KM definitions at the same version as the client. Check and update other clients that connect to the same repository to the same patch version as the current client.
ODI-26211
Mapping name is not unique.
Category:
Other
Cause:
Duplicate mapping name. Mapping with the same name already exists in this folder.
Action:
Choose another mapping name.
ODI-26212
Reusable mapping name is not unique.
Category:
Other
Cause:
Duplicate reusable mapping name. Reusable mapping with the same name already exists in this folder, or there is another global reusable mapping with the same name.
Action:
Choose another reusable mapping name.
ODI-26213
Cannot create connection from {0} to {1}. Connections can only be made within the same component owner.
Category:
Other
Cause:
Cannot make a connection between two components that are contained in different component owners, for example a connection from a component that is inside a dataset to another component outside the dataset.
Action:
Connect to a component that is contained by the same component owner.
ODI-26214
Cannot find appropriate Knowledge Module for node:{0}
Category:
Programmatic
Cause:
Cannot find a KM to assign to this node.
Action:
Set appropriate KM for physical nodes.
ODI-26215
Error when attempting to set the Loading Knowledge Module to AP node:{0}
Category:
Programmatic
Cause:
Cannot find a LKM to assign to this node.
Action:
Set appropriate LKM for AP nodes.
ODI-26216
Error when attempting to set the Extract Knowledge Module to physical node:{0}
Category:
Programmatic
Cause:
Cannot find a XKM to assign to this node.
Action:
Set appropriate XKM for physical nodes.
ODI-26217
Cannot enable Streaming on Map Physical Design
Category:
Programmatic
Cause:
Map Physical Design does not contain any Execution Unit that supports Streaming
Action:
Set appropriate Streaming value
ODI-26218
Error parsing the data format schema for the {0} attribute: {1}
Category:
Programmatic
Cause:
The data format for the complex type attribute cannot be parsed.
Action:
Correct the data format property for the complex type attribute.
ODI-26219
Data type {0} of complex type field {1} is not a valid HDFS type.
Category:
Programmatic
Cause:
The data type of a field in the complex type attribute is not supported.
Action:
Check the data types used in the data format property for the complex type attribute. Only HDFS types are allowed.
ODI-26220
Complex type attribute {0} for flatten component {1} does not have a data format.
Category:
Programmatic
Cause:
The data format of the complex type attribute cannot be located. The attribute may be a simple type or the data format has not been specified.
Action:
Ensure that the data format of the complex type attribute is set. The format may be specified on a bound data store column or upstream map attribute.
ODI-26221
Complex type attribute {0} for flatten component {1} was not found in any source component.
Category:
Programmatic
Cause:
The complex type attribute cannot be located. The attribute may be spelled incorrectly or may not be in scope in the upstream map components.
Action:
Ensure that the complex type attribute is a valid upstream map attribute.
ODI-26223
Complex data types cannot be used with aggregation. Attribute {0} of aggregate component {1} is a complex type.
Category:
Programmatic
Cause:
Complex type attributes are incompatible with aggregation and grouping. They may not be used with the aggregation component.
Action:
Avoid mapping complex attributes into the aggregate component. The flatten component may be applied to complex types prior to aggregate component mapping.
ODI-26224
Join components may not be used in the same Hive execution unit as flatten components with a complex type with a collection.
Category:
Programmatic
Cause:
Join and Flatten components with a collection are present in the same Hive execution unit. The lateral view clause used for Hive complex type flattening is not compatible with multiple sources in the SQL FROM clause.
Action:
Avoid using flatten components with joins in Hive.
ODI-26300
ODI-26300: Following Flexfields are found missing, which are required to persist this object properly: {0} You can use Security Navigator to define Flexfields for this object type.
Category:
Other
Cause:
There are some required flexfields missing in the editor opened. Without the mentioned flexfields the given object will not persist properly.
Action:
User can use Security Navigator to define Flexfields for this object type.
ODI-26301
ODI-26301: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or cancel the Compare.
Category:
Other
Cause:
The incorrect Export Key entered 3 times.
Action:
Continue comparing this file without cipher data or cancel the Compare.
ODI-26310
ODI-26310: Could not delete the Open Tool {0}. It is used within steps in the following packages: {1}
Category:
Other
Cause:
The Open Tool is used within package steps and cannot be deleted.
Action:
Delete the corresponding steps from the referencing package before deleting the Open Tool.
ODI-30000
Error while parsing request file.
Category:
Files
Cause:
Action:
ODI-30001
One of the following parameters: {0} or {1} must be defined.
Category:
Configuration
Cause:
Action:
ODI-30002
Parameters {0} and {1} cannot be set at the same time.
Category:
Configuration
Cause:
Action:
ODI-30003
OdiOSCommand not supported for this operating system. Use tool "OS Command".
Category:
OperatingSystem
Cause:
Action:
ODI-30004
Agent unreachable
Category:
Network
Cause:
Action:
ODI-30005
One or more child sessions has failed
Category:
Other
Cause:
Action:
ODI-30006
No table matches the specified pattern.
Category:
Other
Cause:
Action:
ODI-30007
No table matches the specified list.
Category:
Other
Cause:
Action:
ODI-30008
No variable with this name is used in the session.
Category:
Other
Cause:
Action:
ODI-30009
Can''t rename file: {0} to {1}
Category:
Files
Cause:
Action:
ODI-30010
Can''t delete old file: {0}
Category:
Files
Cause:
Action:
ODI-30011
Parameter cannot be null:
Category:
Other
Cause:
Action:
ODI-30012
This user does not have the privilege to execute this scenario
Category:
Security
Cause:
Action:
ODI-30013
Context not allowed for this user
Category:
Security
Cause:
Action:
ODI-30014
Cannot create directory
Category:
Files
Cause:
Action:
ODI-30016
Internal error: Invalid datatype
Category:
Other
Cause:
Action:
ODI-30017
Unable to create persistence table
Category:
Other
Cause:
Action:
ODI-30018
Unable to find the tables
Category:
Other
Cause:
Action:
ODI-30019
The Object id is mandatory
Category:
Other
Cause:
Action:
ODI-30020
The command is not valid
Category:
Other
Cause:
Action:
ODI-30021
Value 0 is not allowed for -GLOBAL_ROWCOUNT.
Category:
Other
Cause:
Action:
ODI-30022
Version is mandatory ...
Category:
Other
Cause:
Action:
ODI-30023
Scenario name is mandatory ...
Category:
Other
Cause:
Action:
ODI-30024
File name is mandatory...
Category:
Other
Cause:
Action:
ODI-30025
Agent name is mandatory ...
Category:
Other
Cause:
Action:
ODI-30026
Either the "{0}" or the "{1}" parameter is mandatory ...
Category:
Other
Cause:
Action:
ODI-30027
The parameter -LSCHEMA is mandatory.
Category:
Other
Cause:
Action:
ODI-30028
The parameter -SUBSCRIBER_NAME is mandatory.
Category:
Other
Cause:
Action:
ODI-30029
Parameter -RESUME_KEY_COL is mandatory when -RESUME_KEY_VAR is used
Category:
Other
Cause:
Action:
ODI-30030
Please do not pass values for both "{0}" and "{1}" options together. These two options together are not supported
Category:
Other
Cause:
Action:
ODI-30031
The parameter "{0}" is mandatory.
Category:
Other
Cause:
Action:
ODI-30032
Unrecognized ODI object type "{0}". Please check the value passed to the parameter "{1}".
Category:
Other
Cause:
Action:
ODI-30033
The parameter "-CONTEXT" is mandatory when running from command line.
Category:
Other
Cause:
Action:
ODI-30034
Only positive integer values are valid for {0} parameter
Category:
Other
Cause:
Action:
ODI-30035
Only non-negative integer values are valid for {0} parameter
Category:
Other
Cause:
Action:
ODI-30036
This step cannot be executed in execution work repository because the model meta data does not exist
Category:
Other
Cause:
Action:
ODI-30037
The specified marker does not exist
Category:
Other
Cause:
Action:
ODI-30038
OS command returned {0}. Error details are [{1}].
Category:
Other
Cause:
Action:
ODI-30039
Parameter -RESUME_KEY_VAR is mandatory when -RESUME_KEY_COL is used
Category:
Other
Cause:
Action:
ODI-30040
The -TABLE_NAME parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30041
LSCHEMA parameter is mandatory
Category:
Other
Cause:
Action:
ODI-30042
SUBSCRIBER_NAME parameter is mandatory
Category:
Other
Cause:
Action:
ODI-30043
You cannot use the OPTIMIZED_WAIT option with the current journalizing method.
Category:
Other
Cause:
Action:
ODI-30044
Invalid parameter
Category:
Other
Cause:
Action:
ODI-30045
Impossible to find a valid name on this machine for the "{0}" file
Category:
Other
Cause:
Action:
ODI-30046
Session stopped
Category:
Other
Cause:
Action:
ODI-30047
You cannot select more than one source.
Category:
Other
Cause:
Action:
ODI-30048
Unable to find the object with type {0} and identifier {1}
Category:
Other
Cause:
Action:
ODI-30049
Version is mandatory ...
Category:
Other
Cause:
Action:
ODI-30050
The same file cannot be used as the source and the target.
Category:
Files
Cause:
Action:
ODI-30051
File does not exist.
Category:
Files
Cause:
Action:
ODI-30052
No file found.
Category:
Files
Cause:
Action:
ODI-30053
File name is mandatory ...
Category:
Files
Cause:
Action:
ODI-30054
It is not possible to delete sessions in the queue.
Category:
Other
Cause:
Action:
ODI-30055
Context is mandatory ...
Category:
Other
Cause:
Action:
ODI-30056
Sequence name is mandatory
Category:
Other
Cause:
Action:
ODI-30057
The position is a mandatory parameter.
Category:
Other
Cause:
Action:
ODI-30058
-SCEN_NAME parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30059
The number of child sessions in error state is greater or equal to the MAX_CHILD_ERROR parameter
Category:
Other
Cause:
Action:
ODI-30060
The parent session "{0}" does not exist.
Category:
Other
Cause:
Action:
ODI-30061
"{0}" is not a correct value for -OBJECT_TYPE
Category:
Other
Cause:
Action:
ODI-30062
There's no table matching the pattern in the database
Category:
Other
Cause:
Action:
ODI-30063
-TABLE_NAME and -CDC_SET_NAME cannot be used simultaneously.
Category:
Other
Cause:
Action:
ODI-30064
You must specify -TABLE_NAME or -CDC_SET_NAME
Category:
Other
Cause:
Action:
ODI-30065
Incorrect length at position :{0} for value : {1} expected max size of {2}
Category:
Other
Cause:
Action:
ODI-30066
All child sessions have failed
Category:
Other
Cause:
Action:
ODI-30067
-UNIT_ROW_COUNT and -CDC_SET_NAME cannot be used simultaneously.
Category:
Other
Cause:
Action:
ODI-30068
Unable to find the table(s): {0}
Category:
Other
Cause:
Action:
ODI-30069
You must specify a Project
Category:
Other
Cause:
Action:
ODI-30070
You have not specified the export scenarios location.
Category:
Other
Cause:
Action:
ODI-30071
You have not specified the export location.
Category:
Other
Cause:
Action:
ODI-30072
Unable to delete a running session
Category:
Other
Cause:
Action:
ODI-30073
Unable to delete a waiting session
Category:
Other
Cause:
Action:
ODI-30074
{0}: Illegal value
Category:
Other
Cause:
Action:
ODI-30075
Cannot be specified at the same time: {0} and {1}
Category:
Other
Cause:
Action:
ODI-30076
Unable to save the line number sum
Category:
Other
Cause:
Action:
ODI-30077
The variable in use is null.
Category:
Other
Cause:
Action:
ODI-30078
No message.
Category:
Other
Cause:
Action:
ODI-30079
Mandatory Parameter "{0}" is missing
Category:
Other
Cause:
Action:
ODI-30080
Cannot copy a directory "{0}" to a regular file "{1}"
Category:
Files
Cause:
Action:
ODI-30081
The source directory file "{0}" does not exist
Category:
Files
Cause:
Action:
ODI-30082
The source directory file "{0}" is not a directory
Category:
Files
Cause:
Action:
ODI-30083
Invalid value "{0}" passed for parameter "{1}"
Category:
Other
Cause:
Action:
ODI-30084
File "{0}" does not exist
Category:
Files
Cause:
Action:
ODI-30085
Cannot copy file with a regular expression to a regular file "{0}"
Category:
Files
Cause:
Action:
ODI-30086
The FROMDATE {0} should be earlier than the TODATE {1}
Category:
Other
Cause:
Action:
ODI-30087
Import failed. No work repository name was defined and the import failed in the master repository.
Category:
Other
Cause:
Action:
ODI-30088
Timed out. No result.
Category:
Other
Cause:
Action:
ODI-30089
Source file "{0}" does not exist
Category:
Files
Cause:
Action:
ODI-30090
Scenario name is mandatory ...
Category:
Other
Cause:
Action:
ODI-30091
Invalid internal object transition
Category:
Other
Cause:
Action:
ODI-30092
Cannot create directory
Category:
Files
Cause:
Action:
ODI-30093
PORT and NAME parameters can''t be used together.
Category:
Other
Cause:
Action:
ODI-30094
Log files can only be imported in synonym mode INSERT.
Category:
Other
Cause:
The value of parameter -IMPORT_MODE is invalid for this type of object.
Action:
Modify the value of parameter -IMPORT_MODE to SYNONYM_INSERT
ODI-30095
PROMPT option can only be used when ReverseManageShortcut tool is run from ODI UI and on a Local Agent.
Category:
Other
Cause:
The value of parameter -SHORTCUT_HANDLING_MODE is invalid for this mode of execution.
Action:
Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP
ODI-30096
Invalid shortcut handling mode.
Category:
Other
Cause:
The value of parameter -SHORTCUT_HANDLING_MODE is invalid.
Action:
Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP or PROMPT.
ODI-30097
-LOCATION parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30098
-OBJECT_NAME parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30099
-OBJECT_TYPE parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30100
-WORKSPACE parameter is mandatory.
Category:
Other
Cause:
Action:
ODI-30101
Enterprise Data Quality project {0} not found.
Category:
Other
Cause:
Action:
ODI-30102
Enterprise Data Quality Job {0} not found in Enterprise Data Quality project {1}.
Category:
Other
Cause:
Action:
ODI-30103
Enterprise Data Quality matching query returned with empty or ambiguous result for {0}.
Category:
Other
Cause:
Action:
ODI-30104
Model Internal ID is not supported when Legacy ID Compatible Mode is switched off.
Category:
Other
Cause:
Action:
ODI-30105
Internal ID is not supported for "{0}" when Legacy ID Compatible Mode is switched off. Only Global ID is supported.
Category:
Other
Cause:
Action:
ODI-30106
JAX-WS Dispatch proxy object could not be created. Check ODI Agent log for error messages.
Category:
Other
Cause:
Action:
ODI-30107
Upgrade key is required for pre-12.x object import.
Category:
Other
Cause:
Action:
ODI-30108
Target directory "{0}" does not exist
Category:
Files
Cause:
Action:
ODI-30109
Error while polling run status of load plan {0} (instance id {1}, run {2}) for execution completion. Last polled status value: {3}.
Category:
Other
Cause:
Action:
ODI-30110
Execution of load plan {0} (instance id {1}, run {2}) ended in status "{3}" instead of "{4}". {5}
Category:
Other
Cause:
Action:
ODI-30111
Value for mandatory parameter {0} is missing.
Category:
Other
Cause:
Action:
ODI-30112
Invalid logical schema "{0}" selected for PROCESS_LSCHEMA parameter. Oracle Golden Gate process logical schema is expected.
Category:
Other
Cause:
Action:
ODI-30113
Values for mandatory parameters PROCESS_LSCHEMA and OPERATION are missing.
Category:
Other
Cause:
Action:
ODI-30114
Oracle GoldenGate process logical schema with the name {0} does not exist.
Category:
Other
Cause:
Action:
ODI-30115
All selected load plan runs ({0}) have completed, with {1} in Error status.
Category:
Other
Cause:
Action:
ODI-30116
The number of load plan runs in error status ({0} in error out of {1} completed runs), is at or above the MAX_LP_ERROR limit of {2}.
Category:
Other
Cause:
Action:
ODI-30117
The parent session "{0}" does not exist.
Category:
Other
Cause:
Action:
ODI-30118
The value "{0}" specified for the -NB_PROCESS parameter is invalid. A valid value must be a positive integer.
Category:
Other
Cause:
Action:
ODI-30119
Error while splitting XML file. Target file {0} already exists.
Category:
Other
Cause:
Action:
ODI-30120
Authentication mechanisms (parameter: AUTHMECHANISMS) is required when Use Authentication (parameter: AUTH) is set to Yes.
Category:
Other
Cause:
Action:
ODI-30121
This operation {0} is not to be invoked
Category:
Other
Cause:
Action:
ODI-30122
Error while writing output XML file - {0}.
Category:
Other
Cause:
Action:
ODI-30124
Error while parsing input XML file - {0}.
Category:
Other
Cause:
Action:
ODI-30125
Error while creating SystemID using the XML file input - {0}.
Category:
Other
Cause:
Action:
ODI-30126
Error on parsing header.
Category:
Other
Cause:
Action:
ODI-30127
Error on parsing footer.
Category:
Other
Cause:
Action:
ODI-30128
Error while joining XML files.
Category:
Other
Cause:
Action:
ODI-30129
The user {0} does not have privileges to export Scenario {1} ({2})
Category:
Other
Cause:
Action:
ODI-30130
The user {0} does not have privileges to import a Scenario.
Category:
Other
Cause:
Action:
ODI-30131
The user {0} does not have privileges to generate a Scenario.
Category:
Other
Cause:
Action:
ODI-30132
The user {0} does not have privileges to export Scenarios.
Category:
Other
Cause:
Action:
ODI-30133
Specified folder with ID {0} does not exist in repository.
Category:
Other
Cause:
Action:
ODI-30134
Specified scenario {0} of version {1} does not exist in repository.
Category:
Other
Cause:
Action:
ODI-30135
Invalid arguments for OdiExportObject tool. EXPORT_DIR="{0}",FILE_NAME="{1}". When EXPORT_DIR value is not specified, FILE_NAME value must contain absolute path.
Category:
Other
Cause:
Action:
ODI-30136
Incorrect EDQ server domain name {0}.
Category:
Other
Cause:
Action:
ODI-30137
Invalid arguments for OdiExportAllScen when connected to Runtime Repository. Design repository parameters cannot be used on runtime repository.
Category:
Other
Cause:
Action:
ODI-30138
Invalid Source type provided. Valid Source types for OdiCreateDeploymentArchive are ODI or VCS.
Category:
Other
Cause:
Action:
ODI-30139
Invalid Archive type provided. Valid Archive type for Source type ODI is INITIAL.
Category:
Other
Cause:
Action:
ODI-30140
VCS Label not provided for Source VCS.
Category:
Other
Cause:
Action:
ODI-30141
Invalid VCS type provided. Valid VCS type is SVN.
Category:
Other
Cause:
Action:
ODI-30142
Invalid VCS Authentication type provided. Valid values are SVNBASIC|BASIC|PROXY|SSH|SSL|FILE.
Category:
Other
Cause:
Action:
ODI-30143
VCS URL not provided.
Category:
Other
Cause:
Action:
ODI-30144
VCS User name is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30145
VCS Password is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30146
Proxy Host as well as Proxy port are mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30147
Invalid Archive type provided. Valid Archive types for OdiApplyDeploymentArchive are INITIAL or PATCH.
Category:
Other
Cause:
Action:
ODI-30148
Invalid Archive type provided. Valid Archive type for OdiRollbackDeploymentArchive is ROLLBACK.
Category:
Other
Cause:
Action:
ODI-30149
The timeout was reached before all of the sessions could be retrieved.
Category:
Other
Cause:
Action:
ODI-30150
Current user is not VCS ADMIN to perform unlock operation
Category:
Other
Cause:
Action:
ODI-30151
Error while setting parameters on tool: {0}
Category:
Other
Cause:
Action:
ODI-30152
Archive Name needs to be provided.
Category:
Other
Cause:
Action:
ODI-30153
Export Key is required when Create without cipher data option is selected as No.
Category:
Other
Cause:
Action:
ODI-30154
Parameter {0} cannot be null, when -LSCHEMA is null. Either -LSCHEMA or (all of -HOST,-PORT,-USER,-PASSWORD,-DOMAIN) are mandatory and cannot be null.
Category:
Other
Cause:
Action:
ODI-30155
SSH Port is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30156
Neither VCS Password nor Private Key file details provided for SSH.
Category:
Other
Cause:
Action:
ODI-30157
---------- Environment Variables Defined By OSCommand -ENV.* Parameters ----------
Category:
Other
Cause:
Action:
ODI-30158
---------- Environment Variables Used By OSCommand ----------
Category:
Other
Cause:
Action:
ODI-30159
Parameters {0} and {1} cannot be set at the same time.
Category:
Configuration
Cause:
Action:
ODI-30160
Incomplete multipart parameters.
Category:
Configuration
Cause:
Action:
ODI-30161
Invalid content type specified for multipart request.
Category:
Configuration
Cause:
Action:
ODI-30162
Non-numeric value specified for numeric parameter : {0}
Category:
Configuration
Cause:
Action:
ODI-30163
REST tool invocation failed with response code : {0}. URL : {1}
Category:
Other
Cause:
Action:
ODI-30164
Rest invocation failed with error. URL : {0}
Category:
Other
Cause:
Action:
ODI-30165
Unable to read file from HDFS path : {0}
Category:
Other
Cause:
Action:
ODI-30166
Error while reading the content of body part file : {0}
Category:
Other
Cause:
Action:
ODI-30167
Error accessing trace file. Trace file path : {0}
Category:
Other
Cause:
Action:
ODI-30168
Error accessing response file. Response file path : {0}
Category:
Other
Cause:
Action:
ODI-30169
Response status generation failed. File path : {0}
Category:
Other
Cause:
Action:
ODI-30170
Multipart bodypart creation failed.
Category:
Other
Cause:
Action:
ODI-30171
No response file specified for mode : {0}
Category:
Configuration
Cause:
Action:
ODI-30172
Invalid operation : {0}
Category:
Configuration
Cause:
Action:
ODI-30173
Unable to resolve physical schema due to invalid LSchema/Context pair : {0}/{1}
Category:
Configuration
Cause:
Action:
ODI-30174
WaitForSparkJob getStatus request failed : url={0} exception={1}
Category:
Other
Cause:
Action:
ODI-30175
WaitForSparkJob getStatus bad response code : expected={0} received={1} url={2}
Category:
Other
Cause:
Action:
ODI-30176
WaitForSparkJob getStatus response not compatible : expected={0} received={1} url={2}
Category:
Other
Cause:
Action:
ODI-30177
WaitForSparkJob killJob request failed : url={0} exception={1}
Category:
Other
Cause:
Action:
ODI-30178
WaitForSparkJob killJob bad response code : expected={0} received={1} url={2}
Category:
Other
Cause:
Action:
ODI-30179
WaitForSparkJob killJob response not compatible : expected={0} received={1} url={2}
Category:
Other
Cause:
Action:
ODI-30180
WaitForSparkJob killJob : stop requested but -STOP_URL not specifed url={0}
Category:
Other
Cause:
Action:
ODI-30181
Error Obtaining data schema for the given Logical Schema={0}
Category:
Files
Cause:
Action:
ODI-30182
WaitForSparkJob url : {0} redirected to {1}
Category:
Other
Cause:
Action:
ODI-30183
Unable to connect to REST service after {0} retry attempts. REST URL : {1}
Category:
Other
Cause:
Action:
ODI-30184
Unable to resolve next request. Resolver class used : {0}
Category:
Other
Cause:
Action:
ODI-30185
Invalid next request resolver provided. Next request resolver : {0} Resolver Class : {1}
Category:
Configuration
Cause:
Action:
ODI-30186
Invalid rest request object modification by next page resolver : {1}. Rest request object should contain request path
Category:
Other
Cause:
Action:
ODI-30187
Invocation retry interrupted with {0} attempts left. REST URL : {1}
Category:
Other
Cause:
Action:
ODI-30188
Unable to retrieve value for tool parameter : {0}
Category:
Other
Cause:
Action:
ODI-30189
Invalid value "{0}" provided for tool parameter : {1}
Category:
Configuration
Cause:
Action:
ODI-30190
Error while copying temp response file to original response file
Category:
Other
Cause:
Action:
ODI-30191
Invalid ResponseDataContainerResolver expression : {0}. It should be either Xpath nor JSONPath expression
Category:
Configuration
Cause:
Action:
ODI-30192
Invalid Resolver Overwrite class : {0}
Category:
Configuration
Cause:
Action:
ODI-30193
No value provided for request body part
Category:
Configuration
Cause:
Action:
ODI-30194
No body provided for request body part. Please provide either body part value or body part input stream.
Category:
Configuration
Cause:
Action:
ODI-30195
-REQUEST_BODY_FILE parameter is mandatory for Chunk Upload. User should specify a directory or file path in local file system or HDFS file system
Category:
Configuration
Cause:
Action:
ODI-30196
Invalid Runtime Template set by the user : {0}
Category:
Configuration
Cause:
Action:
ODI-30197
Offsetbased pagination will not terminate due to invalid -NEXT_REQUEST_RESOLVER : {0}
Category:
Configuration
Cause:
Action:
ODI-30198
A runtime template : {0} is found to be initialized in the tool parameter. Runtime templates should be initialized only while defining the operation.
Category:
Configuration
Cause:
Action:
ODI-30199
A value has been set to runtime template "{0}". But the runtime template is not used in the REST invocation. Please check if you have missed to specify it in either path,query or header.
Category:
Configuration
Cause:
Action:
ODI-30200
Source Logical schema not provided.
Category:
Other
Cause:
Action:
ODI-30201
Target Logical schema not provided.
Category:
Other
Cause:
Action:
ODI-30202
File names filter not provided.
Category:
Other
Cause:
Action:
ODI-30203
Retry on error is greater than 0 and retry interval seconds is null or empty.
Category:
Other
Cause:
Action:
ODI-30204
Encrypt is true and encrypt key is null or empty.
Category:
Other
Cause:
Action:
ODI-30205
Encrypt is not applicable for storage type ARCHIVE.
Category:
Other
Cause:
Action:
ODI-30206
Storage type is invalid.
Category:
Other
Cause:
Action:
ODI-30207
Source Logical schema not provided.
Category:
Other
Cause:
Action:
ODI-30208
Target Logical schema not provided.
Category:
Other
Cause:
Action:
ODI-30209
File names filter not provided.
Category:
Other
Cause:
Action:
ODI-30211
No matching files to {0}. Check your filter string.
Category:
Other
Cause:
Action:
ODI-30212
The value: {0} specified for the parameter: {1} is invalid. A valid value must be a positive integer.
Category:
Other
Cause:
Action:
ODI-30213
VCS Lock type is invalid.
Category:
Other
Cause:
Action:
ODI-30214
Invalid VCS type provided.
Category:
Other
Cause:
Action:
ODI-30215
Invalid VCS Authentication type provided. Valid values are SVNBASIC|BASIC|PROXY|SSH|SSL|FILE.
Category:
Other
Cause:
Action:
ODI-30216
VCS URL is not provided.
Category:
Other
Cause:
Action:
ODI-30217
VCS User name is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30218
VCS Password is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30219
Proxy Host as well as Proxy port are mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30220
SSH Port is mandatory for authentication type {0}.
Category:
Other
Cause:
Action:
ODI-30221
Neither VCS Password nor Private Key file details provided for SSH..
Category:
Other
Cause:
Action:
ODI-30222
Provided Password is not encrypted for parameter : {0}.
Category:
Other
Cause:
Action:
ODI-30223
Git Repository is not cloned, Please clone from remote Git repository.
Category:
Other
Cause:
Action:
ODI-30224
No matching files to {0}. Check your filter string.
Category:
Other
Cause:
Action:
ODI-30225
Storage type not provided.
Category:
Other
Cause:
Action:
ODI-30226
Provided key is not encrypted for parameter : {0}.
Category:
Other
Cause:
Action:
ODI-30227
Rest invocation failed with error : {0}. Response code : {1}. URL : {2}
Category:
Other
Cause:
Action:
ODI-40001
Cannot join two journalized sets of data: {0} and {1}.
Category:
Programmatic
Cause:
The generated query object has detected multiple journalized data sources, only one is allowed.
Action:
Switch off journalizing for one of the sources, in the logical or physical graph.
ODI-40100
Invalid JDBC URL {0} . No XSD or DTD was provided.
Category:
Configuration
Cause:
Action:
ODI-40101
Not Supported
Category:
Other
Cause:
Action:
ODI-40102
The parameter {0} has already been specified for {1}.
Category:
Other
Cause:
Action:
ODI-40103
No value provided for JMS_DESTINATION
Category:
Other
Cause:
Action:
ODI-40104
The URL {0} does not start with {1}
Category:
Other
Cause:
Action:
ODI-40105
Connecting to JMS using URL {0} failed
Category:
Other
Cause:
Action:
ODI-40106
JNDI protocol not specified after the JMS XML protocol prefix : {0}
Category:
Other
Cause:
Action:
ODI-40107
Path separator ":" after JNDI protocol not found {0}
Category:
Other
Cause:
Action:
ODI-40108
"//" after colon not found : {0}
Category:
Other
Cause:
Action:
ODI-40109
Need more information than JNDI hostname. eg: port, provider : {0}
Category:
Other
Cause:
Action:
ODI-40110
Could not find JNDI host, port, provider info : {0}
Category:
Other
Cause:
Action:
ODI-40111
Error closing JMS XML connection
Category:
Other
Cause:
Action:
ODI-40200
Cannot create the initial JNDI context. Check that the JNDI server is running, and that the following URL is correct ({0}).
Category:
Other
Cause:
Action:
ODI-40201
Cannot create the initial JNDI context
Category:
Other
Cause:
Action:
ODI-40202
Cannot find the target in JNDI ({0})
Category:
Other
Cause:
Action:
ODI-40203
Cannot find the Connection Factory ({0}) in JNDI
Category:
Other
Cause:
Action:
ODI-40204
The URL cannot be null
Category:
Network
Cause:
Action:
ODI-40205
No connection.
Category:
Network
Cause:
Action:
ODI-40206
Problem with getInternalSession
Category:
Other
Cause:
Action:
ODI-40207
You must specify the URL parameter
Category:
Configuration
Cause:
Action:
ODI-40208
This function has no effect for this connection
Category:
Other
Cause:
Action:
ODI-40209
Unable to create the table
Category:
Other
Cause:
Action:
ODI-40210
Unable to drop the table
Category:
Other
Cause:
Action:
ODI-40212
Missing file structure in the request
Category:
Other
Cause:
Action:
ODI-40213
Error performing update
Category:
Other
Cause:
Action:
ODI-40214
Error creating prepared statement
Category:
Other
Cause:
Action:
ODI-40215
Error performing commit
Category:
Other
Cause:
Action:
ODI-40216
Error performing update
Category:
Other
Cause:
Action:
ODI-40217
Error closing resultset
Category:
Other
Cause:
Action:
ODI-40218
Error getting next element in resultset
Category:
Other
Cause:
Action:
ODI-40219
Error opening file for insert
Category:
Other
Cause:
Action:
ODI-40220
Error creating prepared statement
Category:
Other
Cause:
Action:
ODI-40221
Error writing
Category:
Other
Cause:
Action:
ODI-40222
Error initializing
Category:
Other
Cause:
Action:
ODI-40223
Error performing commit
Category:
Other
Cause:
Action:
ODI-40224
Error obtaining connection
Category:
Other
Cause:
Action:
ODI-40225
Error performing rollback
Category:
Other
Cause:
Action:
ODI-40226
Error initializing
Category:
Other
Cause:
Action:
ODI-40227
Error performing commit
Category:
Other
Cause:
Action:
ODI-40228
Error obtaining connection
Category:
Other
Cause:
Action:
ODI-40229
Error performing rollback
Category:
Other
Cause:
Action:
ODI-40230
Error closing JMS
Category:
Other
Cause:
Action:
ODI-40231
Error closing JNDI
Category:
Other
Cause:
Action:
ODI-40232
Error closing JNDI
Category:
Other
Cause:
Action:
ODI-40233
Error closing JNDI
Category:
Other
Cause:
Action:
ODI-40234
Error writing received message to temp file
Category:
Other
Cause:
Action:
ODI-40300
File is read-only.
Category:
Files
Cause:
Action:
ODI-40301
Invalid COL ALIAS "{0}" for column "{1}"
Category:
Other
Cause:
Action:
ODI-40302
Invalid format description
Category:
Files
Cause:
Action:
ODI-40303
XML/LDAP driver encountered exception during decryption of password for DB connection
Category:
Other
Cause:
Action:
ODI-40304
The URL can not be null.
Category:
Other
Cause:
Action:
ODI-40305
Invalid property "{0}"
Category:
Other
Cause:
Action:
ODI-40306
Property {0} has invalid value {1}
Category:
Other
Cause:
Action:
ODI-40307
Parameter "{0}" has been declared twice. Old value : "{1}" New value : "{2}"
Category:
Other
Cause:
Action:
ODI-40400
Invalid format description
Category:
Files
Cause:
Action:
ODI-40401
Mis-matched start/end delimiters
Category:
Files
Cause:
Action:
ODI-40402
File metadata could not be obtained for {0}
Category:
Files
Cause:
Action:
ODI-40403
Unable to obtain row structure for file {0}
Category:
Files
Cause:
Action:
ODI-40404
Array must not be null
Category:
Other
Cause:
Action:
ODI-40405
End must be greater than begin: {0} > {1}
Category:
Other
Cause:
Action:
ODI-40406
Bytes are too big for array
Category:
Other
Cause:
Action:
ODI-40407
Begin interval must be >= 0: {0}
Category:
Other
Cause:
Action:
ODI-40408
End interval must not go beyond the size of the pointed array: {0}
Category:
Other
Cause:
Action:
ODI-40409
Array must not be null
Category:
Other
Cause:
Action:
ODI-40410
End must be greater than begin: {0} > {1}
Category:
Other
Cause:
Action:
ODI-40411
Begin interval must be >= 0: {0}
Category:
Other
Cause:
Action:
ODI-40412
End interval must not go beyond the size of the pointed array: {0}
Category:
Other
Cause:
Action:
ODI-40413
Bytes are too long for array
Category:
Files
Cause:
Action:
ODI-40414
Reader has been closed
Category:
Files
Cause:
Action:
ODI-40415
File {0} already exists
Category:
Files
Cause:
Action:
ODI-40416
Could not create file {0}
Category:
Files
Cause:
Action:
ODI-40417
An IOException was caught while creating the file saying {0}
Category:
Files
Cause:
Action:
ODI-40418
File not found: {0}
Category:
Files
Cause:
Action:
ODI-40419
Could not delete file: {0}
Category:
Files
Cause:
Action:
ODI-40420
Bad String size, hex Strings should have an even size
Category:
Other
Cause:
Action:
ODI-40421
Cannot code String {0} into {1} bytes using the encoding {2}.
Category:
Other
Cause:
Action:
ODI-40422
The array of bytes is not a valid number:
Category:
Other
Cause:
Action:
ODI-40423
A bad number was found in a COMP3 format: {0} at position {1}
Category:
Other
Cause:
Action:
ODI-40424
Cannot code value {0} on {1} bytes.
Category:
Other
Cause:
Action:
ODI-40425
Bad number in a ZONED format: {0} at position {1}
Category:
Other
Cause:
Action:
ODI-40426
URL must start with {0}
Category:
Other
Cause:
Action:
ODI-40427
Unknown property: {0}
Category:
Other
Cause:
Action:
ODI-40428
Could not write header rows to file: {0}
Category:
Files
Cause:
Action:
ODI-40429
An IOException occured while writing a row saying: {0}
Category:
Other
Cause:
Action:
ODI-40430
Unknown property
Category:
Other
Cause:
Action:
ODI-40431
Could not close output file
Category:
Files
Cause:
Action:
ODI-40432
File {0} is read-only
Category:
Files
Cause:
Action:
ODI-40433
File {0} was not found
Category:
Other
Cause:
Action:
ODI-40434
Could not clone a row of type {0}
Category:
Other
Cause:
Action:
ODI-40435
Could not transform data for column {0} value {1} because: {2}
Category:
Other
Cause:
Action:
ODI-40436
JVM 1.4 at least is required
Category:
Compliance
Cause:
Action:
ODI-40437
Number of bad rows actually detected: {0}
Category:
Other
Cause:
Action:
ODI-40438
File not found: {0}
Category:
Files
Cause:
Action:
ODI-40439
Could not read heading rows from file
Category:
Other
Cause:
Action:
ODI-40440
Could not close file: {0}
Category:
Other
Cause:
Action:
ODI-40441
Error reading file: {0} said {1}
Category:
Other
Cause:
Action:
ODI-40442
Could not translate value for column {0}
Category:
Other
Cause:
Action:
ODI-40443
Could not convert value of type {0} to BigDecimal
Category:
Other
Cause:
Action:
ODI-40444
Column not found: {0}
Category:
Other
Cause:
Action:
ODI-40445
Column {0} > {1}.
Category:
Other
Cause:
Action:
ODI-40446
Column {0} negative or zero.
Category:
Other
Cause:
Action:
ODI-40447
This type is not valid datatype
Category:
Other
Cause:
Action:
ODI-40448
File is read-only.
Category:
Files
Cause:
Action:
ODI-40449
File not found: {0}
Category:
Files
Cause:
Action:
ODI-40450
An IOException occured saying: {0}
Category:
Files
Cause:
Action:
ODI-40451
Column Not Found:
Category:
Other
Cause:
Action:
ODI-40452
Missing file structure in the request
Category:
Files
Cause:
Action:
ODI-40453
Missing JMS properties in the request
Category:
Other
Cause:
Action:
ODI-40454
Missing host variable at index
Category:
Other
Cause:
Action:
ODI-40455
Not a numeric value
Category:
Other
Cause:
Action:
ODI-40456
A Number datatype was expected instead of :
Category:
Other
Cause:
Action:
ODI-40457
Parsing error
Category:
Other
Cause:
Action:
ODI-40458
Unknown column datatype
Category:
Other
Cause:
Action:
ODI-40459
An IOException occurred saying {0}
Category:
Files
Cause:
Action:
ODI-40460
Could not transform the data: {0}
Category:
Other
Cause:
Action:
ODI-40461
A Date datatype was expected instead of :
Category:
Other
Cause:
Action:
ODI-40462
File already exists
Category:
Files
Cause:
Action:
ODI-40463
Invalid cursor state
Category:
Other
Cause:
Action:
ODI-40464
Invalid descriptor index
Category:
Other
Cause:
Action:
ODI-40465
Data array must not be null
Category:
Other
Cause:
Action:
ODI-40466
String is too long: {0}
Category:
Other
Cause:
Action:
ODI-40467
Too many columns on this row
Category:
Other
Cause:
Action:
ODI-40468
Row rejected because column {0} contains a bad value.
Category:
Other
Cause:
Action:
ODI-40469
Value was incorrect for column {0}: {1}
Category:
Other
Cause:
Action:
ODI-40470
EOF reached but not expected
Category:
Files
Cause:
Action:
ODI-40471
Tried to retrieve an int with an {0} object.
Category:
Other
Cause:
Action:
ODI-40472
Tried to retrieve a short with an {0} object.
Category:
Other
Cause:
Action:
ODI-40473
This resultset accepts only FETCHFORWARD requests
Category:
Other
Cause:
Action:
ODI-40474
This function is unsupported: the software you are using might not be compatible with this driver.
Category:
Other
Cause:
Action:
ODI-40475
Invalid column name
Category:
Other
Cause:
Action:
ODI-40476
Expected a comma.
Category:
Other
Cause:
Action:
ODI-40477
Cannot have a parameter inside a bare statement: {0}
Category:
Other
Cause:
Action:
ODI-40478
Could not transform data.
Category:
Other
Cause:
Action:
ODI-40479
Unrecognized command.
Category:
Other
Cause:
Action:
ODI-40480
Malformed INSERT statement.
Category:
Other
Cause:
Action:
ODI-40481
Invalid COL ALIAS "{0}" for column "{1}"
Category:
Other
Cause:
Action:
ODI-40482
Two selected columns have the same alias: {0}
Category:
Other
Cause:
Action:
ODI-40483
Could not read value {0}
Category:
Other
Cause:
Action:
ODI-40484
Could not read null value
Category:
Other
Cause:
Action:
ODI-40485
Not a ?
Category:
Other
Cause:
Action:
ODI-40486
Could not read value {0}
Category:
Other
Cause:
Action:
ODI-40487
Unknown file format
Category:
Files
Cause:
Action:
ODI-40488
Invalid COL ALIAS "{0}" for column "{1}"
Category:
Other
Cause:
Action:
ODI-40489
Not Supported
Category:
Files
Cause:
Action:
ODI-40490
Datatype {0} is not implemented for now
Category:
Other
Cause:
Action:
ODI-40491
ResultSet already closed. Cannot call next() on it.
Category:
Other
Cause:
Action:
ODI-40492
Property "{0}" is having invalid value "{1}".
Category:
Other
Cause:
Action:
ODI-40493
Parameter "{0}" has been declared twice. Old value : "{1}" New value : "{2}".
Category:
Other
Cause:
Action:
ODI-40494
Value for Parameter "{0}" not specified.
Category:
Other
Cause:
Action:
ODI-40500
Unknown parameter : {0}
Category:
Other
Cause:
Action:
ODI-40501
Syntax: {0}
Category:
Other
Cause:
Action:
ODI-40502
Can''t begin loading while loading another context
Category:
Other
Cause:
Action:
ODI-40503
Creating a new element {0} from the object {1} in DN {2} which contains attributes {3}
Category:
Other
Cause:
Action:
ODI-40504
Found the key {0} for the element {1} in DN {2}
Category:
Other
Cause:
Action:
ODI-40505
Entry {0} in {1} has a key {2} which is different from the original key found: {3}
Category:
Other
Cause:
Action:
ODI-40506
Adding new attribute {0} for object {1}
Category:
Other
Cause:
Action:
ODI-40507
Model Builder
Category:
Other
Cause:
Action:
ODI-40508
Not finished loading!
Category:
Other
Cause:
Action:
ODI-40509
Can''t begin loading while loading another context
Category:
Other
Cause:
Action:
ODI-40510
Not finished loading!
Category:
Other
Cause:
Action:
ODI-40511
Bad element {0} while in level
Category:
Other
Cause:
Action:
ODI-40512
Because an element {0} is not supposed to appear here. Please check your data model.
Category:
Other
Cause:
Action:
ODI-40513
Entry {0} in {1} has a key {2} which is different from the original key found: {3}
Category:
Other
Cause:
Action:
ODI-40514
Not implemented
Category:
Other
Cause:
Action:
ODI-40515
Not implemented
Category:
Other
Cause:
Action:
ODI-40516
Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.
Category:
Other
Cause:
Action:
ODI-40517
Could not add table {0} because the model told us it''s a duplicate. Please try changing the grouping factor.
Category:
Other
Cause:
Action:
ODI-40518
The table {0} already exists in the model and could not be added
Category:
Other
Cause:
Action:
ODI-40519
The table {0} is a duplicate root
Category:
Other
Cause:
Action:
ODI-40520
The table {0} doesn''t exist
Category:
Other
Cause:
Action:
ODI-40521
A NamingException occurred saying {0} because of {1} with the remaining name {2}
Category:
Other
Cause:
Action:
ODI-40522
Exception {0} occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40523
Property {0} is invalid
Category:
Other
Cause:
Action:
ODI-40524
Property {0} from the URL is invalid
Category:
Other
Cause:
Action:
ODI-40525
Internal connection is null. This shouldn''t happen that way.
Category:
Other
Cause:
Action:
ODI-40526
A NamingException occured saying: {0} with this explanation: {1} and this remaining name: {2}
Category:
Other
Cause:
Action:
ODI-40527
Could not read alias bundle because an IOException occurred saying: {0}
Category:
Other
Cause:
Action:
ODI-40528
A {0} occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40529
Could not write alias bundle because an IOException occurred saying {0}
Category:
Other
Cause:
Action:
ODI-40530
The schema is now in a read only mode because the technology is not HSQL
Category:
Other
Cause:
Action:
ODI-40531
Exception {0} occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40532
Could not find the element for row of table {0}: {1}
Category:
Other
Cause:
Action:
ODI-40533
Element {0} has no identifier so this row could not be updated.
Category:
Other
Cause:
Action:
ODI-40534
Exception getting original attributes of baseDN={0}
Category:
Other
Cause:
Action:
ODI-40535
Key column {0} has a null value though it''s required
Category:
Other
Cause:
Action:
ODI-40536
Deleting attribute {0} from Object {1}
Category:
Other
Cause:
Action:
ODI-40537
Deleting object {0}
Category:
Other
Cause:
Action:
ODI-40538
Creating attribute value {0} in attribute {1} from Object {2}
Category:
Other
Cause:
Action:
ODI-40539
Adding object {0} to the database from row {1}
Category:
Other
Cause:
Action:
ODI-40540
Modifying attribute value {0} to {1} in attribute {2} from Object {3}
Category:
Other
Cause:
Action:
ODI-40541
Adding attribute value {0} in attribute {1} from Object {2}
Category:
Other
Cause:
Action:
ODI-40542
This update is not permitted because it would move the element to another location in the hierarchy.
Category:
Other
Cause:
Action:
ODI-40543
This update is not permitted because it would move this attribute to another element.
Category:
Other
Cause:
Action:
ODI-40544
The attribute {0} cannot exist in an element of class {1}
Category:
Other
Cause:
Action:
ODI-40545
Modifying attribute value {0} to {1} in attribute {2} from Object {3}
Category:
Other
Cause:
Action:
ODI-40546
A user has not been provided
Category:
Other
Cause:
Action:
ODI-40547
Not Supported
Category:
Other
Cause:
Action:
ODI-40548
Parameter {0} has already been specified. Old value : {1} New value : {2}
Category:
Other
Cause:
Action:
ODI-40549
Invalid value specified for {0}
Category:
Other
Cause:
Action:
ODI-40550
Unable to create IntialLdapContext for {0}. Pagination is not possible. Is LDAP server LDAPv3?
Category:
Other
Cause:
Action:
ODI-40551
LdapContext needed for pagination. Found {0}
Category:
Other
Cause:
Action:
ODI-40552
Invalid page size : {0}
Category:
Other
Cause:
Action:
ODI-40553
Unable to get cipher without instance
Category:
Other
Cause:
Action:
ODI-40554
Unable to encrypt LDAP2 password
Category:
Other
Cause:
Action:
ODI-40555
Unable to encrypt LDAP2 password
Category:
Other
Cause:
Action:
ODI-40556
URL must start with {0}
Category:
Other
Cause:
Action:
ODI-40557
objectClass attribute not found for {0} from parent {1}
Category:
Other
Cause:
Action:
ODI-40558
objectClass attribute not found for element with attributes {0}
Category:
Other
Cause:
Action:
ODI-40559
LDAP server URL is mandatory.
Category:
Other
Cause:
Action:
ODI-40700
Schema {0} cannot be dropped because it is referenced by one or more connections.
Category:
Other
Cause:
Action:
ODI-40701
Exception {0} occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40702
XSD is required for processing flat files
Category:
Other
Cause:
Action:
ODI-40703
Root element name is required for processing flat file
Category:
Other
Cause:
Action:
ODI-40704
The schema {0} already exists. Use the "REPLACE" option to replace the schema
Category:
Other
Cause:
Action:
ODI-40705
The schema parameter is required in the command SET SCHEMA
Category:
Other
Cause:
Action:
ODI-40706
This schema doesn''t exist: {0}
Category:
Other
Cause:
Action:
ODI-40707
No existing schema with this name: "{0}". Please verify that it is the same schema name than the one you specified in your URL connection.
Category:
Other
Cause:
Action:
ODI-40708
Error synchronizing automatically the schema
Category:
Other
Cause:
Action:
ODI-40709
The xml file is required in a LOAD FILE command
Category:
Other
Cause:
Action:
ODI-40710
The schema name is mandatory for the CREATE SCHEMA command
Category:
Other
Cause:
Action:
ODI-40711
This schema has no DTD and cannot be saved to a XML file
Category:
Other
Cause:
Action:
ODI-40712
This table doesn''t exist in the schema so it can''t be the root table: {0}
Category:
Other
Cause:
Action:
ODI-40713
The file parameter is required to write a file
Category:
Other
Cause:
Action:
ODI-40714
Could not find a file to verify: make sure you are on a schema associated with a file or use the "VALIDATE FILE <FileName>" syntax.
Category:
Other
Cause:
Action:
ODI-40715
Exception {0} occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40716
Parameter {0} has been declared twice. Old value : {1} New value : {2}
Category:
Other
Cause:
Action:
ODI-40717
Unknown parameter : {0}
Category:
Other
Cause:
Action:
ODI-40718
Could not read the input XML data
Category:
Other
Cause:
Action:
ODI-40719
Could not read the XML data because a SAXException occurred saying: {0}
Category:
Other
Cause:
Action:
ODI-40720
Could not read the XML data because the parser is not configured correctly: {0}
Category:
Other
Cause:
Action:
ODI-40721
Could not read the XML data because an IOException occurred saying: {0}
Category:
Other
Cause:
Action:
ODI-40722
The data has been altered: {0} !!!
Category:
Other
Cause:
Action:
ODI-40723
XmlParser not validated.
Category:
Other
Cause:
Action:
ODI-40724
The same connection should have been returned but I got another one
Category:
Other
Cause:
Action:
ODI-40725
Custom varchar column size was not correct: {0} instead of 300
Category:
Other
Cause:
Action:
ODI-40726
Truncate did not truncate a table
Category:
Other
Cause:
Action:
ODI-40727
Custom numeric column size was not correct: {0} instead of 12
Category:
Other
Cause:
Action:
ODI-40728
Could not find the row with a pk=20
Category:
Other
Cause:
Action:
ODI-40729
Error: Dropping of a schema that is referenced by another connection is allowed!
Category:
Other
Cause:
Action:
ODI-40730
Standalone schema type is not compatible with external database storage
Category:
Other
Cause:
Action:
ODI-40733
Creating a data inserter which uses prepared statements
Category:
Other
Cause:
Action:
ODI-40734
An UnsupportedDatatypeException occurred
Category:
Other
Cause:
Action:
ODI-40735
Model type not supported: {0}. Expecting one of dtd, xsd.
Category:
Other
Cause:
Action:
ODI-40736
IOException occurred
Category:
Other
Cause:
Action:
ODI-40737
A parsing exception occurred
Category:
Other
Cause:
Action:
ODI-40738
A SAXException was caught while reading the model saying: {0}
Category:
Other
Cause:
Action:
ODI-40739
A ParserConfigurationException was caught while reading the model
Category:
Other
Cause:
Action:
ODI-40740
A duplicate element was found in the DTD/XSD
Category:
Other
Cause:
Action:
ODI-40741
A duplicate type was found in the DTD/XSD
Category:
Other
Cause:
Action:
ODI-40742
An unknown element was found in the DTD/XSD
Category:
Other
Cause:
Action:
ODI-40743
Namespace not found
Category:
Other
Cause:
Action:
ODI-40744
Ambiguous name
Category:
Other
Cause:
Action:
ODI-40745
Malformed QName
Category:
Other
Cause:
Action:
ODI-40746
Unsupported model
Category:
Other
Cause:
Action:
ODI-40747
Duplicate attribute
Category:
Other
Cause:
Action:
ODI-40748
Duplicate reference to an element
Category:
Other
Cause:
Action:
ODI-40749
Conflicting namespaces
Category:
Other
Cause:
Action:
ODI-40750
The model generated by the model mapper was not accepted by a validator
Category:
Other
Cause:
Action:
ODI-40751
An XMLUnsupportedException was caught
Category:
Other
Cause:
Action:
ODI-40752
The DTD file "{0}" doesn''t exist: {0}
Category:
Other
Cause:
Action:
ODI-40753
No DTD is associated to the file {0}
Category:
Other
Cause:
Action:
ODI-40754
File {0} is already locked by another instance of the XML driver.
Category:
Other
Cause:
Action:
ODI-40755
Could not lock file {0}: {1}
Category:
Other
Cause:
Action:
ODI-40756
No DTD was found so no data was retrieved
Category:
Other
Cause:
Action:
ODI-40757
An exception occurred while reading the file
Category:
Other
Cause:
Action:
ODI-40758
Malformed qualified name in root properties: {0}
Category:
Other
Cause:
Action:
ODI-40759
Both the schema "{0}" and the file "{1}" have been modified!
Category:
Other
Cause:
Action:
ODI-40760
The root table ({0}) doesn''t exist!
Category:
Other
Cause:
Action:
ODI-40761
Not enough memory to read the XML file
Category:
Other
Cause:
Action:
ODI-40762
Cannot write the file because this schema is opened in a read-only mode.
Category:
Other
Cause:
Action:
ODI-40763
Invalid property definition: "{0}" in "{1}"
Category:
Other
Cause:
Action:
ODI-40764
File {0} is not locked or cannot be unlocked.
Category:
Other
Cause:
Action:
ODI-40765
Cannot write to an URL.
Category:
Other
Cause:
Action:
ODI-40766
Could not delete existing file {0}.
Category:
Other
Cause:
Action:
ODI-40767
Could not rename existing file {0} to make a backup
Category:
Other
Cause:
Action:
ODI-40768
Could not save the file {0} because a {1} occurred and said: {2}
Category:
Other
Cause:
Action:
ODI-40769
Could not close the file. You should probably close your application: {0}
Category:
Other
Cause:
Action:
ODI-40770
Could not delete the output file after an error occurred
Category:
Other
Cause:
Action:
ODI-40771
Could not restore the original file after an error occurred
Category:
Other
Cause:
Action:
ODI-40772
No DTD was found so no data was retrieved
Category:
Other
Cause:
Action:
ODI-40773
Connection type not supported: {0}
Category:
Other
Cause:
Action:
ODI-40774
No DTD was found so no data was retrieved
Category:
Other
Cause:
Action:
ODI-40775
Should not occur for prefix generation
Category:
Other
Cause:
Action:
ODI-40776
Could not free the file {0}. Verify that no .lck file is left.
Category:
Other
Cause:
Action:
ODI-40777
Found PCDATA in element {0} with values ({1})
Category:
Other
Cause:
Action:
ODI-40778
Attribute {0} of element {1} doesn''t exist in the DTD.
Category:
Other
Cause:
Action:
ODI-40779
Root element was not found in the XML Model
Category:
Other
Cause:
Action:
ODI-40780
Root element is ambiguous in the XML Model
Category:
Other
Cause:
Action:
ODI-40781
Could not find the prefix {0}
Category:
Other
Cause:
Action:
ODI-40782
Could not find the namespace for the root element
Category:
Other
Cause:
Action:
ODI-40783
Root element has a malformed name
Category:
Other
Cause:
Action:
ODI-40784
Prefix {0} should exist
Category:
Other
Cause:
Action:
ODI-40785
Malformed QName: {0}
Category:
Other
Cause:
Action:
ODI-40786
Prefix not found: {0}
Category:
Other
Cause:
Action:
ODI-40787
Ambiguous qname for an attribute: {0}
Category:
Other
Cause:
Action:
ODI-40788
Element {0} is ambiguous and was found in more than one namespace: {1}, {2}
Category:
Other
Cause:
Action:
ODI-40789
Element {0} doesn''t match the DTD
Category:
Other
Cause:
Action:
ODI-40790
Could not find parent element {0}
Category:
Other
Cause:
Action:
ODI-40791
Element {0} doesn''t match the DTD
Category:
Other
Cause:
Action:
ODI-40792
Prefix not found: {0}
Category:
Other
Cause:
Action:
ODI-40793
Malformed QName: {0}
Category:
Other
Cause:
Action:
ODI-40794
Element {0} is ambiguous and was found in more than one namespace
Category:
Other
Cause:
Action:
ODI-40795
Element {0} is ambiguous and was found in more than one namespace
Category:
Other
Cause:
Action:
ODI-40796
Conflicting namespaces: {0} => {1}
Category:
Other
Cause:
Action:
ODI-40797
Namespace {0} was not declared in the model
Category:
Other
Cause:
Action:
ODI-40798
Unknown type: {0}
Category:
Other
Cause:
Action:
ODI-40799
Root element "{0}" of XML file doesn''t match the DTD/XSD element with name "{1}" from namespace "{2}" set as root element
Category:
Other
Cause:
Action:
ODI-40800
No root found!
Category:
Other
Cause:
Action:
ODI-40801
Ambiguous name: {0}
Category:
Other
Cause:
Action:
ODI-40802
Namespace not found for {0}
Category:
Other
Cause:
Action:
ODI-40803
Malformed qualified name {0}
Category:
Other
Cause:
Action:
ODI-40804
Empty table for multiple links in attribute {0}
Category:
Other
Cause:
Action:
ODI-40805
Unknown link type: {0}
Category:
Other
Cause:
Action:
ODI-40806
Multiple roots found: {0} and {1}. Use the parameter 'root_elt' in the URL to choose the root element.
Category:
Other
Cause:
Action:
ODI-40807
No root found in the DTD file
Category:
Other
Cause:
Action:
ODI-40808
Should not occur {0}
Category:
Other
Cause:
Action:
ODI-40809
Creating a RDB model from an XML model is currently not supported
Category:
Other
Cause:
Action:
ODI-40810
Creating an XML model from a RDB model is currently not supported
Category:
Other
Cause:
Action:
ODI-40811
No root on model
Category:
Other
Cause:
Action:
ODI-40812
The table {0} which is linked to attribute {1} was not found
Category:
Other
Cause:
Action:
ODI-40813
Unknown attribute: {0}
Category:
Other
Cause:
Action:
ODI-40814
Unknown link type: {0}
Category:
Other
Cause:
Action:
ODI-40815
Ambiguous name: {0}
Category:
Other
Cause:
Action:
ODI-40816
Bad attribute: {0} in element
Category:
Other
Cause:
Action:
ODI-40817
Namespace not found: {0}
Category:
Other
Cause:
Action:
ODI-40818
Internal error: expected to find PCData in element {0}
Category:
Other
Cause:
Action:
ODI-40819
Malformed QName: {0}
Category:
Other
Cause:
Action:
ODI-40820
*** FATAL *** A duplicate root has been found: {0}
Category:
Other
Cause:
Action:
ODI-40821
*** FATAL *** The potential root is not in the model: {0}
Category:
Other
Cause:
Action:
ODI-40822
Duplicate attribute: {0}
Category:
Other
Cause:
Action:
ODI-40823
Type unsupported for PCDATA attribute of element
Category:
Other
Cause:
Action:
ODI-40824
Two namespaces are in conflict and we cannot build aliases: {0}
Category:
Other
Cause:
Action:
ODI-40825
*** FATAL *** Could not create a table because it already exists in the model.
Category:
Other
Cause:
Action:
ODI-40826
A Qualified name cannot begin with a colon
Category:
Other
Cause:
Action:
ODI-40827
A Qualified name cannot end with a colon
Category:
Other
Cause:
Action:
ODI-40828
SnpsXmlNamespaceNotFoundException occured: Should not occur while setting prefixes
Category:
Other
Cause:
Action:
ODI-40829
This is a fixed namespace and elements cannot be added to it
Category:
Other
Cause:
Action:
ODI-40830
The request type is different
Category:
Other
Cause:
Action:
ODI-40831
The request command is different
Category:
Other
Cause:
Action:
ODI-40832
A parameter is missing
Category:
Other
Cause:
Action:
ODI-40833
A parameter has a bad value
Category:
Other
Cause:
Action:
ODI-40834
This token was not expected anymore: {0}
Category:
Other
Cause:
Action:
ODI-40835
Function not implemented yet: {0}
Category:
Other
Cause:
Action:
ODI-40836
Cannot drop the default schema
Category:
Other
Cause:
Action:
ODI-40837
An error occurred during the creation of the schema: {0}
Category:
Other
Cause:
Action:
ODI-40838
An error occurred in the cleanup of the schema: {0}
Category:
Other
Cause:
Action:
ODI-40839
InvalidTableException said: {0}
Category:
Other
Cause:
Action:
ODI-40840
The table {0} already exists in the schema {1}.
Category:
Other
Cause:
Action:
ODI-40841
Could not create schema with URL "{0}"
Category:
Other
Cause:
Action:
ODI-40842
As no XML and no DTD were provided, the XML schema cannot be created
Category:
Other
Cause:
Action:
ODI-40843
No DTD found and no XML file provided: the XML schema cannot be created
Category:
Other
Cause:
Action:
ODI-40844
Could not generate the DTD because the file could not be created. Verify that you have write permission in the directory.
Category:
Other
Cause:
Action:
ODI-40845
While generating the DTD from the XML file, a "{0}" exception occurred saying: {1}
Category:
Other
Cause:
Action:
ODI-40846
Could not close the file because an IOException occurred saying: {0}
Category:
Other
Cause:
Action:
ODI-40847
An UnupportedDatatypeException occurred saying: {0}
Category:
Other
Cause:
Action:
ODI-40848
Could not find the file called {0}
Category:
Other
Cause:
Action:
ODI-40849
IOException reading file called {0}
Category:
Other
Cause:
Action:
ODI-40850
Unsupported DB property "{0}"
Category:
Other
Cause:
Action:
ODI-40851
Table {0} not found in schema {1}
Category:
Other
Cause:
Action:
ODI-40852
The default schema cannot be read/write
Category:
Other
Cause:
Action:
ODI-40853
The schema {0} cannot be set read/write because it has no associated file
Category:
Other
Cause:
Action:
ODI-40854
No file provided for synchronization. Use CREATE FILE <file> FROM <schema> command
Category:
Other
Cause:
Action:
ODI-40855
Table {0} already exists but it doesn''t have the correct number of columns
Category:
Other
Cause:
Action:
ODI-40856
Column {0} doesn''t exist in table {1}, it is required for this DTD
Category:
Other
Cause:
Action:
ODI-40857
Expected one of auto, xml or xsd for parameter ns_prefix_generation
Category:
Other
Cause:
Action:
ODI-40858
Found that the file references the DTD or XSD: {0}
Category:
Other
Cause:
Action:
ODI-40859
Could not read the file to get its associated schema because an IOException occurred saying {0}
Category:
Other
Cause:
Action:
ODI-40860
Could not read the file to get its associated schema because a SAXException occurred saying {0}
Category:
Other
Cause:
Action:
ODI-40861
Could not read the file to get its associated schema because a ParserConfigurationException occurred saying {0}
Category:
Other
Cause:
Action:
ODI-40862
No DTD was provided and the property "generate_dtd" is set to no
Category:
Other
Cause:
Action:
ODI-40863
The parameter generate_dtd has a bad value: {0} . One of 'AUTO', 'YES', 'NO' was expected
Category:
Other
Cause:
Action:
ODI-40864
XSD {0} was found
Category:
Other
Cause:
Action:
ODI-40865
No DTD named {0} was found so the XML schema could not be created
Category:
Other
Cause:
Action:
ODI-40866
This schema is in a {0} state and cannot be opened in another state.
Category:
Other
Cause:
Action:
ODI-40867
Could not connect on schema because it is {0}
Category:
Other
Cause:
Action:
ODI-40868
The path {0} doesn''t exist
Category:
Other
Cause:
Action:
ODI-40869
The path {0} is not a directory
Category:
Other
Cause:
Action:
ODI-40870
You already have a schema opened on this file with another name: {0}
Category:
Other
Cause:
Action:
ODI-40871
Duplicate attribute where no attribute should have been set yet.
Category:
Other
Cause:
Action:
ODI-40872
Unsupported exception saying {0}
Category:
Other
Cause:
Action:
ODI-40873
There are several root tables and the unload is not supported in this case
Category:
Other
Cause:
Action:
ODI-40874
Expected to find attribute {0}
Category:
Other
Cause:
Action:
ODI-40875
Something unexpected occured. Expected to find datatype {0}
Category:
Other
Cause:
Action:
ODI-40876
Extension found in an object of type {0} is not permitted.
Category:
Other
Cause:
Action:
ODI-40877
Cannot merge types for element {0}.
Category:
Other
Cause:
Action:
ODI-40878
Restriction violated : {0}
Category:
Other
Cause:
Action:
ODI-40879
An IOException occured while including another schema saying {0}
Category:
Other
Cause:
Action:
ODI-40880
A ParserConfigurationException occured while including another schema saying {0}
Category:
Other
Cause:
Action:
ODI-40881
Unexpected element of type {0}
Category:
Other
Cause:
Action:
ODI-40882
Cannot add a restriction!: {0}
Category:
Other
Cause:
Action:
ODI-40883
Cannot add a restriction on a non simple type or attribute
Category:
Other
Cause:
Action:
ODI-40884
Extension found outside an element
Category:
Other
Cause:
Action:
ODI-40885
Type {0} was not found
Category:
Other
Cause:
Action:
ODI-40886
Cannot merge types for element "{0}"
Category:
Other
Cause:
Action:
ODI-40887
Unexpected element of type {0} in hierarchy before simple type
Category:
Other
Cause:
Action:
ODI-40888
Unexpected element of type {0}
Category:
Other
Cause:
Action:
ODI-40889
Could not affect complex type to object of type {0}
Category:
Other
Cause:
Action:
ODI-40890
Unexpected element of type {0}
Category:
Other
Cause:
Action:
ODI-40891
An element has no name and doesn''t refer to another element
Category:
Other
Cause:
Action:
ODI-40892
Cannot add an element to an attributeGroup (wanting to add {0} to group {1} )
Category:
Other
Cause:
Action:
ODI-40893
Cannot add an element to an object of type {0}
Category:
Other
Cause:
Action:
ODI-40894
Could not find namespace: {0}
Category:
Other
Cause:
Action:
ODI-40895
Conflicting Namespace Error: Should not occur: {0}
Category:
Other
Cause:
Action:
ODI-40896
Unknown prefix: {0}
Category:
Other
Cause:
Action:
ODI-40897
Cannot handle type [{0}] as a simple type
Category:
Other
Cause:
Action:
ODI-40898
Element {0} referenced in group {1} was not found
Category:
Other
Cause:
Action:
ODI-40899
Attributes' group {0} not found in the file.
Category:
Other
Cause:
Action:
ODI-40900
Duplicate attribute: {0}
Category:
Other
Cause:
Action:
ODI-40901
Unsupported exception: {0}
Category:
Other
Cause:
Action:
ODI-40902
Element group {0} not found in the file.
Category:
Other
Cause:
Action:
ODI-40903
Duplicate reference while adding an element of a group: {0}
Category:
Other
Cause:
Action:
ODI-40904
Unsupported exception while adding an element of a group: {0}
Category:
Other
Cause:
Action:
ODI-40905
Namespace {0} for element {1} referenced in group {2} was not found.
Category:
Other
Cause:
Action:
ODI-40906
Element {0} referenced in group {1} has an ambiguous name
Category:
Other
Cause:
Action:
ODI-40907
An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group
Category:
Other
Cause:
Action:
ODI-40908
No more pending objects left in hierarchy
Category:
Other
Cause:
Action:
ODI-40909
An object of one of these types was expected in the hierarchy: element, type, attribute, attribute group
Category:
Other
Cause:
Action:
ODI-40910
Cannot add element {0} to type {1} because it doesn''t handle references.
Category:
Other
Cause:
Action:
ODI-40911
One pending element was not found: {0}
Category:
Other
Cause:
Action:
ODI-40912
Simple type {0} has a restriction on a type {1}
Category:
Other
Cause:
Action:
ODI-40913
The object of type {0} is missing type {1} but don't know how to deal with it.
Category:
Other
Cause:
Action:
ODI-40914
Element {0} is missing but is referenced
Category:
Other
Cause:
Action:
ODI-40915
Type {0} is missing but is needed.
Category:
Other
Cause:
Action:
ODI-40916
Element {0} has no type.
Category:
Other
Cause:
Action:
ODI-40917
One pending element's namespace was not found: {0}
Category:
Other
Cause:
Action:
ODI-40918
One pending element has an ambiguous name: {0}
Category:
Other
Cause:
Action:
ODI-40919
Cannot add element {0} to type {1} because it doesn''t handle references.
Category:
Other
Cause:
Action:
ODI-40920
An attribute must have a simple type
Category:
Other
Cause:
Action:
ODI-40921
Could not find the root element that we've just set.
Category:
Other
Cause:
Action:
ODI-40922
This qualified name is malformed: {0}
Category:
Other
Cause:
Action:
ODI-40923
Inner type of element {0} is not defined or is not a complex type
Category:
Other
Cause:
Action:
ODI-40924
Renamed column {0} to {1}
Category:
Other
Cause:
Action:
ODI-40925
Should not occur
Category:
Other
Cause:
Action:
ODI-40926
Internal error
Category:
Other
Cause:
Action:
ODI-40927
Not Supported
Category:
Other
Cause:
Action:
ODI-40928
Not supported for XML driver commands
Category:
Other
Cause:
Action:
ODI-40929
Property {0} has invalid value {1}
Category:
Other
Cause:
Action:
ODI-40930
Root element {0} specified by user not a global element in the NXSD
Category:
Other
Cause:
Action:
ODI-40931
Unrecognised request type for {0}
Category:
Other
Cause:
Action:
ODI-40932
Unable to find root element in DTD.
Category:
Other
Cause:
Action:
ODI-40933
Unable to build XSD from DTD.
Category:
Other
Cause:
Action:
ODI-40934
The schema {0} is not created using the appropriate compatibility mode.
Category:
Other
Cause:
Action:
ODI-40935
The schema {0} was created with correct compatibility mode, but has incorrect XML model type
Category:
Other
Cause:
Action:
ODI-40936
Namespace URI for the prefix {0} was not found in the XSD/DTD or XML
Category:
Other
Cause:
Action:
ODI-40937
Encountered one more close tag while no more open tags were found
Category:
Other
Cause:
Action:
ODI-40938
Error splitting prefixed string {0}
Category:
Other
Cause:
Action:
ODI-40939
The XML construct "{0}" in element "{1}" from type "{2}" is not supported by XML JDBC driver
Category:
Other
Cause:
Action:
ODI-40940
No global elements were found in the XSD
Category:
Other
Cause:
Action:
ODI-40941
Requested root element {0} was not found in the XSD
Category:
Other
Cause:
Action:
ODI-40942
Ending on "{0}" but needed to find "{1}"
Category:
Other
Cause:
Action:
ODI-40945
XSD parser ecnountered error parsing XSD/DTD. Check validity.
Category:
Other
Cause:
Action:
ODI-40946
Error processing XSD/DTD
Category:
Other
Cause:
Action:
ODI-40947
Unable to write xpath mapping information
Category:
Other
Cause:
Action:
ODI-40948
Could not find namespace URI {0} in XML model for {1}
Category:
Other
Cause:
Action:
ODI-40949
Old object type found for namespace {0}
Category:
Other
Cause:
Action:
ODI-40951
Unable to find namespace URI : {0}
Category:
Other
Cause:
Action:
ODI-40952
Element {0} of type {1} at xpath {2} appears to be same as element {3} of type {4} at xpath {5}.
Category:
Other
Cause:
Action:
ODI-40953
Prefix "{0}" is already mapped to "{1}" in current XML scope. New uri : "{2}"
Category:
Other
Cause:
Action:
ODI-40956
Root element {0} is substitutionGroup head. This is not allowed.
Category:
Other
Cause:
Action:
ODI-40957
Unable to resolve path of XSD "{0}"
Category:
Other
Cause:
Action:
ODI-40958
Illegal state. Currently coalescing for "{0}".
Category:
Other
Cause:
Action:
ODI-40959
Illegal state. Not coalescing yet.
Category:
Other
Cause:
Action:
ODI-40960
Unknown object "{0}" found
Category:
Other
Cause:
Action:
ODI-40961
You cannot use v1 compatibility flag along with v3 mode
Category:
Other
Cause:
Action:
ODI-40962
Error occurred checking if table "{0}" exists
Category:
Other
Cause:
Action:
ODI-40963
XSD does not define "anyAttribute" for {0}, but found it in DB.
Category:
Other
Cause:
Action:
ODI-40964
Element "{0}" is defined in XSD to have "any" element child, but could not find it in model.
Category:
Other
Cause:
Action:
ODI-40965
Illegal metadata on element "{0}". Element results in column, but has table metadata.
Category:
Other
Cause:
Action:
ODI-40966
Column metadata set on element with xpath "{0}" while it has child : "{1}"
Category:
Other
Cause:
Action:
ODI-40967
Illegal metadata on attribute "{0}" with xpath "{1}". Attribute may only have column metadata.
Category:
Other
Cause:
Action:
ODI-40968
Property only supported for complex file driver when inxb/is_nxsd_based=true.
Category:
Other
Cause:
Action:
ODI-40969
Trying to use "{0}" data type with Statement not supported. {1} xPath "{2}". Either user has requested not to use PreparedStatement or your DB/driver does not support PreparedStatement
Category:
Other
Cause:
Action:
ODI-40970
Trying to use table "{0}" used by "{1}" for "{2}"
Category:
Other
Cause:
Action:
ODI-40971
When user specifies DB type, length and scale must also be specified. Not done for "{0}"
Category:
Other
Cause:
Action:
ODI-40972
More than one "any" associated with element "{0}"
Category:
Other
Cause:
Action:
ODI-40973
URL must start with {0}
Category:
Other
Cause:
Action:
ODI-40974
Element with xpath {0} already set with recursion head as {1}
Category:
Other
Cause:
Action:
ODI-40975
Element with xpath {0} already set with recursion on {1}
Category:
Other
Cause:
Action:
ODI-40976
xpath {0} already seen with {1}
Category:
Other
Cause:
Action:
ODI-40977
URL syntax error {0}. Consult driver documentation
Category:
Other
Cause:
Action:
ODI-41000
Groovy code in stage {0} could not be compiled
Category:
Other
Cause:
Action:
ODI-41001
Groovy code in stage {0} could not be converted to GroovySource
Category:
Other
Cause:
Action:
ODI-41002
GroovySource for stage {0} is null
Category:
Other
Cause:
Action:
ODI-41003
Groovy code for stage {0} pointed by {1} could not be located as file or classpath resource
Category:
Other
Cause:
Action:
ODI-41004
Groovy script for stage {0} could not be read
Category:
Other
Cause:
Action:
ODI-41005
Groovy script for stage {0} could not be compiled
Category:
Other
Cause:
Action:
ODI-41006
Java class {0} for stage {1} could not be found
Category:
Other
Cause:
Action:
ODI-41007
Stage definition {0} is invalid. Need at least one of "code", "groovyScript" or "javaClass"
Category:
Other
Cause:
Action:
ODI-41008
Unable to find constructor with right signature for stage {0}. Expected constructor with params {1}
Category:
Other
Cause:
Action:
ODI-41009
Error instantiating stage {0}
Category:
Other
Cause:
Action:
ODI-41010
Stage {0} incorrectly attempts to create an InputDecorator. This class is not meant for instantiation.
Category:
Other
Cause:
Action:
ODI-41011
Stage {0} incorrectly attempts to create an OutputDecorator. This class is not meant for instantiation.
Category:
Other
Cause:
Action:
ODI-41012
LinkageError trying to instantiate Java class {0} for stage {1}
Category:
Other
Cause:
Action:
ODI-41013
InitializationError trying to instantiate Java class {0} for stage {1}
Category:
Other
Cause:
Action:
ODI-50000
Java exception thrown: {0}.
Category:
Programmatic
Cause:
A java exception was thrown during processing.
Action:
Internal Error: contact Oracle support.
ODI-999999
Expression reference not found: {0}.
Category:
Programmatic
Cause:
The expression being parsed has a column reference that cannot be found.
Action:
Check the expression