58 ODI-01200 to ODI-03278

ODI-01200: The session failed: 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: The session failed to start on agent {0}: JDBC connection error while connecting to the master repository: Cause: Incorrect connection for the master repository database, or repository database is down.; Action: Verify the master repository connection information and the status of the master repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01202: The session failed to start on agent {0}: data source for master repository does not contain a master repository: Cause: The master repository connection information points to a database schema that does not contain a master repository.; Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01203: The session failed to start on agent {0}: the master repository is in an invalid state: Cause: The master repository is in a state that does 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-01204: The session failed to start 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: The session failed to start on agent {0}: an authentication error occurred while connecting to the master repository: Cause: The ODI user or password is incorrect for this master repository.; Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01206: The session failed to start on agent {0}: the agent is not defined in the topology for master repository: Cause: The session has not been found in the repository.; Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01207: The session failed to start on agent {0}: JDBC connection error while connecting to the work repository {1}: Cause: Incorrect connection for the work repository database, or repository database is down.; Action: Verify the work repository connection information and the status of the work repository database.
Level: 1

Type: ERROR

Impact: Other

ODI-01208: The session failed to start on agent {0}: database schema {1} does not contain a work repository: Cause: The work repository connection information points to a database schema that does not contain a work repository.; Action: Verify the work repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01209: The session failed to start on agent {0}: work repository {1} is in an invalid state: Cause: The work repository is in a state that does 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-01210: The session failed to start 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: The session failed to start on agent {0}: work repository {1} is not bound to the master repository: Cause: The work repository specified in the request is 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: The session could not be prepared: scenario {0} does not exist in work repository {1}: Cause: The session request was received, but the agent is 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: The session could not be prepared: scenario {0} version {1} does not exist in work repository {2}: Cause: The session request was received, and the scenario exists in the work repository, but not with the specified version; Action: Verify that the scenario version matches an existing scenario version in the work repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01214: The session could not be prepared: context {0} does not exist in the master repository.: Cause: The session request was received, but the agent is unable to find the context in the master repository; Action: Verify that the context matches an existing context code in the Topology.
Level: 1

Type: ERROR

Impact: Other

ODI-01215: The session could not be prepared: insufficient privileges to run scenario {0}.{1} in repository {2}.: Cause: User privileges are not sufficient for running this scenario in this repository.; Action: Verify the user privileges.
Level: 1

Type: ERROR

Impact: Other

ODI-01216: The session could not be prepared: insufficient privileges to use Context {0} ({1}).: Cause: User privileges are not sufficient for using this context.; Action: Verify the user privileges.
Level: 1

Type: ERROR

Impact: Other

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

Type: ERROR

Impact: Other

ODI-01218: The session could not be prepared: database error while connecting to the master repository.: Cause: The agent has 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: The session could not be prepared: database error while connecting to work repository {0}: Cause: The agent has 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: The session could not be prepared: an unexpected exception occurred.: Cause: The remote agent has 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 was not found in work repository {1}: Cause: The session to restart does not exist in the repository. This session may have been deleted, the session ID or work repository provided may be incorrect.; Action: Verify that a session with this ID exists in the repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01222: The session failed to start on agent {0}: logical schema {1} cannot be found in the master repository: Cause: The object that you are trying to execute refers to a logical schema that does not exist in the master repository.; Action: Verify that logical schema configuration in your master repository.
Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.: Cause: Incorrect connection for the master repository database, or repository database is 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: Incorrect connection for the work repository database, or repository database is 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 occurered: Cause: The agent has faced an unexpected error.; 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} failed after {1} attempt(s): Cause: This is an execution warning. The session step has failed to execute after the maximum number of retries. If step failure is not handled in the package design, the session finishes in 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}) failed on the source {2} connection {3}: Cause: This is an execution warning. The command on the source for this task has 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}) failed on the target {2} connection {3}: Cause: This is an execution warning. The command on the target for this task has 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 {1}: Cause: This is an execution warning. The operation specified has 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 has 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 failed.: Cause: This is an execution warning. The procedure execution has 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 has 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 has 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 has 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 variable setting has failed.; Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} has failed because the maximum number of allowed errors ({1} rows) was exceeded during the flow check. This flow loads target table {2}: Cause: This is an execution warning. The interface has 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} has failed because the maximum percentage of allowed errors ({1} %) was exceeded during the flow check. This flow loads target table {2}: Cause: This is an execution warning. The interface has 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} has failed while performing a {1} operation. This flow loads target table {2}.: Cause: This is an execution warning. The interface has 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 failed.: Cause: This is an execution warning. The tool execution has 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 failed.: Cause: This is an execution warning. Execution of the operating system command has 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}) failed 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01244: The session {0} {1} was prepared successfully but session failed 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01245: The session could not be prepared: 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.: Cause: The logical schema is not set and this object cannot 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: The session {0} {1} was prepared successfully but session failed 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01248: The session could not be prepared 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) failed 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 needs to be restarted.
Level: 1

