Skip Headers
Oracle® Fusion Middleware Error Messages Reference
11g Release 1 (11.1.1.5.0)

Part Number E10113-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

62 ODI-01100 to ODI-30095

ODI-01100: Agent {0} successfully cleaned up {1} stale sessions from work repository {2} using {3}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01101: 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}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01102: Agent {0} successfully completed session {1} ({2}) on {3} using context {4} with statistics: Rows {5} Inserts {6} Updates {7} Deletes {8} Errors {9}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01103: Agent {0} successfully completed step {1} in session {2}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01104: Agent {0} successfully connected to master repository using {1}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01105: Agent {0} successfully connected to work repository {1} using {2}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01106: Agent {0} created load plan {1}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01107: Agent {0} created session {1} ({2}) in work repository {3}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01108: Agent {0} created session {1} ({2}) from scenario {3} in work repository {4} using context {5}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01109: Agent {0} is delegating session {1} on work repository {2} to agent {3}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01110: Agent {0} successfully retrieved {1} schedules from work repository {2} using {3}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01111: Agent {0} started. Agent version: {1}. Port: {2}. JMX Port: {3}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01112: Agent {0} received a request to recalculate its schedule on work repository {1}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01113: Agent {0} received a data server test request for {1}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01114: Agent {0} received a request to stop load plan instance {1} on work repository {2}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01115: Agent {0} received a ping request.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01116: Agent {0} received a request to retrieve its schedule on work repository {1}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01117: Agent {0} received a request to restart load plan instance ({1}) in work repository {2}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01118: Agent {0} received a request to start load plan {1} on work repository {2} using context {3}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01119: Agent {0} received a request to start scenario {1}.{2} on work repository {3} using context {4}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01120: Agent {0} received a request to restart session {1} on work repository {2} using context {3}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01121: Agent {0} received a request to stop session {1} on work repository {2}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01122: Agent {0} successfully restarted {1} queued sessions from work repository {2} using {3}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01123: Agent {0} sent a request to agent {1}.
Cause: null
Action: null

Level: 16

Type: TRACE

Impact: Other

ODI-01124: Agent {0} started load plan {1}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01125: Agent {0} started session {1} ({2}) from scenario {3} in work repository {4} using context {5}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01126: Agent {0} started session {1} ({2}) in work repository {3} using context {4}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01127: Agent {0} started step {1} in session {2}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01128: Agent {0} is starting. Application Server: {1}. Agent Version: {2}. Port: {3}. JMX Port: {4}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01129: Agent {0} stopped.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01130: Agent {0} is stopping.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01131: Agent {0} encountered an error: {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01132: Agent {0} encountered a warning: {1}
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01133: Agent {0} detected that the work repository {1} went down.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01134: Agent {0} encountered an error: {1}
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01135: Agent {0} detected that the master repository went down.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01136: Starting Schedulers on Agent {0}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01137: Scheduler started for work repository {0} on Agent {1}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01138: Migrating Schedulers for Agent {0}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01139: 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.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01140: Unable to stop session ({0}) immediately. This session will be stopped by the agent ({1}) before next task begins.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01141: Agent {0} started load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01142: Agent {0} successfully completed load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01143: Agent {0} starting processing for load plan instance {1} ({2}), run {3}, from step id {4} in work repository {5}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01144: Agent {0} completed processing for load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01145: Agent {0} not found when trying to stop session with id {1} in work repository {2}.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01146: Agent {0} invocation error when trying to stop session with id {1} in work repository {2}: {3}
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01147: Agent {0} stopped load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01148: Agent {0} executing load plan log purge for work repository {1} at {2}.
Cause: null
Action: null

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01149: Agent {0} purge failed for load plan instance ({1}): {2}
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01150: Agent {0} purge failed for load plan instance ({1}): {2}
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01151: Agent {0} cannot continue load plan instance {1} ({2}), run {3} in work repository {4}, because the instance has been deleted.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01152: Agent {0} continuing processing for load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01153: An exception occurred while processing scheduled job for scenario {0} and version {1}. The exception message is : {2}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01154: An exception occurred while processing scheduled job for loadplan {0}. The exception message is : {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01155: Invalid repetition interval {0} specified in scheduled job for scenario {1} {2}. The schedule would not be repeated.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01156: Invalid repetition interval {0} specified in scheduled job for loadplan {1}. The schedule would not be repeated.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01157: Coherence cluster property {0} is not found in the system properties for Agent {1}. Agent may connect to an unintended coherence cluster.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

ODI-01200: Session start failure: the request is incorrectly formed.
Cause: A malformed request was sent to the agent.
Action: Verify the request format and parameters sent to the agent.

Level: 1

Type: ERROR

Impact: Other

ODI-01201: Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01202: Session start failure on agent {0}: data source for master repository does not contain a master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01203: Session start failure on agent {0}: the master repository is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01204: Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01205: Session start failure on agent {0}: an authentication error occurrs while connecting to the master repository.
Cause: An incorrect ODI user or password was specified for this master repository.
Action: Verify the ODI user and password used for connecting.

Level: 1

Type: ERROR

Impact: Other

ODI-01206: Session start failure on agent {0}: the agent is not defined in the topology for master repository.
Cause: The session was not found in the master repository.
Action: Verify that a session with this ID exists in the repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01207: Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01208: Session start failure on agent {0}: database schema {1} does not contain a work repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01209: Session start failure on agent {0}: work repository {1} is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01210: Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01211: Session start failure on agent {0}: work repository {1} is not bound to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01212: Session preparation failure: scenario {0} does not exist in work repository {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01213: Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01214: Session preparation failure: context {0} does not exist in the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01215: Session preparation failure: privileges are insufficient to run scenario {0}.{1} in repository {2}.
Cause: User privileges were not sufficient for running this scenario in this repository.
Action: Ensure that the user has sufficient privileges for this task.

Level: 1

Type: ERROR

Impact: Other

ODI-01216: Session preparation failure: insufficient privileges to use Context {0} ({1}).
Cause: User privileges were not sufficient for using this context.
Action: Ensure that the user has sufficient privileges for this task.

Level: 1

Type: ERROR

Impact: Other

ODI-01217: Session {0} ({1}) fails with return code {2}.
Cause: The session finished in an error state.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01218: Session preparation failure: database error occurs while connecting to the master repository.
Cause: The agent received a database error from the master repository while creating the session.
Action: Verify the state of the master repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01219: Session preparation failure: database error while connecting to work repository {0}.
Cause: The agent received a database error from the work repository while creating the session.
Action: Verify the state of the work repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01220: Session preparation failure: an unexpected exception occurred.
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).

Level: 1

Type: ERROR

Impact: Other

ODI-01221: Unable to restart session {0}: session is not found in work repository {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01222: Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01224: Database error while connecting to work repository {0}
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01225: An unexpected exception occurred.
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).

Level: 1

Type: ERROR

Impact: Other

ODI-01226: Step {0} fails after {1} attempt(s).
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01227: Task {0} ({1}) fails on the source {2} connection {3}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01228: Task {0} ({1}) fails on the target {2} connection {3}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01229: An error occurred while performing a {0} operation on model code {1}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01231: An error occurred while performing a {0} operation on datastore {1}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01232: Procedure {0} execution fails.
Cause: This is an execution warning. The procedure execution failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01233: Error while evaluating variable the following expression: {0} {1} {2}
Cause: This is an execution warning. The variable evaluation failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01235: Error while incrementing variable {0} to value {1}
Cause: This is an execution warning. The variable increment failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01236: Error while refreshing variable {0}.
Cause: This is an execution warning. The variable refresh failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01237: Error while setting variable {0} to value {1}.
Cause: This is an execution warning. The set variable operation failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01239: Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01240: Flow {0} fails while performing a {1} operation. This flow loads target table {2}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01241: Oracle Data Integrator tool execution fails.
Cause: This is an execution warning. The tool execution failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01242: Operating system command execution fails.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01243: Session {0} ({1}) fails because work repository {2} went down.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01244: Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01245: Session preparation failure: work repository {0} went down during session preparation.
Cause: Work repository went down while session was being prepared.
Action: Verify the state of the work repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01247: Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01248: Session preparation failure by Agent {0}: master repository went down during session preparation.
Cause: Master repository went down while session was being prepared.
Action: Verify the state of the master repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) fails because master repository went down.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01250: Session {0} ({1}) could not be stopped by Agent {2} because session {0} {1} already completed execution.
Cause: The session has already completed and cannot be stoppped.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01251: Session ({0}) could not be stopped by Agent {1} because session ({0}) was not found in work repository {2}.
Cause: The session was not found in the work repository.
Action: Verify that a session with this ID exists in the repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01252: Session ({0}) could not be stopped by Agent {1}: insufficient privileges to access session.
Cause: User privileges were not sufficient for accessing this session in this agent.
Action: Ensure that the user has sufficient privileges for this task.

Level: 1

Type: ERROR

Impact: Other

ODI-01253: Session {0} ({1}) could not be stopped by Agent {2}: an unknown error occurred.
Cause: An unexpected Exception occurred.
Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.

Level: 1

Type: ERROR

Impact: Other

ODI-01254: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01255: Session {0} ({1}) could not be stopped by Agent {2}: insufficient privileges to stop the session.
Cause: User privileges were not sufficient for stopping this session in this agent.
Action: Ensure that the user has sufficient privileges for this task.

Level: 1

Type: ERROR

Impact: Other

ODI-01256: Session {0} ({1}) stopped (Normal) by user {2}.
Cause: Session was stopped by the user.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01257: Session {0} ({1}) stopped (Immediate) by user {2}.
Cause: Session was stopped by the user.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01258: Session {0} ({1}) stopped (Abort) by user {2}.
Cause: Session was aborted by the user.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01259: Session Task {0} ({1}) stopped (Normal) by user {2}.
Cause: Task was stopped by the user.
Action: Review the task execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01260: Session Task {0} ({1}) stopped (Immediate) by user {2}.
Cause: Task was stopped by the user.
Action: Review the task execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01261: Session Task {0} ({1}) stopped (Abort) by user {2}.
Cause: Task was aborted by the user.
Action: Review the task execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01262: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01263: Step {0} stopped (Normal) by user {1}.
Cause: Step was stopped by the user.
Action: Review the step execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01264: Step {0} stopped (Immediate) by user {1}.
Cause: Step was stopped by the user.
Action: Review the step execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01265: Step {0} stopped (Abort) by user {1}.
Cause: Step was aborted by the user.
Action: Review the step execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01266: Agent {0} detected Session as stale session and set to error status.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01267: Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01268: Agent {0} does not support stopping asynchronous child sessions.
Cause: The agent attempted to stop an asynchronouse child session and this is not supported.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01269: Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01270: 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.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01271: The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01272: The Logical Schema has not been set on {0} for {1}.
Cause: The logical schema for this object has not been set.
Action: Verify that the logical schema has been set in the Topology.

Level: 1

Type: ERROR

Impact: Other

ODI-01273: The selected technology {0} is not supported on source for {1}.
Cause: The selected technology is not supported for this object.
Action: Verify that the object has a valid technology.

Level: 1

Type: ERROR

Impact: Other

ODI-01274: Agent Exception
Cause: An error was detected by the agent when performing an operation.
Action: Review the underlying exception for more details.

Level: 1

Type: ERROR

Impact: Other

ODI-01275: An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01276: An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01277: An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01278: Load plan instance {0}, run {1} does not exist in work repository {2}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01279: The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01280: The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01281: 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.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01311: JobDefinition with name {0} already exists.
Cause: JobDefinition already exists.
Action: Check JobDefinition name.

Level: 32

Type: ERROR

Impact: Other

ODI-01312: Schedule with name {0} already exists.
Cause: Schedule already exists.
Action: Check Schedule name.

Level: 32

Type: ERROR

Impact: Other

ODI-01313: Unable to find job definition for ID {0}.
Cause: Wrong ID.
Action: Check ID.

Level: 32

Type: ERROR

Impact: Other

ODI-01314: Unable to find job definition with name {0}.
Cause: Wrong name.
Action: Check name.

Level: 32

Type: ERROR

Impact: Other

ODI-01315: Unable to update job definition.
Cause: Exception during updating.
Action: Check cause exception details.

Level: 32

Type: ERROR

Impact: Other

ODI-01316: Unable to remove job request.
Cause: Exception was thrown.
Action: Check cause exception details.

Level: 32

Type: ERROR

Impact: Other

ODI-01317: Unable to find scheduler definition with name {0}.
Cause: Wrong name.
Action: Check name.

Level: 32

Type: ERROR

Impact: Other

ODI-01318: jobDefnition is required to have a not null ID.
Cause: Metadata Object ID is null.
Action: Check job definition.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-01400: Agent {0} start failure: JDBC connection error occurs while connecting to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01401: Agent {0} start failure: data source for master repository did not contain a master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01402: Agent {0} start failure: the master repository is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01403: Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01404: Agent {0} start failure: an authentication error occurred while connecting to the master repository.
Cause: An incorrect ODI user or password was specified for this master repository.
Action: Verify the ODI user and password used for connecting.

Level: 1

Type: ERROR

Impact: Other

ODI-01405: Agent {0} start failure: the agent is not defined in the topology for master repository.
Cause: This agent was not declared in the topology.
Action: Add this physical agent in the list of agents in the ODI topology.

Level: 1

Type: ERROR

Impact: Other

ODI-01406: Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01407: Agent {0} started with warning: connection details of {1} do not contain a work repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01408: Agent {0} started with warning: work repository {1} is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01409: Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01410: Agent {0} started with warning: work repository {1} is not bound to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01411: Agent {0} started with warning: a database error occurs while cleansing stale sessions.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01412: Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01413: Request is incorrectly formed.
Cause: A malformed request was sent to the agent.
Action: Review the request format and parameters sent to the agent.

Level: 1

Type: ERROR

Impact: Other

ODI-01414: Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01415: Error connecting to agent {0}: data source for master repository did not contain a master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01416: Error connecting to agent {0}: the master repository is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01417: Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01418: Error connecting to agent {0}: an authentication error occurs while connecting to the master repository.
Cause: An incorrect ODI user or password was specified for this master repository.
Action: Verify the ODI user and password used for connecting.

Level: 1

Type: ERROR

Impact: Other

ODI-01419: Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01420: Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01421: Warning connecting to Agent {0}: work repository {1} is in an invalid state.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01422: Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01423: Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01424: Agent host or port cannot be reached using {0}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application cannot be reached using {0}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01426: Agent {0} is not defined in the topology for the master repository.
Cause: This agent was not declared in the topology.
Action: Add this physical agent to the list of agents in the ODI topology.

Level: 1

Type: ERROR

Impact: Other

ODI-01427: invalid parameters
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.

Level: 1

Type: WARNING

Impact: Other

ODI-01428: internal error
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).

Level: 1

Type: FATAL

Impact: Other

ODI-01429: The user {0} is not authorized to perform request {1} on Agent {2}.
Cause: The user had insufficient privileges for performing this request against the remote agent.
Action: Amend the user privileges.

Level: 1

Type: ERROR

Impact: Other

ODI-01430: Agent {0} cannot clean the stale sessions in work repository {1} due to a database error.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01431: Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01432: Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01433: The Internal agent does not support cleaning stale sessions from multiple work repositories.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01434: Agent {0} start failure: error while trying to use JMX Port {1}.
Cause: JMX Registry was unable to use the given port.
Action: Specify a different port by using the command-line parameter JMXPORT.

Level: 1

Type: ERROR

Impact: Other

ODI-01435: 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}.
Cause: Storage space was low for some IDs in this repository.
Action: Consider creating a new repository.

Level: 1

Type: WARNING

Impact: Other

ODI-01436: Error retrieving ID statistics for repository {0}.
Cause: The ID statistics for this repository could not be verified.
Action: Verify the statistics for this repository manually.

Level: 1

Type: WARNING

Impact: Other

ODI-01437: Error retrieving information from the credential store map.
Cause: Could not retrieve information from the credential store map.
Action: Verify that the credentials have been entered correctly into the credential store map.

Level: 1

Type: ERROR

Impact: Other

ODI-01438: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on master repository {2}.
Cause: Some SQL Exception occurred on the Master Repository.
Action: Verify that other operations on the Agent are working correctly.

Level: 1

Type: ERROR

Impact: Other

ODI-01439: Agent {0} cannot be stopped by user {1}: a JDBC error occurred on work repository {2}.
Cause: Some SQL Exception occurred on the Work Repository.
Action: Verify that other operations on the Agent are working correctly.

Level: 1

Type: ERROR

Impact: Other

ODI-01440: Agent {0} cannot be stopped by user {1}: an unknown error occurred.
Cause: An unexpected Exception occurred.
Action: Verify your Agent configuration and make sure other operations on Agent are working correctly.

Level: 1

Type: ERROR

Impact: Other

ODI-01441: Unable to connect to the master repository at JBDC URL={0} with USER={1}.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01442: Unable to load JBDC Driver {0} configured for master repository connection.
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.

Level: 1

Type: ERROR

Impact: Other

ODI-01443: Error while starting agent : {0}
Cause: Error occurred while starting the embedded web container.
Action: Verify your Agent configuration and make sure that the specified ports are available.

Level: 1

Type: ERROR

Impact: Other

ODI-01500: SQL Exception when accessing work repository {0} while executing load plan instance {1} - {2}
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

Level: 1

Type: ERROR

Impact: Other

ODI-01501: Cannot find variable "{0}" in the definition of load plan instance {1}.
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

Level: 1

Type: ERROR

Impact: Other

ODI-01502: Load plan instance {0} is in an inconsistent state: {1}
Cause: Indicates a problem in the ODI code, like a wrapped IllegalStateException
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01503: Load plan logs for instance {0}, run {1} are corrupted: {2}
Cause: Indicates a problem in the ODI code, it is a wrapped IllegalStateException
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01504: 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.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01505: 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}).
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01506: "Comparison value of step "{2}" ("{0}") is not a valid value of type {3} (load plan instance {4}, variable tested "{1}").
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01507: Load Plan Instance restart called for instance {0}, but no previous runs were found.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01508: Load Plan Instance start called for instance {0}, but previous runs have been found.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01509: Load Plan Instance {0} cannot be restarted because the previous run ({1}) did not finish with an "Error" status.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01510: The same load plan instance {0} simultaneously started by two agents.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01511: Step "{0}" should have already been marked as started before adding value for variable "{1}" (load plan instance {2}, run {3}).
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01512: 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}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01513: Error reading load plan information for session number {0}: "{1}"
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01514: Error trying to stop load plan, instance {0} not found.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01515: Load Plan instance {0} could not be stopped by agent {1} because stop type ({2}) provided in the request is invalid.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01516: Can not start load plan: load plan with name "{0}" does not exist in work repository {1}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01517: Load Plan instance {0}, run {1} could not be stopped because that run is already completed (with status "{2}").
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01518: 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}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01519: Serial step "{0}" failed because child step "{1}" is in error.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01520: Case-When/Else step "{0}" failed because child step "{1}" is in error.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01521: Case step "{0}" failed; the selected child "{1}" is in error.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01522: Run Scenario step failed during invocation. Error message was: {0}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01523: Exception handler for step "{0}" failed, because the root exception serial step "{1}" is in error.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01524: Physical agent {0} could not be found.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01525: Physical agent not found for logical agent name "{0}" and context "{1}" while executing step "{2}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01526: Error encountered while trying to start scenario "{1}{2}" (step "{3}"): {0}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01527: Error refreshing variable "{0}": the associated SQL query returned no results.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01528: Error refreshing variable "{0}": {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01529: Refresh of variable "{0}" failed : {1} {2}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01530: Load plan instance was stopped by user request.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01531: Timeout triggered while executing step "{0}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01532: Timeout triggered on a parent step "{0}" while executing step "{1}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01533: Error refreshing variable "{0}": could not get a connection to the logical schema "{1}" using context {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01534: Could not get SQL query text for variable "{0}" while trying to refresh it.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01535: Can not continue load plan instance {0}, run {1}, because the instance has been deleted.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01536: Load plan instance {0}, run {1} failed to launch scenario: scenario {2} does not exist in work repository {3}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01537: Load plan instance {0}, run {1} failed to launch scenario: Version {3} of scenario {2} does not exist in work repository {4}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01538: Unexpected Exception occurred while executing Load plan instance {0}, run {1}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01539: Agent {0} cannot continue load plan processing for instance {1}, run {2} on work repository {3}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01540: Agent {0} start failure: error while trying to use Http Port {1}.
Cause: Http service was unable to use the given port.
Action: Specify a different port by using the command-line parameter PORT.

Level: 1

Type: ERROR

Impact: Other

ODI-01541: Load Plan start failure on agent {0}: ODI User and Password not specified.
Cause: ODI user and password are not set.
Action: Please specify ODI user and password.

Level: 1

Type: ERROR

Impact: Other

ODI-01542: Start Scenario failure on agent {0}: ODI User and Password not specified.
Cause: ODI User and password are not set.
Action: Please specify ODI user and password.

Level: 1

Type: ERROR

Impact: Other

ODI-01543: RuntimeAgent cannot be used inside an opened transaction, it must be used outside a TransactionTemplate
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01544: None of the agents in Load Balancing list is able to handle this execution ({0}).
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01545: Missing odi supervisor credentials in credential store map [{0}] with key [{1}].
Cause: Could not retrieve information from the credential store map.
Action: Verify that the credentials have been entered correctly into the credential store map.

Level: 1

Type: ERROR

Impact: Other

