21 ODI-01100 to ODI-999999
- 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 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-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-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-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-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-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-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 stopped.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer.
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-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-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-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-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-01283: Owb preparation failure: Owb object {0} of type {1} in location {2} does not exist in Owb repository {3}.
-
Cause: The session request was received, but the agent was unable to find the named Owb object in the Owb repository.
-
Action: Verify that the Owb object name matches an existing Owb object in the location in the Owb repository.
Level: 1
Type: ERROR
Impact: Other
- ODI-01285: Session {0} ({1}) Retreival of audit for auditId {2} failed in the {3} phase {4}. Please use OWB Design Client or Browser for further information.
-
Cause: An error was raised during the retreival of the Owb audit data.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1
Type: ERROR
Impact: Other
- ODI-01287: Session {0} ({1}) with Owb audit Id {2} is in an invalid state to be aborted.
-
Cause: The session being aborted is not in a state that can be aborted.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1
Type: ERROR
Impact: Other
- ODI-01288: Session {0} ({1}) with Owb audit Id {2} abort fails.
-
Cause: The session abort finished in an error state.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1
Type: ERROR
Impact: Other
- ODI-01289: Agent {0} detected Session as stale session and set to error status. Please use OWB Design Client or Browser for further information.
-
Cause: The agent detected a stale OWB session and the session status was set to error status.
-
Action: Review the session execution details in the OWB Design Client or Browser.
Level: 1
Type: ERROR
Impact: Other
- ODI-01290: Session {0} ({1}) Loading of audit for auditId {2} failed in the {3} phase {4}.
-
Cause: An error was raised during the loading of the Owb audit data.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Also please use OWB Design Client or Browser for further information.
Level: 1
Type: ERROR
Impact: Other
- ODI-01296: The Cleanup Tool encountered the following {0} nested errors when executing the Cleanup tasks: {1}
-
Cause: Messages were raised during the Cleanup tool execution.
-
Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.
Level: 1
Type: ERROR
Impact: Other
- 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-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-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-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-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-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-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-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-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-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-01444: The master repository signature specified by the client {0} does not match the master repository signature of the agent {1}.
-
Cause: The client and the agent are not using the same master repository
-
Action: Verify the client and the agent are using the same master repository. Verify that the client is calling the correct agent.
Level: 1
Type: ERROR
Impact: Other
- ODI-01460: Unable to insert into table {0} for concurrent execution control. Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem. Error message: {1}
-
Cause: An exception was raised when inserting a record into the concurrent execution control table.
-
Action: Exceptions due to competing insertions can happen and are handled to continue execution. Other exceptions likely indicate a runtime problem.
Level: 1
Type: WARNING
Impact: Other
- ODI-01461: {0} job status has changed unexpectedly from {1} to {2} while waiting for its turn to run under concurrent execution control.
-
Cause: The status of a job was likely changed outside of the control of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.
-
Action: The job may have been changed outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1
Type: WARNING
Impact: Other
- ODI-01462: {0} job [{1}] should be the last one in the following waiting {0} list: {2}
-
Cause: The job may have been changed or deleted outside of the runtime agent while the job was waiting for its turn to run under concurrent execution control by the agent.
-
Action: The job may have been changed or deleted outside of the agent, and the agent skipped the job execution. Start the job again if it was not executed.
Level: 1
Type: WARNING
Impact: Other
- ODI-01463: {0} job [{1}] blocked by the following {0} job(s) due to potential concurrent execution condition: {2}{3}
-
Cause: The job was under concurrent execution control with Raise Error violation behavior, and there were existing runnable and/or waiting jobs submitted ahead of the job.
-
Action: Start the job when other concurrently running and waiting jobs are completed, or change the job's violation behavior to Wait To Execute before starting the job.
Level: 1
Type: WARNING
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-01578: Invalid load plan log level value specified: {0}. A valid load plan log value is between {1} and {2}.
-
Cause: Invalid load plan log level value was supplied in the request.
-
Action: Check that the load plan log level value supplied was valid (1 - 6) for the request.
Level: 1
Type: ERROR
Impact: Other
- ODI-01579: Agent {0} start failure: data source for master repository did not contain a master repository using JDBC URL={1} with USER={2}.
-
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-01591: The ODI agent name {0} specified in the client request does not match with the ODI agent {1} serving the request.
-
Cause: The client and the agent are not using the same physical agent name.
-
Action: Verify the client and the agent are using the same agent name. Verify that the client is calling the correct agent.
Level: 1
Type: ERROR
Impact: Other
- ODI-01593: The following bind parameters ({0}) in the task command {1} are not bound to any value. All the bind parameters should be bound for the command to be successful.
-
Cause: Either the source command is not providing values for some of the bind parameters in target command or the Odi Variables and/or Odi Sequence meta-data is not generated for the Scenario.
-
Action: Verify that either the source command is correct or the Odi Variables and/or Odi Sequences meta-data is generated in the Scenario.
Level: 1
Type: ERROR
Impact: Other
- ODI-01616: DESCRIPTION Starts an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agent.(cmd|sh) -NAME=<agent name> [-PORT=<port>] [-PROTOCOL=<protocol>] [-JMXPORT=<jmxport>] [-ODI_CONNECTION_RETRY_COUNT=<nn>] [-ODI_CONNECTION_RETRY_DELAY=<nn>] PORT represents the listening port. It should match the port value specified against the physical agent defined in Topology. PROTOCOL represents the listening protocol, HTTP or HTTPS. Its default value is HTTP. NAME represents the name of this physical agent. It should match the name of a physical agent defined in Topology. User must have created an agent with this name using configuration wizard. JMXPORT represents the JMX port used for JMX notifications etc. Its default value is calculated as PORT + 1000, or 20810 if the calculated value is greater than 65535 ODI_CONNECTION_RETRY_COUNT represents the number of times a connection to the ODI Repository will be retried. Its default value is 10 ODI_CONNECTION_RETRY_DELAY represents the number of milliseconds between connection retries to the ODI Repository. Its default value is 7000
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01617: DESCRIPTION Stops an agent. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX agentstop.(cmd|sh) "-NAME=<agent name>" ["-AGENT_URL=<agent_url>"] ["-IMMEDIATE=<true(default)|false>" ["-MAX_WAIT=<stop timeout in millis>"]]
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01618: DESCRIPTION Restarts execution of a load plan instance. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartloadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"]
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01620: DESCRIPTION Starts a load plan. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startloadplan.sh "-INSTANCE=<instance_name>" <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01621: DESCRIPTION Starts a scenario. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startscen.(cmd|sh) "-INSTANCE=<instance_name>" <scenario_name> <scenario_version> <context_code> [<log_level>] ["-SESSION_NAME=<session_name>"] ["-KEYWORDS=<keywords>"] ["-AGENT_URL=<agent_url>"] ["-ASYNC=(no|yes)"] ["-DEBUGGABLE=(no|yes)"] ["-SUSPEND_FIRST_STEP=(no|yes)"] ["-DESCENDANTS_DEBUGGABLE=(no|yes)"] ["-BREAK_ON_ERROR=(no|yes)"] ["<variable>=<value>"]* -ASYNC=no is default; -ASYNC=yes is valid only if -AGENT_URL is specified.
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01622: DESCRIPTION Stops a load plan instance execution. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stoploadplan.(cmd|sh) "-INSTANCE=<instance_name>" <load_plan_instance_id> [<load_plan_run_count>] "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-01623: DESCRIPTION Stops the execution of a running session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX stopsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> "-AGENT_URL=<agent_url>" ["-STOP_LEVEL=<normal(default)|immediate>"]
-
Cause:
-
Action:
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- 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-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-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-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-03150: Invalid Context code. Context code cannot have lower case characters and white spaces. Though, it can contain '$' and '_' special characters.
-
Cause: A validation error occured
-
Action: Context code cannot have lower case characters and white spaces
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-05001: Session {0} ({1}) could not be stopped by Agent {2}: Session run on an 'Internal' agent cannot be stopped from another process.
-
Cause: Stopping a session being run by an internal agent from another process is not possible.
-
Action: Review the session execution details in the Operator Navigator or Repository Explorer.
Level: 1
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-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-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-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-10148: Repository is in error install/upgrade state and needs to be repaired. Connection has been disabled.
-
Cause: Repository install/upgrade did not complete successfully.
-
Action: Check install/upgrade log files and/or ODI user documentation for information on reparation process.
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-10161: Trying to create authentication with Subject parameter which should be applicable when OPSS authentication is used, but ODI shows it is using ODI internal authentication.
-
Cause: ODI internal authentication is used instead of OPSS authentication.
-
Action: Check authentication type.
Level: 32
Type: ERROR
Impact: Programmatic
- 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-10212: Parent object {0}: ''{1}'' already has child {2}: ''{3}''. Technical details: {2} : ''{3}'' (with global id: {7} and internal id: {8}) violates alternate key constraint {4} {5} for values {6}
-
Cause: Object violated alternate key constraint.
-
Action: Check object properties and constraint's values.
Level: 32
Type: ERROR
Impact: Other
- ODI-10213: Fixed format file field {0} (starts at {1} ends at {2}) has a file position that overlaps with the file position of field {3} (starts at {4} ends at {5}).
-
Cause: Two fields from a fixed format file have overlapping file positions.
-
Action: Modify the file positions or remove a field if the overlapping file positions are not correct.
Level: 32
Type: ERROR
Impact: Other
- ODI-10214: Fixed format file fields {0} (starts at {1} ends at {2}) and {3} (starts at {4} ends at {5}) have unused file positions between them.
-
Cause: Two fields from a fixed format file have unused file positions between them.
-
Action: Modify the file positions if having unused file positions is not correct.
Level: 32
Type: ERROR
Impact: Other
- ODI-10218: Invalid WAS_HOME ("{0}") set or WebSphere library jar ({1}) not found under WAS_HOME/plugins.
-
Cause: Wrong WAS_HOME set (or) WebSphere libraries (com.ibm.ws.admin.core.jar, com.ibm.ws.admin.services.jar, com.ibm.ws.runtime.jar) are moved
-
Action: Check that the environment-variable WAS_HOME is set properly to point to WebSphere Application Server root. Also, ensure the libraries exist under WAS_HOME/plugins.
Level: 32
Type: ERROR
Impact: Other
- ODI-10223: A non-legacy compatible import source cannot be imported into a legacy compatible repository.
-
Cause: An attempt was made to import a non-legacy compatible import source into a legacy compatible repository.
-
Action: Import a legacy compatible import source or make repository not legacy compatible.
Level: 32
Type: Error
Impact: Other
- ODI-10225: Invalid wallet password: A valid password must have a minimum length of eight characters and contain alphabetic characters combined with numbers or special characters.
-
Cause: Invalid wallet password.
-
Action: Please choose a valid wallet password accordingly.
Level: 32
Type: ERROR
Impact: Security
- ODI-10231: Interface {0} cannot be imported because source temporary interface / mapping {1} is not found.
-
Cause: An attempt was made to import an interface with a source temporary interface / mapping that cannot be found in the import source or target repository.
-
Action: Import the missing source temporary interface / mapping.
Level: 32
Type: ERROR
Impact: Other
- ODI-10243: Cannot import an export file with parents using regular import and INSERT_UPATE mode. Use smart import instead.
-
Cause: An attempt was made to import an export file created with parent objects using regular import and INSERT_UPATE mode. This would cause all other objects under the parent objects and not in the import file to be deleted.
-
Action: Use smart import to import an export file created with parent objects when INSERT_UPDATE functionality is needed.
Level: 32
Type: ERROR
Impact: Other
- ODI-10244: Cannot import {0} {1} (with global id: {2} and internal id: {3}) because referenced {4} with global id {5} does not exist.
-
Cause: The referenced object for a foreign key cannot be found in order to set the reference and a missing reference cannot be created.
-
Action: Import the missing referenced object before importing the referencing object.
Level: 32
Type: ERROR
Impact: Other
- ODI-10245: Cannot import {0} {1} (with global id: {2} and internal id: {3}) belonging to {4} {5} (with global id: {6} and internal id: {7}) because its referenced object is not found in the target repository.
-
Cause: The object was imported in a SYNONYM UPDATE mode and the referenced object was not found in the repository.
-
Action: Change the import mode to INSERT_UPDATE or import the file twice first in INSERT MODE and then in UPDATE mode.
Level: 32
Type: ERROR
Impact: Other
- ODI-13704: Could not locate the physical schema associated with OWB workspace {0} in context {1}.
-
Cause: An error occurred when finding the schema related to an OWB workspace in a context.
-
Action: Verify that the OWB workspace is related to a physical schema in the context.
Level: 1
Type: ERROR
Impact: Other
- ODI-14091: Work repository is already attached to another master repository.
-
Cause: Attempt to attach already attached work repository was made while work repository can be attached to only one master repository at the moment.
-
Action: Work repository should be first detached from the master repository it is attached to at the moment.
Level: 32
Type: ERROR
Impact: Other
- ODI-14121: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 11.2.0.3.0 in 11g. Refer to the certification matrix for supported DB versions.
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14122: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.5.3.0. Refer to the certification matrix for supported DB versions
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14124: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 5.5.14. Refer to the certification matrix for supported DB versions.
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14129: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 12.1.0.1.0 in 12c. Refer to the certification matrix for supported DB versions.
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-14130: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 10.2.0.4.0 in 10g or version equal to or higher than 11.1.0.7.0 in 11g. Refer to the certification matrix for supported DB versions
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14131: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 2008 R2. Refer to the certification matrix for supported DB versions.
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14132: The database you are connecting is not a supported version. Enter Database with version equal to or higher than 9.7 in 9 series and equal to or higher than 10.1 FP2 in 10 series. Refer to the certification matrix for supported DB versions.
-
Cause: Database version is not supported
-
Action: Refer to the certification matrix for supported DB versions.
Level: 32
Type: ERROR
Impact: Other
- ODI-14134: The database you are connecting is with non-AL32UTF8 character set. Oracle strongly recommends using AL32UTF8 as the database character set.
-
Cause: The database you are connecting is with non-AL32UTF8 character set
-
Action: Use AL32UTF8 as the database character set.
Level: 32
Type: ERROR
Impact: Other
- ODI-14139: Encryption Standard is not set in Master Repository.
-
Cause: Master Repository configured with invalid or no Encryption Standard.
-
Action: Set the Encryption Standard to be used in the Master Repository, with valid value for algorithm ('AES') and key-length ('128' / '256').
Level: 32
Type: ERROR
Impact: Security
- ODI-14141: The provided key is not matching the key-specification. Key must : be of length 8-100, contain at least one alphabet (lower/uppercase), contain at least one numeric-digit (or) a special-character from: [@ # $ % + / =].
-
Cause: The provided key is not matching the key-specification.
-
Action: Provide key that matches the key-specification
Level: 32
Type: ERROR
Impact: Security
- ODI-14142: The Security Policy currently in force, does not allow the use of AES-256.
-
Cause: The Security Policy in force does not allow using AES-256 Encryption Standard.
-
Action: To use AES-256, please replace the security policy files in JRE_HOME/lib/security, with Unlimited Strength Policy Files available at Java SE downloads at http://www.oracle.com/technetwork/java. Refer Java SE documentation for more information.
Level: 32
Type: ERROR
Impact: Security
- ODI-14143: Encryption Standard persisted in master repository is not AES-128 or AES-256.
-
Cause: The Encryption Standard configured in the repository is not supported.
-
Action: Edit the master repository configuration to set the Encryption Standard as AES-128 or AES-256.
Level: 32
Type: ERROR
Impact: Security
- ODI-14147: An error occurred while migrating cipher text in object {0} - '{1}' (with Internal ID: {2} and Global ID: {3})
-
Cause: Invalid Cipher content or Invalid Export Key
-
Action: If exporting, check if the cipher data present in the object is correct. If importing, check if Export Key is correct.
Level: 32
Type: ERROR
Impact: Security
- 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-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-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-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-15054: Scenario generation error: Cannot regenerate the scenario. The physical mapping design used to generated the scenario is not found.
-
Cause: The physical mapping design used to generated the scenario is not found.
-
Action: Choose to create or replace the scenario.
Level: 32
Type: ERROR
Impact: Programmatic
- 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-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-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-15160: Native Sequences may not be supported by the target technology after transforming with the Platform Compiler
-
Cause: Using Native Sequence and Platform Compiler Enabled User Param Set
-
Action: Make sure that all target technologies will support native sequences
Level: 32
Type: WARNING
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-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-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-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-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-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-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-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-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-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-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-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 construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.
-
Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
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 construction of the InterfaceActionSwitchDataSetOrders class is not used in the interface.
-
Action: Recheck the datasets being switched for this interface. Both datasets must be used in the interface.
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-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-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-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-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-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-15644: The physical data server for the source code and for sequqnce(s) {0} is not the same, this may result in the same sequence value being used for each row.
-
Cause: The sequence may be remote so a single nextval is calculated and reused per row.
-
Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32
Type: INFO
Impact: Other
- ODI-15645: The physical data server for the target code and for sequence(s) {0} is not the same, this may result in the same sequence value being used for each row.
-
Cause: The sequence may be remote so a single nextval is calculated and reused per row.
-
Action: Make sure the sequence and task have the same data server if you want the sequences to use distinct values per row.
Level: 32
Type: INFO
Impact: Other
- ODI-16005: Join component inside dataset has no valid source references in the join condition. Join: {0} , condition = {1}.
-
Cause: Join component inside dataset has no valid source references in the join condition.
-
Action: Check source references in the join condition.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16006: Join component inside dataset has only one source references in the join condition, must have at least 2 references. Join: {0}, condition = {1}
-
Cause: Join component inside dataset has only one source references in the join condition, must have at least 2 references.
-
Action: Check join condition.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16008: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.
-
Cause: There is no possible pairwise join order that satisfies both the join condition references and the user order numbers.
-
Action: Check both the join condition references and the user order numbers.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16009: Lookup component creation is not complete: it misses either driving and/or lookup source information.
-
Cause: Lookup component: {0} in dataset: {1} is incomplete. (Driving source: {2}, lookup source: {3})
-
Action: Set the missing driving and/or lookup source on the lookup component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16017: The join component: {0} has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.
-
Cause: The join component has more than 2 input connector points. This is not recommended. ANSI SQL join syntax may not be supported.
-
Action: Check the join component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16018: The join condition for component: {0} only references {1} sources, but there are {2} input connector points. Expression text: {3}
-
Cause: The number of references sources is less than the number of input connector points.
-
Action: Check the join condition and input connector points.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16019: Set component output attribute {0} contains {1} expressions, but there are only {2} input connector points.
-
Cause: The number of input expressions is greater than the number of input connector points.
-
Action: Check expressions and input connector points.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16020: Set component output attribute expression for attribute: {0} does not have a scoping input connector point specified. Set component input expressions must have an associated scoping input connector point.
-
Cause: A scoping input connector point need to be specified.
-
Action: Check If set component input expressions have an associated scoping input connector point.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16021: The immediate downstream node {0} of the AP node {1}, which uses a push style LKM, is not a target.
-
Cause: A push style LKM is assigned to an AP node but its immediate downstream node is not a target.
-
Action: Either change the LKM to a pull style LKM or move some physical nodes to source execution unit(s).
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16024: The expression contains unresolved attribute references. {0} Expression: {1} Unresolved identifiers: {2}.
-
Cause: The expression contains identifiers that were not resolved as attribute references.
-
Action: Check all identifiers in the expression for accessibility through a valid input connector point.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16025: An access point (AP) node has been created in the physical graph, but it does not have any columns: {0}.
-
Cause: ERROR: An access point (AP) node has been created in the physical graph, but it does not have any columns.
-
Action: Check access points.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16028: Expression push is not allowed because it would push the expression through projector node: {0}.
-
Cause: Expression push is not allowed because it would push the expression through projector node.
-
Action: The action attempted is not supported.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16035: Target node {0} has assigned IKM {1}. The IKM will be ignored.
-
Cause: A target node that is loaded by an upstream AP node with a transparent target LKM assigned does not need an IKM assigned, since the loading functionality will be handled by the LKM transparent push.
-
Action: Set IKM to null.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16037: Only one target allowed for AP node: {0} with SQL multi-connect LKM assigned.
-
Cause: An AP node with multi-connect LKM assigned cannot have multiple targets.
-
Action: Pick different LKM, or remove all but one of the targets in the mapping.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16038: No extra logical components are allowed downstream from AP node: {0} with SQL multi-connect LKM assigned. The AP node must have a direct connection to target.
-
Cause: An AP node with multi-connect LKM assigned must be connected directly to the target, with no intervening nodes.
-
Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16039: The AP node: {0} has a transparent target LKM assigned, but it is not connected directly to the target.
-
Cause: An AP node with transparent target LKM assigned must be connected directly to the target, with no intervening nodes.
-
Action: Pick a different LKM, or reconfigure the physical graph such that the AP nodes connects directly to the target.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16041: The manual group by clause is missing a required attribute: {0}
-
Cause: The maual group-by expression is missing one or more attributes required for the SQL group-by clause.
-
Action: Edit the manual group-by expression to included the missing attribute.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16042: The expression for attribute: {0} does not contain an aggregate function, but the group by column setting is NO. Non aggregate attributes should be part of the group-by clause.
-
Cause: The group-by column setting for an attribute is NO, but it should be part of the group-by clause because the expression does not contain an aggregate function.
-
Action: If the attribute expression does not contain an aggregate, set the group by column setting to YES.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16043: The expression for attribute: {0} contains an aggregate function, but the group by column setting is YES. Only non aggregate attributes should be included in the group-by clause.
-
Cause: The group by column setting for an attribute is YES, but it should not be part of the group-by clause because the expression contains an aggregate function.
-
Action: If the attribute expression contains an aggregate, set the group by column setting to NO.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16044: The having clause references aggregate attribute: {0}, but an aggregate function is not specified.
-
Cause: An aggregated attribute is used in a having clause without an aggregate function.
-
Action: If the having clause references an aggregated attribute, include the aggregate function used with that attribute.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16045: Input connector point {0} is not referenced by any attribute expression. That input to the set component is unused.
-
Cause: An input connector point for a set component is unused because no attribute expressions reference attributes scoped through that connector.
-
Action: At least one attribute expression should reference an attribute through the input connector in order to use that input to the set.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16047: Set component output attribute: {0} must have a non empty expression for input connector point {1}.
-
Cause: The number of input expressions is less than the number of input connector points.
-
Action: Specify a non empty expression for each input. Specify null if no attribute reference is used.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16049: Reusable mapping component {0} has one or more output connector points, but none are connected or contain target components. DML cannot be generated without a target component connected downstream or within the reusable mapping.
-
Cause: None of the output connector points for the reusable mapping component are connected or contain target components.
-
Action: Add a connection for at least one output connector point.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16050: Native sequence and ORDER BY operation are performed on the same flow. This might not be allowed in some technologies such as Oracle.
-
Cause: Sequence is used before order by, this is now allowed in Oracle.
-
Action: Remove sorter component or place sorter in an execution unit different from the sequence expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16051: The Sub select option may not be set for reusable mappings having an input signature.
-
Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if an input signature is present.
-
Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16052: The Sub select option may not be set for reusable mappings having more than one output signature.
-
Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if more than one output signature is present.
-
Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16054: An unparsed identifier, {0}, was found in the aggregate HAVING clause. This identifier was not found in any other aggregate or group by expressions.
-
Cause: An identifier was found in the HAVING clause, but is invalid because it is not present in any aggregation or group by expression.
-
Action: Remove this expression from the HAVING clause or use it in one of the aggregate output attribute expressions.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16056: The driver connection for lookup component {0} is not connected to any source.
-
Cause: A connection has not been made between the source and driving connection of the lookup component.
-
Action: Connect a source to the lookup component driver connection.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16057: The lookup connection for lookup component {0} is not connected to any source.
-
Cause: A connection has not been made between the source and lookup connection of the lookup component.
-
Action: Connect a source to the lookup component lookup connection.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16064: When processing an AP node with SQL multi-connect LKM assigned, the downstream target node does not have a multi-connect IKM assigned.
-
Cause: The IKM assigned to the target is not a multi-connect IKM. If an AP node uses a multi-connect LKM, a multi-connect IKM is required on the target.
-
Action: Assign a multi-connect IKM to the target.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16065: Cannot get an entity manager for the mapping object. The entity manager must be set for the owning mapping or reusable mapping by calling IOdiEntityManager.persist() or Mapping.setEntityManager(), before this operation can be done. Mapping object= {0}
-
Cause: An mapping operation is being performed that requires the mapping to resolve a reference, but the mapping entity manager has not been set.
-
Action: Set the entity manager for the mapping, by calling IOdiEntityManager.persist() or Mapping.setEntityManager().
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16067: The Sub select option may not be set for reusable mappings having no output signature.
-
Cause: The reusable mapping component setSubSelect method was called with a value of true, but sub select is not allowed if no output signature is present.
-
Action: Avoid calling the setSubSelect method or specify false for the value parameter.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16068: A parse error was encountered when parsing the expression: {0}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.
-
Cause: Expression is syntactically incorrect.
-
Action: Make sure the expression is well-formed.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16079: Reusable mapping {0} is not compatible with dataset {1}. A reusable mapping within a dataset must have no input signatures and exactly one output signature.
-
Cause: An incompatible reusable mapping is being added to the dataset. The reusable mapping must have no input signatures and exactly one output signature.
-
Action: Choose a different compatible reusable mapping or modify the resuable mapping to contain just a single output signature and no input signatures.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16081: Physical Mapping Design {0} cannot be calculated with no optimization context.
-
Cause: The optimization context of the physical design is not set, or it becomes invalid because the referenced context is deleted.
-
Action: Check the optimization context of the physical design and specify an appropriate context.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16082: The physical node {0} cannot be supported by technology {1} on execution unit {2} of mapping {3}.
-
Cause: The physical node cannot be moved to the execution unit because its technology does not support the node.
-
Action: Do not move the physical node to this execution unit.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16083: Input Attribute {0} of reusable mapping component {1} does not have an expression to connect it to any source, but is referenced in the reusable mapping.
-
Cause: An input signature attribute in a reusable mapping is referenced by another component, but the input is not connected in the parent mapping.
-
Action: Assign an expression to the reusable mapping component input attribute.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16084: The proposed connection would create a circular graph.
-
Cause: The proposed connection would create a logical graph which contains a circular path, which connects a source component through some other components and back to itself.
-
Action: Fix the connections to get rid of the circular path.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16086: Set component {0} input connector point {1}: set operator {2} is not valid for {3} technology.
-
Cause: The set operation chosen for the connector point is not valid for the technology.
-
Action: Choose a set operation valid for the technology.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16088: Map component {0}, attribute {1} contains an aggregate function. Aggregate functions are only supported by the aggregate component.
-
Cause: An aggregate function is used in the expression of a datastore attribute. The Datastore component does not support aggregate functions and will not generate the required GROUP BY clause.
-
Action: Create an aggregate component to contain the aggregate function.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16091: Expression component {0} has no attributes.
-
Cause: An expression has no attributes. Expression components are projectors and must have attributes in order to be referenced by downstream components.
-
Action: Add one or more attributes to the expression component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16093: The subselect option is not valid for reusable mapping component {0} because the reusable mapping contains an expression referencing a native sequence.
-
Cause: The reusable mapping has an expression referencing a native sequence, and the subselect option has been chosen for the reusable mapping component.
-
Action: Avoid using the subselect option for reusable mappings having expressions which reference native sequences.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16094: Physical node {0} is associated with logical schema {1}, but it is not mapped to a physical server in context {2}.
-
Cause: The physical schema of the physical node cannot be resolved, as its logical schema is not mapped in the execution context.
-
Action: Associate the logical schema with a physical schema in the context specified.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16101: Name {0} contains invalid characters. Only letters, digits or underscore characters are allowed.
-
Cause: Proposed name contains invalid characters, such as space. Only letters, digits or underscore characters are allowed.
-
Action: Provide a different name for the object.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16102: Name {0} contains invalid characters. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.
-
Cause: Proposed name contains invalid characters, such as space. Only uppercase letters, digits or underscore characters are allowed, and the first character needs to be a letter.
-
Action: Provide a different name for the object.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16104: The expression for attribute {0} cannot be resolved because it references an input signature which could not be redirected to an upstream expression. Input connector connections may be incorrect.
-
Cause: An expression references an input signature, but it could not be redirected to an expression upstream of the input signature. Invalid input connector point connections are the most common cause.
-
Action: Check all input connector points for correct upstream connections.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16105: Expression of attribute {0} does not refer to any upstream attribute. If {0} is an attribute of an input signature component, the corresponding attribute of the reusable mapping component does not have an expression text, or the input connector point of the reusable mapping component is not properly connected.
-
Cause: The expression is not set or the input connector point is not properly connected.
-
Action: Verify the expression or the connection to the input connector point.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16107: The data type for datastore component {0}, attribute {1} is not defined.
-
Cause: The data type of the column to which the datastore attribute is bound is null. This may occur when reverse engineering an unknown data type.
-
Action: Add the data type to the technology and set the data type of the column.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16108: Preset Staging Location explicitly set to target location. This may result in the addition of another execution unit and decreased performance. Consider using the default Preset Staging Location, which is already set to use the target location.
-
Cause: The preset staging location has been explicitly set, instead of using the default value. When an explicit value is set, and execution unit will be created, even if the location is the same as the target location.
-
Action: Consider using the default value for the preset staging location.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16109: Encountered {0} at line {1} column {2}. Was expecting one of: {3}. The default parser supports ANSI SQL delimiters. If a non-standard syntax is desired, use the free-form expression delimiters /%% and %%/ around the expression.
-
Cause: A parser error was encountered when parsing the expression.
-
Action: Fix the syntax of the expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16112: Reusable mapping component {0}, output connector point {1} is not connected.
-
Cause: An output connector point of a reusable mapping component is not connected.
-
Action: Check that connections from all output connector points are optional.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16114: Error when ordering the components for physical design:{0}, component re-ordering is not valid. A skipped component was not able to be placed in an execution unit because of dependency errors.
-
Cause: When attempting to reorder the component nodes in the physical graph, an eror was found.
-
Action: Do not reorder the component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16120: Warning: Target Load Order -- Child component is ordered before parent component.
-
Cause: A datastore component with foreign key relationships is ordered before its parent datastore component.
-
Action: Change the load order to put parent component before child component or keep the load order knowing that it may result in error in loading due to missing primary record.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16121: Error: Target Load Order -- Load order is not consistent with processing graph from source to target. Please modify the graph or change the load order.
-
Cause: A target component is ordered before its source component.
-
Action: Change the load order to put source component before target component or change the mapping design.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16135: File technology has limited capability to serve as a staging area. Consider switching the staging area to another technology, such as in-memory engine.
-
Cause: File technology unit set as staging area.
-
Action: Set staging area to non-file technology.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16137: IKM {0} is selected for physical node {1}, but the corresponding logical component {2} of reusable mapping {3} is not marked as derived sub-select.
-
Cause: An IKM is used for extraction of a physical node, but derived sub-select is not enabled.
-
Action: Change the KM selected for the physical node, or mark the logical component as derived sub-select.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16138: Internal error occurred during mapping metadata conversion. Please check the original 11g interface to see if it is complete and valid. Only interfaces that pass validation are supported during the upgrade process. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
-
Cause: Internal error occurred or unexpected exception received during mapping metadata conversion.
-
Action: Make sure the original 11g interface is valid. If the 11g interface validates properly (in 11g) and then fails to upgrade cleanly, you should contact Oracle Support. The detailed exceptions information can be found in log file.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16142: Cannot bind a datastore component to file model datastore {0}, use a file component instead.
-
Cause: Attempt to bind a datastore component to a datastore with file technology.
-
Action: Use a file component instead, and bind the file object to it.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16143: Cannot bind a file component to non-file model datastore {0}, use a datastore component instead.
-
Cause: Attempt to bind a file component to a datastore with non-file technology.
-
Action: Use a datastore component instead, and bind the file object to it.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16146: The join condition for component {0} contains a filter expression that does not reference a different schema on each side of the equality operator: {1}. Filter expressions may not behave as expected in joins.
-
Cause: The join condition contains a filter expression. Filter expressions may not be effective in joins, and are inherently problematic in outer joins.
-
Action: Move the extra filter condition to a separate filter component to eliminate interaction with the join.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16147: The join condition for component {0} does not contain an identifiable equality operator to join the input sources: {1}.
-
Cause: The join condition may be missing an equality operator needed to match rows when joining the input sources.
-
Action: Check the join expression for a valid equality operator.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16148: The size of map attribute {0} ({1}) is greater than the size of attribute {2} ({3}), to which it is mapped. Truncation or runtime errors are possible, depending on the technology.
-
Cause: A map attribute is mapped to an attribute of smaller size. This may result in data truncation or DML errors.
-
Action: Verify the size of both attributes and make any adjustments necessary to avoid truncation. Add an expression to explicitely truncate the data if necessary.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16149: For lookup component {0}, the option {1} for non matching rows may only be selected if option {2} is selected for multiple matching rows.
-
Cause: The no match rows property has not been correctly configured for lookup component. It may only be used if the multiple matching rows option specifies all rows.
-
Action: Correct the no match rows property for lookup component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16151: The context value {0} for map component {1} does not map to a physical location.
-
Cause: The forced context value of a data storage component, combined with the model and logical schema, does not map to a physical schema. A map physical design cannot be created.
-
Action: Use the logical schema editor or SDK to set a physcial schema for the chosen component context.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16152: Error processing KM target expression for mapping: {0}, KM line: {1}, KM error: {2}
-
Cause: An exception was thrown during KM processing of the target expression for a particular line.
-
Action: Review the KM line and error to determine the cause.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16153: Error processing KM source expression for mapping: {0}, KM line: {1}, KM error: {2}
-
Cause: An exception was thrown during KM processing of the source expression for a particular line.
-
Action: Review the KM line and error to determine the cause.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16155: Join or Lookup component {0} is inactive. Components joining sources must be active.
-
Cause: A join or lookup component has been set to inactive. Components which join sources must be active because all sources will not be in scope without the join.
-
Action: Set the component to active.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16156: Join type {0} in {1} cannot be supported due to circular relationships in Dataset {2}.
-
Cause: If a circle of relationships exist in a Dataset, one of the joinis must be reduced to a filter. The join type defined on it could be lost.
-
Action: Examine the logic in the Dataset and try to reduce the number of outer joins if possible as the currently specified logic in Dataset cannot be translated to a SQL query.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16157: Ambiguous expression reference due to split path. {0} Expression: {1}, Available paths: {2}
-
Cause: The connection path to the referenced attribute is split and the reference does not include a path specifier with a sufficient number of connector names to specify an unambiguous path..
-
Action: Add a path specifier qualifier to the expression reference.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16158: Component in path specifier has multiple output connector points. {0} Expression: {1}, Component={2}
-
Cause: A map component specified in the expression path specifier has multiple output connector points.
-
Action: A specific connector point must be specified in the path specifier.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16159: Path specifier contains nonexistent identifier. {0} Expression: {1}, Identifier={2}
-
Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.
-
Action: Fix the path specifier in the expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16160: Path specifier contains out-of-scope identifier. {0} Expression: {1}, Identifier={2}
-
Cause: An identifier specified in the expression path specifier is not found in the set of upstream components or connector points.
-
Action: Fix the path specifier in the expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16164: Internal Error: Cannot find input query select item for expression cross reference: {0}
-
Cause: The code generator cannot generate code for the map expression cross reference because the upstream query does not include the referenced object.
-
Action: Fix the expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16165: An attribute input expression for a set component must reference upstream attributes through only one input connector point. Attribute: {0}.
-
Cause: An attribute input expression for a set component must reference upstream attributes through only one input connector point.
-
Action: Check input expressions for the set component.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16166: Cannot parse the syntax of user defined function or language element {0}: {1}.
-
Cause: The syntax text of the user defined function or language element cannot be parsed by the code generator.
-
Action: Check the syntax text of the user defined function or language element.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16167: The function call {0} does not match the number of parameters defined for user defined function or language element {1}.
-
Cause: The function call in the expression text does not match the number of parameters of the user defined function or language element.
-
Action: Check the function call in the expression.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16168: Invalid parameter syntax in the syntax text of user defined function or language element {0}: {1}.
-
Cause: One of the parameters in the syntax text contains invalid parameter syntax.
-
Action: Check the syntax text of the user defined function or language element.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16169: Invalid parameter syntax in the implementation text of user defined function or language element {0}: {1}.
-
Cause: One of the parameters in the implementation text contains invalid parameter syntax.
-
Action: Check the implementation text of the user defined function or language element.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- ODI-16170: Cannot locate calling parameter {0} in implementation text from the syntax text of user defined function or language element {1}.
-
Cause: The calling parameter in the implementation text does not match any parameters that are defined in the syntax of the user defined function or language element.
-
Action: Check the implementation text of the user defined function or language element.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic
- 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-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-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-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-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 attributes of datastores belonging to the selected model.
-
Action: Ensure datatype conversion rules exist for all datatypes used by attributes of datastores belonging to the selected model or do not use datatypes that cannot be converted.
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-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-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 retrying the addition. Consider using the synchronize option to verify the solution's coherence.
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 Attribute.
-
Action: Ensure the ODI user security permissions are correct specifically the Attribute Duplication setting.
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-20344: ODI-20344: Cannot launch the editor for this expression
-
Cause: An error occured while retrieving the language for the expression. This may be due to an unexpected exception, or the language may not be available for the schema's technology.
-
Action: Review the message log for additional errors. Ensure that the schema has a valid technology for which the language is set.
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-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-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-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 temporary target table may be deleted.
-
Action: You cannot delete the row.
Level: 32
Type: ERROR
Impact: Other
- ODI-20360: ODI-20360: Only Expression columns support Copy and Paste from other applications. For all other columns, please perform a copy first on that column before pasting.
-
Cause: Only values from other applications may be copied into Expression columns.
-
Action: For all other columns, perform a copy first on that column before pasting.
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-20361: ODI-20361: Can not perform Copy and Paste across tables, except for Expression columns (Lookup Expression, Join Expression, Filter Expression, and Mapping Expression).
-
Cause: Values may not be copied between tables in Quick Edit, apart from between Expression columns.
-
Action: Please enter the values manually.
Level: 32
Type: SET_AT_RUNTIME
Impact: Other
- ODI-20374: ODI-20374 : A model cannot contain a datastore and a datastore shortcut to another datastore with the same datastore name
-
Cause: A model cannot contain a datastore and a shortcut to another datastore with the same datastore name
-
Action: Try another folder destination or fix model contents.
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 plan variables 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-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-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-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-20734: ODI-20734: Changing the name of a user function only impacts the user function itself; Users need to manually change object(s) which reference the old user function name.
-
Cause: The user function name has been updated
-
Action: It is the user's responsibility to determine where the user function is referenced and to manually change the name of the user function in those places
Level: 32
Type: WARNING
Impact: Other
- ODI-20749: ODI-20749: Selected Capture/Initial Load Capture process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.
-
Cause: Selected Goldengate Capture/Initial Load Capture process is used in a different model.
-
Action: Select a different set of process instances for this model.
Level: 32
Type: ERROR
Impact: Other
- ODI-20750: ODI-20750: Selected Delivery/Initial Load Delivery process is associated with another model. This may cause conflicts during 'Start Journal' action, if the logical process instance selected uses the same physical process instance.
-
Cause: Selected Goldengate Delivery/Initial Load Delivery process is used in a different model.
-
Action: Select a different set of process instances for this model.
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-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-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 exists in the Master Repository.
-
Action: Ensure the Context for the Physical Schema is correct by either selecting a valid Context for the Physical Schema or recreating the missing Context.
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-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-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-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-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.
-
Action: Associate a logical agent with a physical agent using the Topology Navigator and then resubmit your schedule request.
Level: 32
Type: ERROR
Impact: Other
- ODI-23038: ODI-23038: Cannot resolve the table name. Check the masks defined for this physical schema.
-
Cause: The table and schema format could not be calculated. This is because the object mask has not been set for the Physical Schema that contains this table.
-
Action: From the Topology Navigator edit the Physical Schema containing this table and ensure the Masks parameter value is valid for the schema based on its technology (for example "%SCHEMA.%OBJECT").
Level: 32
Type: ERROR
Impact: Other
- ODI-23042: ODI-23042: An error occurred while changing the repository number.
-
Cause: An error occured while changing the repository number.
-
Action: Correct any errors identified in the message log and retry the action. If the problem persists then contact Oracle Support Services.
Level: 32
Type: ERROR
Impact: Other
- ODI-23044: ODI-23044: The new ID you have chosen is already in use as a table "{0}" primary key. The renumbering has been aborted. No changes have been made.
-
Cause: The Repository ID specified is already used by an existing object.
-
Action: Enter a different value for the Repository ID parameter ensuring it is unique within the repository.
Level: 32
Type: ERROR
Impact: Other
- ODI-23045: ODI-23045: You may not renumber a repository before version 11. Please upgrade your repository first.
-
Cause: The renumber functionality is not supported for ODI Repository versions prior to version 11.
-
Action: Upgrade the repository to version 11 (or higher) and then renumber it.
Level: 32
Type: ERROR
Impact: Other
- ODI-23046: ODI-23046: An error was encountered during the test.
-
Cause: An attempt to connect a Work Repository failed.
-
Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32
Type: ERROR
Impact: Other
- ODI-23047: ODI-23047: Could not connect to the work repository. The renumbering process has been aborted. No changes have been made.
-
Cause: An attempt to connect a Work Repository failed.
-
Action: Correct any errors identified in the message log. Ensure the Work Repositories are available and the connection information is correctly specified in the Master Repository. Retry the test.
Level: 32
Type: ERROR
Impact: Other
- ODI-23049: ODI-23049: Error Detected during Repository Installation
-
Cause: An error occured during the creation or import of the Master Repository.
-
Action: Correct any errors described in the message log and retry the installation process. If the problem persists then contact Oracle Support Services.
Level: 32
Type: ERROR
Impact: Other
- ODI-23053: ODI-23053: Maximum number of threads cannot be less than maximum number of threads per session.
-
Cause: Maximum number of threads less than maximum number of threads per session
-
Action: Enter valid values for maximum number of threads and maximum number of threads per session
Level: 32
Type: ERROR
Impact: Other
- ODI-23058: ODI-23058: This Technology does not support multiple schemas.
-
Cause: Attempt to create multiple Physical Schemas for Technologies that support only one Schema.
-
Action: The solution for Technologies that do not support multiple Physical Schemas is to create separate Data Dervers from the Physical Schemas.
Level: 32
Type: ERROR
Impact: Other
- ODI-23062: ODI-23062: Maximum number of threads cannot be less then the maximum number of sessions.
-
Cause: Value for maximum number of threads is less than the maximum number of sessions
-
Action: Ensure that maximum number of threads is equal to or greater than the maximum number of sessions
Level: 32
Type: ERROR
Impact: Other
- ODI-24004: ODI-24004: There are no supervisor accounts in the ODI repository with matching entries in the identity store. Please provide a suitable supervisor account.
-
Cause: The ODI repository does not have any supervisor account that matches the entries in the identity store.
-
Action: Create a supervisor account in the ODI repository that matches an entry in the identify store.
Level: 32
Type: ERROR
Impact: Other
- ODI-24006: ODI-24006: An error occurred while switching the authentication mode for the master repository.
-
Cause: An unexpected error occurred.
-
Action: Check the exception to see if it gives details about the error and contact Oracle Support Services for further assistance.
Level: 32
Type: ERROR
Impact: Other
- ODI-26001: ODI-26001: Boolean does not correspond to the Field Update Object Layer.
-
Cause: The repository contained an invalid value of the Field Update property for a checkbox or radio group.
-
Action: Ensure the repository value is a boolean for checkbox or a valid action command for a radio group.
Level: 32
Type: ERROR
Impact: Other
- ODI-26002: ODI-26002: This object is referenced by another object. View the details for more information. You may also see where this object is used in the hierarchy.
-
Cause: The specified object could not be used because it is referenced by another object.
-
Action: Remove references to this object. The "Uses" hierarchy may be useful in finding objects references.
Level: 32
Type: ERROR
Impact: Other
- ODI-26003: ODI-26003: This object cannot be removed: it is referenced by another object.
-
Cause: The specified object could not be deleted because it is referenced by another object.
-
Action: Remove references to this object before deleting it. The "Uses" hierarchy may be useful in finding objects references.
Level: 32
Type: ERROR
Impact: Other
- ODI-26005: ODI-26005: You are importing an object from another repository with the same identifier. It is forbidden.
-
Cause: An object in the import file has an identifier which already exists in the repository.
-
Action: Consider manually changing the "com.sunopsis.dwg.dwgobj.SnpImportRep" object section of the import XML file to use a unique identifier.
Level: 32
Type: ERROR
Impact: Other
- ODI-26013: ODI-26013: Your security parameters are insufficient to perform this action.
-
Cause: The ODI user security parameters do not specifically permit the user to perform this particular action.
-
Action: Ensure this ODI user is granted the security access to perform this action.
Level: 32
Type: ERROR
Impact: Other
- ODI-26015: ODI-26015: You do not have sufficient privileges to perform this operation.
-
Cause: The ODI user security parameters do not specifically permit the user to perform this particular operation.
-
Action: Ensure this ODI user is granted the security access to perform this operation.
Level: 32
Type: ERROR
Impact: Security
- ODI-26016: ODI-26016: The requested operation cannot succeed. The object no longer exists.
-
Cause: The specified ODI object cannot be accessed because it no longer exists in the repository (it may have been deleted by another ODI user).
-
Action: Recreate the specified ODI object. Consider importing the object from a backup.
Level: 32
Type: ERROR
Impact: Other
- ODI-26022: ODI-26022: Unrecoverable error during object saving.
-
Cause: The object could not be saved. This is possibly due to a repository connection error, or inconsistent data values supplied. It's also possible that the object was modified by another user.
-
Action: Ensure the repository database is available and the data values supplied are valid. Try to save changed data, then refresh edited object and apply changed data again.
Level: 32
Type: ERROR
Impact: Other
- ODI-26029: ODI-26029: Could not deploy the datasource automatically.
-
Cause: Weblogic Administration server is not up and running, the server connection parameters are wrong.
-
Action: Please check Weblogic Administration server connection parameters and the server state.
Level: 32
Type: ERROR
Impact: Other
- ODI-26030: ODI-26030: The new password does not meet the password policy. Your change could not be saved.
-
Cause: The new password does not meet the password policy.
-
Action: Please verify that the new password meets the password policy (go to the "Security Navigator -> Password policies...").
Level: 32
Type: ERROR
Impact: Other
- ODI-26031: ODI-26031: You may not delete work repository {0} because you are connected to it. To delete this repository, reconnect to a different work repository or use a master repository only connection.
-
Cause: Deletion of a work repository which is currently connected is not supported.
-
Action: Disconnect from the repository and then connect utilizing a Master Repository Only connection or a different work repository before attempting to delete the specified work repository.
Level: 32
Type: ERROR
Impact: Other
- ODI-26032: ODI-26032: This object was modified by {0} on {1} at {2}. Your changes cannot be saved.
-
Cause: The object was changed in the repository after the editor was opened for this object.
-
Action: Close the editor without saving changes. Open the editor again and reapply the edits and save. Note: consider using the lock object facility to disallow current modifications to an object.
Level: 32
Type: ERROR
Impact: Other
- ODI-26033: ODI-26033: You cannot edit this object because it is locked by another user ({0}). You can only view it.
-
Cause: The ODI object opened for editing is locked by another user. Other ODI users can only view such objects.
-
Action: Try to edit the object later.
Level: 32
Type: ERROR
Impact: Other
- ODI-26034: ODI-26034: An error occurred while deleting executions.
-
Cause: The specified executions could not be deleted. This is possibly caused by the repository database connection problems.
-
Action: Retry to delete the executions. If problem persists, contact Oracle Support Services.
Level: 32
Type: ERROR
Impact: Other
- ODI-26036: ODI-26036: Error while encrypting.
-
Cause: A general error occured during the ecrypting process, possibly caused by caused by repository database access problems, lack of security permissions, or encryption engine failures,
-
Action: Retry the encrypt action again.
Level: 32
Type: ERROR
Impact: Other
- ODI-26038: ODI-26038: Unable to execute, the selected Logical Agent is not associated to a Physical Agent in the desired Context.
-
Cause: A Logical Agent was not associated with this Physical Agent in this Context.
-
Action: Ensure a valid "Logical Agent - Physical Agent" association exists in the desired Context.
Level: 32
Type: ERROR
Impact: Other
- ODI-26039: ODI-26039: Connection failed.
-
Cause: The attempt to connect to the repository failed. This may be due to one or more of the following: invalid connection parameters specified, database problems, network problems.
-
Action: Ensure the repository database is available and acceccesible and the repository connection parameters are correct.
Level: 32
Type: ERROR
Impact: Other
- ODI-26053: ODI-26053: An error occurred during initialization.
-
Cause: Initialization failed possibly due a repository access failure or insufficient ODI security permissions.
-
Action: Ensure the repository database is available, and the ODI user security permissions permit connection.
Level: 32
Type: ERROR
Impact: Other
- ODI-26076: ODI-26076: You do not have enough memory to generate this report. Increase the maximum Java heap size value (-Xmx).
-
Cause: There was not enough memory allocated to generate the report.
-
Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32
Type: ERROR
Impact: Other
- ODI-26080: ODI-26080: Unable to delete version {0} for {1} {2}. It is referenced by solution {3}
-
Cause: Deletion of a version of an object referenced by a Solution was attempted.
-
Action: Delete the solution referencing the object version. Then retry deleting the object version.
Level: 32
Type: ERROR
Impact: Other
- ODI-26089: ODI-26089: This object is currently locked by user: {0}. Version restoration cancelled.
-
Cause: The object selected for restoration was locked by another user.
-
Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32
Type: ERROR
Impact: Other
- ODI-26095: ODI-26095: This object is locked by {0}. You cannot edit it unless it is unlocked.
-
Cause: Object could not be opened for write access because it was already locked by another user.
-
Action: Ensure the selected object is not locked by another user before retrying the operation.
Level: 32
Type: ERROR
Impact: Other
- ODI-26102: ODI-26102: The Service cannot be generated. An Application Server is not selected on the Model.
-
Cause: No Application Server was assigned to the Model.
-
Action: Enter an Application Server for the Model before performing Generate Service. Consider using the Model editor to make entry.
Level: 32
Type: ERROR
Impact: Other
- ODI-26109: ODI-26109: Error while reading the search criteria. Invalid file
-
Cause: The selected file did not contain search criteria in a valid format.
-
Action: Ensure the selected file is one exported from the ODI search UI and contains correctly formatted search criteria information.
Level: 32
Type: ERROR
Impact: Other
- ODI-26118: ODI-26118: External password storage connection test failed.
-
Cause: Could not connect to the external password storage with the specified connection details.
-
Action: Ensure the external password storage is available and valid connection details are supplied.
Level: 32
Type: ERROR
Impact: Other
- ODI-26123: ODI-26123: Cannot connect to the repository with the provided login information.
-
Cause: Could not connect to a repository with the specified connection details.
-
Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32
Type: ERROR
Impact: Other
- ODI-26124: ODI-26124: Exception during connection to the repository with the provided login information:
-
Cause: Could not connect to a repository with the specified connection details.
-
Action: Ensure the repository database is available and valid connection details are supplied.
Level: 32
Type: ERROR
Impact: Other
- ODI-26125: ODI-26125: The configured external password storage is still accessible. Instead, use the Password Storage Switch service to change the configuration.
-
Cause: Could not connect to the external password storage with the specified connection details.
-
Action: Ensure the external password storage is available and valid connection details are supplied. Consider using the Password Storage Switch service to change the configuration.
Level: 32
Type: ERROR
Impact: Other
- ODI-26127: ODI-26127: The selected master repository configured to use internal password storage. Recovery is possible only for external storages.
-
Cause: Recovery was attempted for a master repository configured to use internal password storage.
-
Action: Select a master repository not configured to use internal password storage.
Level: 32
Type: ERROR
Impact: Other
- ODI-26156: ODI-26156: Designer cannot connect to an Execution repository. The operation will be canceled.
-
Cause: Unable to establish a connection to the Execution repository.
-
Action: Ensure the Execution repository is available and the connection details are correct.
Level: 32
Type: ERROR
Impact: Other
- ODI-26164: ODI-26164: The reverse cannot be executed. Your Model will be created.
-
Cause: The specified technology or driver did not support standard reverse-engineering.
-
Action: Ensure the technology or driver supports standard reverse-engineering. Otherwise choose Customized Reverse and select an appropriate RKM for the technology.
Level: 32
Type: ERROR
Impact: Other
- ODI-26167: ODI-26167: File System Error: {0}
-
Cause: Creation of the Server Template file failed due to an error detected by the file system.
-
Action: Correct any errors identified in the error log. Ensure the file system location is accessible and retry the operation.
Level: 32
Type: ERROR
Impact: Other
- ODI-26182: ODI-26182: Object was modified by another user and cannot be saved.
-
Cause: The object could not be saved. It's possible that the object was modified by another user.
-
Action: Try to save changed data, then refresh edited object and apply changed data again.
Level: 32
Type: ERROR
Impact: Other
- ODI-26185: ODI-26185: File does not exist or cannot be created. See error details for more information.
-
Cause: UI action tried to open a file which did not exist, or create a file which could not be created due to some reasons.
-
Action: Make sure the file path is typed correctly. Make sure application has enough file system permissions in order to create a file at the specified path.
Level: 32
Type: ERROR
Impact: Other
- ODI-26188: ODI-26188: There is no enough memory to perform this UI action. Increase the maximum Java heap size value (-Xmx).
-
Cause: UI action requires more memory than available at the current moment.
-
Action: Increase the maximum Java heap size value by using the "-Xmx" JVM option.
Level: 32
Type: ERROR
Impact: Other
- ODI-26190: ODI-26190: A user with same name {0} already exists in ODI. Note: LDAP user name is case insensitive. You have to first drop that user prior to registering or changing this one.
-
Cause: Due to LDAP user name is case insensitive so ODI will follow same rule in external authenticaiton mode.
-
Action: Please drop the existing user with same name(ingoring case) first prior to registering this one.
Level: 32
Type: ERROR
Impact: Other
- ODI-26196: ODI-26196: Failed to migrate login information to new format.
-
Cause: ODI was not able to migrate login information from old format into the new format.
-
Action: Make sure that directory %ODI_HOME%/oracledi has write permissions. Try manually copying %ODI_HOME%/oracledi/snps_login_work.xml into %ODI_HOME%/oracledi/snps_login_work_12.xml file.
Level: 32
Type: ERROR
Impact: Other
- ODI-26197: ODI-26197: Failed to delete old login information.
-
Cause: ODI was not able to delete old login information after migration from old format into the new format.
-
Action: Make sure that directory %ODI_HOME%/oracledi and file %ODI_HOME%/oracledi/snps_login_work.xml have write permissions. Try manually removing %ODI_HOME%/oracledi/snps_login_work.xml file.
Level: 32
Type: ERROR
Impact: Other
- ODI-26201: ODI-26201: Invalid Export Key. Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).
-
Cause: Export Key must have a minimum length of eight characters and maximum length of 100 characters, contain at least one alphabetic (lower/upper case) character, at least one numeric-digit or a special characters (@ # $ % + / =).
-
Action: Provide a valid Export Key
Level: 32
Type: ERROR
Impact: Other
- ODI-26204: ODI-26204: The incorrect Export Key is entered three times. The Export Key field will be disabled now. You can Import this file without an Export Key (the cipher data will not be imported) or Cancel import.
-
Cause: The incorrect Export Key entered 3 times.
-
Action: Continue import this file without importing cipher data or Cancel import.
Level: 32
Type: ERROR
Impact: Other
- ODI-26205: ODI-26205: The incorrect Export Key is entered three times. The Export Key field will be disabled now. Please consider other options or Cancel import.
-
Cause: The incorrect Export Key entered 3 times.
-
Action: Continue import this file or all files without importing cipher data, or Skip the file, or Cancel import.
Level: 32
Type: ERROR
Impact: Other
- ODI-26208: ODI-26208: Unable to perform move because {0} already exists in folder {1}.
-
Cause: A folder already consists a such type of object with the same name as a moving object.
-
Action: Rename an object, which you want to move, or rename, or delete an existing object from a folder.
Level: 32
Type: ERROR
Impact: Other
- ODI-30095: PROMPT option can only be used when ReverseManageShortcut tool is run from ODI UI and on a Local Agent.
-
Cause: The value of parameter -SHORTCUT_HANDLING_MODE is invalid for this mode of execution.
-
Action: Modify the value of parameter -SHORTCUT_HANDLING_MODE to ALWAYS_MATERIALIZE or ALWAYS_SKIP
Level: 32
Type: ERROR
Impact: Other
- ODI-40001: Cannot join two journalized sets of data: {0} and {1}.
-
Cause: The generated query object has detected multiple journalized data sources, only one is allowed.
-
Action: Switch off journalizing for one of the sources, in the logical or physical graph.
Level: 32
Type: SET_AT_RUNTIME
Impact: Programmatic