Type: ERROR

Impact: Other

ODI-01400: Agent {0} is unable to start: JDBC connection error while connecting to the master repository: Cause: Incorrect connection for the master repository database, or repository database is 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} is unable to start: data source for master repository does not contain a master repository: Cause: The master repository connection information points to a database schema that does not contain a master repository.; Action: Verify the master repository connection information.
Level: 1

Type: ERROR

Impact: Other

ODI-01402: Agent {0} is unable to start: the master repository is in an invalid state: Cause: The master repository is in a state that does 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} is unable to start: 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} is unable to start: an authentication error occurred while connecting to the master repository: Cause: The ODI user or password is incorrect for this master repository.; Action: Verify the ODI user and password used for connecting.
Level: 1

Type: ERROR

Impact: Other

ODI-01405: Agent {0} is unable to start: the agent is not defined in the topology for master repository: Cause: This agent is 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 while connecting to the work repository in schema {1}: Cause: Incorrect connection for the work repository database, or repository database is 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} does not contain a work repository: Cause: The work repository connection information points to a database schema that does not contain a work repository.; Action: Verify the work repository connection information.
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 is in a state that does 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 is 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-01411: Agent {0} started with warning: a database error occurred while cleansing stale sessions.: Cause: The agent has encountered a database error while attempting to close stale sessions.; Action: Verify 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 occurred while cleaning stale sessions: Cause: The agent has 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 was 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-01414: Error connecting to agent {0}: a JDBC error occurred while connecting to the master repository: Cause: The remote agent has incorrect connection for the master repository database, or repository database is 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 does not contain a master repository: Cause: The master repository connection information for the remote agent points to a database schema that does not contain a master repository.; Action: Verify the master repository connection information.
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 is in a state that does 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 occurred while connecting to the master repository: Cause: The ODI user or password is incorrect 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 while connecting to the work repository {1}: Cause: The remote agent has incorrect connection for the work repository database, or repository database is 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} does not contain a work repository: Cause: The work repository connection information for the remote agent points to a database schema that does 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 is in a state that does 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 is 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 could not be reached using {0}: Cause: Incorrect host/port information was provided, or the agent is not started on the remote host.; Action: Verify the host/port information or Verify the agent status.
Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application could not be reached using {0}: Cause: An incorrect application name is provided for this agent, or the agent application is not started on the host.; Action: Verify 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 master repository: Cause: This agent is 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-01427: Invalid parameters.: Cause: The parameters supplied in the request are invalid.; 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: An internal error occurred: Cause: This message indicates an agent internal error.; 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: User privileges are not sufficient for performing this request against the remote agent.; Action: Verify the user privileges.
Level: 1

Type: ERROR

Impact: Other

ODI-01430: The agent {0} failed to clean the stale sessions in work repository {1} due to database error: Cause: The remote agent has faced a database error while attempting to close stale sessions.; Action: Verify the status of the sessions for this agent, and manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01431: The agent {0} failed to 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: Verify the status of the repository. Once this repository is running, manually remove the stale sessions.
Level: 1