ODI-01546: The dbms_lock acquisition with lock handle {0} timed out.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01547: The Agent detected deadlock on dbms_lock acquisition with lock handle {0}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01548: The dbms_lock acquisition failed with illegal lock handle {0}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01549: The dbms_lock acquisition with lock handle {0} failed with illegal params error. The parameters are {1}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01550: The dbms_lock acquisition with lock handle {0} failed with unknown return code {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01551: The dbms_lock acquisition failed with a sql exception {0}. Please check if the work repository db user has EXECUTE privilege on DBMS_LOCK package.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01552: The dbms_lock release failed with illegal lock handle {0}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01553: The dbms_lock release for lock handle {0} failed with invalid parameters.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01554: The dbms_lock release for lock handle {0} failed because you do not own the lock.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01555: The dbms_lock release for lock handle {0} failed with an unknown return code {1}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01556: The lock acquisition failed. The lock is already locked by other connection object.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01557: Error refreshing variable "{0}": the associated SQL query returned a NULL value.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01558: 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.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01559: Load Plan Instance {0} cannot be restarted because the context {1} was not found in the work repository {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01560: Load Plan {0} cannot be started because the context {1} was not found in the work repository {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01561: Load Plan {0} cannot be started because the user {1} does not have view privileges to the execution context {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01562: Load Plan Instance {0} cannot be restarted because the user {1} does not have view privileges to the execution context {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01563: Load Plan {0} cannot be started because the user {1} does not have execute privileges to the Load Plan {0}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01564: Load Plan Instance {0} cannot be restarted because the user {1} does not have restart privileges.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01565: Load Plan {0} cannot be started because an unknown exception occurred.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01566: Load Plan Instance {0} cannot be restarted because an unknown exception occurred.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01567: Load Plan {0} cannot be started because a SQL Exception occurred.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01568: Load Plan Instance {0} cannot be restarted because a SQL Exception occurred.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01569: Error trying to stop load plan, instance {0} run {1} not found.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01570: 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.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01571: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because User {3} does not have privileges to stop Sessions.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01572: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because a SQL Exception occurred while accessing the Repository.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01573: Load Plan Instance {0}, run {1} cannot be stopped by Agent {2} because an Unknown error has occurred.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01574: Day of week is not specified for the schedule.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01575: Invalid value specified for the excluded days of month filter: {0}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01576: LoadPlan Operation {0} on Agent {1} failed with the exception {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01577: Parallel step error triggered on a parent step "{0}" while executing step "{1}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01800: Exception {0} has occurred as ESS-EM linking is disabled.
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.

Level: 1

Type: ERROR

Impact: Configuration

ODI-01801: Agent target discovery mbean registration has failed due to {0}.
Cause: A runtime error has occurred.
Action: Check the log for details on the error and take corrective action.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01802: Agent target discovery mbean unregistration has failed due to {0}.
Cause: A runtime error has occurred.
Action: Check the log for details on the error and take corrective action.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01803: Error {0} has occurred during mbean registration.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01804: Error {0} has occurred during mbean deregistration.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01805: Error {0} has occurred during notification listener registration.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01806: Error {0} has occurred during notification listener deregistration.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01807: Error {0} has occurred during deregistration of ODI Service Mbean {1}.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01808: Error {0} has occurred during registration of Agent Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the server and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01809: Error {0} has occurred during registration of Master Repository Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the error and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01810: Error {0} has occurred during registration of Work Repository Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the error and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01811: Error {0} has occurred during registration of Session Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the error and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01812: Error {0} has occurred during registration of Event Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the error and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01813: Error {0} has occurred during registration of Session Search Service Mbean.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the error and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01814: No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.
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.

Level: 1

Type: ERROR

Impact: Configuration

ODI-01815: Exception {0} has occurred during Session Search by id.
Cause: A runtime error has occurred.
Action: No action is required. The session id mentioned for search is not available.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01816: Session status passed {0} is invalid.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01817: Error {0} has occurred while fetching statistics for agents. Statistics shown might not be complete.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01818: Agent Service Mbean is not initialized. Re-initialization of agents in tree is disabled.
Cause: A runtime error has occurred.
Action: Check the log for details on the error, fix the same and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01819: Event Service Mbean is not initialized. Re-initialization of event notification listeners is disabled.
Cause: A runtime error has occurred.
Action: Check log for details on the error, fix the same and restart the OdiConsole application.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01820: Agent {0} is not up at {1} for reason {2}.
Cause: A runtime error has occurred.
Action: Check the log for details on the error.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03000: error in creating repository connection {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03001: error in updating repository connection {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03002: error in deleting repository connection {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03003: Failed to connect to the error table {0}. Check the connection details and retry.
Cause: The table might no longer exist or the structure of the table might not be correct.
Action: Check the connection details and retry.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03016: Creation of Work Repository failed because a previous Work repository was found, and the user had asked not to overwrite any existing repository.
Cause: Work repository already exists and overwriting of the repository was not chosen
Action: Select overwriting of Work Repository

Level: 1

Type: ERROR

Impact: Data

ODI-03017: Exception occurred while creating Work Repository at {0} failed. Failure reason {1}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03018: Test connection failed due to {0}.
Cause: Connection to DB failed
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03019: Exception occurred while exporting Master Repository. Failure reason {0}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03020: Only zip files can be uploaded , the {0} upload was unsuccessful.
Cause: A file with extension other than zip was uploaded.
Action: Make sure file uploaded has zip as extension

Level: 1

Type: ERROR

Impact: Data

ODI-03021: Exception occurred while importing Work Repository. Failure reason {0}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03031: Creation of Master Repository failed at {0}.
Cause: Creation of Master Repository Failed
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03032: Exception occurred while creating Master Repository at {0} failed. Failure reason {1}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03033: Supervisor Password and Confirm Supervisor Password fields should match.
Cause: Supervisor Password and Confirm Supervisor Password fields must match
Action: Input same passwords

Level: 1

Type: ERROR

Impact: Data

ODI-03034: Test connection failed due to {0}.
Cause: Testing of DB connection failed
Action: Check the logs

Level: 1

Type: ERROR

Impact: Data

ODI-03035: Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.
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

Level: 1

Type: ERROR

Impact: Data

ODI-03036: Only zip files can be uploaded , the {0} upload was unsuccessful.
Cause: zip files to be uploaded condition failed
Action: Make sure file uploaded is zip file

Level: 1

Type: ERROR

Impact: Data

ODI-03037: Exception occurred while exporting Master Repository. Failure reason {1}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03038: Exception occurred while exporting Physical Topology. Failure reason {1}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03039: Exception occurred while Importing Master Repository. Failure reason {1}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03040: Unable to connect to the Repository User. {0}
Cause: Testing of DB connection failed
Action: Check the logs

Level: 1

Type: ERROR

Impact: Data

ODI-03041: Unable to connect to the DBA User. {0}
Cause: Testing of DB connection failed
Action: Check the logs

Level: 1

Type: ERROR

Impact: Data

ODI-03046: unable to find the agent for given logical agent and context code
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.

Level: 1

Type: ERROR

Impact: Data

ODI-03047: exception while executing {0}. Failure reason {1}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03048: Only XML files can be uploaded: the {0} upload fails
Cause: File selected for import was not a XML file.
Action: Provide the XML file.

Level: 1

Type: ERROR

Impact: Data

ODI-03049: exception while importing {0}. Failure reason {1}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03075: Error in purging Load Plans Executions/Sessions {0}
Cause: An exception has occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03076: exception while killing {0}. Failure reason {1}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03077: Selected Session {0} is in {1} State, and therefore cannot be killed.
Cause: The selected session was in Done, Error, or Warning state.
Action: No action is required.

Level: 1

Type: ERROR

Impact: Data

ODI-03078: Selected Session {0} is in {1} State, and therefore cannot be restarted.
Cause: The selected session was not in Error state.
Action: No action is required.

Level: 1

Type: ERROR

Impact: Data

ODI-03079: exception while restarting {0}. Failure reason {1}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03080: exception while clearing stalesessions. Failure reason {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03081: Error fetching records from error table {0}. The table might no more exist or the format of the table is not correct
Cause: The table might no longer exist or the structure of the table might not be correct
Action: Upgrade the CKM

Level: 1

Type: ERROR

Impact: DATA

ODI-03082: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.
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.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03083: Scenario "{0}" parent not found.
Cause: Trying to get the Odi Object which does not exist or has been deleted.
Action: Check the logs

Level: 1

Type: ERROR

Impact: Data

ODI-03101: import of {1} from {0) failed
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03102: export of {1} to {0) failed
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03103: failed to stop a loadplan instance id : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03104: failed to start a loadplan : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03105: failed to start a scenario : {0} ? {1}
Cause: An unexpected error occured
Action: Check the logs1

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03106: failed to restart session : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03107: failed to clean stale sessions for repository : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03108: failed to stop session : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03109: Creation of work runtime repository at {0} failed. Failure reason {1}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03110: Update of work runtime repository at {0} failed. Failure reason {1}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03111: failed to read config.properties
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03112: shared config dir path is not valid : {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03114: {0} not set
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03115: {0} is not correct
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03116: failed to read
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03117: datasource not located at {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03118: Could not get the service locator. JpsServiceLocator service is not configured.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03119: JPS Exception {0} was thrown. Credential Store might not be configured.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03120: Credential store could not be found.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03121: Not populating any values in credential store
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03122: Exception in purging Session/Load Plan Executions
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03123: Exception occured while inserting usedInContext in Physical Schema
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03124: Exception occured while deleting usedInContext in Physical Schema
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03125: Exception occured while inserting usedInContext in Edit Phsyical Schema
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03126: Exception in adding an entity
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03127: Odi object not found
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03128: Exception in update
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03129: Unable to find odi object {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03130: Loading of entity failed
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03131: Unauthorized to delete entity of type
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03132: error occurred while executing method
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03133: no repository definition found for alias {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03134: login failed for user {0}=
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03135: version mismatch
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03136: unable to connect to repository with alias {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03137: Error occurred in EMIntegrationServlet.doOperation() - {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03138: failed to init jview diagrammer
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03139: repositories.xml path not set
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03140: {0} file does not exist at {1}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03141: failed to create RepositoryDefinitionRegistry
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03142: error logging out a user after session expired
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03143: Creation of work dev repository at {0} failed. Failure reason {1}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03144: Creation of Master Repository failed at {0}. Failure reason {1}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03146: ???
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03147: Delete operation failed
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03148: Maximum number of sessions should be in between 1 and 99999.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03149: Port Number should not be non negative.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03150: Invalid Context code. Context code cannot have lower case characters and white spaces.
Cause: A validation error occured
Action: Context code cannot have lower case characters and white spaces

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03151: Context code cannot exceed {0} characters
Cause: A validation error occured
Action: Context code cannot exceed some specified limit

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03265: Exception occurred while creating Datasource. Failure reason {0}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03266: Data Source already exists for {0}.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03267: No valid repository alias is found. Click on management link on top right corner to create one.
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.

Level: 1

Type: ERROR

Impact: Data

ODI-03276: Tab limit reached.Please close at least one tab.
Cause: Max limit on the number of tabs that can be open has been met.
Action: Close at least one tab

Level: 1

Type: ERROR

Impact: Data

ODI-03277: Object cannot be found.
Cause: The object might have been deleted.
Action: Refresh your view.

Level: 1

Type: ERROR

Impact: Data

ODI-03278: View operation fails with the following exception {0}. See the server log for details.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03279: Add operation failed with the following exception {0}. Please see the server log for details.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03280: Edit operation failed with the following exception {0}. Please see the server log for details.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03281: Delete operation failed with the following exception {0}. Please see the server log for details.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03290: You are not authorized to add a new entity of this type.
Cause: User doesn't have required privileges to add an new entity of a particular type
Action: No action

Level: 1

Type: ERROR

Impact: Data

ODI-03326: Please specify a valid search text
Cause: Invalid search text was specified
Action: Provide a valid search text

Level: 1

Type: ERROR

Impact: Data

ODI-03327: Please choose at least one model or project type.
Cause: No model or project type was selected
Action: Select at least one model or project type so that search criteria is valid

Level: 1

Type: ERROR

Impact: Data

ODI-03328: Please choose at least one topology type.
Cause: No topology type was selected
Action: Select at least one topology type so that search criteria is valid

Level: 1

Type: ERROR

Impact: Data

ODI-03329: Please choose at least one runtime type.
Cause: No runtime type was selected
Action: Select at least one runtime type so that search criteria is valid

Level: 1

Type: ERROR

Impact: Data

ODI-10001: Action unauthorized for this license: {0}
Cause: Action was unauthorized for this license.
Action: Choose another license.

Level: 32

Type: ERROR

Impact: Security

ODI-10002: Only one local repository can be defined; {0} were found.
Cause: More than one local repository was found.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-10004: File already exists.
Cause: File already existed.
Action: Choose another file.

Level: 32

Type: ERROR

Impact: File

ODI-10005: Repository is expected to be a master repository.
Cause: Repository was expected to be a master repository.
Action: Choose master repository.

Level: 32

Type: ERROR

Impact: Other

ODI-10006: Repository is expected to be enterprise repository.
Cause: Repository was expected to be an enterprise repository.
Action: Choose enterprise repository.

Level: 32

Type: ERROR

Impact: Other

ODI-10007: Object must be in editable state before using set methods.
Cause: The object was not in editable state.
Action: Edit this object.

Level: 32

Type: ERROR

Impact: Other

ODI-10008: Object must be in consult mode before using methods get.
Cause: The object was not in consult mode.
Action: Consult the object.

Level: 32

Type: ERROR

Impact: Other

ODI-10009: Object does not exist in the repository.
Cause: The repository did not contains this object.
Action: Choose another object or create first this one.

Level: 32

Type: ERROR

Impact: Other

ODI-10010: This type of object cannot be updated.
Cause: Object could not be updated.
Action: Do not update this object.

Level: 32

Type: ERROR

Impact: Other

ODI-10011: Invalid object; it has been updated by another user.
Cause: Object was updated by another user.
Action: Refresh the object.

Level: 32

Type: ERROR

Impact: Other

ODI-10012: Object cannot be inserted
Cause: Object could not be inserted.
Action: Check object.

Level: 32

Type: ERROR

Impact: Other

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.
Cause: Import could damage your repository.
Action: Check identifier sequences.

Level: 32

Type: ERROR

Impact: Other

ODI-10015: The work repository {0} is not declared in this master repository, the import process has been cancelled.
Cause: Work repository was not declared in this master repository.
Action: Declare work repository and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10016: Import aborted.
Cause: Import was aborted.
Action: Check objects and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10017: This import is forbidden: the text {0} has a different origin in the repository and in the import file.
Cause: The text has a different origin in the repository and in the import file.
Action: Check import file and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10018: The repository {0} is not coherent between the current repository and the import file.
Cause: The repository was not coherent between the current repository and the import file.
Action: Check import file.

Level: 32

Type: ERROR

Impact: Other

ODI-10019: Impossible to create the directory {0}.
Cause: I was not possible to create the directory.
Action: Check your system rigth for creating directory; directory's path and name.

Level: 32

Type: ERROR

Impact: File

ODI-10020: Impossible to replace the file
Cause: It was not possible to replace the file.
Action: Check, if you have enough rigths for this operation.

Level: 32

Type: ERROR

Impact: File

ODI-10021: Unspecified save directory.
Cause: Directory to save environment information was unspecified.
Action: Specify the directory for saving the environment information file.

Level: 32

Type: ERROR

Impact: Other

ODI-10022: You must specify all options.
Cause: Missed one or more options.
Action: Specify missed options.

Level: 32

Type: ERROR

Impact: Other

ODI-10023: Invalid license. This license is suitable for {0}.
Cause: Invalid license.
Action: Check license.

Level: 32

Type: ERROR

Impact: Security

ODI-10024: Your installation of Oracle Data Integrator is corrupted.
Cause: The technology description file contains errors.
Action: Reinstall Oracle Data Integrator.

Level: 32

Type: ERROR

Impact: Other

ODI-10025: Your installation of Oracle Data Integrator is corrupted.
Cause: The technology description file is missing.
Action: Reinstall Oracle Data Integrator.

Level: 32

Type: ERROR

Impact: Other

ODI-10026: Error while testing the Master Repository technology.
Cause: Error occurred while testing the Master Repository technology.
Action: Check parameters.

Level: 32

Type: ERROR

Impact: Other

ODI-10027: The import is cancelled because at least one object is locked by another user.
Cause: At least one object was locked by another user.
Action: Check objects' locks.

Level: 32

Type: ERROR

Impact: Other

ODI-10028: It is forbidden to import a log into a repository having the same ID.
Cause: The log had the same ID as repository.
Action: Check log and/or repository id.

Level: 32

Type: ERROR

Impact: Other

ODI-10029: Version {0} for object {1} already exists.
Cause: Version already existed.
Action: Choose another version.

Level: 32

Type: ERROR

Impact: Other

ODI-10031: Object {0}: {1} is locked by user {2}
Cause: Object was locked by another user.
Action: Wait until object is unlocked.

Level: 32

Type: ERROR

Impact: Other

ODI-10032: You cannot import this object ({0}). A referenced object ({1}) does not exist in the repository.
Cause: A referenced object does not exist in the repository.
Action: Check import file.

Level: 32

Type: ERROR

Impact: Other

ODI-10033: You cannot delete this object because it is locked by another user ({0}).
Cause: This object was locked by another user.
Action: Wait until object is unlocked.

Level: 32

Type: ERROR

Impact: Other

ODI-10034: The technology hosting your master repository does not support Versioning.
Cause: The technology did not support versioning.
Action: Choose another repository or technology.

Level: 32

Type: ERROR

Impact: Other

ODI-10035: {0} : {1} violates alternate key constraint {2} {3} for values {4}
Cause: Object violated alternate key constraint.
Action: Check object properties and constraint's values.

Level: 32

Type: ERROR

Impact: Other

ODI-10036: Importing object {0} : {1} failed.
Cause: Import failed.
Action: Check import file and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10037: Import-replace for this node is supported for action groups only. The import file is invalid.
Cause: Import-replace for this node was supported for action groups only.
Action: Check import file.

Level: 32

Type: ERROR

Impact: Other

ODI-10038: The interface you are trying to use ({0}) is related to a logical schema ({1}) that no longer exists.
Cause: Logical schema was not found.
Action: Check interface.

Level: 32

Type: ERROR

Impact: Other

ODI-10040: Cannot create directory
Cause: Directory could not be created.
Action: Check directory path/name.

Level: 32

Type: ERROR

Impact: File

ODI-10044: Unable to save the interface. Maximum number of source datastores exceeded.
Cause: Maximum number of source datastores was exceeded.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-10045: a2.getCargo() not instance of SAPSegment
Cause: a2.getCargo() not instance of SAPSegment
Action: Check SAP Tree.

Level: 32

Type: ERROR

Impact: Other

ODI-10046: No IDoc.
Cause: Missed IDoc.
Action: Check IDoc.

Level: 32

Type: ERROR

Impact: Other

ODI-10047: Repository is not a development work repository
Cause: Repository was not a development work repository.
Action: Choose development work repository.

Level: 32

Type: ERROR

Impact: Other

ODI-10048: No work repository found.
Cause: No work repository was found.
Action: Check your connection settings or database.

Level: 32

Type: ERROR

Impact: Other

ODI-10049: Missing parameter
Cause: Parameter was missing.
Action: Check all parameters.

Level: 32

Type: ERROR

Impact: Other

ODI-10050: Missing parameter at: {0} SQL: {1}
Cause: Parameter was missing.
Action: Check all parameters.

Level: 32

Type: ERROR

Impact: Other

ODI-10051: Some objects cannot be exported because they do not exist in the repository: {0} {1}
Cause: Objects did not exist in the repository.
Action: Check objects state.

Level: 32

Type: ERROR

Impact: Other

ODI-10052: A problem occurred in your repository.
Cause: A problem occurred in your repository.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-10053: Problem retrieving JCOFunction object. {0}
Cause: Problem occurred retrieving JCOFunction object.
Action: Check JCO Function object.

Level: 32

Type: ERROR

Impact: Other

ODI-10054: Unable to find the XML file corresponding to your technology.
Cause: XML file corresponding to your technology was not found.
Action: Check technology and/or XML file for the technology.

Level: 32

Type: ERROR

Impact: Other

ODI-10055: This ID is already in use in the repository
Cause: This ID was already in use in the repository.
Action: Change ID.

Level: 32

Type: ERROR

Impact: Other

ODI-10056: This repository ID already exists. This repository cannot be created.
Cause: Repository ID already existed.
Action: Change repository ID.

Level: 32

Type: ERROR

Impact: Other

ODI-10057: Unrecognized export type.
Cause: Export type was unrecognized.
Action: Check export type.

Level: 32

Type: ERROR

Impact: Other

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.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-10059: Repository is null
Cause: Repository was null.
Action: Check repository.

Level: 32

Type: ERROR

Impact: Other

ODI-10060: Saputil is mandatory.
Cause: Saputil was mandatory.
Action: Check Saputil

Level: 32

Type: ERROR

Impact: Other

ODI-10061: Empty XML Character Set
Cause: XML Character Set was empty.
Action: Fill XML Character Set.

Level: 32

Type: ERROR

Impact: Other

ODI-10062: Unable to find license key {0}. An exception {1} occurred with message: {2}
Cause: An exception occurred.
Action: Check license key.

Level: 32

Type: ERROR

Impact: Other

ODI-10063: Unable to check the license key. An exception {0} occurred with message: {1}
Cause: An exception occurred.
Action: Check license key.

Level: 32

Type: ERROR

Impact: Other

ODI-10064: The interface must have a JMS datastore as a source or target. Another license is required otherwise.
Cause: The interface must have a JMS datastore as a source or target.
Action: Check datastore type and/or license.

Level: 32

Type: ERROR

Impact: Other

ODI-10065: You license does not include these features. Please contact your reseller.
Cause: You license does not include these features.
Action: Please contact your reseller.

Level: 32

Type: ERROR

Impact: Other

ODI-10066: The interface is using a Datastore defined in Model "{0}" which is linked to a logical schema "{1}" that no longer exists.
Cause: Logical schema was not found.
Action: Correct interface.

Level: 32

Type: ERROR

Impact: Other

ODI-10067: Target file already exists.
Cause: Target file already existed.
Action: Choose another target file name.

Level: 32

Type: ERROR

Impact: File

ODI-10068: SnpsConnection: Isolation level not supported
Cause: Isolation level not supported.
Action: Check isolation level.

Level: 32

Type: ERROR

Impact: Other

ODI-10069: Unsupported XML Character Set: {0}
Cause: Unsupported XML Character Set.
Action: Check XML charset.

Level: 32

Type: ERROR

Impact: Other

ODI-10070: Cannot delete this object. It is being edited or viewed
Cause: Object was being edited or viewed.
Action: Stop edit or view object and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10071: Cannot delete this object
Cause: Could not delete this object.
Action: Check object state.

Level: 32

Type: ERROR

Impact: Other

ODI-10073: A repository already exists on this data server
Cause: A repository already existed on this data server.
Action: Choose another data server.

Level: 32

Type: ERROR

Impact: Other

ODI-10080: Incorrect License ....
Cause: Incorrect License.
Action: Contact your seller.

Level: 32

Type: ERROR

Impact: Other

ODI-10081: You are not authorized to Insert the Object: {0}: {1} / {2}
Cause: You were not authorized to Insert the Object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10082: You are not authorized to View the Object: {0}: {1}
Cause: You were not authorized to View the Object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10083: You are not authorized to Delete the Object: {0}: {1} / {2}
Cause: You were not authorized to Delete the Object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10084: You are not authorized to Edit the Object: {0}: {1} / {2}
Cause: You were not authorized to Edit the Object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10085: You cannot consult this object
Cause: You could not consult this object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10086: You cannot edit this object
Cause: You could not edit this object.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10087: You can only give Supervisor Access Privileges if you are a Supervisor.
Cause: You could only give Supervisor Access Privileges if you are a Supervisor.
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10088: Empty Java Character Set.
Cause: Java Character Set was empty.
Action: Fill Java charset.

Level: 32

Type: ERROR

Impact: Other

ODI-10089: You cannot modify another user''s password
Cause: You cannot modify another user''s password
Action: Login with user with right privileges.

Level: 32

Type: ERROR

Impact: Security

ODI-10090: Object {0} {1} is referenced by: {2}. Cannot remove.
Cause: Object was referenced by another one.
Action: Check object''s references.

Level: 32

Type: ERROR

Impact: Other

ODI-10092: Some objects cannot be exported. They do not exist in the repository.
Cause: Objects did not exist in the repository.
Action: Check objects'' state.

Level: 32

Type: ERROR

Impact: Other

ODI-10093: You are importing an object from another repository with the same identifier. It is forbidden.
Cause: You tried to import an object from another repository with the same identifier.
Action: Change repository ID.

Level: 32

Type: ERROR

Impact: Other

ODI-10094: Problem while computing new name.
Cause: A problem occurred while computing new name.
Action: Try again.

Level: 32

Type: ERROR

Impact: Other

ODI-10098: No connection available. Check connection parameters.
Cause: No connection was available.
Action: Check connection parameters.

Level: 32

Type: ERROR

Impact: Network

ODI-10099: Object cannot be exported because the file with name {0} could not be created.
Cause: Object could not be exported because the file could not be created.
Action: Check your system rights to write files and file name.

Level: 32

Type: ERROR

Impact: Other

ODI-10100: Empty XML Version
Cause: XML version was empty.
Action: Fill XML Version.

Level: 32

Type: ERROR

Impact: Other

ODI-10101: Invalid XML Version: {0}
Cause: XML Version was invalid.
Action: Check XML version.

Level: 32

Type: ERROR

Impact: Other

ODI-10102: Alias with the name '{0}' already exists.
Cause: Alias already exists.
Action: Change alias.

Level: 32

Type: ERROR

Impact: Other

ODI-10103: Alias with the name '{0}' does not exist.
Cause: Alias doesn't exit.
Action: Check alias name ant try again.

Level: 32

Type: Error

Impact: Other

ODI-10104: File {0} is not a Smart Export file and cannot be imported by Smart Import.
Cause: Smart Export file not specified for Smart Import.
Action: Specify a Smart Export file for importing via Smart Import.

Level: 32

Type: ERROR

Impact: Other

ODI-10105: Smart Import file name cannot be null.
Cause: Smart Export file name not specified for Smart Import.
Action: Specify a Smart Export file for importing via Smart Import.

Level: 32

Type: ERROR

Impact: Other

ODI-10106: Smart Import response file name cannot be null.
Cause: Smart import response file name not specified for Smart Import.
Action: Specify a Smart Import response file.

Level: 32

Type: ERROR

Impact: Other

ODI-10107: Smart Import file {0} not found.
Cause: File does not exist.
Action: Specify an existing Smart Export file for importing via Smart Import.

Level: 32

Type: ERROR

Impact: Other

ODI-10108: Smart Import response file {0} not found.
Cause: Response file does not exist.
Action: Specify an existing Smart Import response file.

Level: 32

Type: ERROR

Impact: Other

ODI-10109: File {0} is not a valid Smart Import Response file.
Cause: File is not a valid Smart Import response.
Action: Specify an existing Smart Import response file.

Level: 32

Type: ERROR

Impact: Other

ODI-10110: {0} with the same {1} exists.
Cause: An object with the same alternative key value(s) exists.
Action: Change the alternative key value to be unique.

Level: 32

Type: ERROR

Impact: Other

ODI-10111: Referenced {0} is missing.
Cause: A referenced object does not exist.
Action: Either import the missing object or change to reference a different object.

Level: 32

Type: WARNING

Impact: Other

ODI-10112: Project code will be changed from <{0}> to <{1}>.
Cause: The import will make a change to an existing project code.
Action: Determine whether the change to project code is desired or not.

Level: 32

Type: WARNING

Impact: Other

ODI-10113: {0} with {1} <{2}> does not exist.
Cause: A referenced object does not exist.
Action: Either import the missing object or change to reference a different object.

Level: 32

Type: WARNING

Impact: Other

ODI-10114: {0} with {1} id <{2}> does not exist.
Cause: A referenced object does not exist.
Action: Either import the missing object or change to reference a different object.

Level: 32

Type: WARNING

Impact: Other

ODI-10115: {0} with the same name <{1}> already exists.
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.

Level: 32

Type: WARNING

Impact: Other

ODI-10116: Model code will be changed from <{0}> to <{1}>.
Cause: The import will make a change to an existing model code.
Action: Determine whether the change to model code is desired or not.

Level: 32

Type: WARNING

Impact: Other

ODI-10117: Sub-model code will be changed from <{0}> to <{1}>.
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.

Level: 32

Type: WARNING

Impact: Other

ODI-10120: Context code will be changed from <{0}> to <{1}>.
Cause: The import will make a change to an existing context code.
Action: Determine whether the change to context code is desired or not.

Level: 32

Type: WARNING

Impact: Other

ODI-10121: Logical schema name will be changed from <{0}> to <{1}>.
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.

Level: 32

Type: WARNING

Impact: Other

ODI-10122: Logical agent name will be changed from <{0}> to <{1}>.
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.

Level: 32

Type: WARNING

Impact: Other

ODI-10123: {0} with {1} <{2}> and {3} <{4}> does not exist.
Cause: A referenced object does not exist.
Action: Either import the missing object or change to reference a different object.

Level: 32

Type: WARNING

Impact: Other

ODI-10124: Smart import of file {0} cannot be run due to unfixed critical issues.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-10125: Smart Export file name cannot be null.
Cause: Smart Export file name not specified for Smart Export.
Action: Specify a Smart Export file via Smart Export.

Level: 32

Type: ERROR

Impact: Other

ODI-10126: File {0} already exists.
Cause: The file already exists.
Action: Specify another file name.

Level: 32

Type: ERROR

Impact: Other

ODI-10127: Column position {0} is being used by another object <{1}>.
Cause: The position value is already in use.
Action: Specify a unique position value.

Level: 32

Type: ERROR

Impact: Other

ODI-10128: Multiple primary keys found. Only one primary key can be defined per datastore.
Cause: Multiple primary keys defined.
Action: Delete or match primary keys so that only one is defined.

Level: 32

Type: ERROR

Impact: Other

ODI-10129: Object with id {0} and type {1} is not a smart exportable object.
Cause: Smart Export does not support the type of object specified.
Action: Do not export this object.

Level: 32

Type: ERROR

Impact: Other

ODI-10130: Smart Import Response file {0} is not valid for Smart Export file {1}.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-10131: Entity of type {0} cannot be merged.
Cause: Wrong entity type.
Action: Check entity type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10132: Entity of type {0} cannot be removed.
Cause: Wrong entity type.
Action: Check entity type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10133: Cannot create a transaction against the extended persistent context [{0}].
Cause: Another persistence context is already bound to the current thread.
Action: Unbound persistence context from current thread.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10134: You don't have READ permission on at least one object from the collection/list.
Cause: Insufficient level of permissions.
Action: Check your permissions

Level: 32

Type: ERROR

Impact: Security

ODI-10135: Max value ({1}) reached for sequence {0} and reset is not allowed.
Cause: Reset is not allowed.
Action: Check configuration of sequence behaviour.

Level: 32

Type: ERROR

Impact: Other

ODI-10136: Illegal transaction state: transaction synchronization is active but entity manager is not synchronized within the transaction.
Cause: Entity manager is not synchronized within the transaction.
Action: Syncronize entity manager and try again.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10137: Your program needs to set authentication first.
Cause: There is no authentication set.
Action: Set authentication via odiInstance.getSecurityManager().setGlobalAuthentication(.) or odiInstance.getSecurityManager().setCurrentThreadAuthentication(.), see the SecurityManager API for more detail.

Level: 32

Type: ERROR

Impact: Security

ODI-10138: Unable to create DwgConnectConnection to {0} repository.
Cause: Exception during connection.
Action: Check repository configuration.

Level: 32

Type: ERROR

Impact: Other

ODI-10139: {0} must not be null or empty.
Cause: Parameter is null or empty.
Action: Check parameter name.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10140: {0} must be greater or equal 0.
Cause: Parameter is negative.
Action: Check parameter value.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10141: Unable to create datasource provider from class [{0}].
Cause: Exception during creation.
Action: Check configuration.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10142: Active transaction is required to use the method {0} on the TransactionalOdiEntityManager.
Cause: Transaction isn't active.
Action: Check transaction state.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10143: Error while accessing the {0} repository.
Cause: Network problems.
Action: Check the network connection and the database status.

Level: 32

Type: ERROR

Impact: Network

ODI-10144: OdiInstance is closed.
Cause: OdiInstance is closed.
Action: Check OdiInstance status.

Level: 32

Type: ERROR

Impact: Other

ODI-10145: Limited persistence support.
Cause: Limited persistence support.
Action: Check OdiInstance configuration.

Level: 32

Type: ERROR

Impact: Other

ODI-10146: Cannot create JDBC DataSource for this type of DataServer.
Cause: Invalid connection provider.
Action: Check connection provider.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10147: Repository type mismatches.
Cause: Wrong repository type.
Action: Check repository type.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10148: Repository status isn't OK.
Cause: Repository status isn't OK.
Action: Check install state of repository.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10149: Local Repository table is empty.
Cause: Local Repository table is empty.
Action: Check repository configuration.

Level: 32

Type: ERROR

Impact: 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}.
Cause: Work repository with ID is not bound to master repository.
Action: Check work and master repositories configuration.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10151: Unable to get ID for entity {0}.
Cause: Wrong entity ID.
Action: Check entity properties.

Level: 32

Type: ERROR

Impact: Security

ODI-10152: I_OBJECTS for entity class {0} is not found.
Cause: Entity type is not mapped to I_OBJECTS.
Action: Check entity class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10153: {0} is denied.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10154: {0} is denied for {1}.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10155: You don't have {0} permission on at least one object from the collection/list.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10156: Impossible to connect to JPS MBean Server.
Cause: Exception during connection.
Action: Check configuration.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10157: {0}: must call preWebLogic() before postWebLogic().
Cause: Wrong API usage.
Action: Call preWebLogic() before postWebLogic().

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10158: The credential with map name {0} and key {1} already exists.
Cause: Wrong credential.
Action: Check credential configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10159: The user {0} hasn't required CONNECT profile.
Cause: The user hasn't required profile.
Action: Grant the user CONNECT profile first.

Level: 32

Type: ERROR

Impact: Security

ODI-10160: Unable to load user.
Cause: Exception during user loading.
Action: Check repository connection.

Level: 32

Type: ERROR

Impact: Other

ODI-10162: This OPSS user '{0}' is not registered to Oracle Data Integrator.
Cause: The user is not registered to ODI.
Action: Check user name.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10163: This OPSS user '{0}' has different GUID than the one found in Oracle Data Integrator repository.
Cause: OPSS user differs from ODI user in GUID.
Action: Check user GUID.

Level: 32

Type: ERROR

Impact: Security

ODI-10164: Only supervisor user can invoke this API.
Cause: Insufficient level of permissions.
Action: Check user role.

Level: 32

Type: ERROR

Impact: Security

ODI-10165: The RunAsUser {0} is not a valid user from external user identity store.
Cause: User isn't valid.
Action: Check user.

Level: 32

Type: ERROR

Impact: Security

ODI-10166: The RunAsUser: {0} has different GUID in ODI repository and external user identity store.
Cause: User from external user identity store differs from ODI user in GUID.
Action: Check user.

Level: 32

Type: ERROR

Impact: Security

ODI-10167: Authentication is missing.
Cause: Authentication is missing.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Security

ODI-10168: There is already an Authentication bound to this thread.
Cause: There is already an Authentication bound to this thread.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10169: Trying to set authentication object which is not created by this security manager.
Cause: Authentication object isn't created by this security manager.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10170: There is currently no Authentication bound to this thread.
Cause: There is currently no Authentication bound to this thread.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Security

ODI-10171: There is already an Authentication bound as global Authentication.
Cause: There is already an Authentication bound as global Authentication.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10172: There is currently no global Authentication bound to this SecurityManager.
Cause: There is currently no global Authentication bound to this SecurityManager.
Action: Check authentication configuration.

Level: 32

Type: ERROR

Impact: Security

ODI-10173: You are not authorized to change the password for external user '{0}'.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10174: You are not authorized to change the password for user '{0}'.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10175: You are not authorized to change the password for external user.
Cause: Insufficient level of permissions.
Action: Check permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10176: Authentication is needed to change password.
Cause: Authentication is missed.
Action: Authenticate first.

Level: 32

Type: ERROR

Impact: Security

ODI-10177: ODI was not able to load the jdbc driver class "{0}" provided on {1}.
Cause: Wrong jdbc driver class.
Action: Check that the driver class name is correct and that this driver is available to ODI classloader.

Level: 32

Type: ERROR

Impact: Other

ODI-10178: The jdbc URL "{0}" was not accepted by the jdbc driver class "{1}" provided on {3}.
Cause: Insufficient jdbc URL.
Action: Check that the jdbc URL and the driver class name are matching.

Level: 32

Type: ERROR

Impact: Other

ODI-10179: Client requires a repository with version {0} but the repository version found is {1}.
Cause: Isufficient repository version.
Action: Check repository configuration.

Level: 32

Type: ERROR

Impact: Other

ODI-10180: ODI was not able to load the jdbc driver class {0} specified in ODI topology for work repository {1}.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-10181: Uncategorized configuration exception.
Cause: An unexpected error occurred.
Action: Check exception cause for details.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10182: Uncategorized exception during repository access.
Cause: An unexpected error occurred.
Action: Check exception cause for details.

Level: 32

Type: ERROR

Impact: Other

ODI-10183: {0} is an invalid finder class.
Cause: Wrong finder class.
Action: Check finder class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10184: Could not get ESS {0}.
Cause: Exception during session retrieving.
Action: Check configuration and try again.

Level: 32

Type: ERROR

Impact: Session

ODI-10185: Operation is not granted.
Cause: Current level of permission is not sufficient.
Action: Check your permissions.

Level: 32

Type: ERROR

Impact: Security

ODI-10186: User {0} is inactive.
Cause: There is no GUID defined for this User in ODI repository
Action: Check user GUID.

Level: 32

Type: ERROR

Impact: Security

ODI-10187: The authentication API is used in wrong way.
Cause: The authentication API is used in wrong way.
Action: Check usage of API.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10188: Error while login from OPSS.
Cause: Exception was thrown during login process.
Action: Make sure OPSS is configured correctly for this installation.

Level: 32

Type: ERROR

Impact: Other

ODI-10189: Password policy {0} is not matched.
Cause: Week password.
Action: Check password policy and correct password.

Level: 32

Type: ERROR

Impact: Security

ODI-10190: The user {0} has its account expired.
Cause: Account expired
Action: Request supervisor for account unlocking.

Level: 32

Type: ERROR

Impact: Security

ODI-10191: Unable to create datasource provider.
Cause: Exception during creation.
Action: Check configuration.

Level: 32

Type: ERROR

Impact: Configuration

ODI-10192: Unable to retrieve user GUID.
Cause: Exception during GUID retrieving.
Action: Check repository connection.

Level: 32

Type: ERROR

Impact: Other

ODI-10193: Unexpected null value in port.
Cause: JPS port value is null.
Action: Check JPS configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10194: Uncategorized security exception.
Cause: An unexpected error occurred.
Action: Check exception cause for details.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10195: CsfAccessor is only available for CsfPasswordStorageConfiguration
Cause: Password storage configuration is internal.
Action: Check storage configuration.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10196: Error while accessing the repository.
Cause: Network problems.
Action: Check the network connection and the database status.

Level: 32

Type: ERROR

Impact: Network

ODI-10197: Instance is not connected to a work repository
Cause: Work datasource is null.
Action: Check work datasource.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10198: Context with code '{0}' wasn't found.
Cause: Context wasn't found.
Action: Check context code.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10199: Incorrect ODI username or password.
Cause: Incorrect ODI username or password.
Action: Check username nad password.

Level: 32

Type: ERROR

Impact: Security

ODI-10200: Work repository {0} wasn't found.
Cause: Wrong repository name or repository isn't defined.
Action: Check repository name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10201: The user {0} has its password expired.
Cause: Account expired
Action: Request supervisor for changing password.

Level: 32

Type: ERROR

Impact: Security

ODI-10202: Supervisor privilege is required to setup repository.
Cause: Insufficient level of permissions.
Action: User supervisor account for this operation.

Level: 32

Type: ERROR

Impact: Security

ODI-10203: Transaction state is illegal.
Cause: Transaction state is illegal.
Action: Check transaction state.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10204: Inappropriate usage of a ODI transaction API.
Cause: Inappropriate usage of a ODI transaction API.
Action: Check ODI transaction API.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10205: Unexpected rollback.
Cause: Attempt to commit a transaction resulted in an unexpected rollback.
Action: Check transaction.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10206: Transaction can't be created.
Cause: Exception was thrown during transaction creation.
Action: Check transaction.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10207: Uncategorized exception during transaction system usage.
Cause: An unexpected error occurred.
Action: Check exception cause for details.

Level: 32

Type: ERROR

Impact: Other

ODI-10208: Error when changing password for user {0}.
Cause: An unexpected error occurred.
Action: Check exception cause for details.

Level: 32

Type: ERROR

Impact: Other

ODI-10209: Cannot access a closed IOdiEntityManager.
Cause: IOdiEntityManager has been closed.
Action: Check IOdiEntityManager state.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-10210: File {0} does not contain any objects to be imported by Smart Import.
Cause: Smart Export file specified for Smart Import is empty.
Action: Specify a Smart Export file with objects for importing via Smart Import.

Level: 32

Type: ERROR

Impact: Other

ODI-14064: Error while applying DDL from file {0}
Cause: Exception during execution of session.
Action: Check session.

Level: 32

Type: ERROR

Impact: Other

ODI-14066: upgrade error while executing {0} params = {1}
Cause: Wrong parameters at Sql query.
Action: Check parameters.

Level: 32

Type: ERROR

Impact: Upgrade

ODI-14070: Import failed. The parent object was not found in the repository.
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

Level: 32

Type: ERROR

Impact: Other

ODI-15000: BSF Not Present
Cause: Bean Scripting Framework manager cannot be found.
Action: Ensure that class org.apache.bsf.BSFManager is available in the classpath.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15001: No End Separator for the following text:
Cause: No end delimiter found for a delimited text in the expression.
Action: Add an end delimiter to the delimited text.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15002: The string to be transformed cannot be null.
Cause: Parsing failed for an expression reference tag.
Action: Fix the expression.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15003: Error during Code Interpretor creation
Cause: Code generator internal error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15005: The datatype source: {0} for the technology: {1} does not exist.
Cause: The datatype for a column is not supported by the technology.
Action: Change the datatype or the technology of the execution location.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15006: The source datatype is null for the column: {0}, and the technology: {1}
Cause: The datatype for a column is null for the technology.
Action: Change the datatype or the technology of the execution location.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15007: Syntax not set for 'Create Table' for the datatype: {0} for the technology: {1}.
Cause: The execution location technology does not have any "Create Table" syntax set up.
Action: Edit the technology definition and add "Create Table" syntax.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15009: No text for the 'Writable Datatype Syntax' for the datatype: {0} in technology: {1}
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".

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15010: No conversion for the datatype {0}, for the source technology {1} and for the target technology {2}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15011: The variable does not exist in the database.
Cause: A variable is being referenced but it does not exist in the repository.
Action: Create the variable in the repository.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15012: Sequence does not exist in database
Cause: A sequence is referenced but does not exist in the repository.
Action: Create the sequence in the repository.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15013: The table {0} has fatal errors.
Cause: The table cannot be processed.
Action: Check the table for inconsistencies.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15014: The referenced text does not exist in the database.
Cause: The text reference in the expression does not exist in the repository.
Action: Repository corruption has occurred, contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15015: Too much recursion in this text resolution.
Cause: The expression text references other text recursively too many times.
Action: Review the expression and try to simplify.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15016: Commands Undefined.
Cause: KM is missing a block of lines.
Action: Check the KM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15017: Table not selected (null).
Cause: Target table not found.
Action: Check interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15018: CKM not selected.
Cause: The CKM is not selected for the object.
Action: Select a CKM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15019: Missing context
Cause: The context object cannot be found.
Action: Check the context selection.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15020: No JKM available
Cause: JKM has not been set or is not found.
Action: Set a valid JKM for the interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15021: Journalizing requires a Primary Key on the Table:
Cause: Journalizing is enabled, but the target table has no primary key.
Action: Add a primary key to the target table.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15022: No RKM Set.
Cause: RKM has not been set or is not found.
Action: Set a valid RKM for the object.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15023: Cannot perform standard reverse. Choose customized reverse and set RKM.
Cause: Standard reverse engineering is not supported for this object.
Action: Select customized reverse engineering for the object and select an RKM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15025: The interface clause text does not exist.
Cause: The interface clause refers to text that does not exist.
Action: Check interface clauses for (join, filter, etc.) for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15026: Interface clauses are missing.
Cause: the code generator cannot find the clause collection for the interface.
Action: Check the interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15027: Interface source tables are missing.
Cause: the code generator cannot find the source table collection for the interface.
Action: Check the interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15028: Interface result collection is null.
Cause: Internal error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15029: Interface error clause collection is missing.
Cause: Internal error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15030: Interface is missing the integration work table collection.
Cause: Internal error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15031: Technology not selected.
Cause: No technology is selected for the interface target execution location.
Action: Check the technology selection for the interface target.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15032: Unknown object in interface source table collection
Cause: Internal Error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15033: The expression: {0} does not have an associated column.
Cause: The expression should represent a column, but no column is found for the name.
Action: Fix the expression.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15034: A scenario with the same name and the same number already exists. Please select other values.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15036: Scenario''s name and/or number are missing.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15037: The interface {0} has fatal errors.
Cause: The interface has fatal errors.
Action: Check and fix interface issues.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15038: The scenario name substitution pattern {0} is not supported. Please check the user parameter for the scenario naming convention.
Cause: Invalid substitution pattern used for scenario name.
Action: Change the substitution pattern.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15039: The interface {0} use native sequence. Native sequence are not allowed for Derived Table (sub select statement)
Cause: Native sequence was used in a sub-select or derived interface.
Action: Remove the native sequence usage.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15040: Errors detected when building SQL clauses.
Cause: An error occurred when generating code for the SQL clauses.
Action: Fix the interface clauses.

Level: 32

Type: ERROR

Impact: Programmatic

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.
Cause: An aggregation function was used inside a join condition expression.
Action: Change the join condition to remove the aggregation function.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15042: Unable to regenerate this scenario. It references an package that does not exist.
Cause: The scenario must reference a package, but it does not.
Action: Delete the scenario and create a new one.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15043: Unable to regenerate this scenario from a Runtime repository.
Cause: The scenario must cannot be regenerated from the runtime repository.
Action: Delete the scenario and create a new one.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15044: Invalid pScenSource type when calling SnpGeneratorSQLCIT.mainGenScenSourceScenario
Cause: Internal error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15045: Invalid value for KM type.
Cause: An invalid value was specified for the KM type.
Action: Specify a valid value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15046: The column cache is null during code generation.
Cause: Internal Error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15047: The cached column is null in the column cache during code generation.
Cause: Internal Error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15050: Flow Control not possible if no key is declared in your target datastore
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15051: Missing mapping instance for interface.
Cause: The target column does not have any mapping.
Action: Add a mapping expression for the target column.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15052: The interface is missing a dataset.
Cause: There is no dataset for the interface source.
Action: Check the interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15055: Character '']'' missing in: {0}.
Cause: A bracketed tag inside a KM line is missing a closing bracket ("]") character.
Action: Fix the KM line.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15057: Non-ordered outer join not supported for technology.
Cause: Non-ordered outer join syntax disabled for technology.
Action: Correct join.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15058: Variable scenario generation error: Logical schema is required.
Cause: Variable scenario cannot be generated if logical schema is not set.
Action: Set the logical schema.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15059: I_TXT is mandatory.
Cause: A call was made to SnpTxtCachedHashMap.getInstance, but the pITxt parameter was null.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15060: The JKM line {0} uses an unsupported execution channel: {1}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15061: The JKM line {0} uses an unsupported commit type: {1}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15062: Invalid commit type: {0}
Cause: An invalid commit type was passed to SnpServiceGenerator.convertCommitType
Action: Contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15063: The alternate key {0} is not unique.
Cause: An alternate key defined by the repository is found to be non-unique.
Action: Check the data or the alternate key definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15064: The primary key {0} is not unique.
Cause: A primary key defined by the repository is found to be non-unique.
Action: Check the data or primary key definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15065: Join error ({0}) between the table {1} and the table {2}.
Cause: A foreign key relationship is not found.
Action: A foreign key relationship between 2 tables defined in the repository is not valid.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15066: The column {0} cannot be null.
Cause: The column is marked in the repository as not nullable.
Action: Check the data, or change the not null value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15067: The datatype value ''{0}'' is incorrect.
Cause: An invalid datatype has been found.
Action: The repository table contains an invalid datatype.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15068: Unknown flexfield code.
Cause: An undefined flex field code is being referenced
Action: Check the flex field references in the KM, and the flex field definitions

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15069: {0} Is not valid without session context.
Cause: A current session context does not exist.
Action: Check session definition.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15070: Unable to find method object: PythonInterpreter.initialize(Properties, Properties, String[]) method
Cause: The python method used by the script is not found.
Action: Check the KM step.

Level: 32

Type: ERROR

Impact: Other

ODI-15071: Error occurred
Cause: An exception was thrown while executing a python script in the KM step.
Action: Check the cause.

Level: 32

Type: ERROR

Impact: Other

ODI-15072: There is no PK constraint
Cause: There is a call to "getPK" in the KM, but no PK is found.
Action: Check the KM and the PK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15073: There is no index
Cause: There is a call to "getIndex" in the KM, but no index is found.
Action: Check the KM and the index definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15076: no dataset
Cause: A KM line is calling "getDataSet", but no data set is found.
Action: Check the KM or the DataSet definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15077: No Current Model Set
Cause: There is a call to "getModel" in the KM, but no model is found.
Action: Check the KM and the model definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15078: There is no Not Null column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15079: There is no current Pop.
Cause: There is a call to "getPop" in the KM, but no interface is found.
Action: Check the KM and the interface definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15080: There is no Step
Cause: There is a call to "getStep" in the KM, but no step is found.
Action: Check the KM and the step definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15081: There is no Target Table
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15083: Multiple Primary Keys have been detected for {0} .
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15084: There is no session
Cause: There is a call to "getSession" in the KM, but no session is found.
Action: Check the KM and the session definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15085: The value : ''({0})'' is unknown.
Cause: A KM line has a templated call which contains an unknown bracketed property.
Action: Fix the KM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15086: There is no Temporary Index
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15087: There is no current execution context defined.
Cause: There is a call to "getContext" in the KM, but no context is found.
Action: Check the KM and the context definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15088: Not in designer mode
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15089: asked '({0})' and available value are between 0 and ({1}).
Cause: A KM line is calling "getDataSet", but the specified index is out of range.
Action: Fix the KM or the DataSet definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15090: Table "{0}" not found on model "{1}", schema "{2}"
Cause: Attempt to initialize data services from a table that cannot be found
Action: Change data services reference or make sure that table exists

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15091: Impossible to connect to JPS MBean Server
Cause: Cannot connect to JPS MBean server.
Action: Internal Error.

Level: 32

Type: ERROR

Impact: Other

ODI-15092: Unable to generate data service - the column {0} does not exist in the database.
Cause: A data service references a column that does not exist
Action: Fix the data service reference or make sure that the column exists

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15093: Unable to regenerate this scenario. It references a null package.
Cause: The scenario must reference a package, but the package is null.
Action: Delete the scenario and create a new one.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15094: You must give a name for the published entity for each datastore.
Cause: A web services data store does not have a name.
Action: Give the data store a name.

Level: 32

Type: ERROR

Impact: Other

ODI-15095: Invalid entity for datastore: {0}
Cause: A web services data store has an invalid entity.
Action: Associate the data store with a valid entity.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15096: Property name must not be null.
Cause: The KM line is calling "isColAttrChanged", but the property value is null.
Action: Internal error, contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15097: Unknown value {0} for property
Cause: The KM line is making a templated call, but the property value is unknown.
Action: Fix the KM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15098: You must define a data source for the model.
Cause: The model used by a web service does not have any data source.
Action: Define a data source for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15099: You must specify a JKM for the model.
Cause: The model used by a web service does not have an associated JKM.
Action: Define a JKM for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15100: You must define a Java package for the model.
Cause: The model used by a web service does not have an associated Java package.
Action: Define a Java package for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15101: Invalid Java package format: {0}
Cause: The Java package associated with a model has an invalid package format.
Action: Correct the package format for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15103: Invalid namespace: {0}
Cause: A model namespace used by a web service is invalid.
Action: Correct the namespace for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15104: You must specify an SKM for the model.
Cause: A model used by a web service does not have an associated SKM.
Action: Add an SKM to the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15105: You must specify which schema the model will be deployed to.
Cause: No web service deployment schema is specified for the model.
Action: Specify a schema to which the model will be deployed.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15106: You must specify a name for the Data Service for the model.
Cause: The data service for the model does not have a name.
Action: Set a valid name for the data service.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15107: Invalid model name: {0}. It should follow the Java identifiers naming conventions.
Cause: The web service model name does not follow the standard Java identifier naming convention.
Action: Set a valid name for the model.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15108: Invalid model Data Service name: {0}. It should follow the Java identifiers naming conventions.
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.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15109: Invalid web service name for datastore: {0}
Cause: The web service model data store has an invalid name.
Action: Set a valid name for the model data store.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15110: SKM is empty
Cause: The web service SKM has no valid lines.
Action: Add some lines to the SKM.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15111: Problem during deployment
Cause: Internal error.
Action: Contact Oracle support.

Level: 32

Type: SET_AT_RUNTIME

Impact: Deployment

ODI-15113: Reverse table {0} for model {1} already exists.
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.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

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.
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.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15117: Not allowed (OLD and NEW are involved)
Cause: The KM line is calling "getColumn", but the ADH action origin is not ''NEW'' or ''OLD''.
Action: Change the ADH action origin.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15118: Invalid FTP URL
Cause: The URL given for a web services FTP connection is not correct.
Action: Check the URL for the FTP connection.

Level: 32

Type: SET_AT_RUNTIME

Impact: Network

ODI-15119: Column {0} has no Java datatype.
Cause: The column being processed has no java datatype.
Action: Internal Error: contact Oracle support.

Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15120: Column {0} has no String datatype.
Cause: The column being processed has no string datatype.
Action: Internal Error: contact Oracle support.

Level: 32

Type: SET_AT_RUNTIME

Impact: Programmatic

ODI-15121: Selector must be not null
Cause: The ADH selector value must not be null when "getColumn" is called from the KM line.
Action: Change the ADH selector value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15122: Exception getPKColList
Cause: An exception was found when calling "getPKColList" during KM execution.
Action: Fix the KM or the PK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15123: There is no AK constraint
Cause: There is a call to "getAK" in the KM, but no AK is found.
Action: Check the KM and the AK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15125: Missing DataSet.
Cause: The interface is missing a dataset.
Action: Check interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15126: The sub-model must be set.
Cause: The sub-model is not set for the source or target.
Action: Check the interface for consistency.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15127: There is no CK constraint
Cause: There is a call to "getCK" in the KM, but no CK is found.
Action: Check the KM and the CK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15128: There is no FK constraint
Cause: There is a call to "getFK" in the KM, but no FK is found.
Action: Check the KM and the FK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15129: Selector value must be 'OLD' or 'NEW'
Cause: The ADH selector value must be 'OLD' or 'NEW' when "getColumn" is called from the KM line.
Action: Change the ADH selector value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15130: Unknown object in interface source table list
Cause: Internal Error.
Action: Contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15131: You must define the name of each web service to be generated for each datastore.
Cause: A web service associated with a data store has no name.
Action: Give a name to the web service.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-15132: Exception getPK
Cause: An exception was found when calling "getPK" during KM execution.
Action: Fix the KM or the PK definitions.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15135: There is no current index.
Cause: The current index can not be found for the property name.
Action: Check the reference.

Level: 32

Type: ERROR

Impact: Other

ODI-15140: Unable to regenerate the following scenario:
Cause: The scenario must reference a package, but it does not
Action: Delete the scenario and create a new one

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15141: Repository is not a development work repository
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

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15142: [PROPERTY: {0} not found.]
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15143: Invalid isolation level : {0}
Cause: An invalid isolation level value was passed to SnpServiceGenerator.convertIsolationLevel
Action: Contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15200: Tried to retrieve an int with an {0} object
Cause: Attempted to read the column from RDB as an integer, but the column type is not integer
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15201: Tried to retrieve a short with an {0} object
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

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15202: This resultset accepts only FETCHFORWARD requests
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

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15203: This function is unsupported: the software you are using might not be compatible with this driver.
Cause: A jdbc call was made that is not supported by the currently loaded jdbc driver for RDB
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15204: The {0} call is not implemented in this result set class.
Cause: A result set call was made that is not implemented by the ODI RDB result set class
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15205: The call is not supported in this result set class.
Cause: A result set call was made that is not supported by the ODI RDB result set class
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15207: Unmanaged numeric type {0}
Cause: When selecting a parent row based on a primary key, multiple rows were returned
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15208: The PK column of the root table has an unknown type: {0}
Cause: When unloading data from the RDB, the PK column of the parent table has an unknown type
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15209: Unsupported technology (Driver: {0}, Url: {1})
Cause: The jdbc driver is not supported by the ODI RDB
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15210: Unsupported technology: HSQL cannot create FKs after the tables have been created
Cause: The Hypersonic SQL engine cannot create FK after the table is already created
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15211: Unsupported technology: HSQL cannot create PKs after the tables have been created
Cause: The Hypersonic SQL engine cannot create PK after the table is already created
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15212: Datatype NULL (0) unsupported
Cause: The Hypersonic SQL engine does not support the null datatype
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15213: JDBC Datatype '{0}' unsupported
Cause: The Hypersonic SQL engine does not support the datatype
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15214: JDBC Datatype '{0}' with length parameter unsupported
Cause: The Hypersonic SQL engine does not support the datatype with length
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15215: JDBC Datatype '{0}' with length and scale parameters unsupported
Cause: The Hypersonic SQL engine does not support the datatype with scale
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15216: JDBC Datatype '{0}' unsupported
Cause: The internal MS Sql Server database does not support the datatype
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15217: JDBC Datatype '{0}' with length parameter unsupported
Cause: The internal MS SQL Server database does not support the datatype with length
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15218: JDBC Datatype '{0}' with length and scale parameters unsupported
Cause: The internal MS SQL Server database engine does not support the datatype with length and scale
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15219: Please transform your URL into: {0};SelectMethod=cursor
Cause: The internal MS SQL Server database engine does not recognize the supplied URL
Action: Change the format of the connection URL

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15220: need length param
Cause: The internal Oracle database does not support the selected type without a length param
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15221: Datatype NULL (0) unsupported
Cause: The internal Oracle SQL engine does not support the null datatype
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15222: JDBC Datatype '{0}' unsupported
Cause: The internal Oracle database does not support the datatype
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15223: JDBC Datatype '{0}' with length parameter unsupported
Cause: The internal Oracle database does not support the datatype with length
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15224: JDBC Datatype '{0}' with length and scale parameters unsupported
Cause: The internal Oracle database engine does not support the datatype with length and scale
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15225: No key found on table {0}
Cause: The internal database table does not have a key
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15226: The root table {0} has no data
Cause: The internal database table does not have any data
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15227: Multiple keys found on table {0}
Cause: The internal database table has multiple keys
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15228: *** FATAL *** Table {0} could not be validated
Cause: The internal database cannot validate the table
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15229: *** FATAL *** Table {0} could not be found
Cause: The internal database cannot find the table
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15230: Could not convert object {0} to a {1}
Cause: The internal database cannot convert the datatype of the selected column
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15231: No '=' sign found on line {0} of bundle {1}
Cause: The internal database engine encountered a syntax error when reading the property file
Action: Fix the property file

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15232: The alias {0} for table {1} is already used by another table, when reading bundle {2}
Cause: The internal database found a duplicate table alias in a property file
Action: Fix the property file

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15233: Table {0} is used twice. Make sure that the table names and aliases do not conflict.
Cause: The internal database found a duplicate table name in the property bundle
Action: Fix the property file

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15234: Internal RDB database table {0} not found
Cause: The requested table cannot be found in the internal database
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15235: Internal RDB database key {0} not found
Cause: The requested key cannot be found in the internal database
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15236: Unknown table {0}
Cause: The requested table cannot be found in the internal database
Action: Correct the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15237: Duplicate table
Cause: The internal database table is a duplicate table
Action: Correct the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15238: Could not find table although we should have created it!
Cause: The newly created table cannot be found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15239: Only SnpsRDBDiffActionImportDifference are supported for now.
Cause: When processing diff actions in a diff operation, an unsupported diff action class was found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15240: Unknown key {0}
Cause: When processing diff actions in a diff operation, a nonexistent key was specified by the diff action
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15241: This type of difference is not managed for now: {0}
Cause: When processing diff actions in a diff operation, an unsupported diff action class was found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15242: Unknown difference type: {0}
Cause: When processing diff actions in a diff operation, an unknown diff class was found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15243: Bad model number: {0}
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

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15244: Could not add a key because {0} is not an ID key.
Cause: When building a model, the specified key class instance was not an id key
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15246: Unknown key type: {0}
Cause: When building a model, an unknown key class was found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15247: The table {0} cannot be found. It is referenced by key: {1}.
Cause: When building a model, an table name is referenced by a key, but the table cannot be found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15248: The column {0} in table {1} cannot be found. It is referenced by key: {2}.
Cause: When building a model, an column name is referenced by a key, but the column cannot be found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15249: An {0} was caught while adding a key which is not an FK. Very strange.
Cause: When building a model, an column name is referenced by a key, but the column cannot be found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15250: The key {0} referenced by table {1} cannot be found.
Cause: When building a model, a key name is referenced by a table, but the key cannot be found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15251: A duplicate key was found: {0}
Cause: When dropping a model, a duplicate key was found in the model
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15252: Key already exists: {0}
Cause: When updating a model, a duplicate key was found in the model
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15253: Key not found: {0}
Cause: When updating a model, the key was not found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15254: Could not find a constructor with a key name for class {0}
Cause: When creating a key class instance, the constructor could not be found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15255: Could not instantiate an object of class {0}
Cause: Could not instantiate the key class
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15256: Could not create an object for class {0} for security reasons
Cause: Could not instantiate the key class, due to a security failure
Action: Check security settings

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15257: Could create an object for class {0} because a {1} occurred saying {2}
Cause: Could not instantiate the key class, due to an invocation target exception
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15258: Column {0} not found
Cause: The column could not be found
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15259: The key class {0} is not an ID key class.
Cause: The specified key class instance was not a SnpsRDBIdKey instance
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15260: Could not add column {0}: Unsupported datatype: {1}
Cause: Cannot add the column to the model because the datatype is not supported by the technology
Action: Correct the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15261: Unsupported action: {0}
Cause: The action class is not supported by the ODI RDB
Action: Internal Error: contact Oracle support

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15262: Cannot drop column {0}. It is used in a foreign key!
Cause: An attempt was made to drop a column that participates in a foreign key
Action: Drop the key first, then the column

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15263: Cannot drop column {0}. It is used in a primary key!
Cause: An attempt was made to drop a column that participates in a primary key
Action: Drop the key first, then the column

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15264: Cannot modify this column. It is used in a foreign key!
Cause: An attempt was made to modify a column that participates in a foreign key
Action: Drop the key first, then modify the column

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15265: Cannot modify this column. It is used in a primary key!
Cause: An attempt was made to modify a column that participates in a primary key
Action: Drop the key first, then modify the column

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15268: Table not found: {0}
Cause: When attempting to drop a table during an update, the table name is not found
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15270: Key type {0} is not supported here.
Cause: The key type is not supported
Action: Correct the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15272: An error occurred while executing a RDB command: {0}
Cause: When executing a command action, an exception was thrown
Action: Check root cause

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15273: {0}: action is not accepted: {1}
Cause: Attempt to execute a command action, but it is not accepted
Action: Check root cause

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15274: Multiple PKs are not allowed on a table
Cause: When reverse engineering a primary key, multiple primary keys were found for the table
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15275: An exception ocurred while retrieving a table primary key: {0}
Cause: When reverse engineering a table, a primary key could not be retrieved
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15276: An exception occurred while retrieving the indexes of a table: {0}
Cause: When reverse engineering a table, the indexes could not be retrieved
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15277: An exception ocurred while retrieving a table foreign keys: {0}
Cause: When reverse engineering a table, the foreign keys could not be retrieved
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15278: An exception occurred while retrieving the check constraints of a table: {0}
Cause: When reverse engineering a table, the check constraints could not be retrieved
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15279: An exception occurred while retrieving the alternate keys of a table: {0}
Cause: When reverse engineering a table, the alternate keys could not be retrieved
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15280: *** FATAL *** Table {0} is duplicate as root
Cause: The table is duplicated as the root when determining the root tables of the model
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15281: *** FATAL ** Table {0} is unknown
Cause: The root table is unknown
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15282: Table {0} is unknown though it was reversed
Cause: The table cannot be found in the ODI model, although it was reversed
Action: Retry the reverse engineering

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15283: Duplicate declaration for table {0}
Cause: The model XML contains a duplicate table declaration
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15285: FK {0} references a table with no PK.
Cause: The model XML contains a foreign key that references a table with no defined primary key
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15286: Unknown PK table for foreign key {0}: please check the name and order of the tables and FK.
Cause: The model XML contains a foreign key that references an unknown primary key table
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15287: Unknown element: {0}
Cause: The model XML contains an unknown element
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15288: An {0} error occurred with the following message: {1}
Cause: An error occurred when writing the model to a file
Action: See root cause

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15290: Column {0} was not found in table {1}
Cause: The column was not found when building the columns from column names
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15291: *** FATAL *** Could not rename table {0} to {1}
Cause: Could not rename table
Action: Check permissions and security settings

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15292: *** FATAL *** Could not rename table {0} because it was not found in the model!
Cause: Could not rename table, because the table to be renamed does not exist
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15293: Unknown FK table for foreign key {0}: please check the name and order of the tables and FK.
Cause: The model XML contains a foreign key that references an unknown table
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15294: unknown element: {0}
Cause: The model XML contains an unknown XML element
Action: Fix the XML

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15295: Unsupported datatype: {0}
Cause: The datatype is unsupported when creating the column from attributes
Action: Check the model

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15300: A {0} occurred while creating the helper of class {1}. Error message: {2}
Cause: INTERNAL ERROR: A helper cannot be created.
Action: Internal error: contact Oracle support.

Level: 32

Type: ERROR

Impact: Other

ODI-15301: Choose: {0}
Cause: Choose one of the displayed options.
Action: Choose one of the displayed options.

Level: 32

Type: ERROR

Impact: Other

ODI-15302: FK is null: {0}
Cause: The FK is null, may indicate repository corruption.
Action: Internal error: contact Oracle support.

Level: 32

Type: ERROR

Impact: Other

ODI-15400: Error in generating data service
Cause: Exception thrown when creating the data service used for DDL generation and reverse engineering.
Action: Check the root cause.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15401: Unknown key {0}
Cause: Unknown key encountered when processing diff class instances during DDL generation.
Action: Check the model.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15402: Exception thrown in the DDL generation service: {0}
Cause: An exception was thrown while generating DDL.
Action: Check the root cause.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15403: The method is not supposed to sort something else than the expected actors. Attempting to sort class instances: {0}, {1}
Cause: While sorting action commands, the DDL generator service encountered an unknown class instance type.
Action: Internal Error: contact Oracle support.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15404: Scenario generation has not been implemented for this container.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15405: Scenario generation exception: {0}
Cause: An exception was thrown during scenario generation.
Action: Check root cause.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15500: Column {0} is executed on the target
Cause: Possible Cause
Action: Suggested Action

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15501: Cannot attach a data store to a target mapping because column {0} is not found.
Cause: The specified target column was not found.
Action: Verify that the correct column has been specified.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15502: Target mapping not found for column {0}
Cause: The specified column is not mapped.
Action: Map the specified column.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15503: Cannot set the attached datastore because the mapping is not executed on the SOURCE
Cause: The mapping has been configured for execution on the target.
Action: Configure the mapping for execution on the source.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15504: Unknown indicator type: {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15505: Invalid UD number: {0}
Cause: An invalid UD number has been specified.
Action: Specify a UD number 1 to 10.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15506: The specified target column was not found: {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15507: Column {0} may not be removed. It is used in other mappings, join clauses, or filter clauses
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15508: Column {0} may not be removed because it is referenced in interface {1}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15509: The specified target column was not found: {0}
Cause: The specified target column was not found.
Action: Verify the column name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15510: A column was not found while updating the key
Cause: The update key contains a column that does not exist.
Action: Check the columns of the update key.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15511: The join must be attached to the datastore to expand a lookup.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15512: Cannot transform a normal datastore into a normal lookup.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15513: Cannot transform a normal, non-lookup join into a normal join.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15514: Cannot transform a lookup datastore into a lookup.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15515: Cannot transform a lookup join into a lookup.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15516: The join must be attached to the datastore to make a lookup.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15517: Cannot add a column with the same name as an existing target column: {0}.
Cause: The column being added already exists.
Action: Add a column with a unique name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15518: A dataset is already assigned the order: {0}.
Cause: Another dataset has already been assigned the order that is being set.
Action: Assign a unique order to the dataset.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15519: The target datastore cannot be changed. Interface {0} is used in interface(s) {1} as a source datastore.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15520: Temporary interface from another project is not allowed.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15521: A source datastore with alias {0} already exists.
Cause: The datastore alias has already been used.
Action: Specify a unique alias.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15522: Cannot transform a join into a CrossJoin or natural join if it does not have both attached datastores set.
Cause: The join does not have datastores attached yet.
Action: Attach both join datastores before transforming to a cross join.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15523: LKM {0} not accepted for source set {1}
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15524: LKM {0} not accepted for staging area to target
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15525: CKM {0} not accepted for target technology
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15526: IKM {0} not accepted for staging and target technology
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15527: IKM {0} not accepted for target technology
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15528: Mapping expression cannot be set because the target column {0} was not found.
Cause: The column was not found when setting the expression for a mapping.
Action: Specify a valid column for the expression.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15529: Action was not reversible.
Cause: The actions causing an impact are not reversible.
Action: Avoid the sequence of actions causing the impact.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15530: The interface does not have a source set.
Cause: The interface does not have a source set.
Action: Add a source set to the interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15531: The execution location parameter for the computeExpression method is invalid.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15532: The pExecutableTextHolder parameter for the getLogicalSchemaForTextHolder method does not have a valid execution location.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15533: The physical schema could not be mapped from logical schema {0} and context {1}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15534: Sub interface must not be null.
Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.
Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15535: The technology {0} of the source temporary interface {1} used as a derived table does not support derived tables.
Cause: The pSubInterface parameter passed to the checkSubInterfaceValid method is null.
Action: A non-null sub interface parameter is required for the checkSubInterfaceValid method.

Level: 32

Type: ERROR

Impact: Programmatic

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}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

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}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

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}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

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.
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.

Level: 32

Type: ERROR

Impact: Programmatic

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.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15541: Source temporary interface {0} uses a journalized datastore and cannot be used as a derived table.
Cause: The temporary interface cannot be used because it uses a journalized datastore.
Action: Use only non journalized data stores in temporary interfaces.

Level: 32

Type: ERROR

Impact: Programmatic

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.
Cause: The temporary interface cannot be used because it uses a journalized datastore.
Action: Use only non journalized data stores in temporary interfaces.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15543: Another interface with the same name already exists in this folder. Please choose a unique interface name.
Cause: Another interface with the same name already exists in this folder.
Action: Specify a unique interface name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15544: The interface must have a name.
Cause: The interface does not have a name.
Action: Specify a unique interface name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15545: Temporary target datastore has no name.
Cause: The temporary target datastore has no name
Action: Specify a unique datastore name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15546: The interface must have a logical schema.
Cause: The interface does not have a logical schema.
Action: Specify a logical schema for the interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15547: Could not fix a missing reference correctly.
Cause: The interface is missing one or more references.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15548: The source datastore has already been set.
Cause: The source datastore has already been set.
Action: Only invoke setSourceDataStore once.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15549: Cannot set the source filter because the source datastore is not set.
Cause: The source datastore has not been set prior to setting the filter.
Action: Set the source datastore prior to setting the filter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15550: The target datastore has already been set.
Cause: The source datastore has already been set.
Action: Only invoke setSourceDataStore once.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15551: Mappings on the target are not allowed in this helper.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15552: A source filter requires a source datastore.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15553: The target datastore must be set.
Cause: The target datastore for the interface has not been set.
Action: Set the target datastore before saving the interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15554: An LKM must be set on the source set.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15555: Target IKM must be set on the target table.
Cause: An integration knowledge module has not been assigned to the target table.
Action: Set the IKM for the target before saving the interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15556: Unknown generic clause type: {0}
Cause: An unknown generic clause class was passed to the createSnpPopClauseFromGenericClause method.
Action: Pass only generic clause classes for join or filter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15557: Unknown execution location type: {0}
Cause: An unknown execution location enumeration was passed to the getStringExeDbFromExecutionLocation method.
Action: Pass only location enumerations of ExecutionLocation.SOURCE, ExecutionLocation.WORK, ExecutionLocation.TARGET.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15558: There is a conflict between physical schemas
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15559: Unsupported component: {0}
Cause: An unsupported component was passed as a parameter to createDataAccessinfo.
Action: For the pInterfaceSubComponents parameter, supported components are SourceDataStore, ISourceColumn, TargetMapping, and GenericClause.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15560: Fatal interface condition: {0}
Cause: A fatal issue was discovered while saving or verifying an interface.
Action: Correct the interface issue before saving it.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15561: Could not find column {0} which choosing a mapping.
Cause: The MappingChooserFirst.chooseMapping method was called with an column name that does not exist.
Action: Check the column name passed to chooseMapping.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15562: Source sets cannot be computed because one execution area doesn't have a physical schema. Check the errors on the interface.
Cause: Source sets cannot be computed because one execution area doesn't have a physical schema.
Action: Check the errors on the interface.

Level: 32

Type: ERROR

Impact: Programmatic

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.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15564: There should be one source set on the interface.
Cause: The interface has more than one source set.
Action: Ensure that only one source set is defined.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15565: Column {0} not found while setting the update key.
Cause: A column specified for the update key does not exist.
Action: Recheck the column names used to define the update key.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15566: No target column was found while setting the target data store.
Cause: No target column was found while setting the target data store.
Action: Define columns before setting the target datastore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15567: Target column {0} was not found.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15568: Column {0} not found on datastore {1}.
Cause: A referenced column was not found in a source data store.
Action: Check the source datastore columns and references for a mismatch.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15569: Cannot create a data source.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15570: Cannot add a datastore of type {0} as source.
Cause: An invalid datastore type has been specified.
Action: Specify a datastore of type TargetDataStore, SourceDataStore, or OdiDataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15571: Unexpected join type {0}
Cause: An invalid join type has been specified when setting join properties.
Action: Specify a join type of INNER, CROSS, or NATURAL.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15572: Unexpected join state.
Cause: An invalid join state has been reached. The expected join type is CROSS or NATURAL.
Action: .

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15573: Failed to create an interface helper instance.
Cause: A general exception was encountered while constructing an interface helper.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15574: General exception encountered in the interface helper while preparing to persist.
Cause: General exception encountered in the interface helper while preparing to persist.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15575: Two journalized datastores have been found. There should be only one.
Cause: Two journalized datastores have been found. There should be only one.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15576: Two journalized filters have been found. There should be only one.
Cause: Two journalized filters have been found. There should be only one.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15577: Unmanaged type: {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15578: No interface was found in the elements.
Cause: No interface could be traced to the elements passed to the prepareSQLStatement method.
Action: Create an interface.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15579: No dataset was found in the elements.
Cause: No data set could be traced to the elements passed to the prepareSQLStatement method.
Action: Ensure that a datase has been created first.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15580: The target is a temporary table.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15581: Cannot build the query because the ordered joins are not correct.
Cause: The SQL clause cannot be generated because the ordered joins are not correct.
Action: Ensure that all joins are correct.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15582: This operation is not supported on joined file datastores.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15583: This operation is not supported on multiple file datastores.
Cause: More than one source datastore was found.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15584: Elements are from different interfaces.
Cause: The components passed to prepareSQLStatement are from different interfaces.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15585: Elements are from different datasets.
Cause: The components passed to prepareSQLStatement are from different data sets.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15586: Unsupported component: {0}
Cause: An invalid component type was passed to connectionForData.
Action: Only pass components of type SourceDataStore, ISourceColumn, TargetMapping, TargetColumn, GenericClause, or TargetDataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15587: Journalization filter not found for the journalized table.
Cause: The journalized table does not have a filter.
Action: Define a journalizing filter for the table.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15588: The SQL join clause is not valid for a cross join.
Cause: A join clause has been specified for a cross join.
Action: Remove the join condition or change the join type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15589: Cannot change the ON_TARGET indicator on a temporary interface.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15590: Unknown indicator type: {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15591: Staging Area is on the target and cannot be switched to another logical schema.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15592: GenericClause is of unknown type: {0}
Cause: InterfaceActionRemoveGenericClause was constructed with an invalid generic clause.
Action: Use a generic clause type of JOIN or FILTER.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15593: Could not set LKM for object of type {0}
Cause: An LKM is being set for a TargetDataStore or some other invalid type.
Action: Only set an LKM for a SourceSet or StagingArea.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15594: Could not set the CKM for a holder of type {0}
Cause: A CKM is being set for a SourceSet, StagingArea, or some other invalid type.
Action: Only set a CKM for a TargetDataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15595: Could not set the IKM for a holder of type {0}
Cause: An IKM is being set for a SourceSet, StagingArea, or some other invalid type.
Action: Only set an IKM for a TargetDataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15596: Invalid KM type: {0}
Cause: An invalid object type is being used to set a KM.
Action: Only set a KM of type LKM, CKM, or IKM.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15597: Could not set the LKM option for a holder of type {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15598: Could not set the CKM option for a holder of type {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15599: Could not set the IKM option for a holder of type {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15600: Dataset 1 was not found in the list of the interface datasets used with the interface.
Cause: The first dataset given as a parameter in the constuction 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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15601: Dataset 2 was not found in the list of the datasets used with the interface.
Cause: The second dataset given as a parameter in the constuction 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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15602: Dataset 2 was not found in the list of the datasets used with the interface.
Cause: An unimplemented method has been called. This is an ODI internal error.
Action: Do not call this method.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15603: Cannot create an alias for a datastore of type {0}
Cause: The method computeAliasForDataStore was called with an invalid datastore type.
Action: Only call computeAliasForDataStore for datastores of type TargetDataStore or OdiDataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15604: A non ordered clause was passed to the buildTreeSet method.
Cause: A non ordered clause is passed to the construction of ordered joins trees method.
Action: Use ordered join clauses with this method.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15605: Multiple ordered joins in this dataset use the same order number.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15606: Join references the same table twice (directly or indirectly).
Cause: A join clause contains two references to the same table.
Action: Ensure that the join clause only references one table.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15607: Join references the same table twice through other joins.
Cause: A join clause contains two references to the same table.
Action: Ensure that the join clause only references one table.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15608: Subcomponent type of {0} is not supported.
Cause: An unsupported type was passed to getIssuesComputer.
Action: Only pass types of OdiInterface, DataSet, SourceDataStore, Filter, Join, StagingArea, TargetDataStore, SourceSet, TargetMapping, or TargetColumn.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15609: Invalid KM holder type: {0}
Cause: An anvalid 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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15610: Component must be a source datastore or a source colum.
Cause: ReferenceManagerAbstract.getReferencesTo was called with an invalid subcomponent.
Action: Only pass subcomponent types of SourceDataStore or ISourceColumn.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15611: Column not found from an xref.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15612: Failed to attach an element of type {0} to a source set.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15613: Interface must have only one dataset.
Cause: This sourceset computer can only handle a single dataset, and more than one was found.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15614: Interface must have only one source table.
Cause: This sourceset computer can only handle a single table, and more than one dataset was found.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15615: Interface must not have joins.
Cause: This sourceset computer can only handle a single table, and the interface contains a join.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15616: Source datastore must be a real table
Cause: This sourceset computer can only handle a single, real table.
Action:

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15617: Invalid type for a TextHolder: {0}
Cause: The method getExecutableTextHolderFor was called with an invalid TextHolder component type.
Action: Valid types are TargetMapping, TargetColumn, Filter, and Join.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15618: Cannot set a source set on a target column.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15619: Inconsistent filter with a clauseType of {0}
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15620: Execution location is null. Target technology cannot be determined
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15621: Attached dataStore is null. Target technology cannot be determined
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15622: Staging area does not have a logical schema. Target technology cannot be determined
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15623: Invalid technology for the given index type
Cause: The technology of the clause and index type do not match.
Action: Ensure that the index type technology matches the clause technology.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15624: Inconsistent join with clauseType = {0} and joinType = {1}
Cause: The join clause type is invalid.
Action: This exception is thrown from a deprecated method. Use isCross or isOrdered methods instead.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15625: Cannot set OdiDataType on a journalized source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15626: Cannot set the length on a journalized source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15627: Cannot set the scale on a journalized source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15628: Cannot set the data type on a source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15629: Cannot set the length on a source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15630: Cannot set the scale on a source column
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15631: Connection information is not available.
Cause: The physical schema has not been set.
Action: Define physical and logical schemas.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15632: Column {0} may not be removed because it is mapped in interface {1}.
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.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15633: Data Type must be set first.
Cause: Data Type is null.
Action: Set Data Type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15634: Length is not allowed for the current Data Type
Cause: Data Type doesn't support length.
Action: Check Data Type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15635: Scale is not allowed for the current Data Type.
Cause: Data Type doesn't support scale.
Action: Check Data Type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15636: Cannot change the column because it's not a temporary column.
Cause: Column isn't a temporary.
Action: Check column state.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15637: Execution location must be either null or target.
Cause: Wrong Execution location state.
Action: Check Execution location.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15638: Scenario {0} contains invalid characters. Try {1}.
Cause: String contains invalid characters.
Action: Check scenario name.

Level: 32

Type: ERROR

Impact: Other

ODI-15639: Scenario version is not set.
Cause: Scenario version is not set.
Action: Set scenation version.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15640: No Scenario was found through the Tag : {0}.
Cause: No Scenario was found.
Action: Check tag.

Level: 32

Type: ERROR

Impact: Other

ODI-15641: The refresh SQL statement of a variable cannot contain sequence references when the variable is added to a load plan.
Cause: SQL statement contains sequence references.
Action: Check refresh SQL statement.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-15642: Scenario name must be {0} characters long max.
Cause: Scenario name is too long.
Action: Check name length.

Level: 32

Type: ERROR

Impact: Other

ODI-15700: Exception thrown in the Odi shortcut service: {0}
Cause: An exception was thrown while materializing a shortcut object.
Action: Check the root cause.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17500: Invalid old password.
Cause: Old password did not match current password.
Action: Provide the correct password.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17501: Temporary table has no column.
Cause: No column have been defined for the temporary table.
Action: Define a column mapping to the temporary table.

Level: 32

Type: ERROR

Impact: Other

ODI-17502: No next value returned.
Cause: No sequence next value was found for given context code.
Action: Verify sequence definition or context code.

Level: 32

Type: ERROR

Impact: Other

ODI-17504: An ordered join references the same table twice (directly or indirectly).
Cause: A same table was referenced twice by a join.
Action: Check interface definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17505: An ordered join references the same table twice through another join.
Cause: A join was referencing the same table twice through another join.
Action: Check interface definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17506: Variable has no value
Cause: Variable had no value.
Action: Provide value for variable.

Level: 32

Type: ERROR

Impact: Other

ODI-17507: Key does not exist
Cause: Key was unknown.
Action: Provide a known key.

Level: 32

Type: ERROR

Impact: Other

ODI-17508: No conversion for data type "{0}" from source technology "{1}" to destination technology "{2}"
Cause: No data type conversion between technology was found.
Action: Define corresponding data type conversion.

Level: 32

Type: ERROR

Impact: Other

ODI-17509: Query to access value for specific sequence {0} has failed. Query="{1}"
Cause: Query for sequence has failed.
Action: Check sequence definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17510: Driver does not exist.
Cause: Driver was not found.
Action: Check repository.

Level: 32

Type: ERROR

Impact: Other

ODI-17511: No value to be set to variable {0}.
Cause: No value was returned to be set to the variable.
Action: Check variable value.

Level: 32

Type: ERROR

Impact: Other

ODI-17512: Sequence is already locked
Cause: The sequence was already locked.
Action: Unlock the sequence.

Level: 32

Type: ERROR

Impact: Other

ODI-17513: Variable does not exist
Cause: Variable was not found.
Action: Check variable.

Level: 32

Type: ERROR

Impact: Other

ODI-17514: Unrecognized Oracle Data Integrator built-in function: {0}
Cause: Oracle Data Integrator built-in function was not recognized.
Action: Check function syntaxe.

Level: 32

Type: ERROR

Impact: Other

ODI-17515: Invalid loading command (INSERT,UPDATE...).
Cause: Loading command was invalid.
Action: Check loading command.

Level: 32

Type: ERROR

Impact: Other

ODI-17517: Error during task interpretation. Task: {0} {1} Text: {2}.
Cause: A task interpretation error has occured.
Action: Check tasks and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17518: Error while interpreting the user name.
Cause: User name interpretation has failed.
Action: Check user name.

Level: 32

Type: ERROR

Impact: Other

ODI-17519: Error while interpreting the URL
Cause: URL interpretation has failed
Action: Check URL.

Level: 32

Type: ERROR

Impact: Other

ODI-17520: Error while interpreting the password
Cause: Password interpretation has failed.
Action: Check password.

Level: 32

Type: ERROR

Impact: Other

ODI-17521: Error while interpreting the driver
Cause: Driver interpretation has failed.
Action: Check driver.

Level: 32

Type: ERROR

Impact: Other

ODI-17522: Empty column name are not allowed
Cause: A empty column name was found.
Action: Fill column name.

Level: 32

Type: ERROR

Impact: Other

ODI-17523: There is no connection for this logical schema / context pair: {0} / {1}.
Cause: No connection was found for this logical schema / context pair.
Action: Check schema and context assignment.

Level: 32

Type: ERROR

Impact: Other

ODI-17524: Cannot set an empty alias for a source table.
Cause: Source table''s alias was empty.
Action: Fill alias of source table.

Level: 32

Type: ERROR

Impact: Other

ODI-17525: Cannot set an empty source set name.
Cause: Source set name was empty.
Action: Fill alias of a source table.

Level: 32

Type: ERROR

Impact: Other

ODI-17526: Cannot set Longc value in a PopCol having a column
Cause: Cannot set Longc value in a PopCol having a column.
Action: Check interface`s columns.

Level: 32

Type: ERROR

Impact: Other

ODI-17527: Cannot set SourceDt value in a PopCol having a column
Cause: Cannot set SourceDt value in a PopCol having a column.
Action: Check interface`s columns.

Level: 32

Type: ERROR

Impact: Other

ODI-17528: Cannot set Scalec value in a PopCol having a column
Cause: Cannot set Scalec value in a PopCol having a column.
Action: Check interface`s columns.

Level: 32

Type: ERROR

Impact: Other

ODI-17529: Reference check failure
Cause: Reference check has failed.
Action: Check control conditions.

Level: 32

Type: ERROR

Impact: Other

ODI-17530: Incomplete join may result in partial cross join
Cause: An incomplete join was found.
Action: Check joins.

Level: 32

Type: ERROR

Impact: Other

ODI-17531: KM already encrypted.
Cause: KM has been already encrypted.
Action: Skip encryption.

Level: 32

Type: ERROR

Impact: Other

ODI-17532: KM not encrypted.
Cause: KM was not encrypted.
Action: Check KM.

Level: 32

Type: ERROR

Impact: Other

ODI-17533: Clause set to cross join on a technology that does not support cross joins.
Cause: Technology did not support cross joins.
Action: Correct joins.

Level: 32

Type: ERROR

Impact: Other

ODI-17534: Clause set to full join on a technology that does not support full joins.
Cause: Technology did not support full joins.
Action: Correct joins.

Level: 32

Type: ERROR

Impact: Other

ODI-17535: Clause set to outer join on a technology that does not support left outer joins or right outer joins.
Cause: Technology did not support left outer joins.
Action: Correct joins.

Level: 32

Type: ERROR

Impact: Other

ODI-17536: Incomplete clause (Missing order number).
Cause: Order number was missing.
Action: Correct clause.

Level: 32

Type: ERROR

Impact: Other

ODI-17537: Incomplete clause (table1 and/or table2 must be set).
Cause: Table1 and/or table2 were undefined.
Action: Set clause''s table1 and/or table2 tables.

Level: 32

Type: ERROR

Impact: Other

ODI-17538: Filter is not properly set (The table must be defined)
Cause: The table must have been set.
Action: Set filter''s table.

Level: 32

Type: ERROR

Impact: Other

ODI-17539: Clause is ordered on a technology that does not support it
Cause: Technology did not support ordering.
Action: Remove ordering.

Level: 32

Type: ERROR

Impact: Other

ODI-17540: Connection is not set for this source set {0}.
Cause: Source set''s connection was not set.
Action: Set connection.

Level: 32

Type: ERROR

Impact: Other

ODI-17542: Sequence must be locked before using this function
Cause: Sequence was not locked.
Action: Lock sequence and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17543: Technology does not support joins
Cause: Technology did not support joins.
Action: Check technology and/or joins.

Level: 32

Type: ERROR

Impact: Other

ODI-17544: This Technology does not support the WHERE clause
Cause: Technology did not support the WHERE clause
Action: Check technology and/or clause.

Level: 32

Type: ERROR

Impact: Other

ODI-17545: Technology not set for this source set {0}
Cause: Source set''s technology was undefined.
Action: Set technology.

Level: 32

Type: ERROR

Impact: Other

ODI-17546: Specified variable not found in the Repository
Cause: Variable was not found in the Repository.
Action: Define variable and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17547: Data type "{0}" for the technology "{1}" does not exist.
Cause: Data type for the technology did not exist.
Action: Check data type and/or technology.

Level: 32

Type: ERROR

Impact: Other

ODI-17548: The file reverse-engineering is only possible for delimited files.
Cause: The file reverse-engineering was performed against a not delimited file.
Action: Use delimited files.

Level: 32

Type: ERROR

Impact: Other

ODI-17549: Source data type "{0}" for the technology "{1}" does not exist.
Cause: Source data type was not found.
Action: Check data type and/or technology.

Level: 32

Type: ERROR

Impact: Other

ODI-17550: Missing default Physical Schema for Data Server "{0}"
Cause: Default Physical Schema was undefined.
Action: Specify default Physical Schema.

Level: 32

Type: ERROR

Impact: Other

ODI-17551: Duplicate clause order numbers
Cause: Duplicated order numbers were found.
Action: Check clause definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17552: Duplicate join order numbers
Cause: Duplicated join order numbers were found.
Action: Check join.

Level: 32

Type: ERROR

Impact: Other

ODI-17553: Exceeded the maximum number of errors allowed.
Cause: The maximum number of errors allowed were exceeded.
Action: Check maximum error numbers.

Level: 32

Type: ERROR

Impact: Other

ODI-17554: Agent "{0}" does not exist.
Cause: Agent was not found.
Action: Check agent definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17555: You cannot unlock this object. Only the lock owners and Supervisors can unlock objects.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-17556: Error during decryption of text.
Cause: Text decryption has failed.
Action: Try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17557: No condition defined for this rule.
Cause: No condition have been defined for this rule.
Action: Define conditions.

Level: 32

Type: ERROR

Impact: Other

ODI-17558: The field for this rule is not specified.
Cause: The field was unspecified.
Action: Specify field for this rule.

Level: 32

Type: ERROR

Impact: Other

ODI-17559: The operator for this rule is not specified.
Cause: The operator was unspecified.
Action: Specify operator for this rule.

Level: 32

Type: ERROR

Impact: Other

ODI-17560: The value to test is not defined.
Cause: The value to test was not defined.
Action: Specify value.

Level: 32

Type: ERROR

Impact: Other

ODI-17561: This operator is not supported.
Cause: This operator was not supported.
Action: Correct operator.

Level: 32

Type: ERROR

Impact: Other

ODI-17562: This operator cannot be used with this field.
Cause: The operator could not be used with the given field.
Action: Correct operator.

Level: 32

Type: ERROR

Impact: Other

ODI-17563: There is no work repository matching the name "{0}".
Cause: Work repository was not found.
Action: Check work repository with the given name exists.

Level: 32

Type: ERROR

Impact: Other

ODI-17564: More than one work repository found with the name "{0}" for this master repository.
Cause: More than one work repository with the specified name was found for this master repository.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-17565: Scenario has been already encrypted. No encryption was performed.
Cause: Scenario has been already encrypted.
Action: Decrypt and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17566: Scenario is not encrypted. No decryption was performed.
Cause: Scenario was not encrypted.
Action: Check Scenario.

Level: 32

Type: ERROR

Impact: Other

ODI-17567: A Scenario generated from a Variable cannot be encrypted or decrypted.
Cause: An attempt was made to encrypte or decrypte a Scenario generated from a Variable.
Action: Change Scenario'' source component.

Level: 32

Type: ERROR

Impact: Other

ODI-17568: Could not connect to the database referenced by the context and the logical schema
Cause: Connection to the database failed.
Action: Check context and logical schema.

Level: 32

Type: ERROR

Impact: Network

ODI-17569: Unable to update sequence''s next value.
Cause: Updating sequence was not possible.
Action: Check sequence definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17570: Your text is too long. Please shorten it or choose the ''LONG TEXT'' datatype.
Cause: Text was too long.
Action: Shorten the text or choose the LONG TEXT data type.

Level: 32

Type: ERROR

Impact: Other

ODI-17571: Password does not respect the following rule: "{0}".
Cause: The password did not respect the rule.
Action: Choose another password.

Level: 32

Type: ERROR

Impact: Security

ODI-17572: This SnpFfValuee does not exist.
Cause: Value was not found.
Action: Check FlexField value.

Level: 32

Type: ERROR

Impact: Other

ODI-17573: This SnpFfValuem does not exist.
Cause: Value was not found.
Action: Check FlexField value.

Level: 32

Type: ERROR

Impact: Other

ODI-17574: This SnpFfValuew does not exist.
Cause: Value was not found.
Action: Check FlexField value.

Level: 32

Type: ERROR

Impact: Other

ODI-17575: SnpLicense does not exist.
Cause: SnpLicense was not found.
Action: Check License.

Level: 32

Type: ERROR

Impact: Other

ODI-17576: Unknown actual constraint type for an interface constraint.
Cause: Interface constraint type was unknown.
Action: Check constraint type.

Level: 32

Type: ERROR

Impact: Other

ODI-17577: Unknown variable data type.
Cause: Variable data type was unknown.
Action: Check variable data type.

Level: 32

Type: ERROR

Impact: Other

ODI-17578: Name "{0}" is already used.
Cause: Name was already used.
Action: Use another name or change mode of import.

Level: 32

Type: ERROR

Impact: Other

ODI-17579: Type of clause is not set.
Cause: Type of clause was not set.
Action: Set type of clause.

Level: 32

Type: ERROR

Impact: Other

ODI-17580: Type of join is not set.
Cause: Type of join was not set.
Action: Set type of join.

Level: 32

Type: ERROR

Impact: Other

ODI-17581: A non ordered clause is passed to the construction of ordered joins trees method.
Cause: A non ordered clause was passed to the construction of ordered joins trees method.
Action: Check clauses.

Level: 32

Type: ERROR

Impact: Other

ODI-17582: Missing order number for an ordered clause.
Cause: Clause order was not set.
Action: Set the clause order.

Level: 32

Type: ERROR

Impact: Other

ODI-17583: More than one unique constraint associated to an interface constraint.
Cause: More than one unique constraint associated to an interface constraint was found.
Action: Check constraints.

Level: 32

Type: ERROR

Impact: Other

ODI-17584: URL does not exist.
Cause: URL was not found.
Action: Check URL.

Level: 32

Type: ERROR

Impact: Other

ODI-17585: Key cannot be checked.
Cause: Key could not be checked.
Action: Check key definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17586: Field separator is mandatory for a delimited file.
Cause: Field separator was missing.
Action: Check separator and/or file type.

Level: 32

Type: ERROR

Impact: Other

ODI-17587: Object name "{0}" is too long for the technology "{1}" (Logical schema : "{2}" ; Context Code : "{3}")
Cause: Object name was too long.
Action: Correct object name.

Level: 32

Type: ERROR

Impact: Other

ODI-17588: Unable to load work repository info.
Cause: Work repository was not found.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-17589: Logical schema has not been specified for sequence "{0}"
Cause: Logical schema was not specified.
Action: Specify logical schema.

Level: 32

Type: ERROR

Impact: Other

ODI-17590: Code {0} for model "{1}" is already used by another model.
Cause: An already used code was assigned.
Action: Change code for model.

Level: 32

Type: ERROR

Impact: Other

ODI-17591: Name "{0}" is already used.
Cause: A name already used was assigned.
Action: Change name.

Level: 32

Type: ERROR

Impact: Other

ODI-17592: Object is not in execution work repository.
Cause: Object was not in execution work repository.
Action: Check object and/or repository.

Level: 32

Type: ERROR

Impact: Other

ODI-17593: Maximum number or source/target technologies exceeded. Current limit is {0}.
Cause: Maximum number or source/target technologies was exceeded.
Action: Check limit and number of technologies.

Level: 32

Type: ERROR

Impact: Other

ODI-17594: Cannot encrypte already encrypted action.
Cause: This action has been already encrypted.
Action: Skip encryption.

Level: 32

Type: ERROR

Impact: Other

ODI-17595: This action is not encrypted.
Cause: This action was not encrypted.
Action: Check parameters and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-17596: Query to retrieve value for native sequence "{0}" has failed Query="{1}"
Cause: Query has failed.
Action: Check query.

Level: 32

Type: ERROR

Impact: Other

ODI-17597: Cannot mix ordered and non-ordered join syntax within a dataset for technology.
Cause: Mixed join not allowed within a dataset.
Action: Change all joins in dataset to same join syntax (either ordered or non-ordered).

Level: 32

Type: ERROR

Impact: Other

ODI-17598: Non-ordered natural join is not supported.
Cause: Non-ordered natural join is not supported.
Action: Change natural join to use ordered syntax.

Level: 32

Type: ERROR

Impact: Other

ODI-17599: Ordered inner join is not supported.
Cause: Ordered inner join is disabled for technology.
Action: Change join type.

Level: 32

Type: ERROR

Impact: Other

ODI-17600: Ordered left outer join is not supported.
Cause: Ordered left outer join is disabled for technology.
Action: Change join type.

Level: 32

Type: ERROR

Impact: Other

ODI-17601: Ordered right outer join is not supported.
Cause: Ordered right outer join is disabled for technology.
Action: Change join type.

Level: 32

Type: ERROR

Impact: Other

ODI-17602: Non-ordered full outer join is not supported.
Cause: Non-ordered full outer join is not supported.
Action: Change full outer join to use ordered syntax.

Level: 32

Type: ERROR

Impact: Other

ODI-17603: Sql error checking a condition. {0}
Cause: Sql error checking a condition.
Action: Correct the Sql in the condition.

Level: 32

Type: ERROR

Impact: Other

ODI-17604: Reference column isn't associated with this instance of reference.
Cause: Reference column isn't associated with this instance of reference.
Action: Check reference column.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17605: Column is not associated to this datastore.
Cause: Datastore doesn't have this column.
Action: Check datastore and column.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17606: {0} already belongs to another OdiDataStore.
Cause: Object belongs to another datastore.
Action: Check object and datastore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17607: Parameter pReference is not an outbound reference for this OdiDataStore.
Cause: Parameter is not an outbound reference for OdiDataStore.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17608: Invalid technology for the given data type.
Cause: Invalid technology for the given data type.
Action: Check technology.

Level: 32

Type: ERROR

Impact: Other

ODI-17609: Invalid data type code.
Cause: Invalid data type code.
Action: Check data type code.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17610: Found NULL in STEP_TYPE.
Cause: Step type is null.
Action: Check step type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17611: STEP_TYPE is not valid.
Cause: Step type isn't valid.
Action: Check step type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17612: MultiConnectionSupported is not settable for {0}.
Cause: MultiConnectionSupported is not settable.
Action: Check knowledge module.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17613: Cannot handle {0} of type {1}.
Cause: Cannot handle object.
Action: Check object's type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17614: Unknown key type: {0}.
Cause: Unknown key type.
Action: Check key.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17615: The command is not an ODI Tool command.
Cause: Wrong command.
Action: Check command.

Level: 32

Type: ERROR

Impact: Other

ODI-17616: No WorkTextOrig was found for ID: {0}.
Cause: Invalid ID.
Action: Check ID.

Level: 32

Type: ERROR

Impact: Other

ODI-17617: Class descriptor for WorkTextOrig [ {0} ] is null.
Cause: Descriptor is null.
Action: Check class descriptors.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17618: Unable to deal with an AliasedColumnCrossRef with type {0}.
Cause: Incorrect column type.
Action: Check column type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17619: Unexpected CrossRef {0} type.
Cause: Incorrect CrossRef type.
Action: Check CrossRef.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17620: Object type is not valid.
Cause: Object type is not valid.
Action: Check object type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17621: Unable to manage crossRef for object from class [ {0} ].
Cause: Illegal object type.
Action: Check object type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17622: pSqlIndGroup is not a valid group type.
Cause: Invalid group type.
Action: Check type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17623: Too many parameters for function {0}, Object {1}, Language {2}.
Cause: Too many parameters.
Action: Check parameters count.

Level: 32

Type: ERROR

Impact: Other

ODI-17624: Missing parameter for function {0}, Object {1}, Language {2}.
Cause: Missing parameter.
Action: Check parameters count.

Level: 32

Type: ERROR

Impact: Other

ODI-17625: Only OdiColumns are currently supported for SnpsExpressionTag.
Cause: Wrong column type.
Action: Check column type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17626: Cannot reassign a DataType.
Cause: Technology has been assigned yet.
Action: Check DataType

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17627: Inconsistent connection settings.
Cause: Inconsistent connection settings.
Action: Check connection settings type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17628: Unknown IConnectionSettings implementation.
Cause: Unknown IConnectionSettings implementation.
Action: Check settings type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17629: Connection Settings for repository server must be instanceof JdbcSettings.
Cause: Wrong settings type.
Action: Check settings type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17630: Unknown OptionType.
Cause: Unknown OptionType.
Action: Check option type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17631: The given class has no matching OverridenOptionOrig.
Cause: The given class has no matching OverridenOptionOrig.
Action: Check class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17632: Unexpected variable type.
Cause: Unexpected variable type.
Action: Check variable type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17633: {0} datatype is expected.
Cause: Wrong value datatype.
Action: Check value datatype.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17634: Parameter must have text; it must not be null or empty.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17635: Parameter must have text; it must not be null, empty, or blank.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17636: Parameter {0} must be false.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17637: Parameter must not be null.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17638: Parameter {0} must be null.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17639: Parameter must be null.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17640: Parameter {0} must have text; it must not be null or empty.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17641: No {0} matches this IObject: {1}.
Cause: IObject is not matched.
Action: Check class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17642: No Entity Class matches this Snp Class: {0}.
Cause: No Entity Class matches Snp Class.
Action: Check Entity Class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17643: No Snp Class matches this Entity Class: {0}.
Cause: No Snp Class matches Entity Class.
Action: Check Snp Class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17644: Unknown FlexFieldType.
Cause: Unknown FlexFieldType.
Action: Check FlexFieldType type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17645: Parameter must be instance of {0}.
Cause: Wrong parameter type.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17646: It is forbidden to use a variable of one project in a package of another project.
Cause: Variable and package have diferent parents.
Action: Check variable and package.

Level: 32

Type: ERROR

Impact: Other

ODI-17647: Unable to create the expression element, Object {0}, Language {1}.
Cause: Unable to create the expression element.
Action: Check expression parameters.

Level: 32

Type: ERROR

Impact: Other

ODI-17648: A mapping cannot be on the target.
Cause: A mapping cannot be on the target.
Action: Check execution location.

Level: 32

Type: ERROR

Impact: Other

ODI-17649: Can't create join between 2 source datastore from different DataSet.
Cause: Source datastores are from different DataSet.
Action: Correct join.

Level: 32

Type: ERROR

Impact: Other

ODI-17650: A {0} was expected as value since {1} is {2}.
Cause: Wrong type.
Action: Check type.

Level: 32

Type: ERROR

Impact: Other

ODI-17651: Parameter {0} must be instance of [{1}].
Cause: Wrong parameter class.
Action: Check parameter class.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17652: Class {0} is not assignable to {1}.
Cause: Inconsistent classes.
Action: Check classes.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17653: {0} line isn't found.
Cause: Missed line.
Action: Check line count.

Level: 32

Type: ERROR

Impact: Other

ODI-17654: Parameter {0} must be not null.
Cause: Parameter must be not null.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17655: Parameter {0} must be {1} characters long max.
Cause: Parameter length is too long.
Action: Check parameter length.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17656: Can't define variable override for steps in exception tree.
Cause: Step is in exception tree.
Action: Check step and variable for consistency.

Level: 32

Type: ERROR

Impact: Other

ODI-17657: Cannot add a reference column to an OdiReference with type [{0}].
Cause: Reference type isn't ReferenceType.COMPLEX_REFERENCE.
Action: Check reference type.

Level: 32

Type: ERROR

Impact: Other

ODI-17658: Cannot change the target table because it's not a temporary datastore.
Cause: Datastore isn't temporary.
Action: Check target table and datastore.

Level: 32

Type: ERROR

Impact: Other

ODI-17659: Cannot get the journalized columns of a non-journalized datastore.
Cause: Datastore isn't journalized.
Action: Check datastore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17660: Cannot set a clause on the target.
Cause: Wrong execution location.
Action: Check execution location.

Level: 32

Type: ERROR

Impact: Other

ODI-17661: {0} is not supported for this Technology.
Cause: Object is not supported for this Technology.
Action: Check topology.

Level: 32

Type: ERROR

Impact: Other

ODI-17662: Parameter {0} must have text; it must not be null, empty, or blank.
Cause: Incorrect parameter.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17663: Parameter {0} must be uppercase.
Cause: Parameter is lower case.
Action: Check parameter case.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17664: Parameter {0} must not contain whitespaces.
Cause: Parameter contains whitespaces.
Action: Consider to replace whitespace with another symbold (e.g. underscore)

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17665: Column is not associated with this instance of OdiKey.
Cause: Column is not associated with instance of OdiKey.
Action: Check column and OdiKey.

Level: 32

Type: ERROR

Impact: Other

ODI-17666: Column is not present in the key.
Cause: Column is not present in the key.
Action: Check column and key.

Level: 32

Type: ERROR

Impact: Other

ODI-17667: Data type should be set before accessing value.
Cause: Illegal method usage.
Action: Set Data type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17668: Datastore already has a Primary Key.
Cause: Datastore already has a Primary Key.
Action: Remove the current primary key before adding a new one.

Level: 32

Type: ERROR

Impact: Other

ODI-17669: {0} must be set before calling method {1}.
Cause: Illegal method usage.
Action: Set actual value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17670: Default implementation already exists.
Cause: Default implementation already exists.
Action: Check function implementation.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17671: {0} must not be negative.
Cause: Wrong parameter value.
Action: Set value to 0 or greater.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17672: FlexFields isn't initialized.
Cause: FlexFields isn't initialized.
Action: Call initFlexFields method first.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17673: Foreign key column's datastore must be equals to this reference's foreign datastore.
Cause: Inconsistent datastores.
Action: Check datastore.

Level: 32

Type: ERROR

Impact: Other

ODI-17674: IncrementValue is not set.
Cause: IncrementValue is not set.
Action: Set IncrementValue with setVariable method.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17675: Invalid step log's status.
Cause: Step status is not RUNNING.
Action: Check step status.

Level: 32

Type: ERROR

Impact: Other

ODI-17676: Invalid value type.
Cause: Invalid value type.
Action: Check value type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17677: Cycle could be defined in {0} hierarchy.
Cause: It is forbidden to define cycle in {0} hierarchy.
Action: Check hierarchy.

Level: 32

Type: ERROR

Impact: Other

ODI-17678: It is forbidden to fill a key with columns from another datastore.
Cause: It is forbidden to fill a key with columns from another datastore.
Action: Check datastore.

Level: 32

Type: ERROR

Impact: Other

ODI-17679: It is forbidden to link two steps from different packages.
Cause: Steps are from different packages.
Action: Check steps and packages.

Level: 32

Type: ERROR

Impact: Other

ODI-17680: Line wasn't found.
Cause: Line wasn't found.
Action: Check procedure lines.

Level: 32

Type: ERROR

Impact: Other

ODI-17681: Maximum number of sessions must be positive.
Cause: Wrong value.
Action: Check maximum number.

Level: 32

Type: ERROR

Impact: Other

ODI-17682: Method is not valid unless MultiConnectionSupported.
Cause: MultiConnectionSupported is true.
Action: Check procedure.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17683: Model must be in Customized mode.
Cause: Wrong model mode.
Action: Call setReverseType(ReverseType.CUSTOMIZED).

Level: 32

Type: ERROR

Impact: Other

ODI-17684: Name can't be set.
Cause: Name is computed.
Action: Check name.

Level: 32

Type: ERROR

Impact: Other

ODI-17685: No {0} is defined for this model.
Cause: Missed definition.
Action: Define CKM for model.

Level: 32

Type: ERROR

Impact: Other

ODI-17686: No valid {0} name was found from this qualified name.
Cause: Valid name wasn't found.
Action: Check qualified name.

Level: 32

Type: ERROR

Impact: Other

ODI-17687: No valid qualified name was provided.
Cause: Name is invalid.
Action: Check qualified name.

Level: 32

Type: ERROR

Impact: Other

ODI-17688: OdiScenario is undefined.
Cause: OdiScenario is undefined.
Action: Check OdiScenario definition.

Level: 32

Type: ERROR

Impact: Other

ODI-17689: Option must be in the same procedure as line.
Cause: Option procedure is inconsistent.
Action: Check option procedure.

Level: 32

Type: ERROR

Impact: Other

ODI-17690: Package and procedure must be owned by the same project.
Cause: Procedure parent is inconsistent.
Action: Check procedure parent.

Level: 32

Type: ERROR

Impact: Other

ODI-17691: Primary key column's datastore must be equals to this reference's primary datastore.
Cause: Column datastore is inconsistent.
Action: Check datastores.

Level: 32

Type: ERROR

Impact: Other

ODI-17692: Reference column doesn't belong to this reference.
Cause: Column is inconsistent.
Action: Check column.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17693: Reference's foreign datastore is not equal to this datastore.
Cause: Datastores are inconsistent.
Action: Check datastores.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17694: Steps can't be moved from one package to another.
Cause: Steps can't be moved from one package to another.
Action: Conside not to move steps.

Level: 32

Type: ERROR

Impact: Other

ODI-17695: The new position is not valid.
Cause: The new position is not valid.
Action: Check new position.

Level: 32

Type: ERROR

Impact: Other

ODI-17696: The option already exists.
Cause: The option already exists.
Action: Check option.

Level: 32

Type: ERROR

Impact: Other

ODI-17697: The option owner has already been set.
Cause: The option owner has already been set.
Action: Check option owner.

Level: 32

Type: ERROR

Impact: Other

ODI-17698: The reference type must be [ {0} ] in order to define a complex SQL expression.
Cause: Wrong reference type.
Action: Check reference type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17699: The reference type must be [ {0} ] in order to obtain the complex SQL expression.
Cause: Wrong reference type.
Action: Check reference type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17700: The string value length should not exceed MAX_SHORT_TEXT_LENGTH since FlexFieldType is SHORT_TEXT.
Cause: FlexFieldType is SHORT_TEXT.
Action: Check FlexFieldType and string value length.

Level: 32

Type: ERROR

Impact: Other

ODI-17701: This OdiLoadPlanInstanceRun is not ESS Job related.
Cause: OdiLoadPlanInstanceRun is not ESS Job related.
Action: Check OdiLoadPlanInstanceRun.

Level: 32

Type: ERROR

Impact: Other

ODI-17702: This session is not ESS Job related.
Cause: Session is not ESS Job related.
Action: Check session.

Level: 32

Type: ERROR

Impact: Other

ODI-17703: This OdiReference must be from type [{0}] in order to access the primary DataStore alias.
Cause: Wrong OdiReference type.
Action: Check OdiReference type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17704: This OdiReference must be from type [{0}] in order to set the primary DataStore alias.
Cause: Wrong OdiReference type.
Action: Check OdiReference type.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17705: This file descriptor is not consistent with the parent model's technology.
Cause: File descriptor is not consistent.
Action: Check file descriptor and parent technology.

Level: 32

Type: ERROR

Impact: Other

ODI-17706: This setVariable is used for increment.
Cause: Increment value is set.
Action: Use method getIncrementValue().

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17707: Unable to add an alien main partition.
Cause: Main partition datastore is inconsistent.
Action: Check main partition.

Level: 32

Type: ERROR

Impact: Other

ODI-17708: Unable to compute name.
Cause: Name has been set on this physcial schema.
Action: Do not compute name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17709: Parameter must be false.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17710: Parameter {0} must be true.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17711: Undefined ODI work repository name.
Cause: Undefined repository name.
Action: Check repotitory name.

Level: 32

Type: ERROR

Impact: Other

ODI-17712: Variable and Step should be defined in the same Load Plan.
Cause: Variable and Step have different parent Load Plans.
Action: Define variable and step in the same Load Plan.

Level: 32

Type: ERROR

Impact: Other

ODI-17713: VariableDataType should be set before accessing DefaultValue.
Cause: VariableDataType is undefined.
Action: Set VariableDataType.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17714: You can only set KMs contained in the OdiProject containing of the OdiInterface.
Cause: KM has different parent project than OdiInterface.
Action: Check KM.

Level: 32

Type: ERROR

Impact: Other

ODI-17715: Can't add a null variable to load plan.
Cause: Variable is null.
Action: Check variable value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17716: DataTypes must be consistent.
Cause: DataTypes is inconsistent.
Action: Check DataTypes.

Level: 32

Type: ERROR

Impact: Other

ODI-17717: Constraint is not a condition.
Cause: Inconsistent constraint type.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17718: Constraint is not a key.
Cause: Inconsistent constraint type.
Action: Check constraint.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17719: Option is not associated to this procedure.
Cause: Option is not associated to this procedure.
Action: Check option and procedure.

Level: 32

Type: ERROR

Impact: Other

ODI-17720: Constraint is not a reference.
Cause: Inconsistent constraint type.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17721: Parameter {0} already belongs to {1}.
Cause: Parameter has parent.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17722: Parameter {0} does not belong to this instance of {1}.
Cause: Parameter has different parent.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17723: Parameter {0} must belong to this {1}.
Cause: Parameter parent is inconsistent.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17724: Parameter {0} can't be moved to an other {1}.
Cause: Parameter can't be moved.
Action: Do not move parameter.

Level: 32

Type: ERROR

Impact: Other

ODI-17725: Parameter {0} must start with {1} prefix.
Cause: Parameter has wrong prefix.
Action: Check parameter prefix.

Level: 32

Type: ERROR

Impact: Other

ODI-17726: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}.
Cause: Agent is null.
Action: Check agents.

Level: 32

Type: ERROR

Impact: Other

ODI-17727: pDataServiceContainer is not a data service.
Cause: pDataServiceContainer is not a data service.
Action: Check pDataServiceContainer.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17728: Package and interface must be owned by the same project.
Cause: Package and inteface have different parents.
Action: Check package and interface.

Level: 32

Type: ERROR

Impact: Other

ODI-17729: Parameter must be true.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17730: Not legal for shortcut.
Cause: Object is shortcut.
Action: Use getShortcutBaseObject() to access the real object.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17731: Not legal to construct a shortcut from a datastore in a model with a different technology.
Cause: Inconsistent technologies.
Action: Check model and datastore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17732: Odi object Must be shortcut after materialize.
Cause: Object isn't shortcut.
Action: Check object.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17733: Reference's primary datastore must be not null in order to define a ReferenceColumn.
Cause: Primary DataStore is null.
Action: Check DataStore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17734: pDataServiceContainer {0} has no technology defined.
Cause: Data Service Container has no technology defined.
Action: Define technology.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17735: Reference's foreign datastore is not equals to this datastore.
Cause: Reference's foreign datastore is not equals to this datastore.
Action: Check DataStores.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17736: You can only set global KMs or KMs contained in the OdiProject containing the OdiInterface.
Cause: Wrong KM.
Action: Check KM and project.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17737: StepLog and Variable don't belong to the same session.
Cause: Inconsistent session.
Action: Check Session value for StepLog and Variable.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17738: Unable to find '{0}' as variable used by the scenario '{1}' in version '{2}'.
Cause: Variable is null.
Action: Check variable name.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17739: Unable to override '{0}' varibale for execution. It is marked as read-only for scenario '{1}' in version '{2}'.
Cause: Variable is read-only.
Action: Check variable.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17740: Error while connecting to the Application Server at URL {0}.
Cause: Exception was thrown during connection.
Action: Ensure that the Application Server is running and accepting requests.

Level: 32

Type: ERROR

Impact: Network

ODI-17741: Datastore isn't used as a lookup source.
Cause: Datastore isn't used as a lookup source.
Action: Check Datastore.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17742: Parameter {0} must be greater or equal than {1} and less or equal than {2}.
Cause: Wrong parameter value
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17743: Variable should be related to the same {0}.
Cause: Wrong parent for variable.
Action: Check variable.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17744: The status can only be switched from ERROR to DONE or from DONE to ERROR.
Cause: Wrong status
Action: Check status.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17746: Parameter {0} must be greater than {1}.
Cause: Wrong parameter value.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17747: Array {0} must not be empty.
Cause: Array length is 0.
Action: Check array.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17748: Parameter {0} is not relevant to this schedule.
Cause: Wrong parameter.
Action: Check parameter.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-17749: Invalid value was specified. Cannot create {0} with the value {1}.
Cause: Invalid value was specified.
Action: Check value.

Level: 32

Type: ERROR

Impact: Programmatic

ODI-20001: ODI-20001: Cannot check the key because the Datastore does not exist in the database.
Cause: The Datastore referenced by this key did not exist in the database.
Action: Ensure the Datastore refers to an existing database table.

Level: 32

Type: ERROR

Impact: Other

ODI-20002: ODI-20002: Invalid key
Cause: An invalid encryption key file was selected.
Action: Select a valid encryption key file.

Level: 32

Type: ERROR

Impact: Other

ODI-20003: ODI-20003: Cannot edit the condition
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20004: ODI-20004: Cannot edit the reference
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20005: ODI-20005: Cannot edit the variable
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20006: ODI-20006: Cannot display table's data. Data is probably already displayed.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20007: ODI-20007: Cannot display table's data.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20008: ODI-20008: You cannot Display this Column Data. Data is probably already displayed
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

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.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20010: ODI-20010: Cannot display this Column Data
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20011: ODI-20011: Cannot perform this action: a Column of this Datastore is currently being edited
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20012: ODI-20012: Cannot perform this action: the Datastore containing this Column is currently being modified
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20013: ODI-20013: Unable to perform the action because the package is currently being modified
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20014: ODI-20014: Cannot encrypt the Procedure: it is currently being modified
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20015: ODI-20015: Cannot initialize the Flexfields values
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20016: ODI-20016: Unable to add project user functions
Cause: An unsupported action was attempted.
Action: No action required as Project user functions are not a valid selection to be added to a solution.

Level: 32

Type: ERROR

Impact: Other

ODI-20017: ODI-20017: Unable to add project sequences
Cause: An unsupported action was attempted.
Action: No action required as Project sequences are not a valid selection to be added to a solution.

Level: 32

Type: ERROR

Impact: Other

ODI-20018: ODI-20018: Unable to add project variables
Cause: An unsupported action was attempted.
Action: No action required as Project variables are not a valid selection to be added to a solution.

Level: 32

Type: ERROR

Impact: Other

ODI-20019: ODI-20019: Unable to get GBO object
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20020: ODI-20020: Cannot change CKM
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20021: ODI-20021: Cannot change the order of this Command because you do not have 'Edit' privileges on this Object
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20022: ODI-20022: Could not change the KM
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20023: ODI-20023: Cannot Duplicate a Command
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20024: ODI-20024: Cannot create the cross reference for the condition
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20025: ODI-20025: Cannot create the cross references for the reference
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20026: ODI-20026: Cannot view this Datastore: one of its Columns is currently being edited
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20027: ODI-20027: Cannot view this Column: its Datastore is currently being edited
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20028: ODI-20028: Cannot start execution.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20029: ODI-20029: Cannot move a line
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20030: ODI-20030: Cannot start the generation. The file is probably already open.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20031: ODI-20031: Cannot Delete a Command being Edited.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20032: ODI-20032: Cannot Delete a Command
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20033: ODI-20033: Cannot find the KM description
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20034: ODI-20034: Cannot find the Options list for a Command
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20035: ODI-20035: Could not find a description for the KM
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20036: ODI-20036: Impossible to find the technology name, please check your privileges.
Cause: The ODI security permissions were insufficient to allow access to the specified technology.
Action: Ensure the ODI user security permissions are correct.

Level: 32

Type: ERROR

Impact: Other

ODI-20037: ODI-20037: Cannot find data transferred by the Drag'n'Drop
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20038: ODI-20038: Could not connect
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20039: ODI-20039: Incorrect context
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20040: ODI-20040: Problem encountered when determining the context
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20041: ODI-20041: No candidate datastore was found.
Cause: There were no datastores in the current model usable as candidates for generating OUT interfaces.
Action: Consider creating an interface to load data into a datastore of the current model.

Level: 32

Type: ERROR

Impact: Other

ODI-20042: ODI-20042: Property key is empty
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20043: ODI-20043: Invalid property key entered. Property key maximum length is 250 characters
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20044: ODI-20044: Invalid property value entered. Property value maximum length is 250 characters
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20046: ODI-20046: Unable to change an open object
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20047: ODI-20047: Unable to change Value
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20048: ODI-20048: Invalid Value entered. Value maximum length is 250 characters
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20049: ODI-20049: You cannot copy a folder into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Folders cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20050: ODI-20050: You cannot copy a knowledge module into another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20051: ODI-20051: You cannot copy a package into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Packages cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20052: ODI-20052: You cannot copy an interface into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20053: ODI-20053: You cannot copy a procedure into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20054: ODI-20054: You cannot move a folder into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Folders cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20055: ODI-20055: You cannot move a knowledge module into another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20056: ODI-20056: You cannot move a package into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Packages cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20057: ODI-20057: You cannot move an interface into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20058: ODI-20058: You cannot move a procedure into a folder belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20059: ODI-20059: You cannot copy a knowledge module into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be copied into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20060: ODI-20060: You cannot copy an interface into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be copied into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20061: ODI-20061: You cannot copy a procedure into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be copied into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20062: ODI-20062: You cannot move a knowledge module into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be moved into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20063: ODI-20063: You cannot move an interface into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be moved into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20064: ODI-20064: You cannot move a step into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Package steps cannot be moved into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20065: ODI-20065: You cannot move a procedure into a package belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be moved into packages from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20066: ODI-20066: You cannot copy a folder into another project.
Cause: An unsupported operation was attempted.
Action: Folders cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20067: ODI-20067: You cannot copy a procedure into another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20068: ODI-20068: You cannot copy a variable into another project.
Cause: An unsupported operation was attempted.
Action: Variables cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20069: ODI-20069: You cannot move a folder into another project.
Cause: An unsupported operation was attempted.
Action: Folders cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20070: ODI-20070: You cannot move a sequence into another project. Copy the sequence instead.
Cause: An unsupported operation was attempted.
Action: Sequences cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20071: ODI-20071: You cannot move a procedure into another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20072: ODI-20072: You cannot move a variable into another project.
Cause: An unsupported operation was attempted.
Action: Variables cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20073: ODI-20073: You cannot copy a schedule into a scenario belonging to another project.
Cause: An unsupported operation was attempted.
Action: Schedules cannot be copied into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20074: ODI-20074: You cannot move a schedule into a scenario belonging to another project.
Cause: An unsupported operation was attempted.
Action: Schedules cannot be moved into hierarchy of another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20075: ODI-20075: You cannot move a folder into one of its subfolders.
Cause: An unsupported operation was attempted.
Action: Folders cannot be moved into their subfolders.

Level: 32

Type: ERROR

Impact: Other

ODI-20076: ODI-20076: You cannot copy a knowledge module into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be copied into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20077: ODI-20077: You cannot copy an interface into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be copied into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20078: ODI-20078: You cannot copy a procedure into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be copied into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20079: ODI-20079: You cannot move a knowledge module into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Knowledge modules cannot be moved into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20080: ODI-20080: You cannot move an interface into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Interfaces cannot be moved into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20081: ODI-20081: You cannot move a step into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Steps cannot be moved into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20082: ODI-20082: You cannot move a procedure into a package step belonging to another project.
Cause: An unsupported operation was attempted.
Action: Procedures cannot be moved into package steps from another projects.

Level: 32

Type: ERROR

Impact: Other

ODI-20083: ODI-20083: Unable to perform the operation. {0} is being edited.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20084: ODI-20084: Only variables from the same project can be placed in a package.
Cause: An unsupported operation was attempted.
Action: Variables from another projects cannot be placed in packages.

Level: 32

Type: ERROR

Impact: Other

ODI-20085: ODI-20085: Only interfaces from the same project can be placed in a package.
Cause: An unsupported operation was attempted.
Action: Interfaces from another projects cannot be placed in packages.

Level: 32

Type: ERROR

Impact: Other

ODI-20086: ODI-20086: Only procedures from the same project can be placed in a package.
Cause: An unsupported operation was attempted.
Action: Procedures from another projects cannot be placed in packages.

Level: 32

Type: ERROR

Impact: Other

ODI-20087: ODI-20087: Error while duplicating
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20088: ODI-20088: Error while generating the scenario
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20089: ODI-20089: Error during parameter initialization
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20090: ODI-20090: Error while duplicating
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20091: ODI-20091: An unexpected error occurred.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20092: ODI-20092: An error occurred while replacing the version.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20093: ODI-20093: Scenario generation is not allowed for non-saved object
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20094: ODI-20094: Specify the object name to generate Scenario
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20095: ODI-20095: Marker Group save was cancelled
Cause: Marker group save was cancelled by a user.
Action: No action required.

Level: 32

Type: ERROR

Impact: Other

ODI-20096: ODI-20096: Unable to edit the action line.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20097: ODI-20097: The line Name is mandatory
Cause: A value for the Action Line Name field was not specified.
Action: Enter a non-empty value for the Action Line Name field.

Level: 32

Type: ERROR

Impact: Other

ODI-20098: ODI-20098: Some Datatype Conversions between current and new Technologies are absent
Cause: Changing the selected Model's Technology failed because the Physical Architecture did not provide datatype conversion rules for datatypes used by columns of datastores belonging to the selected model.
Action: Ensure datatype conversion rules exist for all datatypes used by columns of datastores belonging to the selected model or do not use datatypes that cannot be converted.

Level: 32

Type: ERROR

Impact: Other

ODI-20099: ODI-20099: Unable to create execution window
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20100: ODI-20100: Unable to access a join or a filter
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20101: ODI-20101: Unable to find mapping alias
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20102: ODI-20102: Unable to find source table alias
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20103: ODI-20103: Unable to access a target column
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20105: ODI-20105: "Schema", "Table", "Column" and "Filter" are mandatory fields.
Cause: Values for the mandatory "Schema", "Table", "Column" and "Filter" fields were not supplied.
Action: Ensure values are supplied for these mandatory fields.

Level: 32

Type: ERROR

Impact: Other

ODI-20106: ODI-20106: Schema and Native sequence name are mandatory fields
Cause: Values for the mandatory Schema and Native sequence name fields were not supplied.
Action: Ensure values are supplied for these mandatory fields.

Level: 32

Type: ERROR

Impact: Other

ODI-20107: ODI-20107: A project sequence with the name "{0}" already exists in the project "{1}"
Cause: Saving the project sequence failed because the Sequence name was not unique within the Project.
Action: Ensure the sequence name entered is unique.

Level: 32

Type: ERROR

Impact: Other

ODI-20108: ODI-20108: A global sequence with the name "{0}" already exists
Cause: Saving the Global sequence failed because the Global Sequence name was not unique.
Action: Ensure the squence name entered is unique.

Level: 32

Type: ERROR

Impact: Other

ODI-20109: ODI-20109: Error while restoring the version
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20110: ODI-20110: No version of this element exist.
Cause: The selected version of this object was not found in version repository.
Action: Create or restore the selected version of the object.

Level: 32

Type: ERROR

Impact: Other

ODI-20111: ODI-20111: Sub-model code cannot be empty.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20112: ODI-20112: The path defined in the logical schema is incorrect.
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.

Level: 32

Type: ERROR

Impact: Other

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.
Cause: The supplied GUID did not match GUID from external identity store.
Action: Provide a valid GUID.

Level: 32

Type: ERROR

Impact: Other

ODI-20114: ODI-20114: Error while subscribing
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20115: ODI-20115: Error while stopping journalizing
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20116: ODI-20116: Aliases are specified and are not unique.
Cause: Duplicate Alises were detected.
Action: Change the name of the join key alias.

Level: 32

Type: ERROR

Impact: Other

ODI-20117: ODI-20117: Error while executing command line.
Cause: An unexpected error occurred while trying to open the Report.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20118: ODI-20118: Error while building the menu.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20119: ODI-20119: Error during generation.
Cause: An unexpected error occurred during the report generation.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20120: ODI-20120: Error while journalizing
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20121: ODI-20121: Error while saving the diagram
Cause: An unexpected error occurred during the saving the diagram.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20122: ODI-20122: Error while unsubscribing
Cause: An unexpected error occurred during the unsubscribing action.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20123: ODI-20123: Error while executing query
Cause:
Action: Check the error details for further actions.

Level: 32

Type: ERROR

Impact: Other

ODI-20124: ODI-20124: Operation cancelled by user.
Cause: Operation cancelled by user
Action: Review the other messages for further actions.

Level: 32

Type: WARNING

Impact: Other

ODI-20126: ODI-20126: TreeTableColumn cannot be added
Cause: TreeTableColumn with this order number already exists
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20127: ODI-20127: This TreeTableColumn cannot be removed.
Cause: TreeTableColumn does not exist.
Action: Contact Oracle Support Servies.

Level: 32

Type: ERROR

Impact: Other

ODI-20128: ODI-20128: Could not rollback.
Cause: An error occurred during rollback operation.
Action: Review other messages for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20129: ODI-20129: Exception occurred.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20130: ODI-20130: You must select a folder.
Cause: A folder was not selected.
Action: Select a folder before attempting this action.

Level: 32

Type: ERROR

Impact: Other

ODI-20131: ODI-20131: Cannot retrieve the table list
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20132: ODI-20132: An interface cannot be moved to another project
Cause: An unsupported drag and drop operation was attempted.
Action: No action required.

Level: 32

Type: ERROR

Impact: Other

ODI-20133: ODI-20133: A procedure cannot be moved to another project
Cause: An unsupported drag and drop operation was attempted.
Action: No action required.

Level: 32

Type: ERROR

Impact: Other

ODI-20134: ODI-20134: A variable cannot be moved to another project
Cause: An unsupported drag and drop operation was attempted.
Action: No action required

Level: 32

Type: ERROR

Impact: Other

ODI-20135: ODI-20135: A step cannot be moved to another package
Cause: An unsupported drag and drop operation was attempted.
Action: No action required

Level: 32

Type: ERROR

Impact: Other

ODI-20138: ODI-20138: An error occured during: dragGesture
Cause: An unexpected error occurred while dragging an object.
Action: Review the message log for more information. If problem persists contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20139: ODI-20139: An error occured during: dragEnter
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20140: ODI-20140: An error occured during: Drop
Cause: An unexpected error occurred while dropping an object.
Action: Review the message log for more information. If problem persists contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20141: ODI-20141: Login Creation Error
Cause: An unexpected error occurred while creating a new Login.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20142: ODI-20142: Popup Menu Creation Error
Cause: An unexpected error occurred while creating a popup menu.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20144: ODI-20144: Error while Deleting
Cause: An unexpected error occurred while deleting a tree object.
Action: Review the error details for further information.

Level: 32

Type: ERROR

Impact: Other

ODI-20145: ODI-20145: Error while Opening splitframe.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20146: ODI-20146: Error occured during duplication
Cause: An unexpected error occurred while duplicating an object.
Action: Review the error details and message log for more information.

Level: 32

Type: ERROR

Impact: Other

ODI-20148: ODI-20148: An error occured during: drag over the object
Cause: An unexpected error occurred while dragging an object over another object.
Action: Review the error details and message log for more information.

Level: 32

Type: ERROR

Impact: Other

ODI-20149: ODI-20149: Logical schema can't be undefined
Cause: A Logical schema was not defined.
Action: Define a Logical schema.

Level: 32

Type: ERROR

Impact: Other

ODI-20150: ODI-20150: KM or Procedure already encrypted. No encryption was performed.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20151: ODI-20151: File is not found. Invalid file location
Cause: The specified file could not be located in the file system.
Action: Ensure file location specified is valid and accessible.

Level: 32

Type: ERROR

Impact: Other

ODI-20152: ODI-20152: Object cannot be deleted
Cause: The specified object could not be deleted.
Action: Ensure the specified object exists and the security permissions permit deletion.

Level: 32

Type: ERROR

Impact: Other

ODI-20153: ODI-20153: The following field is missing: Syntax
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20155: ODI-20155: Changing the Logical Schema may require a re-generation of your Interfaces. It may be better to modify the Topology information instead.
Cause:
Action:

Level: 32

Type: WARNING

Impact: Other

ODI-20158: ODI-20158: Datastores distribution failed.
Cause: An error occured during the datastore distribution process.
Action: Review the message details and message log for more information. If problem persists contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20159: ODI-20159: The Column {0} is used as a Reference
Cause: An attempt was made to delete a column referenced by another object.
Action: Delete the object which references this column then retry deleting this column.

Level: 32

Type: ERROR

Impact: Other

ODI-20160: ODI-20160: The table {0} does not exist.
Cause: An error occured while executing the SQL request
Action: Review the message details for more information. If problem persists contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20161: ODI-20161: Standard reverse-engineering failed.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20162: ODI-20162: The context is not valid.
Cause: A Context was not specified.
Action: Specify a Context.

Level: 32

Type: ERROR

Impact: Other

ODI-20163: ODI-20163: Unable to add object
Cause: An error occurred while dragging and dropping an object.
Action: Review the message details and message log for more information.

Level: 32

Type: ERROR

Impact: Other

ODI-20164: ODI-20164: The line Name is mandatory
Cause: A name was not specified.
Action: Specify a Line name.

Level: 32

Type: ERROR

Impact: Other

ODI-20165: ODI-20165: The project name {0} is a reserved word.
Cause: A reserved word was used as the name of a project.
Action: Enter a different project name.

Level: 32

Type: ERROR

Impact: Other

ODI-20166: ODI-20166: The project code {0} is a reserved word.
Cause: A reserved word was used as the project code.
Action: Enter a different project code.

Level: 32

Type: ERROR

Impact: Other

ODI-20167: ODI-20167: Logical schema is not set for the current context
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20168: ODI-20168: Logical schema is not set for the current context
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20169: ODI-20169: The field {0} is mandatory.
Cause: A mandatory field was not specified.
Action: Enter a value for this field.

Level: 32

Type: ERROR

Impact: Other

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.
Cause: The requested version of the object did not exist in the repository.
Action: Recreate the required version of this object.

Level: 32

Type: ERROR

Impact: Other

ODI-20171: ODI-20171: The solution already contains a child of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.
Cause: The solution already contained the specified object as a child.
Action: Delete the child object from the solution before retrying the addition. Consider using the synchronize option to verify the solution's coherence.

Level: 32

Type: ERROR

Impact: Other

ODI-20172: ODI-20172: The solution already contains a parent of {0}. To add {1} to the solution, you should delete {2} {3}. It is advised to use the button "synchronize" later to check the solution's coherence.
Cause: The solution has already contained the specified object as a parent of {0}.
Action: Delete the parent object from the solution before retyring the addition. Consider using the synchronize option to verify the solution's coherence.

Level: 32

Type: ERROR

Impact: Other

ODI-20173: ODI-20173: An error occurres while generating the procedure
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20174: ODI-20174: Folder {0} already contains an interface named {1}
Cause: An interface of the same name already existed in the specified folder.
Action: Specify another name for the interface.

Level: 32

Type: ERROR

Impact: Other

ODI-20175: ODI-20175: You cannot give an empty name to an interface
Cause: The Interface's name was not specified.
Action: Enter a non-empty value for the interface's name.

Level: 32

Type: ERROR

Impact: Other

ODI-20176: ODI-20176: You cannot create multiple interfaces with the same name
Cause: An interface of the same name already existed.
Action: Specify a different name for the interface.

Level: 32

Type: ERROR

Impact: Other

ODI-20177: ODI-20177: You must select a generation folder
Cause: The Generation folder was not selected.
Action: Select a generation folder.

Level: 32

Type: ERROR

Impact: Other

ODI-20178: ODI-20178: Folder {0} already contains an interface named {1}
Cause: An interface of the same name already existed in the specified folder.
Action: Specify another name for the interface.

Level: 32

Type: ERROR

Impact: Other

ODI-20179: ODI-20179: You cannot create multiple interfaces with the same name
Cause: An interface of the same name already existed.
Action: Specify a different name for the interface.

Level: 32

Type: ERROR

Impact: Other

ODI-20180: ODI-20180: You cannot choose an expiration date in the past.
Cause: Entered expiration date was in the past.
Action: Enter valid expiration date.

Level: 32

Type: ERROR

Impact: Other

ODI-20181: ODI-20181: You cannot set an expiration date if there is no password.
Cause: No password was entered.
Action: Enter a password before setting an expiration date.

Level: 32

Type: ERROR

Impact: Other

ODI-20182: ODI-20182: Error while opening window
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20183: ODI-20183: Error while refreshing Solution
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20184: ODI-20184: The request to retrieve the sequence list has not been defined on the technology.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20185: ODI-20185: Error while opening window
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20186: ODI-20186: Error while saving
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20187: ODI-20187: Error while adding the marker
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20188: ODI-20188: This object is locked by another user. You cannot edit its markers.
Cause: The object was locked by another user.
Action: Wait until the object is unlocked. Consider contacting the user who has the object locked.

Level: 32

Type: ERROR

Impact: Other

ODI-20189: ODI-20189: You do not have the sufficient privileges to reverse-engineer a model
Cause: The model could not be reverse-engineered due to insufficient privileges.
Action: Ensure the SUPERVISOR or owner of model grants the appropriate permissions.

Level: 32

Type: ERROR

Impact: Other

ODI-20190: ODI-20190: You cannot reverse engineer a model in 'Standard' mode: the model technology assumes RKM to be selected.
Cause: No RKM was specified for this model.
Action: Select an RKM for this model.

Level: 32

Type: ERROR

Impact: Other

ODI-20191: ODI-20191: The model you want to reverse-engineer references a logical schema that no longer exists.
Cause: The referenced Logical Schema for the Model was not found.
Action: Ensure a valid Logical Schema is assigned for the Model.

Level: 32

Type: ERROR

Impact: Other

ODI-20192: ODI-20192: Error while replacing versioned object
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20193: ODI-20193: An error occurred during the versioning operation.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20194: ODI-20194: Your license does not allow Versioning operations.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20195: ODI-20195: Unable to unlock this object
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20196: ODI-20196: You must select an object version
Cause: No version selected for checkout.
Action: Select version for checkout.

Level: 32

Type: ERROR

Impact: Other

ODI-20197: ODI-20197: Your license does not allow Versioning operations.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20198: ODI-20198: Error while creating the version.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20199: ODI-20199: Your license does not allow Versioning operations.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20200: ODI-20200: An error happened while comparing the versions
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20201: ODI-20201: Errror while refreshing.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20202: ODI-20202: Synchronisation was stopped by the user.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20203: ODI-20203: The current version for this object no longer exists. Please create a new version for this object.
Cause: The current version for this object was not found in the repository.
Action: Create a new version for this object.

Level: 32

Type: ERROR

Impact: Other

ODI-20205: ODI-20205: Could not delete object. This object is being used.
Cause: The object deletion failed because it was already in use.
Action: Remove the usage of the selected object before retrying the deletion.

Level: 32

Type: ERROR

Impact: Other

ODI-20206: ODI-20206: Could not delete object. This object is being displayed.
Cause: The object deletion failed because it was being displayed.
Action: Close object before retrying the deletion.

Level: 32

Type: ERROR

Impact: Other

ODI-20208: ODI-20208: A code was duplicated:
Cause: A Flex field with the same code already existed.
Action: Enter another Flex field code.

Level: 32

Type: ERROR

Impact: Other

ODI-20209: ODI-20209: An error occurred.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20210: ODI-20210: Error When Printing...
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20211: ODI-20211: Error When Displaying Node...
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20212: ODI-20212: An error occurred while checking errors
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20213: ODI-20213: An error occurred while recovering an object in a node
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20214: ODI-20214: An error occurred while deleting
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20216: ODI-20216: Error while deleting
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20217: ODI-20217: Error while executing the reverse-engineering
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20218: ODI-20218: Error during duplication ...
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20219: ODI-20219: Error while opening
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20220: ODI-20220: Error during data loading ....
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20221: ODI-20221: Error during execution ...
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20222: ODI-20222: Error during scenario creation ...
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20223: ODI-20223: Error When Purging Log
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20224: ODI-20224: An interface with the same name already exists in this folder. Please change the name of the new interface.
Cause: An interface with the same name already existed in this folder.
Action: Specify another name for the interface.

Level: 32

Type: ERROR

Impact: Other

ODI-20225: ODI-20225: Error while creating the popup menu
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20226: ODI-20226: Error while applying the changes
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20227: ODI-20227: You cannot copy this column. Column name already in use.
Cause: Column copy failed because the Datastore already contained a column with the same name.
Action: Select another column to drop to datastore.

Level: 32

Type: ERROR

Impact: Other

ODI-20228: ODI-20228: Error while creating the popup menu
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20229: ODI-20229: Unable to create condition.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20230: ODI-20230: Error while creating the popup menu
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20231: ODI-20231: Unable to create a synonym for this table.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20232: ODI-20232: Error while deleting columns
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20233: ODI-20233: Error during the drag-and-drop operation
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20234: ODI-20234: You do not have the sufficient privileges to add this object.
Cause: The operation failed due to insufficient ODI security on Column.
Action: Ensure the ODI user security permissions are correct specifically the Column Duplication setting.

Level: 32

Type: ERROR

Impact: Other

ODI-20235: ODI-20235: Error during the drag-and-drop operation
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20236: ODI-20236: You do not have the sufficient privileges to add this object.
Cause: The operation failed due to insufficient ODI security on Datastore.
Action: Ensure the ODI user security permissions are correct.

Level: 32

Type: ERROR

Impact: Other

ODI-20237: ODI-20237: Unable to duplicate the column.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20238: ODI-20238: Unable to duplicate the table.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20239: Error during the action
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20240: ODI-20240: Error while deleting
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20241: ODI-20241: Unable to apply changes.
Cause: The changes to the filter could not be applied.
Action: Save the object before retrying to apply the filter.

Level: 32

Type: ERROR

Impact: Other

ODI-20242: ODI-20242: Error while creating the popup menu
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20243: ODI-20243: Unable to add column.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20244: ODI-20244: Unable to add reference
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20245: ODI-20245: Unable to add table
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20246: ODI-20246: Error while applying the changes
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20247: ODI-20247: Unable to add key.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20248: ODI-20248: Error while opening window
Cause: The editor could not be opened.
Action: Save the object before retrying the edit.

Level: 32

Type: ERROR

Impact: Other

ODI-20249: ODI-20249: Error while creating the popup menu
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20250: ODI-20250: Error while
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20251: ODI-20251: An unexpected error has occurred
Cause: Unable to acess the Security Authorization settings.
Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.

Level: 32

Type: ERROR

Impact: Other

ODI-20252: ODI-20252: Unable to apply changes.
Cause: Saving the model condition failed.
Action: Ensure the repository database connection is not broken and the ODI Security permissions are correct.

Level: 32

Type: ERROR

Impact: Other

ODI-20253: ODI-20253: The object was deleted by another user
Cause: The operation could not be performed because the specified object could not found.
Action: Refresh the view and retry the operation.

Level: 32

Type: ERROR

Impact: Other

ODI-20254: ODI-20254: The marker was deleted by another user
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20255: ODI-20255: Marker name is mandatory
Cause: Marker could not be saved because the mandatory Name field was not entered.
Action: Enter a value in the Marker name field.

Level: 32

Type: ERROR

Impact: Other

ODI-20256: ODI-20256: You do not have the sufficient privileges to change the marker
Cause: Modification of the Marker failed due to insufficient ODI security priveleges.
Action: Ensure the ODI user security permissions are correct.

Level: 32

Type: ERROR

Impact: Other

ODI-20257: ODI-20257: The Where text is mandatory when the Filter is active for a static control.
Cause: The WHERE clause was null or empty.
Action: Ensure the WHERE clause is valid.

Level: 32

Type: ERROR

Impact: Other

ODI-20258: ODI-20258: It is not possible to check the expression due to DBMS connection failure
Cause: Connection to the DBMS failed.
Action: Ensure the DBMS is available and the connection information to it is correctly specified.

Level: 32

Type: ERROR

Impact: Other

ODI-20259: ODI-20259: cannot show the data since the join points to different connections
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20260: ODI-20260: Name and Code columns of the FlexField cannot be empty.
Cause: FlexField name or code were found to be empty or null.
Action: Enter a name and a code for the FlexField.

Level: 32

Type: ERROR

Impact: Other

ODI-20261: ODI-20261: The "Procedure Name" is mandatory.
Cause: The "Procedure Name" field value was not specified.
Action: Enter a value for the "Procedure Name" field.

Level: 32

Type: ERROR

Impact: Other

ODI-20300: ODI-20300: Error while printing the diagram
Cause: An unexpected condition has occurred in the print system.
Action: Check the printer settings and physical printer.

Level: 32

Type: ERROR

Impact: Other

ODI-20301: ODI-20301: Error while saving the diagram
Cause: The save file could not be created.
Action: Check the destination folder is writable and that their is sufficient disk space.

Level: 32

Type: ERROR

Impact: Other

ODI-20310: Unsupported Flavor
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20311: ODI-20311: An unexpected exception occurred while reading or writing a text in a business object. Please contact Oracle technical support.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20312: ODI-20312: An error occurred while printing.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20313: ODI-20313: Could not double click
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20315: ODI-20315: Invalid Password
Cause: The Password is incorrect.
Action: Correct the password and try again.

Level: 32

Type: ERROR

Impact: Other

ODI-20316: ODI-20316: A timeout occured while trying to establish a connection.
Cause: A timeout error occurred while connecting to the database.
Action: Verify that the Database Connection details are correct and the database is availble.

Level: 32

Type: ERROR

Impact: Other

ODI-20317: ODI-20317: The field "{0}" is mandatory.
Cause: A value has not been provided for a required field.
Action: Enter a value for the named field.

Level: 32

Type: ERROR

Impact: Other

ODI-20318: ODI-20318: The icon {0} cannot be found.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20319: ODI-20319: {0} is not a valid date for field {1}. The format is: {2}
Cause: The format of the date does not match the required format.
Action: Enter a valid date using the correct date format.

Level: 32

Type: ERROR

Impact: Other

ODI-20320: ODI-20320: Error when applying changes.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20321: ODI-20321: Error when initializing the panel.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20322: ODI-20322: Unable to add a Step.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20323: ODI-20323: Unable to execute the step
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20324: ODI-20324: Cannot execute the Package
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20325: ODI-20325: Unable to open the linked object.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20326: ODI-20326: Unable to edit the text
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20327: ODI-20327: Unable to modify the value.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20328: ODI-20328: Unable to define the next Step.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20329: ODI-20329: Unable to delete Steps(s). You do not have Edit privileges.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20330: ODI-20330: Unable to delete Link(s). You do not have Edit privileges.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20331: ODI-20331: The Step diagram is not be accessible.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20332: ODI-20332: Cannot change the position of this object
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20333: ODI-20333: Cannot view this Step because the Package is being edited
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20335: ODI-20335: Printing Options not accessible.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20336: ODI-20336: Unknown event sent to the Package event manager.
Cause: An unexpected error has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20337: ODI-20337: A Knowledge Module cannot be added as a Step.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20338: ODI-20338: A starting Step must be defined.
Cause: A Starting step has been defined.
Action: Select the first step in the package and mark is the starting step.

Level: 32

Type: ERROR

Impact: Other

ODI-20339: ODI-20339: One or more Steps are not linked.
Cause: All steps must be linked.
Action: Ensure that all steps are linked .

Level: 32

Type: ERROR

Impact: Other

ODI-20340: ODI-20340: Only one starting Step can be defined.
Cause: A package must have one and only one starting steps.
Action: Ensure that you have only one starting step defined .

Level: 32

Type: ERROR

Impact: Other

ODI-20341: ODI-20341: You don't have the appropriate privileges.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-20342: ODI-20342: Cannot open the Expression Editor
Cause: An unexepected error has occured.
Action: Contact Oracle Support Sevices.

Level: 32

Type: ERROR

Impact: Other

ODI-20343: ODI-20343: There are errors in your diagram
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20344: ODI-20344: Cannot launch the editor for this expression
Cause: An error occured while rerieving 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.

Level: 32

Type: ERROR

Impact: Other

ODI-20345: ODI-20345: Cannot change the clause position
Cause: An unexpected internal exception has occured.
Action: Contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-20346: ODI-20346: Cannot get the boolean value of an option
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20347: ODI-20347: Error during data transfer for drag and drop
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20348: ODI-20348: An interface with the same name already exists in this folder. Please change the name of the new interface.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20349: ODI-20349: Unknown event detected by the event manager. Please contact Oracle Support Services.
Cause: The Package Event Manager was called to action an unknown event.
Action: Contact Oracle Support Services for further assistance.

Level: 32

Type: ERROR

Impact: Other

ODI-20350: ODI-20350: Your diagram contains one or more FATAL/CRITICAL errors preventing display of the Flow Editor
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20351: ODI-20351: Error adding source to Quick Edit source table.
Cause: An internal error occured which prevented the source being added.
Action: Contact Oracle Support Services for further assistance.

Level: 32

Type: ERROR

Impact: Other

ODI-20352: ODI-20352: Error adding target datastore to Quick Edit mapping table.
Cause: An internal error occured which prevented the target being added.
Action: Contact Oracle Support Services for further assistance.

Level: 32

Type: ERROR

Impact: Other

ODI-20353: ODI-20353: Only a single column may be pasted into a Quick Edit table.
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.

Level: 32

Type: ERROR

Impact: Other

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).
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20355: ODI-20355: Duplicate value is not supported on this column.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20356: ODI-20356: Can not perform paste into a read-only column.
Cause: The Paste operation is not permitted on read-only columns.
Action: You may not update this value in the table.

Level: 32

Type: ERROR

Impact: Other

ODI-20357: ODI-20357: Can not perform deletion because the target datastore is not temporary.
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 temportay target table may be deleted.
Action: You cannot delete the row.

Level: 32

Type: ERROR

Impact: Other

ODI-20358: ODI-20358: Interface cannot be saved because it has a fatal error: {0}.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20359: ODI-20359: Only one cell can be copied one at a time.
Cause: More than one cell was selected. Quick Edit only supports copying a single cell.
Action: Select and copy a single cell.

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-20370: ODI-20370 : Interface, procedure and package shortcuts within a project can only refer to interfaces, procedures and packages that belong to that same project
Cause: Interface, procedure and package shortcuts within a project can only refer to interfaces, procedures and packages that belong to that same project
Action: =Try another folder destination

Level: 32

Type: ERROR

Impact: Other

ODI-20371: ODI-20371 : No two shortcut objects within a folder may refer to the same base object
Cause: No two shortcut objects within a folder may refer to the same base object
Action: Try another folder destination or fix folder contents

Level: 32

Type: ERROR

Impact: Other

ODI-20372: ODI-20372 : The source and destination models must be defined with the same Technology
Cause: The source and destination models must be defined with the same Technology
Action: Try another model destination or fix model properties.

Level: 32

Type: ERROR

Impact: Other

ODI-20373: ODI-20373 : No two shortcuts within a model may contain the same base object
Cause: No two shortcuts within a model may contain the same base object
Action: Try another folder destination or fix model contents.

Level: 32

Type: ERROR

Impact: Other

ODI-20374: ODI-20374 : A model cannot contain a datastore and a shortcut to another datastore with the same table name
Cause: A model cannot contain a datastore and a shortcut to another datastore with the same table name
Action: Try another folder destination or fix model contents.

Level: 32

Type: ERROR

Impact: Other

ODI-20701: ODI-20701: The Name field is mandatory.
Cause: The Name field was not entered.
Action: Enter a name for the Load Plan.

Level: 32

Type: ERROR

Impact: Other

ODI-20702: ODI-20702: The name given for the Load Plan is already used by another load plan. Please provide another name.
Cause: The name provided for the Load Plan was not unique.
Action: Enter a unique name for the Load Plan.

Level: 32

Type: ERROR

Impact: Other

ODI-20703: ODI-20703: Variable "{0}" is not found.
Cause: The variable could not be found.
Action: Provide another name for the variable.

Level: 32

Type: ERROR

Impact: Other

ODI-20704: ODI-20704: Datatype of variable "{0}" has been changed.
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 pln varibles match.

Level: 32

Type: ERROR

Impact: Other

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?
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.

Level: 32

Type: WARNING

Impact: Other

ODI-20706: ODI-20706: The Step Name is mandatory.
Cause: The Step Name field was not entered.
Action: Enter a name for the Step.

Level: 32

Type: ERROR

Impact: Other

ODI-20707: ODI-20707: The Variable is mandatory.
Cause: A Variable was not selected.
Action: Select a variable.

Level: 32

Type: ERROR

Impact: Other

ODI-20708: ODI-20708: The Scenario is mandatory.
Cause: A Scenario was not selected.
Action: Select a Scenario.

Level: 32

Type: ERROR

Impact: Other

ODI-20709: ODI-20709: The Value is mandatory.
Cause: A Value was not provided.
Action: Enter a Value.

Level: 32

Type: ERROR

Impact: Other

ODI-20710: ODI-20710: The Value format is not valid.
Cause: An incorrect format was given for the Value.
Action: Check the format of the Value and correct it.

Level: 32

Type: ERROR

Impact: Other

ODI-20711: ODI-20711: The Step Name is mandatory.
Cause: The Step Name field was not entered.
Action: Provide the name of the Step.

Level: 32

Type: ERROR

Impact: Other

ODI-20712: ODI-20712: The Variable is mandatory.
Cause: A Variable was not selected.
Action: Select a Variable.

Level: 32

Type: ERROR

Impact: Other

ODI-20713: ODI-20713: The Scenario is mandatory.
Cause: A Scenario was not selected.
Action: Select a Scenario.

Level: 32

Type: ERROR

Impact: Other

ODI-20714: ODI-20714: The Context is mandatory.
Cause: A Context was not selected for execution.
Action: Select an execuion Context.

Level: 32

Type: ERROR

Impact: Other

ODI-20715: ODI-20715: The Logical Agent is mandatory.
Cause: A Logical Agent was not selected for execution.
Action: Select a Logical Agent.

Level: 32

Type: ERROR

Impact: Other

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}".
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20717: ODI-20717: No Physical Agents are running. A Physical Agent must be running in order to Restart a Load Plan.
Cause: There were no Physical Agents running.
Action: Start a Physical Agent before restarting the Load Plan.

Level: 32

Type: ERROR

Impact: Other

ODI-20718: ODI-20718: No Physical Agents are running. A Physical Agent must be running in order to Stop a Load Plan.
Cause: There were no Physical Agents running.
Action: Start the Agent before executing the Load Plan.

Level: 32

Type: ERROR

Impact: Other

ODI-20719: ODI-20719: Scenario "{0}" is not found.
Cause: The scenario was not found.
Action: Specify an existing scenario.

Level: 32

Type: ERROR

Impact: Other

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.
Cause: The Physical Agent was not reachable.
Action: Check the Physical Agent and start it.

Level: 32

Type: ERROR

Impact: Other

ODI-20721: ODI-20721: Interface contains one or more errors. You should correct the errors before attempting to execute it
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.

Level: 32

Type: ERROR

Impact: Other

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.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-20723: ODI-20723: There is no any version of scenario {0} found. A scenario of the step {1} cannot be refreshed.
Cause: The scenario of step was not found.
Action: Check if specified scenario for this step is correct.

Level: 32

Type: WARNING

Impact: Other

ODI-20724: ODI-20724: Journalized data not found. Journal data view: {0}
Cause: Journal is not started or is stopped.
Action: Ensure the journal is started: select Changed Data Capture > Journal Data.

Level: 32

Type: ERROR

Impact: Other

ODI-20726: ODI-20726: The Step Name is mandatory.
Cause: The Step Name field was not entered.
Action: Enter a name for the Step.

Level: 32

Type: WARNING

Impact: Other

ODI-20727: ODI-20727: Scenario "{0}" parent is not found.
Cause: The Scenario source object does not exist.
Action: Check if the source object, from which the Scenario was generated, does exist.

Level: 32

Type: ERROR

Impact: Other

ODI-20728: ODI-20728: The column name is mandatory
Cause: The datastore column could not be saved because the mandatory Name field was not entered.
Action: Enter a value in the column name field.

Level: 32

Type: ERROR

Impact: Other

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.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23001: ODI-23001: The import process failed
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23006: ODI-23006: Agent Test failed
Cause: Agent could not be contacted using the specified connection details.
Action: Ensure the Agent connection details are correct and the Agent is running.

Level: 32

Type: ERROR

Impact: Other

ODI-23007: ODI-23007: Data Source already exists for "{0}".
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23010: ODI-23010: Please enter first a name, an expression and a help text for this language element.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23011: ODI-23011: Name is empty
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23012: ODI-23012: Expression is empty
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23013: ODI-23013: Help is undefined
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23014: ODI-23014: Technology is undefined
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23015: ODI-23015: Logical Schema {0} is already linked to a physical schema in context {1}.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23016: ODI-23016: The context is either invalid or no longer exists in the database.
Cause: One of the Contexts used by the Physical Schema is invalid or no longer exisits 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.

Level: 32

Type: ERROR

Impact: Other

ODI-23017: ODI-23017: This Physical Schema already exists for this data server.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23018: ODI-23018: Unable to connect to Work Repository
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23019: ODI-23019: Error Detected during Repository Installation. Invalid connection parameters.
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 the problem persists then contact Oracle Support Services.

Level: 32

Type: ERROR

Impact: Other

ODI-23020: ODI-23020: Error Detected during Repository Installation. Invalid External Authentication credentials.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23021: ODI-23021: Error Detected during Repository Installation. Invalid External Authentication configuration.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23022: ODI-23022: An error occurred during the generation of the Data Service.
Cause:
Action:

Level: 32

Type: ERROR

Impact: Other

ODI-23023: ODI-23023: The Schema path ({0}) is not supported
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23024: ODI-23024: The URL is mandatory.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23025: ODI-23025: The ID is mandatory.
Cause: The Repository ID parameter has not been entered and is a mandatory parameter.
Action: Enter an integer value for the Repository ID parameter.

Level: 32

Type: ERROR

Impact: Other

ODI-23026: ODI-23026: The ID must be an integer value.
Cause: The value entered for the Repository ID is not a valid integer.
Action: Enter an integer value for the Repository ID parameter.

Level: 32

Type: ERROR

Impact: Other

ODI-23027: ODI-23027: The driver is mandatory.
Cause: A JDBC Driver was not specified and is a mandatory parameter.
Action: Select a JDBC Driver from the list of values.

Level: 32

Type: ERROR

Impact: Other

ODI-23028: ODI-23028: The password is mandatory.
Cause: The Supervior user's Password parameter was not specified.
Action: Enter the Supervisor password.

Level: 32

Type: ERROR

Impact: Other

ODI-23029: ODI-23029: The confirm password is mandatory.
Cause: The Supervisor user's Confirm Password parameter was not specified.
Action: Enter the Supervisor user's password in the Confirm Password parameter.

Level: 32

Type: ERROR

Impact: Other

ODI-23030: ODI-23030: Password and Confirm Password are different
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23031: ODI-23031: The Supervisor username is mandatory.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23032: ODI-23032: Maximum number of sessions cannot be less or equal to 0.
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23033: ODI-23033: The file reverse-engineering is only possible for delimited files.
Cause: The file format for the specified file was not delimited.
Action: Select a delimited format file and retry the reverse-engineering action.

Level: 32

Type: ERROR

Impact: Other

ODI-23035: ODI-23035: Can not update the scheduling - This agent may not be running
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.

Level: 32

Type: ERROR

Impact: Other

ODI-23036: ODI-23036: Logical Schema not set for this Context
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>.

Level: 32

Type: ERROR

Impact: Other

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
Cause: There are no logical agents available to use for scheduling.