Type: ERROR

Impact: Other

ODI-01432: The agent {0} failed to clean the stale sessions in work repository {1} due to an unexpected error thrown: Cause: The remote agent has 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). Verify 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: Please 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} is unable to start: error while trying to use JMX Port {1}: Cause: JMX Registry is unable to use the given port; Action: Please 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. Please consider creating a new repository for the following object types (Object Type: Number Remaining) {1}: Cause: Storage space is low for some IDs in this repository.; Action: Please consider creating a new repository.
Level: 1

Type: WARNING

Impact: Other

ODI-01436: Error retreiving ID statistics for repository {0}: Cause: Cannot verify the ID statistics for this repository.; Action: Please verify the statistics for this repository manually.
Level: 1

Type: WARNING

Impact: Other

ODI-01437: Error retrieving information from the credential store map: Cause: Cannot retrieve information from the credential store map.; Action: Please verify that the credentials have been entered correctly into the credential store map.
Level: 1

Type: ERROR

Impact: Other

ODI-01438: The Agent {0} could not be stopped by user {1}: a JDBC error occurred on master repository {2}: Cause: Some SQL Exception occurred on the Master Repository; Action: Please verify that other operations on the Agent are working fine.
Level: 1

Type: ERROR

Impact: Other

ODI-01439: The Agent {0} could not be stopped by user {1}: a JDBC error occurred on work repository {2}: Cause: Some SQL Exception occurred on the Work Repository; Action: Please verify that other operations on the Agent are working fine.
Level: 1

Type: ERROR

Impact: Other

ODI-01440: The Agent {0} could not be stopped by user {1}: an unknown error occurred: Cause: An unexpected Exception occurred; Action: Please verify your Agent configuration and make sure other operations on Agent are working properly.
Level: 1

Type: ERROR

Impact: Other

ODI-03000: Error in creating repository connection {0}: Cause: Unknown cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03001: Error in creating repository connection {0}: Cause: Unknown cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03046: Unable to find the agent for given logical agent and context code.: Cause: Physical Agent mapping is not defined for selected logical agent and context; Action: None
Level: 1

Type: ERROR

Impact: Data

ODI-03047: Exception occured while executing {0}. Failure reason {1}.: Cause: Unknown cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03048: Only xml Files can be Uploaded, the {0} upload was unsuccessful.: Cause: File selected for import is not a xml file; Action: Provide the xml file
Level: 1

Type: ERROR

Impact: Data

ODI-03049: Exception occured while importing {0}. Failure reason {1}.: Cause: Unknown Cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03076: Exception occured while killing {0}. Failure reason {1}.: Cause: Unknown Cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03077: Selected Session {0} is in {1} State. Hence cannot be killed.: Cause: The selected session is in Done, Error or Warning state; Action: None
Level: 1

Type: ERROR

Impact: Data

ODI-03078: Selected Session {0} is in {1} State. Hence cannot be restarted.: Cause: The selected session is not in Error state; Action: None
Level: 1

Type: ERROR

Impact: Data

ODI-03079: Exception occured while restarting {0}. Failure reason {1}.: Cause: Unknown Cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03080: Exception occured while clearing stalesessions. Failure reason {0}.: Cause: Unknown Cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Programmatic

ODI-03276: No valid repository alias found. Please click on management link on top right corner to create one.: Cause: Either there are no repository connection aliases or those which were created do not have valid JNDI name; Action: Create new
Level: 1

Type: ERROR

Impact: Data

ODI-03277: Object could not be found. It is possible that object could have been deleted. Please refresh your view.: Cause: This is when a link is clicked and the object linked to it was deleted; Action: None
Level: 1

Type: ERROR

Impact: Data

ODI-03278: View operation failed with the following exception {0}.Please see the server log for details.: Cause: Unknown cause; Action: Check the logs
Level: 1

Type: ERROR

Impact: Data