PK 8zDoa,mimetypeapplication/epub+zipPK8zDiTunesMetadata.plistD artistName Oracle Corporation book-info cover-image-hash 228617721 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 516580977 publisher-unique-id E40224-02 unique-id 356519158 genre Oracle Documentation itemName Oracle® Fusion Middleware Error Messages, 12c (12.1.2) releaseDate 2014-02-04T12:39:01Z year 2014 PKTaIDPK8zDMETA-INF/container.xml PKYuPK8zDOEBPS/chapter_jrf_messages.htm JRF-10001 to JRF-20036

17 JRF-10001 to JRF-20036

JRF-10001: Fail to retrieve the application identifier. The internal exception is: {0}.
Cause: The MBean server could not be accessed to retrieve the application name.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10002: Fail to retrieve the WebLogic domain adminser server name. The internal exception is: {0}.
Cause: The MBean server could not be accessed to retrieve the admin server name.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10003: Fail to retrieve the current server name. The internal exception is: {0}.
Cause: The MBean server could not be accessed to retrieve the server name based on the current thread.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10004: Fail to check if the current server is admin server. The internal exception is: {0}.
Cause: The MBean server could not be accessed to verify that the server in the current thread is the admin server.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10005: Fail to retrieve the server log path. The internal exception is: {0}.
Cause: The MBean server could not be accessed to retrieve the server log path.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10006: Fail to copy the config file from {0} to the server directory {1}. The internal exception is: {2}.
Cause: The server config directory could not be accessed.
Action: Use the applyJRF() wlst command to ensure that the server has been properly configured.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10007: Fail to retrieve the system property domain.home.
Cause: The system property domain.home was not specified during WebLogic server startup.
Action: Specify the system property domain.home when starting the WebLogic server.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10008: I/O exception occurs when aceessing to the JRF template at {0}.
Cause: The specified JRF template was not accessaible.
Action: Verify that the template jar from the template location is present and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10009: I/O exception occurs when parsing config/config.xml from the JRF template at {0}.
Cause: The config.xml might be missing from the JRF template or the JRF template jar might be corrupted.
Action: Verify that the JRF template is properly installed within the Oracle Home.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10010: The file config.xml under domain {0} does not exist.
Cause: The config.xml under domain config was missing or corrupted.
Action: Verify that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10011: Fail to parse the config.xml file from JRF template.
Cause: The domain config.xml might be missing or the JRF template jar might be corrupted.
Action: Verify that the JRF template is properly installed within the Oracle Home and that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10012: Fail to retrieve the property for the Common Components Home.
Cause: The Common Components Home property was not set.
Action: Set the Oracle Home property using the system property common.components.home or the environment variable COMMON_COMPONENTS_HOME.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10013: The specified Oracle Home directory {0} does not exist.
Cause: The Common Components Home directory did not exist.
Action: Verify that Common ComponentsHome, specified through the system property common.components.home or environment variable COMMON_COMPONENTS_HOME, is a valid directory.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10014: Fail to retrieve the current server name. The internal exception is: {0}.
Cause: The MBean server could not be accessed to retrieve the application server platform information.
Action: Verify that the MBean server is running and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10015: The specified application server platform {0} is not supported by JRF.
Cause: JRF does not support the specified platform.
Action: Contact Oracle Support Services for the JRF supported application server platforms.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10016: The initialization of the server config directory from the Oracle Home {0} with domain directory {1} for copying fails. The internal exception is: {2}.
Cause: Could not retrieve the servers from the domain config.xml file.
Action: Verify that the domain contains a valid config.xml file.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10017: Unable to invoke {0} because the domain {1} has not been extended with JRF template.
Cause: Domain has not been extended with JRF template.
Action: Apply JRF template to the domain.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10018: Server or cluster "{0}" is not found.
Cause: The server or cluster is not found.
Action: Create the server or cluster.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10019: Could not obtain edit lock on the domain
Cause: Domain is being edited by someone else
Action: Wait until the edit lock on the domain is released and retry.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10020: Could not load/instantiate a WebLogic server platform support instance.
Cause: Could not load/instantiate a WebLogic server platform support instance.
Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10021: Could not load/instantiate a WebSphere server platform support instance.
Cause: Could not load/instantiate a WebSphere server platform support instance.
Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10022: Could not load system property 'oracle.domain.config.dir'.
Cause: Could not load system property 'oracle.domain.config.dir'.
Action: Verify JRF is installed and provisioned properly and the system property 'oracle.domain.config.dir' is set.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10023: Could not load system property 'oracle.server.config.dir'.
Cause: Could not load system property 'oracle.server.config.dir'.
Action: Verify JRF is installed and provisioned properly and the system property 'oracle.server.config.dir' is set.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10024: JRF is unable to determine the current application server platform.
Cause: JRF is unable to determine the current platform.
Action: Contact Oracle Support Services for the JRF supported application server platforms.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10025: Could not load/instantiate a JBoss server platform support instance.
Cause: Could not load/instantiate a JBoss server platform support instance.
Action: Check if the server platform support class can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10026: Failed to get application server edition
Cause: JRF Failed to retrieve application server edition
Action: Verify that the application server is installed and accessible.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10027: Operation is not supported on this application server edition
Cause: Operation is not supported on this platform edition.
Action: Verify it is the right application server edition.

Level: 1

Type: ERROR

Impact: Configuration

JRF-10028: Invoke startup and shutdown class {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-10029: String {0} is in invalid format . Example of correct string format is {1}
Cause: String format is invalid.
Action: Correct the string format, see example of a correct string format in the exception message

Level: 1

Type: ERROR

Impact: Configuration

JRF-20001: Read domain {0} to applyJRF
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20002: Update JRF changes to domain {0} in {1} mode
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20003: Target JRF components to "{0}"
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20004: Cannot copy {0} to {1}: "{2}"
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20005: Environment variables {0} not set
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20006: Copying JRF configuration files from {0} to {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20007: Unable to add help for JRF commands: "{0}"
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20008: No domain has been read
Cause: JRF detects that domain has not been read.
Action: Read the domain offline or connect online before invoke JRF WLST command.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20009: JRF component or service with type "{0}" and name "{1}" is not found on server "{2}".
Cause: Domain has not been extended with JRF or upgraded with new JRF version, or the applyJRF command is out-of-sync with JRF in the domain
Action: Extend domain with JRF template, or invoke upgradeJRF() to upgrade the domain if the install is upgraded.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20010: {0} is not found.
Cause: file not found
Action: Verify oraclehomeproperties.xml exist

Level: 1

Type: ERROR

Impact: Configuration

JRF-20011: Node GUID does not exist or node is empty in {0}.
Cause: node not found or no value
Action: Verify oraclehomeproperties.xml exist

Level: 1

Type: ERROR

Impact: Configuration

JRF-20012: System properties {0} not set
Cause:
Action:

Level: 1

Type: WARNING

Impact: Configuration

JRF-20013: Target does not exist or not valid : {0}.
Cause: target not found or not valid
Action: Verify target exists and valid

Level: 1

Type: ERROR

Impact: Configuration

JRF-20014: Failed to create library at : {0}.
Cause: Creating shared library failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20015: Failed to create custom service : {0}.
Cause: Creating custom service failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20016: JRF_FAILED_CREATE_URLPROVIDER : {0}.
Cause: Creating URL Provider failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20017: Failed to config jvm args for : {0}.
Cause: Config JVM memory arguments failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20018: Failed to add jvm system property for : {0}.
Cause: Adding system property failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20019: Failed to parse template: {0}.
Cause: Template has error
Action: Verify template

Level: 1

Type: ERROR

Impact: Configuration

JRF-20020: Failed to get variable {0} from {1}.
Cause: Get variable failed
Action: Verify variable.xml

Level: 1

Type: ERROR

Impact: Configuration

JRF-20021: Failed to update targets of application {0}.
Cause: Failed to update application target
Action: Verify application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20022: Failed to update {0}.
Cause: Failed to update oracle jdbc driver path
Action: Verify server

Level: 1

Type: ERROR

Impact: Configuration

JRF-20023: Failed to install application {0}.
Cause: Failed to install application
Action: Verify application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20024: Failed to create variable {0} for {1}.
Cause: Failed to create variable
Action: Verify server

Level: 1

Type: ERROR

Impact: Configuration

JRF-20025: Need to apply jrf template to cell.
Cause: Cell is not jrf enabled
Action: Apply jrf template to the cell since this cell is not jrf enabled

Level: 1

Type: ERROR

Impact: Configuration

JRF-20026: Could not load/instantiate {0} JRFService instance.
Cause: Could not load/instantiate a JRFService implementation class instance.
Action: Check if JRFService implementation class in the error message can be loaded/instantiated by the classloader.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20028: JRFService not supported
Cause: JRFService is not supported.
Action: Check if the server has related JRFService available.

Level: 1

Type: ERROR

Impact: Configuration

JRF-20029: MapModulesToServers is disabled, cannot modify target of application {0}.
Cause: MapModulesToServers is disabled, cannot modify target of application.
Action: Enable MapModulesToServers task for this application

Level: 1

Type: ERROR

Impact: Configuration

JRF-20030: Enable StartupBeansService failed on server {0}.
Cause: Enable StartupBeansService failed
Action: Verify server connection

Level: 1

Type: ERROR

Impact: Configuration

JRF-20031: Initializing sun.awt.AppContext to avoid a redeployment leak. Please see bug 7711331
Cause: Avoid a redeployment leak
Action: Initializing sun.awt.AppContext

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20032: sun.awt.AppContext not found
Cause: sun.awt.AppContext not found
Action: Verify jdk

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20033: JRF startups - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual startup stacktrace are included in the error log.
Cause: JRF is not configured properly
Action: Resolve these issues

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20034: JRF shutdowns - {0} failed. JRF is not configured properly. Resolve these issues before continuing. Individual shutdown stacktrace are included in the error log.
Cause: JRF is not configured properly
Action: Resolve these issues

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20035: invalid format.
Cause: invalid url format
Action: fix url format

Level: 1

Type: NOTIFICATION

Impact: Configuration

JRF-20036: checkIfJRFApplied api failed on target {0} with exception {1}
Cause: The operation that checks if JRF applied to a target server or cluster failed
Action: See message and exception stack trace in admin server log to debug

Level: 1

Type: NOTIFICATION

Impact: Configuration

PK`ux{PK8zDOEBPS/chapter_sdp_messages.htm SDP-25001 to SDP-26457

23 SDP-25001 to SDP-26457

SDP-25001: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25001: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25002: Unable to create JNDI Context
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25002: Unable to create JNDI Context
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25003: Unable to create an instance of Driver Locator
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25003: Unable to create an instance of Driver Locator
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25005: Failed to create Sending Core instance
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25005: Failed to create Sending Core instance
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25006: Failed to remove an EJB instance
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25006: Failed to remove an EJB instance
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25007: An error occurred while processing an outbound message.
Cause: The outbound JMS message does not contain a valid message or request information.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25007: An error occurred while processing an outbound message.
Cause: The outbound JMS message does not contain a valid message or request information.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25008: An error occurred while processing an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25008: An error occurred while processing an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25009: An error occurred while storing a message.
Cause: An exception has occurred while processing the message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25009: An error occurred while storing a message.
Cause: An exception has occurred while processing the message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25010: An error occurred while sending an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25010: An error occurred while sending an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25011: An error occurred while transforming an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25011: An error occurred while transforming an outbound message.
Cause: An exception has occurred while processing the outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25012: An error occurred while processing error statuses.
Cause: An exception has occurred while processing error statuses.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25012: An error occurred while processing error statuses.
Cause: An exception has occurred while processing error statuses.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25013: An error occurred while resending an outbound message.
Cause: An exception has occurred while processing the resent outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25013: An error occurred while resending an outbound message.
Cause: An exception has occurred while processing the resent outbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.
Cause: An error has occurred while transforming an outbound message.
Action: Use the messageId to trace the message handling.

Level: 1

Type: WARNING

Impact: Process

SDP-25015: There are no transformed messages of message {0} for recipients {1}. Skipping message delivery to these recipients.
Cause: An error has occurred while transforming an outbound message.
Action: Use the messageId to trace the message handling.

Level: 1

Type: WARNING

Impact: Process

SDP-25016: Could not get TimerService or Timers
Cause: Could not get TimerService or Timers.
Action: Check application server status.

Level: 1

Type: ERROR

Impact: Process

SDP-25016: Could not get TimerService or Timers
Cause: Could not get TimerService or Timers.
Action: Check application server status.

Level: 1

Type: ERROR

Impact: Process

SDP-25017: Could not cancel timer
Cause: Could not cancel timer
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25017: Could not cancel timer
Cause: Could not cancel timer
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25020: Unable to schedule a timed failover event
Cause: An exception has occurred while scheduling a timed failover event.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25020: Unable to schedule a timed failover event
Cause: An exception has occurred while scheduling a timed failover event.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25021: An error occurred while processing a timed failover event
Cause: An exception has occurred while processing a timed failover event.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25021: An error occurred while processing a timed failover event
Cause: An exception has occurred while processing a timed failover event.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25022: Unable to schedule a timed resend event
Cause: An exception has occurred while scheduling a timed resend event.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25022: Unable to schedule a timed resend event
Cause: An exception has occurred while scheduling a timed resend event.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.
Cause: An exception has occurred while scheduling a timer to refresh the driver cache.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25030: Unable to schedule a timer to refresh the driver locator cache.
Cause: An exception has occurred while scheduling a timer to refresh the driver cache.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25032: An error occurred while registering driver information {0}.
Cause: An exception has occurred while registering the driver information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25032: An error occurred while registering driver information {0}.
Cause: An exception has occurred while registering the driver information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25033: An error occurred while unregistering driver information {0}.
Cause: An exception has occurred while unregistering the driver information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25033: An error occurred while unregistering driver information {0}.
Cause: An exception has occurred while unregistering the driver information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}
Cause: A Messaging Driver registered with the Messaging Server
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25034: There are total {0} registered User Messaging Drivers. Driver(s): {1}
Cause: A Messaging Driver registered with the Messaging Server
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25035: Messaging store not found.
Cause: An exception has occurred while attempting to find the messaging store.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25035: Messaging store not found.
Cause: An exception has occurred while attempting to find the messaging store.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25037: Error while retrieving configuration property: {0}.
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25037: Error while retrieving configuration property: {0}.
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml' or the named property does not exist.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25038: Error while loading the messaging server configuration properties. Falling back to default configuration.
Cause: Unable to read from the messaging server configuration file 'configuration/appconfig.xml'.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25040: Unable to create an instance of CommandReceiverBean.
Cause: An exception has occurred while attempting to process a command.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25040: Unable to create an instance of CommandReceiverBean.
Cause: An exception has occurred while attempting to process a command.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25042: An error occurred while processing a command message.
Cause: An exception has occurred while attempting to process a command.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25042: An error occurred while processing a command message.
Cause: An exception has occurred while attempting to process a command.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25043: An unknown command message was received, ignoring: {0}.
Cause: The engine received an unknown command message and was unable to process the command.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25043: An unknown command message was received, ignoring: {0}.
Cause: The engine received an unknown command message and was unable to process the command.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25055: Failed to create Receiving Core instance.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25055: Failed to create Receiving Core instance.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25057: An error occurred while processing an inbound JMS message.
Cause: The inbound JMS message does not contain a valid message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25057: An error occurred while processing an inbound JMS message.
Cause: The inbound JMS message does not contain a valid message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25058: An error occurred while processing an inbound message.
Cause: An exception has occurred while processing the inbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25058: An error occurred while processing an inbound message.
Cause: An exception has occurred while processing the inbound message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25059: An unknown JMS message is received, ignoring: {0}.
Cause: The engine received an unknown JMS message and was unable to process it.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25059: An unknown JMS message is received, ignoring: {0}.
Cause: The engine received an unknown JMS message and was unable to process it.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25060: There is no application that has registered this address as an access point. The message will be delivered when the access point is registered. Address={0}
Cause: There is no application that has registered this recipient address as an access point.
Action: Register the access point. The message is kept in a pending queue until an application registers a corresponding access point.

Level: 1

Type: WARNING

Impact: Process

SDP-25060: There is no application that has registered this address as an access point. The message will be delivered when the access point is registered. Address={0}
Cause: There is no application that has registered this recipient address as an access point.
Action: Register the access point. The message is kept in a pending queue until an application registers a corresponding access point.

Level: 1

Type: WARNING

Impact: Process

SDP-25061: An error occurred while processing inbound message statuses.
Cause: An exception has occurred while attempting to process inbound message statuses.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25061: An error occurred while processing inbound message statuses.
Cause: An exception has occurred while attempting to process inbound message statuses.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25062: Cannot correlate status with any message; storing for possible later processing.
Cause: An inbound status arrived in an unexpected order.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25062: Cannot correlate status with any message; storing for possible later processing.
Cause: An inbound status arrived in an unexpected order.
Action: Check the current log file for additional details, if the system is not functional. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25063: Status not delivered to client since no client information found for application {0}
Cause: There is no application client information stored.
Action: Check the log file for additional information.

Level: 1

Type: WARNING

Impact: Process

SDP-25063: Status not delivered to client since no client information found for application {0}
Cause: There is no application client information stored.
Action: Check the log file for additional information.

Level: 1

Type: WARNING

Impact: Process

SDP-25064: An error occurred while recording a status processing update.
Cause: An exception has occurred while attempting to record a status processing update.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25064: An error occurred while recording a status processing update.
Cause: An exception has occurred while attempting to record a status processing update.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25065: An error occurred while sending a message to failover address {0}.
Cause: An exception has occurred while sending out a failover message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25065: An error occurred while sending a message to failover address {0}.
Cause: An exception has occurred while sending out a failover message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25066: An error occurred while processing an outbound message status.
Cause: An exception has occurred while attempting to process an outbound message status.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25066: An error occurred while processing an outbound message status.
Cause: An exception has occurred while attempting to process an outbound message status.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.
Cause: A severe configuration error has occurred and the system is not functional.
Action: Check the messaging engine configuration and the stack trace, if available, for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25070: Unable to retrieve messaging engine sending and/or receiving queues from configuration.
Cause: A severe configuration error has occurred and the system is not functional.
Action: Check the messaging engine configuration and the stack trace, if available, for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25081: An error occurred while adding a message converter rule: {0}
Cause: An invalid message converter rule was provided.
Action: Check the log file for additional details.

Level: 1

Type: WARNING

Impact: Process

SDP-25081: An error occurred while adding a message converter rule: {0}
Cause: An invalid message converter rule was provided.
Action: Check the log file for additional details.

Level: 1

Type: WARNING

Impact: Process

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).
Cause: An invalid message converter rule was provided.
Action: Check the log file for additional details.

Level: 1

Type: WARNING

Impact: Process

SDP-25082: No predicates and/or devices matched. Ignoring converter rule (MIME type: {0}, delivery type: {1}, predicate: {2}).
Cause: An invalid message converter rule was provided.
Action: Check the log file for additional details.

Level: 1

Type: WARNING

Impact: Process

SDP-25083: Message content is not an instance of MimeMultipart
Cause: An invalid message content was provided to this converter.
Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.

Level: 1

Type: WARNING

Impact: Process

SDP-25083: Message content is not an instance of MimeMultipart
Cause: An invalid message content was provided to this converter.
Action: Check the current log file for additional details. Check User Messaging Service Javadoc on OTN for more information on sending MimeMultipart messages.

Level: 1

Type: WARNING

Impact: Process

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.
Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.
Action: Ensure that messages are assigned unique Message IDs.

Level: 1

Type: WARNING

Impact: Process

SDP-25085: Message {0} has a nonunique Message ID or recipient, and does not look like a redelivery attempt.
Cause: A message was sent or received that appears to be a duplicate of an already processed message; re-enqueuing message with delay specified.
Action: Ensure that messages are assigned unique Message IDs.

Level: 1

Type: WARNING

Impact: Process

SDP-25088: Unable to refresh the driver locator cache, due to the following error: {0}
Cause: An error has occurred while refreshing the driver locator cache.
Action: Check the reported error message and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Process

SDP-25088: Unable to refresh the driver locator cache, due to the following error: {0}
Cause: An error has occurred while refreshing the driver locator cache.
Action: Check the reported error message and correct any configuration problems.

Level: 1

Type: ERROR

Impact: Process

SDP-25101: Caught a database exception.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25101: Caught a database exception.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25105: Initializing Messaging Store in {0} mode.
Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.
Action: n/a

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25105: Initializing Messaging Store in {0} mode.
Cause: Initializing Messaging Store in persistent mode. Message history will persist across server restarts.
Action: n/a

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25106: Conflicting recipient IDs for Message {0}.
Cause: A conflict between recipient identifiers has been detected.
Action: Ensure that applications are using unique Message IDs.

Level: 1

Type: WARNING

Impact: Process

SDP-25106: Conflicting recipient IDs for Message {0}.
Cause: A conflict between recipient identifiers has been detected.
Action: Ensure that applications are using unique Message IDs.

Level: 1

Type: WARNING

Impact: Process

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.
Cause: A status object returned from a driver contained a different Message ID than expected.
Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-25107: Message ID {0} in Status object does not match previously recorded Message ID {1}.
Cause: A status object returned from a driver contained a different Message ID than expected.
Action: Ensure that drivers are mapping Gateway IDs to Message IDs correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-25109: Could not initialize persistence context.
Cause: An exception has occurred while initializing the persistence context.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25109: Could not initialize persistence context.
Cause: An exception has occurred while initializing the persistence context.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}
Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.
Action: Check the reported error message and correct any configuration or database availability problems.

Level: 1

Type: WARNING

Impact: Process

SDP-25110: An error occurred while initializing persistence session, with the following error message: {0}
Cause: An error occurred while attempting to initialize and log in to the TopLink persistence session.
Action: Check the reported error message and correct any configuration or database availability problems.

Level: 1

Type: WARNING

Impact: Process

SDP-25201: No endpoint URL is available for the web service callback operation.
Cause: No endpoint URL is available for the web service listener callback.
Action: Ensure a valid callback URL is specified when registering a message or status listener.

Level: 1

Type: WARNING

Impact: Process

SDP-25201: No endpoint URL is available for the web service callback operation.
Cause: No endpoint URL is available for the web service listener callback.
Action: Ensure a valid callback URL is specified when registering a message or status listener.

Level: 1

Type: WARNING

Impact: Process

SDP-25202: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.
Cause: The client application sent a message without required attribute.
Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.

Level: 1

Type: WARNING

Impact: Process

SDP-25250: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25250: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25251: Messaging Exception while processing Parlay X request.
Cause: A Messaging Exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25251: Messaging Exception while processing Parlay X request.
Cause: A Messaging Exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25252: Exception while initializing Parlay X Messaging servlet.
Cause: An exception occurred while initializing the Parlay X Messaging servlet.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25252: Exception while initializing Parlay X Messaging servlet.
Cause: An exception occurred while initializing the Parlay X Messaging servlet.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25253: Exception while initializing Parlay X Messaging content servlet.
Cause: An exception occurred while initializing the Parlay X Messaging content servlet.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25253: Exception while initializing Parlay X Messaging content servlet.
Cause: An exception occurred while initializing the Parlay X Messaging content servlet.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25254: Exception while processing SOAP attachment content.
Cause: An exception occurred while processing message content in a SOAP attachment.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25254: Exception while processing SOAP attachment content.
Cause: An exception occurred while processing message content in a SOAP attachment.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.
Cause: The client application sent a message with multiple attachment parts.
Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.

Level: 1

Type: WARNING

Impact: Process

SDP-25255: Message contains multiple attachments. All but first attachment will be ignored.
Cause: The client application sent a message with multiple attachment parts.
Action: Client applications should send one attachment part per message. Complex content should be sent as a MIME Multipart object.

Level: 1

Type: WARNING

Impact: Process

SDP-25256: Parameter {0} is missing in SOAPMessageContext sent from client. Generating default value.
Cause: The client application sent a message without required attribute.
Action: Make sure the client application add ApplicationName, ApplicationInstanceName, and ClientType to the SOAPMessageContext.

Level: 1

Type: WARNING

Impact: Process

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.
Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.
Action: Ensure that the server's JAXP framework is configured correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-25257: Error initializing JAXP DatatypeFactory. Some data types may not be converted correctly.
Cause: Could not acquire instance of class javax.xml.datatype.DatatypeFactory. Marshalling/unmarshalling of some XML elements may not happen correctly.
Action: Ensure that the server's JAXP framework is configured correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.
Cause: Could not initialize the Servlet Endpoint Context.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25258: Error initializing the Servlet Endpoint Context. Parlay X module will not be able to service requests correctly.
Cause: Could not initialize the Servlet Endpoint Context.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.
Cause: Could not initialize internal Messaging Client endpoint.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25259: Error initializing access to Messaging Server. Parlay X module will not be able to service requests correctly.
Cause: Could not initialize internal Messaging Client endpoint.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25300: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25300: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25301: JNDI context is null.
Cause: JNDI context was null.
Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.

Level: 1

Type: ERROR

Impact: Process

SDP-25301: JNDI context is null.
Cause: JNDI context was null.
Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to instantiate a JNDI context.

Level: 1

Type: ERROR

Impact: Process

SDP-25302: EJB home for UserPrefsService is null.
Cause: EJB home for UserPrefsService is null.
Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.

Level: 1

Type: ERROR

Impact: Process

SDP-25302: EJB home for UserPrefsService is null.
Cause: EJB home for UserPrefsService is null.
Action: See the Javadoc on Oracle Technology Network (OTN) for more information about how to specify an EJB home.

Level: 1

Type: ERROR

Impact: Process

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.
Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25303: Unable to connect to User Messaging Service (UMS) server at {0}.
Cause: EJB Naming Exception was caught when creating a UserPrefsServices object.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25304: EJB Remote Exception was caught at server {0}
Cause: EJB Remote Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25304: EJB Remote Exception was caught at server {0}
Cause: EJB Remote Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25305: EJB Create Exception was caught at server {0}
Cause: EJB Create Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25305: EJB Create Exception was caught at server {0}
Cause: EJB Create Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25306: XML Document object is null.
Cause: XML Document object is null.
Action: Specify a valid XML document object.

Level: 1

Type: ERROR

Impact: Process

SDP-25306: XML Document object is null.
Cause: XML Document object is null.
Action: Specify a valid XML document object.

Level: 1

Type: ERROR

Impact: Process

SDP-25307: No file to upload. File name is not set.
Cause: The file name to be uploaded was not set.
Action: Invoke setFileName() to set the file name.

Level: 1

Type: ERROR

Impact: Process

SDP-25307: No file to upload. File name is not set.
Cause: The file name to be uploaded was not set.
Action: Invoke setFileName() to set the file name.

Level: 1

Type: ERROR

Impact: Process

SDP-25308: The file, {0}, cannot be read.
Cause: The file cannot be read.
Action: Check the file.

Level: 1

Type: ERROR

Impact: Process

SDP-25308: The file, {0}, cannot be read.
Cause: The file cannot be read.
Action: Check the file.

Level: 1

Type: ERROR

Impact: Process

SDP-25309: File not found: {0}
Cause: The file with the given file name does not exist.
Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.

Level: 1

Type: ERROR

Impact: Process

SDP-25309: File not found: {0}
Cause: The file with the given file name does not exist.
Action: Check to see if the path and file name are correct. File name must be in /path/filename or file://path/filename format.

Level: 1

Type: ERROR

Impact: Process

SDP-25310: The URL is malformed: {0}
Cause: The URL is malformed.
Action: The URL must be in file://path/filename format.

Level: 1

Type: ERROR

Impact: Process

SDP-25310: The URL is malformed: {0}
Cause: The URL is malformed.
Action: The URL must be in file://path/filename format.

Level: 1

Type: ERROR

Impact: Process

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}
Cause: The document cannot be uploaded because parser and stack were out of sync.
Action: Fix mismatched tags.

Level: 1

Type: ERROR

Impact: Process

SDP-25311: The document cannot be uploaded. Parser and stack are out of sync. Tag name: {0} Local name: {1}
Cause: The document cannot be uploaded because parser and stack were out of sync.
Action: Fix mismatched tags.

Level: 1

Type: ERROR

Impact: Process

SDP-25312: Provisioning Exception was caught.
Cause: Provisioning Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25312: Provisioning Exception was caught.
Cause: Provisioning Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25313: Null Pointer Exception was caught.
Cause: Null Pointer Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25313: Null Pointer Exception was caught.
Cause: Null Pointer Exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25314: Rule {0} is already defined.
Cause: Rule with the same name was already defined.
Action: Choose a different rule name to avoid conflict.

Level: 1

Type: ERROR

Impact: Process

SDP-25314: Rule {0} is already defined.
Cause: Rule with the same name was already defined.
Action: Choose a different rule name to avoid conflict.

Level: 1

Type: ERROR

Impact: Process

SDP-25316: Input parameter, UserPrefsServices, is null.
Cause: The UserPrefsServices object was null.
Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25316: Input parameter, UserPrefsServices, is null.
Cause: The UserPrefsServices object was null.
Action: Pass a valid UserPrefsServices object as a parameter. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25317: Required input parameter, UserID, is null.
Cause: Failed to invoke method, because required input parameter, UserID, is null.
Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25317: Required input parameter, UserID, is null.
Cause: Failed to invoke method, because required input parameter, UserID, is null.
Action: Pass a valid UserID. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25318: Invalid input parameter. DeviceAddress object is null.
Cause: Input parameter, DeviceAddress object, is null.
Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25318: Invalid input parameter. DeviceAddress object is null.
Cause: Input parameter, DeviceAddress object, is null.
Action: Pass a valid DeviceAddress object. Check User Messaging Service Javadoc on OTN for more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25319: UserRuleSet is not set. Call initProcessor() first.
Cause: UserRuleSet object is null.
Action: Call initProcessor() first to complete initialization.

Level: 1

Type: ERROR

Impact: Process

SDP-25319: UserRuleSet is not set. Call initProcessor() first.
Cause: UserRuleSet object is null.
Action: Call initProcessor() first to complete initialization.

Level: 1

Type: ERROR

Impact: Process

SDP-25320: Rule Set is null.
Cause: The Rule Set was not available or could not be created.
Action: Use a valid Rule Set.

Level: 1

Type: ERROR

Impact: Process

SDP-25320: Rule Set is null.
Cause: The Rule Set was not available or could not be created.
Action: Use a valid Rule Set.

Level: 1

Type: ERROR

Impact: Process

SDP-25321: XML String representing the Rule Set is null.
Cause: The XML document element representing the Rule Set was null or empty.
Action: Use a valid Rule Set XML element.

Level: 1

Type: ERROR

Impact: Process

SDP-25321: XML String representing the Rule Set is null.
Cause: The XML document element representing the Rule Set was null or empty.
Action: Use a valid Rule Set XML element.

Level: 1

Type: ERROR

Impact: Process

SDP-25322: User Rule Set is null.
Cause: The User Rule Set was not available or could not be created.
Action: Use a valid User Rule Set object.

Level: 1

Type: ERROR

Impact: Process

SDP-25322: User Rule Set is null.
Cause: The User Rule Set was not available or could not be created.
Action: Use a valid User Rule Set object.

Level: 1

Type: ERROR

Impact: Process

SDP-25323: User Rule Set is inconsistent. See exception for more details.
Cause: User Rule Set is inconsistent.
Action: Check User Rule Set for consistency.

Level: 1

Type: ERROR

Impact: Process

SDP-25323: User Rule Set is inconsistent. See exception for more details.
Cause: User Rule Set is inconsistent.
Action: Check User Rule Set for consistency.

Level: 1

Type: ERROR

Impact: Process

SDP-25324: XML document is invalid. See exception for details.
Cause: XML document is invalid. See stacktrace for more details.
Action: Validate the XML document.

Level: 1

Type: ERROR

Impact: Process

SDP-25324: XML document is invalid. See exception for details.
Cause: XML document is invalid. See stacktrace for more details.
Action: Validate the XML document.

Level: 1

Type: ERROR

Impact: Process

SDP-25325: Cannot serialize Rule Session.
Cause: Cannot serialize Rule Session, which is not critical.
Action: No action needed.

Level: 1

Type: WARNING

Impact: Process

SDP-25325: Cannot serialize Rule Session.
Cause: Cannot serialize Rule Session, which is not critical.
Action: No action needed.

Level: 1

Type: WARNING

Impact: Process

SDP-25326: Filter XML is null.
Cause: The Preference Rules were missing or inconsistent.
Action: Use a well-formed User Preference XML document.

Level: 1

Type: ERROR

Impact: Process

SDP-25326: Filter XML is null.
Cause: The Preference Rules were missing or inconsistent.
Action: Use a well-formed User Preference XML document.

Level: 1

Type: ERROR

Impact: Process

SDP-25327: Cannot create Rule Session.
Cause: Cannot create Rule Session.
Action: No action needed.

Level: 1

Type: WARNING

Impact: Process

SDP-25327: Cannot create Rule Session.
Cause: Cannot create Rule Session.
Action: No action needed.

Level: 1

Type: WARNING

Impact: Process

SDP-25328: UserPrefsException was caught.
Cause: UserPrefsException was caught.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25328: UserPrefsException was caught.
Cause: UserPrefsException was caught.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25329: Rule {0} does not exist.
Cause: The expected rule was not found.
Action: Check the rule by name on the User Preference page.

Level: 1

Type: ERROR

Impact: Process

SDP-25329: Rule {0} does not exist.
Cause: The expected rule was not found.
Action: Check the rule by name on the User Preference page.

Level: 1

Type: ERROR

Impact: Process

SDP-25330: Business Term Type has changed. Term = {0}
Cause: Business Term Type has changed.
Action: Recheck the Preference Rules.

Level: 1

Type: WARNING

Impact: Process

SDP-25330: Business Term Type has changed. Term = {0}
Cause: Business Term Type has changed.
Action: Recheck the Preference Rules.

Level: 1

Type: WARNING

Impact: Process

SDP-25331: Cannot instantiate User Preferences Services.
Cause: Cannot instantiate User Preferences Services due to an initialization error.
Action: Check User Prefs Services configuration.

Level: 1

Type: WARNING

Impact: Process

SDP-25331: Cannot instantiate User Preferences Services.
Cause: Cannot instantiate User Preferences Services due to an initialization error.
Action: Check User Prefs Services configuration.

Level: 1

Type: WARNING

Impact: Process

SDP-25332: Directory for User Preferences Services File Persistence does not exist.
Cause: Directory for User Preferences Services File Persistence does not exist.
Action: System will try to create the directory.

Level: 1

Type: WARNING

Impact: Process

SDP-25332: Directory for User Preferences Services File Persistence does not exist.
Cause: Directory for User Preferences Services File Persistence does not exist.
Action: System will try to create the directory.

Level: 1

Type: WARNING

Impact: Process

SDP-25333: Invalid directory: {0}
Cause: The given path was not a valid directory.
Action: Specify a valid directory, not a file.

Level: 1

Type: WARNING

Impact: Process

SDP-25333: Invalid directory: {0}
Cause: The given path was not a valid directory.
Action: Specify a valid directory, not a file.

Level: 1

Type: WARNING

Impact: Process

SDP-25334: Device name is null.
Cause: Device name is null.
Action: Provide a valid Device name.

Level: 1

Type: ERROR

Impact: Process

SDP-25334: Device name is null.
Cause: Device name is null.
Action: Provide a valid Device name.

Level: 1

Type: ERROR

Impact: Process

SDP-25335: invalid user ID: {0}
Cause: An invalid user ID was specified.
Action: Specify a valid user ID.

Level: 1

Type: WARNING

Impact: Process

SDP-25335: invalid user ID: {0}
Cause: An invalid user ID was specified.
Action: Specify a valid user ID.

Level: 1

Type: WARNING

Impact: Process

SDP-25336: Input parameter, UserPrefsObject, is null.
Cause: Required parameter, UserPrefsObject, is null.
Action: Provide a valid UserPrefsObject.

Level: 1

Type: ERROR

Impact: Process

SDP-25336: Input parameter, UserPrefsObject, is null.
Cause: Required parameter, UserPrefsObject, is null.
Action: Provide a valid UserPrefsObject.

Level: 1

Type: ERROR

Impact: Process

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.
Cause: Origin rule number is not valid.
Action: Specify a valid rule number.

Level: 1

Type: ERROR

Impact: Process

SDP-25337: Failed to move a rule: origin rule number is out of the range of existing rules.
Cause: Origin rule number is not valid.
Action: Specify a valid rule number.

Level: 1

Type: ERROR

Impact: Process

SDP-25338: Cannot find object to update: {0}
Cause: Cannot find object to update.
Action: Could be a problem in implementing persistence.

Level: 1

Type: ERROR

Impact: Process

SDP-25338: Cannot find object to update: {0}
Cause: Cannot find object to update.
Action: Could be a problem in implementing persistence.

Level: 1

Type: ERROR

Impact: Process

SDP-25339: Object already exists.
Cause: Tried to persist an object that already exists.
Action: To overwrite existing value, use '-overwrite' flag.

Level: 1

Type: ERROR

Impact: Process

SDP-25339: Object already exists.
Cause: Tried to persist an object that already exists.
Action: To overwrite existing value, use '-overwrite' flag.

Level: 1

Type: ERROR

Impact: Process

SDP-25340: Object not found.
Cause: Tried to remove an object that does not exist.
Action: (None)

Level: 1

Type: ERROR

Impact: Process

SDP-25340: Object not found.
Cause: Tried to remove an object that does not exist.
Action: (None)

Level: 1

Type: ERROR

Impact: Process

SDP-25341: The order of calling methods is wrong.
Cause: The order of calling methods is wrong.
Action: Check the order of the methods being called.

Level: 1

Type: ERROR

Impact: Process

SDP-25341: The order of calling methods is wrong.
Cause: The order of calling methods is wrong.
Action: Check the order of the methods being called.

Level: 1

Type: ERROR

Impact: Process

SDP-25342: Cannot find default address for user {0}.
Cause: The default address of that user was not set.
Action: Check that default address is set from UserPreference Administrator page.

Level: 1

Type: ERROR

Impact: Process

SDP-25342: Cannot find default address for user {0}.
Cause: The default address of that user was not set.
Action: Check that default address is set from UserPreference Administrator page.

Level: 1

Type: ERROR

Impact: Process

SDP-25343: No devices are defined.
Cause: Tried to call delivery preferences without defining devices.
Action: Define devices for use with delivery preferences.

Level: 1

Type: ERROR

Impact: Process

SDP-25343: No devices are defined.
Cause: Tried to call delivery preferences without defining devices.
Action: Define devices for use with delivery preferences.

Level: 1

Type: ERROR

Impact: Process

SDP-25344: Invalid action {0} is found and ignored.
Cause: An invalid action was detected.
Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.

Level: 1

Type: WARNING

Impact: Process

SDP-25344: Invalid action {0} is found and ignored.
Cause: An invalid action was detected.
Action: Use one of the valid actions: BROADCAST, FAIL_OVER, and DO_NOT_SEND.

Level: 1

Type: WARNING

Impact: Process

SDP-25345: Runtime exception was caught.
Cause: Runtime exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25345: Runtime exception was caught.
Cause: Runtime exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25346: No configured Business Terms are available, only system terms will be used.
Cause: Business Term configuration could not be read.
Action: Ensure that business term configuration is correct

Level: 1

Type: WARNING

Impact: Process

SDP-25346: No configured Business Terms are available, only system terms will be used.
Cause: Business Term configuration could not be read.
Action: Ensure that business term configuration is correct

Level: 1

Type: WARNING

Impact: Process

SDP-25347: Device {0} cannot be added because it is present in the list.
Cause: A device was present in the list already.
Action: Ensure that the device to be added is not in the device list.

Level: 1

Type: WARNING

Impact: Process

SDP-25347: Device {0} cannot be added because it is present in the list.
Cause: A device was present in the list already.
Action: Ensure that the device to be added is not in the device list.

Level: 1

Type: WARNING

Impact: Process

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.
Cause: Device ID index number is not valid.
Action: Specify a valid device ID index number.

Level: 1

Type: ERROR

Impact: Process

SDP-25348: Failed to move a device: device ID index number is out of the range of device list.
Cause: Device ID index number is not valid.
Action: Specify a valid device ID index number.

Level: 1

Type: ERROR

Impact: Process

SDP-25349: Name of rule is not set.
Cause: Rule name was not set.
Action: Set the name of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25349: Name of rule is not set.
Cause: Rule name was not set.
Action: Set the name of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25350: FilterOperation of a rule is not set.
Cause: FilterOperation of a rule was not set.
Action: Set the FilterOperation of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25350: FilterOperation of a rule is not set.
Cause: FilterOperation of a rule was not set.
Action: Set the FilterOperation of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25351: ActionOperation of a rule is not set.
Cause: ActionOperation of a rule was not set.
Action: Set the ActionOperation of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25351: ActionOperation of a rule is not set.
Cause: ActionOperation of a rule was not set.
Action: Set the ActionOperation of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25352: Condition of a rule is not set.
Cause: Condition of a rule was not set.
Action: Set the condition of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25352: Condition of a rule is not set.
Cause: Condition of a rule was not set.
Action: Set the condition of the rule.

Level: 1

Type: ERROR

Impact: Process

SDP-25353: unable to send a BROADCAST message because no address is set
Cause: An address has not been set for the BROADCAST action.
Action: Set at least one address for the BROADCAST action.

Level: 1

Type: ERROR

Impact: Process

SDP-25353: unable to send a BROADCAST message because no address is set
Cause: An address has not been set for the BROADCAST action.
Action: Set at least one address for the BROADCAST action.

Level: 1

Type: ERROR

Impact: Process

SDP-25354: A failover address is not set for the FAIL_OVER action.
Cause: An address has not been set for the FAIL_OVER action.
Action: Set at least one address for the FAIL_OVER action.

Level: 1

Type: ERROR

Impact: Process

SDP-25354: A failover address is not set for the FAIL_OVER action.
Cause: An address has not been set for the FAIL_OVER action.
Action: Set at least one address for the FAIL_OVER action.

Level: 1

Type: ERROR

Impact: Process

SDP-25355: Error while loading the business rule terms configuration
Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25355: Error while loading the business rule terms configuration
Cause: The business rule terms configuration file configuration/businessterms.xml could not be read.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.
Cause: An identical device address already exists.
Action: Remove the conflicting device address, overwrite it, or specify a different address.

Level: 1

Type: WARNING

Impact: Process

SDP-25356: Cannot persist device address {0} for user GUID {1}, because one already exists.
Cause: An identical device address already exists.
Action: Remove the conflicting device address, overwrite it, or specify a different address.

Level: 1

Type: WARNING

Impact: Process

SDP-25357: Cannot persist rule set for user GUID {0}, because one already exists.
Cause: A rule set already exists for this user.
Action: Remove the conflicting rule set, or overwrite it.

Level: 1

Type: ERROR

Impact: Process

SDP-25357: Cannot persist rule set for user GUID {0}, because one already exists.
Cause: A rule set already exists for this user.
Action: Remove the conflicting rule set, or overwrite it.

Level: 1

Type: ERROR

Impact: Process

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.
Cause: A rule set already exists for this user.
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Process

SDP-25358: Cannot upload rule set for user GUID {0}, because one already exists.
Cause: A rule set already exists for this user.
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Process

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.
Cause: A user device already exists for this user.
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Process

SDP-25359: Cannot upload user device for user GUID {0}, because one already exists.
Cause: A user device already exists for this user.
Action: Try uploading the user messaging preferences using merge option 'overwrite' or 'append' (refer to command help for details).

Level: 1

Type: ERROR

Impact: Process

SDP-25360: Initializing User Messaging Preferences services.
Cause: User Messaging Preferences services were initialized as part of application startup or deployment.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25360: Initializing User Messaging Preferences services.
Cause: User Messaging Preferences services were initialized as part of application startup or deployment.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25361: The Java VM does not support the encoding {0}.
Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.
Action: Check your server Java VM and make sure it supports the encoding.

Level: 1

Type: ERROR

Impact: Process

SDP-25361: The Java VM does not support the encoding {0}.
Cause: The Java VM does not support the encoding used for XML string representing the RuleSet.
Action: Check your server Java VM and make sure it supports the encoding.

Level: 1

Type: ERROR

Impact: Process

SDP-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.
Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.
Action: None.

Level: 1

Type: ERROR

Impact: Process

SDP-25362: This User Preference object cannot be deleted because it is backed by the user profile in the identity store: {0}.
Cause: An attempt was made to delete a read-only object backed by the user profile in the identity store.
Action: None.

Level: 1

Type: ERROR

Impact: Process

SDP-25363: No UserRuleSet exists for userID {0}.
Cause: The user does not have a UserRuleSet.
Action: Check spelling of user ID.

Level: 1

Type: ERROR

Impact: Process

SDP-25363: No UserRuleSet exists for userID {0}.
Cause: The user does not have a UserRuleSet.
Action: Check spelling of user ID.

Level: 1

Type: ERROR

Impact: Process

SDP-25364: setFilterOperation has not been called.
Cause: Incorrect calling sequence.
Action: Invoke method setFilterOperation() first.

Level: 1

Type: ERROR

Impact: Process

SDP-25364: setFilterOperation has not been called.
Cause: Incorrect calling sequence.
Action: Invoke method setFilterOperation() first.

Level: 1

Type: ERROR

Impact: Process

SDP-25365: Condition does not exist: {0}
Cause: Condition cannot be found.
Action: Check spelling of condition name or ID.

Level: 1

Type: ERROR

Impact: Process

SDP-25365: Condition does not exist: {0}
Cause: Condition cannot be found.
Action: Check spelling of condition name or ID.

Level: 1

Type: ERROR

Impact: Process

SDP-25366: Source parameter is greater than the number of conditions.
Cause: Source parameter is out of range.
Action: Provide correct source parameter.

Level: 1

Type: ERROR

Impact: Process

SDP-25366: Source parameter is greater than the number of conditions.
Cause: Source parameter is out of range.
Action: Provide correct source parameter.

Level: 1

Type: ERROR

Impact: Process

SDP-25367: Error creating FilterCondition, type {0} is not valid.
Cause: Incorrect type has been found.
Action: Use correct type.

Level: 1

Type: ERROR

Impact: Process

SDP-25367: Error creating FilterCondition, type {0} is not valid.
Cause: Incorrect type has been found.
Action: Use correct type.

Level: 1

Type: ERROR

Impact: Process

SDP-25368: Term {0} is not valid.
Cause: Term is not valid.
Action: Use a valid term.

Level: 1

Type: ERROR

Impact: Process

SDP-25368: Term {0} is not valid.
Cause: Term is not valid.
Action: Use a valid term.

Level: 1

Type: ERROR

Impact: Process

SDP-25369: Term of type {0} does not accept operation {1}.
Cause: Unmatched type and operation.
Action: Use matching type and operation.

Level: 1

Type: ERROR

Impact: Process

SDP-25369: Term of type {0} does not accept operation {1}.
Cause: Unmatched type and operation.
Action: Use matching type and operation.

Level: 1

Type: ERROR

Impact: Process

SDP-25370: Method setFilterTerm() has not been called.
Cause: setFilterTerm() method has not been called prior to current method invocation.
Action: Invoke setFilterTerm() first.

Level: 1

Type: ERROR

Impact: Process

SDP-25370: Method setFilterTerm() has not been called.
Cause: setFilterTerm() method has not been called prior to current method invocation.
Action: Invoke setFilterTerm() first.

Level: 1

Type: ERROR

Impact: Process

SDP-25371: FilterTerm should be initialized.
Cause: FilterTerm has not been initialized.
Action: Initialize FilterTerm first.

Level: 1

Type: ERROR

Impact: Process

SDP-25371: FilterTerm should be initialized.
Cause: FilterTerm has not been initialized.
Action: Initialize FilterTerm first.

Level: 1

Type: ERROR

Impact: Process

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}
Cause: Name of filter term does not match the name of filter condition.
Action: Fix the inconsistency of filter term name and filter condition name.

Level: 1

Type: ERROR

Impact: Process

SDP-25372: Inconsistent FilterTerm.getName() : {0}, {1}
Cause: Name of filter term does not match the name of filter condition.
Action: Fix the inconsistency of filter term name and filter condition name.

Level: 1

Type: ERROR

Impact: Process

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}
Cause: Type name of filter term does not match the name of filter condition.
Action: Fix the inconsistency of filter term type name and filter condition type name.

Level: 1

Type: ERROR

Impact: Process

SDP-25373: Inconsistent FilterTerm.getTypeName() : {0}, {1}
Cause: Type name of filter term does not match the name of filter condition.
Action: Fix the inconsistency of filter term type name and filter condition type name.

Level: 1

Type: ERROR

Impact: Process

SDP-25374: Term operation should be defined.
Cause: Undefined term operation.
Action: Define operation of the term.

Level: 1

Type: ERROR

Impact: Process

SDP-25374: Term operation should be defined.
Cause: Undefined term operation.
Action: Define operation of the term.

Level: 1

Type: ERROR

Impact: Process

SDP-25375: Term of type {0} does not accept operation {1}.
Cause: Operation was not accepted by the term.
Action: Specify an operation that can be accepted by the term.

Level: 1

Type: ERROR

Impact: Process

SDP-25375: Term of type {0} does not accept operation {1}.
Cause: Operation was not accepted by the term.
Action: Specify an operation that can be accepted by the term.

Level: 1

Type: ERROR

Impact: Process

SDP-25376: TermOperation must be set.
Cause: TermOperation was not set.
Action: Set TermOperation properly.

Level: 1

Type: ERROR

Impact: Process

SDP-25376: TermOperation must be set.
Cause: TermOperation was not set.
Action: Set TermOperation properly.

Level: 1

Type: ERROR

Impact: Process

SDP-25377: Operand {0} just allows {1} arguments, but {2} is given.
Cause: Number of arguments does not meet the requirement of the operand.
Action: Set correct number of arguments.

Level: 1

Type: ERROR

Impact: Process

SDP-25377: Operand {0} just allows {1} arguments, but {2} is given.
Cause: Number of arguments does not meet the requirement of the operand.
Action: Set correct number of arguments.

Level: 1

Type: ERROR

Impact: Process

SDP-25378: Object {0} should be of type {1}.
Cause: Object has an incorrect Java type.
Action: Correct the type of object.

Level: 1

Type: ERROR

Impact: Process

SDP-25378: Object {0} should be of type {1}.
Cause: Object has an incorrect Java type.
Action: Correct the type of object.

Level: 1

Type: ERROR

Impact: Process

SDP-25379: Type {0} is not supported.
Cause: Object's type is not supported by User Preferences.
Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date

Level: 1

Type: ERROR

Impact: Process

SDP-25379: Type {0} is not supported.
Cause: Object's type is not supported by User Preferences.
Action: Change the type of object to one of following supported Java types: String, Integer, Double and Date

Level: 1

Type: ERROR

Impact: Process

SDP-25380: User {0} does not exist in the system.
Cause: User name not found.
Action: Provide the correct user name.

Level: 1

Type: ERROR

Impact: Process

SDP-25380: User {0} does not exist in the system.
Cause: User name not found.
Action: Provide the correct user name.

Level: 1

Type: ERROR

Impact: Process

SDP-25381: Device not found for user {0}.
Cause: Device does not exist.
Action: Provide a valid Device name or username.

Level: 1

Type: ERROR

Impact: Process

SDP-25381: Device not found for user {0}.
Cause: Device does not exist.
Action: Provide a valid Device name or username.

Level: 1

Type: ERROR

Impact: Process

SDP-25382: DeliveryType is missing in the address {0}.
Cause: Address does not have required DeliveryType.
Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.

Level: 1

Type: ERROR

Impact: Process

SDP-25382: DeliveryType is missing in the address {0}.
Cause: Address does not have required DeliveryType.
Action: Provide a valid DeliveryType in the address in <DeliveryType>:<Address> format.

Level: 1

Type: ERROR

Impact: Process

SDP-25383: Cannot persist device address {0}.
Cause: An exception occurred when storing device address.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25383: Cannot persist device address {0}.
Cause: An exception occurred when storing device address.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25384: Cannot create RuleSet for the user {0}.
Cause: An exception occurred while creating RuleSet for this user.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25384: Cannot create RuleSet for the user {0}.
Cause: An exception occurred while creating RuleSet for this user.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.
Cause: An exception occurred while savinging RuleSet for this user.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25385: Saving UserRuleSet failed. Cannot get XMLString for user {0}.
Cause: An exception occurred while savinging RuleSet for this user.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25386: Could not find entity to update.
Cause: Unable to find the entity in storage.
Action: None.

Level: 1

Type: ERROR

Impact: Process

SDP-25386: Could not find entity to update.
Cause: Unable to find the entity in storage.
Action: None.

Level: 1

Type: ERROR

Impact: Process

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.
Cause: The fact from user or application had an incorrect data type.
Action: Provide the fact with the correct data type as indicated.

Level: 1

Type: WARNING

Impact: Process

SDP-25387: Rule fact for term {0} has been ignored as it does not have the correct type, {1}.
Cause: The fact from user or application had an incorrect data type.
Action: Provide the fact with the correct data type as indicated.

Level: 1

Type: WARNING

Impact: Process

SDP-25388: Device named {0} of user {1} not found.
Cause: The user does not have a device with that name.
Action: Check username and device name.

Level: 1

Type: WARNING

Impact: Process

SDP-25388: Device named {0} of user {1} not found.
Cause: The user does not have a device with that name.
Action: Check username and device name.

Level: 1

Type: WARNING

Impact: Process

SDP-25389: Error while loading profiles.xml
Cause: The configuration file configuration/profiles.xml could not be read.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25389: Error while loading profiles.xml
Cause: The configuration file configuration/profiles.xml could not be read.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25390: Failed to set default address of MESSAGING of user {0}
Cause: Failed to set default address
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25390: Failed to set default address of MESSAGING of user {0}
Cause: Failed to set default address
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25400: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25400: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25401: Unable to set the parameter {0} in the configuration because of exception {1}.
Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25401: Unable to set the parameter {0} in the configuration because of exception {1}.
Cause: An exception has occurred while attempting to set the specified parameter in the configuration object.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.
Cause: There is no such entry for the parameter {0} in the configuration file.
Action: Check configuration parameter.

Level: 1

Type: ERROR

Impact: Process

SDP-25402: Could not find the value for the configuration parameter {0}, using default value.
Cause: There is no such entry for the parameter {0} in the configuration file.
Action: Check configuration parameter.

Level: 1

Type: ERROR

Impact: Process

SDP-25403: Error in registering messaging Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-25403: Error in registering messaging Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-25404: Error in unregistering messaging Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25404: Error in unregistering messaging Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans
Cause: Naming exception thrown while looking up the Management Store EJB.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25405: Naming exception thrown looking up Management Store: Unable to initialize SDP Messaging Runtime MBeans
Cause: Naming exception thrown while looking up the Management Store EJB.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.
Cause: Create exception thrown while creating Management Store EJB.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25406: Create exception thrown while creating Management Store: Unable to initialize SDP Messaging Runtime MBeans.
Cause: Create exception thrown while creating Management Store EJB.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25407: Exception initializing Runtime MBean.
Cause: An exception was thrown during runtime MBean initialization.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25407: Exception initializing Runtime MBean.
Cause: An exception was thrown during runtime MBean initialization.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}
Cause: Invalid combination of query parameters or invalid query value.
Action: Check stack trace.

Level: 1

Type: WARNING

Impact: Process

SDP-25408: Invalid query parameter: query field: {0}, query condition: {1}, query value: {2}
Cause: Invalid combination of query parameters or invalid query value.
Action: Check stack trace.

Level: 1

Type: WARNING

Impact: Process

SDP-25409: Unable to initialize the composite type for the MBean.
Cause: OpenDataException was caught.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25409: Unable to initialize the composite type for the MBean.
Cause: OpenDataException was caught.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}
Cause: OpenDataException was caught.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25410: Unable to convert to composite type and return composite data for the MBean. Name: {0}
Cause: OpenDataException was caught.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25411: Unable to load Driver properties.
Cause: An exception has occurred while attempting to load the driver configuration properties.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25411: Unable to load Driver properties.
Cause: An exception has occurred while attempting to load the driver configuration properties.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.
Cause: There is no such entry for the parameter {0} in the configuration file.
Action: Check configuration parameter.

Level: 1

Type: WARNING

Impact: Process

SDP-25413: Could not find the value for the configuration parameter {0}, using default value.
Cause: There is no such entry for the parameter {0} in the configuration file.
Action: Check configuration parameter.

Level: 1

Type: WARNING

Impact: Process

SDP-25414: Could not find the application deployment MBean for {0}
Cause: The application may not have started correctly.
Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25414: Could not find the application deployment MBean for {0}
Cause: The application may not have started correctly.
Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}
Cause: The application may not have started correctly.
Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25415: Found multiple application deployment MBeans for {0}
Cause: The application may not have started correctly.
Action: Check the application deployment status.

Level: 1

Type: WARNING

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}
Cause: An exception was thrown while attempting to get the parent server MBean.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25416: Error occurred while attempting to get the parent server MBean for {0}
Cause: An exception was thrown while attempting to get the parent server MBean.
Action: Check stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-25500: Failed to schedule Work
Cause: Work could not be scheduled in the WorkManager
Action: Check stacktrace and WorkManager configuration

Level: 1

Type: ERROR

Impact: Process

SDP-25500: Failed to schedule Work
Cause: Work could not be scheduled in the WorkManager
Action: Check stacktrace and WorkManager configuration

Level: 1

Type: ERROR

Impact: Process

SDP-25501: Exception when delivering pending messages
Cause: Exception when delivering pending messages
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25501: Exception when delivering pending messages
Cause: Exception when delivering pending messages
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25502: Unable to create JNDI Context
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25502: Unable to create JNDI Context
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25503: Unable to connect to the messaging server.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25503: Unable to connect to the messaging server.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25504: Unable to register application information with the messaging server.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25504: Unable to register application information with the messaging server.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check that the messaging server is up. Check the JNDI Context initialization parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-25505: Unable to enqueue outbound message.
Cause: Engine Sending Queue may not be available.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25505: Unable to enqueue outbound message.
Cause: Engine Sending Queue may not be available.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25506: Unable to get receiving queues from application information.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the Application information properties.

Level: 1

Type: ERROR

Impact: Process

SDP-25506: Unable to get receiving queues from application information.
Cause: An exception has occurred.
Action: Check the stack trace for more details. Check the Application information properties.

Level: 1

Type: ERROR

Impact: Process

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.
Cause: The client is not aware of any engine queues to enqueue the status.
Action: Check that the application is registered successfully with the messaging server.

Level: 1

Type: ERROR

Impact: Process

SDP-25507: Unable to enqueue inbound message status because no engine queues were found.
Cause: The client is not aware of any engine queues to enqueue the status.
Action: Check that the application is registered successfully with the messaging server.

Level: 1

Type: ERROR

Impact: Process

SDP-25508: Unable to enqueue inbound message status.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25508: Unable to enqueue inbound message status.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25509: An error occurred while notifying the MessageDispatcherBean about engine queues.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25509: An error occurred while notifying the MessageDispatcherBean about engine queues.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25510: An error occurred while attempting to retrieve the actual password from the credential store.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.
Cause: An invalid JMS message was dequeued by the Dispatcher MDB.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25511: An error occurred while dequeuing a message from the application receiving queue.
Cause: An invalid JMS message was dequeued by the Dispatcher MDB.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}
Cause: An invalid JMS message was dequeued by the Dispatcher MDB.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25512: An invalid message was dequeued from the application receiving queue: {0}
Cause: An invalid JMS message was dequeued by the Dispatcher MDB.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25513: JNDI lookup of application callback listener failed.
Cause: An invalid callback listener was previously registered and could not be invoked.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25513: JNDI lookup of application callback listener failed.
Cause: An invalid callback listener was previously registered and could not be invoked.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25514: An error occurred while dispatching an inbound message to the application. {0}
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25514: An error occurred while dispatching an inbound message to the application. {0}
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25515: An error occurred while dispatching an inbound status to the application. {0}
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25515: An error occurred while dispatching an inbound status to the application. {0}
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.
Cause: Message/Status listener was not configured by the application.
Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25516: Message/Status listener not configured. Suspending messaging client MDB to disable asynchronous message/status callbacks.
Cause: Message/Status listener was not configured by the application.
Action: If the application requires asynchronous message/status callbacks, configure the listener information. Otherwise, ignore this warning.

Level: 1

Type: WARNING

Impact: Process

SDP-25517: Messaging client MDB suspend failed: {0}
Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.
Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.

Level: 1

Type: WARNING

Impact: Process

SDP-25517: Messaging client MDB suspend failed: {0}
Cause: 1) The Messaging client was unable to access the MDB MBean because the container may not be in RUNNING state. 2) The server administrator username 'weblogic' does not exist.
Action: 1) Check the state of the container. Check the stack trace for more details. 2) Specify a valid server administrator username using the system property -Doracle.ums.admin.user and restart the server.

Level: 1

Type: WARNING

Impact: Process

SDP-25519: QueueWorker rejected
Cause: QueueWorker rejected
Action: Check WorkManager configuration.

Level: 1

Type: ERROR

Impact: Process

SDP-25519: QueueWorker rejected
Cause: QueueWorker rejected
Action: Check WorkManager configuration.

Level: 1

Type: ERROR

Impact: Process

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.
Cause: An exception has occurred when invoking webservice send().
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25520: MessagingWebServiceClientImpl.send() operation failed.
Cause: An exception has occurred when invoking webservice send().
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.
Cause: An exception has occurred while receiving messages from webservice.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25521: MessagingWebServiceClientImpl.receive() operation failed.
Cause: An exception has occurred while receiving messages from webservice.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25522: The application onMessage() callback operation failed.
Cause: An exception has occurred while attempting to call the application onMessage callback method.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25522: The application onMessage() callback operation failed.
Cause: An exception has occurred while attempting to call the application onMessage callback method.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25523: The application onStatus() callback operation failed.
Cause: An exception has occurred while attempting to call the application onStatus callback method.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25523: The application onStatus() callback operation failed.
Cause: An exception has occurred while attempting to call the application onStatus callback method.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25524: Client called the deprecated method acknowledge()
Cause: The method acknowledge is deprecated.
Action: Use global transactions instead to achieve reliable message reception.

Level: 1

Type: WARNING

Impact: Process

SDP-25524: Client called the deprecated method acknowledge()
Cause: The method acknowledge is deprecated.
Action: Use global transactions instead to achieve reliable message reception.

Level: 1

Type: WARNING

Impact: Process

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25532: An error occurred while retrieving the Application Information from the application JNDI context.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25541: An error occurred while generating received message statuses.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25541: An error occurred while generating received message statuses.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.
Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).
Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.

Level: 1

Type: WARNING

Impact: Process

SDP-25542: Security principal in client EJB Context "{0}" does not match security principal in ApplicationInfo "{1}". This may cause permission errors during future Messaging Client operations.
Cause: The security principal in the current EJBContext is different from the ApplicationInfo security principal field specified when creating the Messaging Client instance (or the default value, if no principal was provided).
Action: Ensure that the security principals used by this application for all Messaging Client operations match one another.

Level: 1

Type: WARNING

Impact: Process

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".
Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.
Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.

Level: 1

Type: WARNING

Impact: Process

SDP-25543: The current authenticated user "{0}" does not match the configured security principal "{1}".
Cause: The security principal in effect for the current thread is different from the security principal field specified when creating the Messaging Client instance.
Action: Ensure that the security principals used by this application for all Messaging Client operations match one another, or avoid configuring a specific security principal.

Level: 1

Type: WARNING

Impact: Process

SDP-25700: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25700: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25701: Unable to instantiate class {0}.
Cause: Unable to instantiate a class.
Action: Check to see if that class is in classpath or not.

Level: 1

Type: ERROR

Impact: Process

SDP-25701: Unable to instantiate class {0}.
Cause: Unable to instantiate a class.
Action: Check to see if that class is in classpath or not.

Level: 1

Type: ERROR

Impact: Process

SDP-25702: Unable to set content of Message object.
Cause: Unable to set content of a message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25702: Unable to set content of Message object.
Cause: Unable to set content of a message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25703: Exception when getting cluster name for server {0}
Cause: Could not get cluster name from RuntimeServiceMBean
Action: Check the stack trace for more details

Level: 1

Type: ERROR

Impact: Process

SDP-25703: Exception when getting cluster name for server {0}
Cause: Could not get cluster name from RuntimeServiceMBean
Action: Check the stack trace for more details

Level: 1

Type: ERROR

Impact: Process

SDP-25704: Error in setMultiplePayload.
Cause: An error occurred in setMultiplePayLoad().
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25704: Error in setMultiplePayload.
Cause: An error occurred in setMultiplePayLoad().
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25705: Exception printing message content.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25705: Exception printing message content.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25706: Failed to clone message content.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25706: Failed to clone message content.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25707: Failed to clone headers. Message = {0} .
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25707: Failed to clone headers. Message = {0} .
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25708: Unable to perform JNDI lookup of JMS QCF: {0}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25709: Unable to perform JNDI lookup.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25709: Unable to perform JNDI lookup.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25710: Exception caught when calling onMessage(), will rollback transaction.
Cause: Exception caught when calling onMessage(), will rollback transaction.
Action: Check log to get more information.

Level: 1

Type: WARNING

Impact: Process

SDP-25710: Exception caught when calling onMessage(), will rollback transaction.
Cause: Exception caught when calling onMessage(), will rollback transaction.
Action: Check log to get more information.

Level: 1

Type: WARNING

Impact: Process

SDP-25711: Received unknown object: {0} on queue {1}
Cause: Received unknown object in JMS queue
Action: Check log to get more information.

Level: 1

Type: WARNING

Impact: Process

SDP-25711: Received unknown object: {0} on queue {1}
Cause: Received unknown object in JMS queue
Action: Check log to get more information.

Level: 1

Type: WARNING

Impact: Process

SDP-25712: Message received with invalid format: {0} on queue {1}
Cause: Invalid message received on JMS queue
Action: Check log to get more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25712: Message received with invalid format: {0} on queue {1}
Cause: Invalid message received on JMS queue
Action: Check log to get more information.

Level: 1

Type: ERROR

Impact: Process

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25713: Unable to perform JNDI lookup of JMS Queue: {0}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25714: Access control exception was caught. Name: {0} Action:{1}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25714: Access control exception was caught. Name: {0} Action:{1}.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25715: Invalid format, skipping: {0}
Cause: Invalid queue information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25715: Invalid format, skipping: {0}
Cause: Invalid queue information.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}
Cause: Error occurred in looking up QueueConnectionFactory in JNDI.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25716: Error occurred in looking up QueueConnectionFactory in JNDI, skipping: {0}
Cause: Error occurred in looking up QueueConnectionFactory in JNDI.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.
Cause: Error occurred in looking up queue in JNDI.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25717: Error occurred in looking up Queue in JNDI, skipping: {0}.
Cause: Error occurred in looking up queue in JNDI.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25718: Error occurred in getQueueInfoList.
Cause: Error occurred in getQueueInfoList().
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25718: Error occurred in getQueueInfoList.
Cause: Error occurred in getQueueInfoList().
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-25719: Failed to authenticate user {0}.
Cause: Failed to authenticate a user.
Action: Check username and password and try again.

Level: 1

Type: ERROR

Impact: Process

SDP-25719: Failed to authenticate user {0}.
Cause: Failed to authenticate a user.
Action: Check username and password and try again.

Level: 1

Type: ERROR

Impact: Process

SDP-25720: Sender Address is null or empty.
Cause: Sender Address has an error.
Action: Enter a valid non-null value for sender.

Level: 1

Type: ERROR

Impact: Process

SDP-25720: Sender Address is null or empty.
Cause: Sender Address has an error.
Action: Enter a valid non-null value for sender.

Level: 1

Type: ERROR

Impact: Process

SDP-25721: Recipient Address is null or empty.
Cause: Recipient Address has an error.
Action: Enter a valid non-null value for Recipient.

Level: 1

Type: ERROR

Impact: Process

SDP-25721: Recipient Address is null or empty.
Cause: Recipient Address has an error.
Action: Enter a valid non-null value for Recipient.

Level: 1

Type: ERROR

Impact: Process

SDP-25722: Message content is empty.
Cause: Message content was not set properly.
Action: Enter a valid non-null value for the content.

Level: 1

Type: ERROR

Impact: Process

SDP-25722: Message content is empty.
Cause: Message content was not set properly.
Action: Enter a valid non-null value for the content.

Level: 1

Type: ERROR

Impact: Process

SDP-25723: Message object is null.
Cause: Message is null.
Action: Set a valid non-null value of Message object.

Level: 1

Type: ERROR

Impact: Process

SDP-25723: Message object is null.
Cause: Message is null.
Action: Set a valid non-null value of Message object.

Level: 1

Type: ERROR

Impact: Process

SDP-25724: Message subject and content are null.
Cause: Message subject and content.
Action: Enter a valid non-null value for subject and/or content.

Level: 1

Type: ERROR

Impact: Process

SDP-25724: Message subject and content are null.
Cause: Message subject and content.
Action: Enter a valid non-null value for subject and/or content.

Level: 1

Type: ERROR

Impact: Process

SDP-25725: Message serialization failed.
Cause: Failed to serialize message due to I/O Error.
Action: Ensure that content is being created according to recommendations for Message class.

Level: 1

Type: ERROR

Impact: Process

SDP-25725: Message serialization failed.
Cause: Failed to serialize message due to I/O Error.
Action: Ensure that content is being created according to recommendations for Message class.

Level: 1

Type: ERROR

Impact: Process

SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.
Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.
Action: Check the value of the remote host and the HTTP Proxy settings.

Level: 1

Type: ERROR

Impact: Process

SDP-25726: Connection failed to remote host {0} using HTTP Proxy {1}. Error: {2}.
Cause: There was a problem with either the remote host or the HTTP Proxy. Check the associated connection error for the exact cause.
Action: Check the value of the remote host and the HTTP Proxy settings.

Level: 1

Type: ERROR

Impact: Process

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.
Cause: There was a problem in the connection to the JMS provider.
Action: Check the container log for additional errors from the JMS adapter.

Level: 1

Type: ERROR

Impact: Process

SDP-25727: Unable to create JMS QueueSender, {0}. Cause: There was a problem in the connection to the JMS provider.
Cause: There was a problem in the connection to the JMS provider.
Action: Check the container log for additional errors from the JMS adapter.

Level: 1

Type: ERROR

Impact: Process

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.
Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.
Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25728: Could not determine server platform type. Generic values will be used for platform-specific data.
Cause: The Java EE server platform could not be determined. Either this application is executing in a Java SE environment, or the Java EE server is configured incorrectly.
Action: If executing in a Java SE environment, no action is necessary. Otherwise ensure that Java Required Files module is deployed to this environment.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}
Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.
Action: Ensure that any WS-Security policies are specified in the correct format.

Level: 1

Type: WARNING

Impact: Process

SDP-25729: An exception occurred while enabling the WS-Security configuration: {0}
Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.
Action: Ensure that any WS-Security policies are specified in the correct format.

Level: 1

Type: WARNING

Impact: Process

SDP-25730: QueueWorker got exception.
Cause: QueueWorker got exception.
Action: Check the log for related information.

Level: 1

Type: WARNING

Impact: Process

SDP-25730: QueueWorker got exception.
Cause: QueueWorker got exception.
Action: Check the log for related information.

Level: 1

Type: WARNING

Impact: Process

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25800: Oracle User Messaging Service configuration is successfully upgraded.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25801: Shall upgrade driver {0} using configuration file at {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25801: Shall upgrade driver {0} using configuration file at {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25802: Driver {0} upgraded using {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25802: Driver {0} upgraded using {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25803: Driver {0} already upgraded. Ignoring configuration in {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25803: Driver {0} already upgraded. Ignoring configuration in {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25804: Shall upgrade server {0} using configuration file at {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25804: Shall upgrade server {0} using configuration file at {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25805: Server {0} upgraded using {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25805: Server {0} upgraded using {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25806: Server {0} already upgraded. Ignoring configuration in {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25806: Server {0} already upgraded. Ignoring configuration in {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25807: Shall upgrade user preference configuration for {0} using file at {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25808: User preference configuration for {0} upgraded using {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}
Cause: An unexpected error occurred during Oracle User Messaging Service configuration upgrade.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25820: Error in upgrading Oracle User Messaging Service configuration. Reason: {0}
Cause: An unexpected error occurred during Oracle User Messaging Service configuration upgrade.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25821: Failed to read the configuration file {0}.
Cause: The configuration file is missing or in wrong format.
Action: Check if the configuration file exists with correct format. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25821: Failed to read the configuration file {0}.
Cause: The configuration file is missing or in wrong format.
Action: Check if the configuration file exists with correct format. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25822: Failed to save the configuration at {0}.
Cause: Error occured while saving the configuration to the configuration file.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25822: Failed to save the configuration at {0}.
Cause: Error occured while saving the configuration to the configuration file.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25823: Failed to delete the old driver configuration file at {0}.
Cause: Error occurred while deleting the old driver configuration file.
Action: Check the file system. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25823: Failed to delete the old configuration file at {0}.
Cause: Error occurred while deleting the old configuration file.
Action: Check the file system. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25824: Failed to parse the configuration file at {0}.
Cause: Error occured while parsing the configuration file.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25824: Failed to parse the configuration file at {0}.
Cause: Error occured while parsing the configuration file.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25850: Oracle User Messaging Service schema upgraded.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25850: Oracle User Messaging Service schema upgraded.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25851: Oracle User Messaging Service schema upgrade is valid.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25851: Oracle User Messaging Service schema upgrade is valid.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25852: Oracle User Messaging Service schema version {0} is the latest one. Upgrade is not required.
Cause: Specified Oracle User Messaging Service database schema version is the latest one. Upgrade is not required.
Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25852: Oracle User Messaging Service schema version {0} is the latest one. Upgrade is not required.
Cause: Specified Oracle User Messaging Service database schema version is the latest one. Upgrade is not required.
Action: No user action is required.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.
Cause: Specified User Messaging Service schema was updated but is invalid.
Action: Restore the User Messaging Service schema from a backup and retry. Check the error messages in Oracle User Messaging Service component log files. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25853: Oracle User Messaging Service schema upgrade is invalid.
Cause: Specified User Messaging Service schema was updated but is invalid.
Action: Restore the User Messaging Service schema from a backup and retry. Check the error messages in Oracle User Messaging Service component log files. Correct the problem before running the Upgrade Assistant again.

Level: 1

Type: ERROR

Impact: Process

SDP-25854: The upgrade is not supported from Oracle User Messaging Service schema version of {0}.
Cause: An unsupported base schema version was being upgraded.
Action: Refer to the Oracle User Messaging Service Upgrade Guide for supported versions to upgrade.

Level: 1

Type: ERROR

Impact: Process

SDP-25854: The upgrade is not supported from Oracle User Messaging Service schema version of {0}.
Cause: An unsupported base schema version was being upgraded.
Action: Refer to the Oracle User Messaging Service Upgrade Guide for supported versions to upgrade.

Level: 1

Type: ERROR

Impact: Process

SDP-25855: Error in upgrading Oracle User Messaging Service schema.
Cause: An unexpected error occurred during Oracle User Messaging Service schema upgrade.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25855: Error in upgrading Oracle User Messaging Service schema.
Cause: An unexpected error occurred during Oracle User Messaging Service schema upgrade.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25856: Oracle User Messaging Service schema status is invalid.
Cause: Specified Oracle User Messaging Service database schema was invalid.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-25856: Oracle User Messaging Service schema status is invalid.
Cause: Specified Oracle User Messaging Service database schema was invalid.
Action: Check the error messages in the log file. Correct the problem before running the Upgrade Assistant again. Contact Oracle Support Services if you are unable to correct the problem.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

SDP-26000: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26000: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26001: Cannot create JNDI Context.
Cause: Cannot create JNDI Context.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26001: Cannot create JNDI Context.
Cause: Cannot create JNDI Context.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26002: The driver {0} is operational
Cause: The driver is operational
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26002: The driver {0} is operational
Cause: The driver is operational
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26004: No Messaging Engine Queue information to enqueue status.
Cause: No Engine Queue information to enqueue status.
Action: Check that the Engine is deployed. Check Engine Queue information.

Level: 1

Type: ERROR

Impact: Process

SDP-26004: No Messaging Engine Queue information to enqueue status.
Cause: No Engine Queue information to enqueue status.
Action: Check that the Engine is deployed. Check Engine Queue information.

Level: 1

Type: ERROR

Impact: Process

SDP-26005: Dispatcher failed to find a driver.
Cause: Dispatcher failed to find a driver.
Action: Compare delivery type and content type between message and available drivers.

Level: 1

Type: WARNING

Impact: Process

SDP-26005: Dispatcher failed to find a driver.
Cause: Dispatcher failed to find a driver.
Action: Compare delivery type and content type between message and available drivers.

Level: 1

Type: WARNING

Impact: Process

SDP-26006: Exception while dispatching message to driver resource adapter.
Cause: Exception while dispatching message to driver resource adapter.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26006: Exception while dispatching message to driver resource adapter.
Cause: Exception while dispatching message to driver resource adapter.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26009: Could not get JNDI InitialContext.
Cause: None
Action: None

Level: 1

Type: ERROR

Impact: Process

SDP-26009: Could not get JNDI InitialContext.
Cause: None
Action: None

Level: 1

Type: ERROR

Impact: Process

SDP-26010: Unable to start driver: {0}.
Cause: Unable to start driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26010: Unable to start driver: {0}.
Cause: Unable to start driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo().
Cause: Exception thrown while invoking registerDriverInfo().
Action: Check stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26011: Failed to invoke registerDriverInfo().
Cause: Exception thrown while invoking registerDriverInfo().
Action: Check stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26012: Unable to remove scheduled workers
Cause: An exception has occurred while removing a driver thread.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26012: Unable to remove scheduled workers
Cause: An exception has occurred while removing a driver thread.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to cleanly stop driver: {0}.
Cause: Unable to cleanly stop driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26013: Unable to cleanly stop driver: {0}.
Cause: Unable to cleanly stop driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.
Cause: Exception occurred while processing inbound message/status.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26014: Unable to process inbound message/status.
Cause: Exception occurred while processing inbound message/status.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.
Cause: Exception occurred while processing command message.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26015: Unable to process command message.
Cause: Exception occurred while processing command message.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26016: Error occurred while attempting to get the parent server MBean for {0}
Cause: Error occurred while attempting to get the parent server MBean
Action: Check stack trace for more details

Level: 1

Type: ERROR

Impact: Process

SDP-26016: Error occurred while attempting to get the parent server MBean for {0}
Cause: Error occurred while attempting to get the parent server MBean
Action: Check stack trace for more details

Level: 1

Type: ERROR

Impact: Process

SDP-26019: Error occurred while registering driver {0}
Cause: Error occurred while registering driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26019: Error occurred while registering driver {0}
Cause: Error occurred while registering driver.
Action: Check stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26020: Registration of driver {0} succeeded.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26020: Registration of driver {0} succeeded.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.
Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.
Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.

Level: 1

Type: WARNING

Impact: Process

SDP-26021: Timed out while waiting for reply from Messaging engine.
Cause: The registration command timed out in the JMS queue because the Messaging engine is down or the system is under heavy load.
Action: Check if the Messaging engine is up and ensure the system is not under extremely heavy load.

Level: 1

Type: WARNING

Impact: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}. Exception: {1}
Cause: Illegal DeliveryType specified.
Action: Check message delivery type.

Level: 1

Type: ERROR

Impact: Process

SDP-26022: Illegal DeliveryType specified, ignoring type {0}. Exception: {1}
Cause: Illegal DeliveryType specified.
Action: Check message delivery type.

Level: 1

Type: ERROR

Impact: Process

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.
Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.
Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.

Level: 1

Type: WARNING

Impact: Process

SDP-26023: Benchmark logging is enabled for all inbound messages, which may slow down system performance. To disable it, unset environment variable sdpm_inbound_benchmark_logging and restart.
Cause: Benchmark logging is enabled when environment variable sdpm_inbound_benchmark_logging=true.
Action: To disable benchmark logging, unset environment variable sdpm_inbound_benchmark_logging and restart.

Level: 1

Type: WARNING

Impact: Process

SDP-26024: Registration of driver {0} did not complete. Current state is {1}. Will retry periodically until messaging server responds.
Cause: None
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26024: Registration of driver {0} did not complete. Current state is {1}. Will retry periodically until messaging server responds.
Cause: None
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26025: Error when registering messaging driver Runtime MBeans for {0}.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-26025: Error when registering messaging driver Runtime MBeans for {0}.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-26026: Error in unregistering messaging driver Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-26026: Error in unregistering messaging driver Runtime MBeans.
Cause: Exception was thrown.
Action: Check stack trace

Level: 1

Type: ERROR

Impact: Process

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.
Cause: A property with an unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26027: Ignoring property {0} with unsupported Java type {1} during driver initialization.
Cause: A property with an unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.
Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26028: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.
Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26029: Unable to load driver configuration properties from 'usermessagingconfig.xml'.
Cause: An exception occurred while attempting to load the driver configuration properties from 'usermessagingconfig.xml'.
Action: Check the stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-26029: Unable to load driver configuration properties from 'usermessagingconfig.xml'.
Cause: An exception occurred while attempting to load the driver configuration properties from 'usermessagingconfig.xml'.
Action: Check the stack trace.

Level: 1

Type: ERROR

Impact: Process

SDP-26030: Unable to schedule worker used to attempt driver registration.
Cause: An exception occurred while scheduling a worker to attempt driver registration.
Action: Check the stack trace.

Level: 1

Type: WARNING

Impact: Process

SDP-26030: Unable to schedule worker used to attempt driver registration.
Cause: An exception occurred while scheduling a worker to attempt driver registration.
Action: Check the stack trace.

Level: 1

Type: WARNING

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26031: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.
Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-26032: JNDI lookup of driver connection factory {0} failed with the following error message: {1}. Will retry until successful.
Cause: Driver connection factory could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the driver connection factory JNDI name is configured correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-26033: Started messaging driver: {0}
Cause: Driver was started.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26033: Started messaging driver: {0}
Cause: Driver was started.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}
Cause: Driver was stopped.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26034: Stopped messaging driver: {0}
Cause: Driver was stopped.
Action: None.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.
Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.

Level: 1

Type: WARNING

Impact: Process

SDP-26035: JNDI lookup of server command endpoint {0} failed with the following error message: {1}. Will retry until successful.
Cause: Messaging Server command module could not be located in JNDI. Driver registration will not occur until this lookup succeeds.
Action: Wait for server startup to proceed. If driver registration does not occur, ensure that the messaging server is deployed and started.

Level: 1

Type: WARNING

Impact: Process

SDP-26100: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26100: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26101: Content type parsing error {0}.
Cause: Error occurred while trying to parse the content type.
Action: Check and see if the content type is specified correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-26101: Content type parsing error {0}.
Cause: Error occurred while trying to parse the content type.
Action: Check and see if the content type is specified correctly.

Level: 1

Type: WARNING

Impact: Process

SDP-26102: Error while writing e-mail message content.
Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26102: Error while writing e-mail message content.
Cause: An exception has occurred while writing e-mail content and headers to an e-mail message.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26103: Error while writing e-mail subject.
Cause: Cannot write the subject.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26103: Error while writing e-mail subject.
Cause: Cannot write the subject.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26104: Recipient address error.
Cause: Recipient e-mail address has an error.
Action: Check and see if the recipient e-mail address is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26104: Recipient address error.
Cause: Recipient e-mail address has an error.
Action: Check and see if the recipient e-mail address is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26105: Unable to deliver to following address(es): {0} Reason: {1}
Cause: One or more recipient e-mail addresses had an error.
Action: Ensure that the e-mail address is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26105: Unable to deliver to following address(es): {0} Reason: {1}
Cause: One or more recipient e-mail addresses had an error.
Action: Ensure that the e-mail address is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26106: Failed to send the e-mail message
Cause: Unable to login to SMTP server.
Action: Check SMTP server host name, port, user name, and password.

Level: 1

Type: WARNING

Impact: Process

SDP-26106: Failed to send the e-mail message
Cause: Unable to login to SMTP server.
Action: Check SMTP server host name, port, user name, and password.

Level: 1

Type: WARNING

Impact: Process

SDP-26107: Failed to add header - name: {0} value: {1}
Cause: Unable to add an e-mail header to a multipart message
Action: Check the stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26107: Failed to add header - name: {0} value: {1}
Cause: Unable to add an e-mail header to a multipart message
Action: Check the stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26108: Failed to initialize e-mail driver
Cause: Could not initialize Email Driver.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26108: Failed to initialize e-mail driver
Cause: Could not initialize Email Driver.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all e-mail servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26109: Caught exception while closing connection to e-mail server.
Cause: An exception was caught while closing connection.
Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Process

SDP-26109: Caught exception while closing connection to e-mail server.
Cause: An exception was caught while closing connection.
Action: Check stack trace or error log.

Level: 1

Type: ERROR

Impact: Process

SDP-26110: Starting Email Driver failed.
Cause: Could not start Email Driver.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26110: Starting Email Driver failed.
Cause: Could not start Email Driver.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26111: Could not remove listener from Email Driver
Cause: Could not remove listener from Email Driver
Action: Check stack trace or error log

Level: 1

Type: ERROR

Impact: Process

SDP-26111: Could not remove listener from Email Driver
Cause: Could not remove listener from Email Driver
Action: Check stack trace or error log

Level: 1

Type: ERROR

Impact: Process

SDP-26112: Null protocol error
Cause: Protocol was null.
Action: Specify an appropriate protocol for this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26112: Null protocol error
Cause: Protocol was null.
Action: Specify an appropriate protocol for this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26113: No incoming e-mail server.
Cause: Incoming server was not set.
Action: Set incoming server parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26113: No incoming e-mail server.
Cause: Incoming server was not set.
Action: Set incoming server parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26114: Username is missing.
Cause: Username was not set.
Action: Set the username in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26114: Username is missing.
Cause: Username was not set.
Action: Set the username in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26115: Failed to receive an inbound e-mail message
Cause: An exception has occurred while receiving an inbound e-mail message.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26115: Failed to receive an inbound e-mail message
Cause: An exception has occurred while receiving an inbound e-mail message.
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26116: Protocol {0} is not supported.
Cause: An unsupported protocol was provided.
Action: Check the e-mail protocol name in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26116: Protocol {0} is not supported.
Cause: An unsupported protocol was provided.
Action: Check the e-mail protocol name in e-mail driver parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26117: Connection information of the inbound e-mail server is missing. Check the server host name, user name, and password.
Cause: Connect information was missing or incomplete.
Action: Provide the required connection information.

Level: 1

Type: ERROR

Impact: Process

SDP-26117: Connection information of the inbound e-mail server is missing. Check the server host name, user name, and password.
Cause: Connect information was missing or incomplete.
Action: Provide the required connection information.

Level: 1

Type: ERROR

Impact: Process

SDP-26118: Failed to open folder: {0}
Cause: Folder name is not correct or does not exist.
Action: Check folder name spelling.

Level: 1

Type: ERROR

Impact: Process

SDP-26118: Failed to open folder: {0}
Cause: Folder name is not correct or does not exist.
Action: Check folder name spelling.

Level: 1

Type: ERROR

Impact: Process

SDP-26119: Max retry limit reached for trying to connect to user {0}
Cause: Email driver has reached Max retry limit to connect to user.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: WARNING

Impact: Process

SDP-26119: Max retry limit reached for trying to connect to user {0}
Cause: Email driver has reached Max retry limit to connect to user.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: WARNING

Impact: Process

SDP-26120: IMAP server failed to expunge e-mail messages. mail box: {0}
Cause: An exception was caught when doing expunge.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26120: IMAP server failed to expunge e-mail messages. mail box: {0}
Cause: An exception was caught when doing expunge.
Action: Check stack trace or error log. Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: ERROR

Impact: Process

SDP-26121: Attempt to reconnect {0}. Error Count: {1} Retry Count: {2}.
Cause: Attempt to reconnect to the incoming e-mail server
Action: Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: WARNING

Impact: Process

SDP-26121: Attempt to reconnect {0}. Error Count: {1} Retry Count: {2}.
Cause: Attempt to reconnect to the incoming e-mail server
Action: Check e-mail driver parameters and make sure all servers are up.

Level: 1

Type: WARNING

Impact: Process

SDP-26122: An exception has been thrown when connecting to user {0}
Cause: Email driver could not connect to user.
Action: Check username and password. Make sure the user exists and is accessible.

Level: 1

Type: ERROR

Impact: Process

SDP-26122: An exception has been thrown when connecting to user {0}
Cause: Email driver could not connect to user.
Action: Check username and password. Make sure the user exists and is accessible.

Level: 1

Type: ERROR

Impact: Process

SDP-26123: Could not initialize Email Store for user {0}
Cause: Could not initialize Email Store for user.
Action: Check stack trace or error log. Check username and password.

Level: 1

Type: ERROR

Impact: Process

SDP-26123: Could not initialize Email Store for user {0}
Cause: Could not initialize Email Store for user.
Action: Check stack trace or error log. Check username and password.

Level: 1

Type: ERROR

Impact: Process

SDP-26124: Invalid folder: {0}
Cause: An invalid folder name was specified.
Action: Check and see if the specified folder is valid and accessable.

Level: 1

Type: ERROR

Impact: Process

SDP-26124: Invalid folder: {0}
Cause: An invalid folder name was specified.
Action: Check and see if the specified folder is valid and accessable.

Level: 1

Type: ERROR

Impact: Process

SDP-26125: An exception has occurred while sending out a message.
Cause: An exception occurred while sending out a message.
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26125: An exception has occurred while sending out a message.
Cause: An exception occurred while sending out a message.
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26126: Unrecoverable message - {0}
Cause: failed to recover an e-mail message
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26126: Unrecoverable message - {0}
Cause: failed to recover an e-mail message
Action: Check stack trace or error log.

Level: 1

Type: WARNING

Impact: Process

SDP-26127: Collision on e-mail message polling. Pausing for {0} seconds.
Cause: Multiple e-mail drivers polling the same e-mail account at the same time.
Action: (None)

Level: 1

Type: WARNING

Impact: Process

SDP-26127: Collision on e-mail message polling. Pausing for {0} seconds.
Cause: Multiple e-mail drivers polling the same e-mail account at the same time.
Action: (None)

Level: 1

Type: WARNING

Impact: Process

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.
Cause: A duplicate message was detected and discarded by the e-mail receiver.
Action: (None)

Level: 1

Type: WARNING

Impact: Process

SDP-26128: A duplicate inbound e-mail message has been discarded: gateway message ID: {0}, recipient addresses: {1}, subject: {2}.
Cause: A duplicate message was detected and discarded by the e-mail receiver.
Action: (None)

Level: 1

Type: WARNING

Impact: Process

SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}
Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.
Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.

Level: 1

Type: WARNING

Impact: Process

SDP-26129: Unable to deliver to following addresses: {0} Reason: {1}
Cause: Recipient e-mail address was valid but sending failed for reason indicated in error message.
Action: Ensure that e-mail driver and SMTP server are operational and configured correctly, baed on information provided in error message.

Level: 1

Type: WARNING

Impact: Process

SDP-26130: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.
Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26130: Ignoring property {0} with invalid value {1} and/or Java type {2} during driver initialization.
Cause: A property with an invalid value and/or unsupported Java type was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid value and/or one of the following valid Java types: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, java.lang.Float, java.lang.Character

Level: 1

Type: WARNING

Impact: Process

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26131: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26132: No configuration was found for this Email Driver deployment: {0}. Create a configuration for {0}.
Cause: No configuration was found for this Email Driver deployment.
Action: Create a configuration this Email Driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26132: No configuration was found for this Email Driver deployment: {0}. Driver disabled until a configuration is created.
Cause: No configuration was found for this Email Driver deployment.
Action: Create a configuration this Email Driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26133: Email Driver {0} is not configured with all the mandatory properties. Configure this driver.
Cause: Email Driver was not configured with all the mandatory properties.
Action: Configure this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26133: Email Driver {0} is not configured with inbound or outbound properties. Driver disabled until configured.
Cause: Email Driver was not configured for inbound or outbound traffic.
Action: Configure this driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26134: Email Driver {0} is not configured with incoming mail properties. No emails (including information about bounced emails) are received.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26135: Email Driver {0} is not configured with outgoing mail properties. Emails cannot be sent through this driver.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26136: Driver property OutgoingDefaultFromAddr is deprecated. Use DefaultSenderAddress instead.
Cause: Driver property OutgoingDefaultFromAddr in 'usermessagingconfig.xml' is deprecated.
Action: Use DefaultSenderAddress instead.

Level: 1

Type: WARNING

Impact: Process

SDP-26137: Both DefaultSenderAddress and the deprecated OutgoingDefaultFromAddr is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.
Cause: Both OutgoingDefaultFromAddr and DefaultSenderAddress is configured in 'usermessagingconfig.xml'. DefaultSenderAddress will be used.
Action: Remove configuration for OutgoingDefaultFromAddr.

Level: 1

Type: WARNING

Impact: Process

SDP-26138: Message was not delivered. No valid sender(From) address available.
Cause: No sender address set in message and DefaultSenderAddress is not configured in 'usermessagingconfig.xml'.
Action: Set sender(From) address in message or set DefaultSenderAddress in 'usermessagingconfig.xml'.

Level: 1

Type: WARNING

Impact: Process

SDP-26150: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26150: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null
Cause: Driver context is null
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26151: Failed to process a received message in SMPP driver, because driver context is null
Cause: Driver context is null
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26152: WorkManager object is null in SMPP driver.
Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument
Action: Make sure WorkManager object is not null.

Level: 1

Type: ERROR

Impact: Process

SDP-26152: WorkManager object is null in SMPP driver.
Cause: The caller of setWorkManager() passed in a null WorkManager object as an argument
Action: Make sure WorkManager object is not null.

Level: 1

Type: ERROR

Impact: Process

SDP-26153: Received status message with incorrect format.
Cause: The status received from SMSC does not have message ID or state.
Action: Correct the SMSC.

Level: 1

Type: ERROR

Impact: Process

SDP-26153: Received status message with incorrect format.
Cause: The status received from SMSC does not have message ID or state.
Action: Correct the SMSC.

Level: 1

Type: ERROR

Impact: Process

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.
Cause: Driver Context is null
Action: Check driver context.

Level: 1

Type: ERROR

Impact: Process

SDP-26154: Failed to process received status in SMPP driver, because driver context is null.
Cause: Driver Context is null
Action: Check driver context.

Level: 1

Type: ERROR

Impact: Process

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.
Cause: The account ID was not set.
Action: Set the correct account information.

Level: 1

Type: ERROR

Impact: Process

SDP-26155: unable to initialize SMPP driver, because a driver attribute, sms.account.id, is not set.
Cause: The account ID was not set.
Action: Set the correct account information.

Level: 1

Type: ERROR

Impact: Process

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.
Cause: SMSC server or account information is not correct or missing.
Action: Check those parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26156: Failed to initialize SMPP Driver because driver attributes sms.server.host, sms.server.transmitter.port or sms.server.receiver.port is not set.
Cause: SMSC server or account information is not correct or missing.
Action: Check those parameters.

Level: 1

Type: ERROR

Impact: Process

SDP-26157: SMPP driver failed to send out a message, because Message object is null.
Cause: Null message object.
Action: Check the caller of this method.

Level: 1

Type: ERROR

Impact: Process

SDP-26157: SMPP driver failed to send out a message, because Message object is null.
Cause: Null message object.
Action: Check the caller of this method.

Level: 1

Type: ERROR

Impact: Process

SDP-26158: Caught exception while closing connection
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26158: Caught exception while closing connection
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26159: Illegal data length value from SMSC received and ignored: {0}
Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.
Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.

Level: 1

Type: WARNING

Impact: Process

SDP-26159: Illegal data length value from SMSC received and ignored: {0}
Cause: SMPP Driver has detected a corrupted data field from SMSC and it is trying to recover.
Action: This error suggests communication errors between SMPP driver and SMSC. Check to see if this driver supports that SMSC.

Level: 1

Type: WARNING

Impact: Process

SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Cause: SMPP Driver was not configured.
Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Level: 1

Type: ERROR

Impact: Process

SDP-26160: SMPP Driver not configured. Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.
Cause: SMPP Driver was not configured.
Action: Configure and restart this driver. Required Properties: SmsAccountId, SmsServerHost, TransmitterSystemId, ReceiverSystemId, TransmitterSystemType, ReceiverSystemType, TransmitterSystemPassword, ReceiverSystemPassword, ServerTransmitterPort, ServerReceiverPort.

Level: 1

Type: ERROR

Impact: Process

SDP-26161: Starting SMPP Driver: {0}
Cause: SMPP Driver resource adapter initialization.
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26161: Starting SMPP Driver: {0}
Cause: SMPP Driver resource adapter initialization.
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26162: Message content could not be decoded using character set {0}
Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.
Action: Ensure that the Default Encoding configuration parameter is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26162: Message content could not be decoded using character set {0}
Cause: The message content retrieved from the SMSC could not be decoded using the specified character set.
Action: Ensure that the Default Encoding configuration parameter is correct.

Level: 1

Type: WARNING

Impact: Process

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC
Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.
Action: None.

Level: 1

Type: WARNING

Impact: Process

SDP-26163: Data stream ended unexpectedly while reading packet from SMSC
Cause: The data stream ended unexpectedly while reading a packet from the SMSC. Message or command will be dropped.
Action: None.

Level: 1

Type: WARNING

Impact: Process

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.
Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.
Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.

Level: 1

Type: WARNING

Impact: Process

SDP-26164: Failed to bind receiver connection; will retry until bind operation is successful.
Cause: Could not bind to the SMSC as a receiver. Bind operation will be retried periodically until it is successful.
Action: None required. Change value of configuration parameter "BindRetryDelay" to adjust retry interval.

Level: 1

Type: WARNING

Impact: Process

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: WARNING

Impact: Process

SDP-26165: Lookup of encoded credential value for account {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: WARNING

Impact: Process

SDP-26200: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26200: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26201: Unable to remove listener from XMPPDriver.
Cause: Unable to remove listener from XMPPDriver .
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26201: Unable to remove listener from XMPPDriver.
Cause: Unable to remove listener from XMPPDriver .
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26202: Unable to shut down XMPPDriver.
Cause: Unable to shut down XMPPDriver.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26202: Unable to shut down XMPPDriver.
Cause: Unable to shut down XMPPDriver.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Cause: XMPP Driver was not configured.
Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Level: 1

Type: ERROR

Impact: Process

SDP-26203: XMPP Driver not configured. Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.
Cause: XMPP Driver was not configured.
Action: Configure and restart this driver. Required properties: IMServerHost, IMServerUsername, IMServerPassword.

Level: 1

Type: ERROR

Impact: Process

SDP-26204: Error occurred while initializing XMPPDriver {0}
Cause: Error occurred while initializing driver instance.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26204: Error occurred while initializing XMPPDriver {0}
Cause: Error occurred while initializing driver instance.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26205: Exception while getting content from message with id={0}
Cause: Exception while getting content from message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26205: Exception while getting content from message with id={0}
Cause: Exception while getting content from message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26206: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: ERROR

Impact: Process

SDP-26206: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: ERROR

Impact: Process

SDP-26207: Invalid value for im.retry.limit. Value reset to default - {0}
Cause: Invalid value for im.retry.limit. Value reset to default
Action: Specify a valid value for im.retry.limit

Level: 1

Type: WARNING

Impact: Process

SDP-26207: Invalid value for im.retry.limit. Value reset to default - {0}
Cause: Invalid value for im.retry.limit. Value reset to default
Action: Specify a valid value for im.retry.limit

Level: 1

Type: WARNING

Impact: Process

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds
Cause: Invalid value for im.retry.interval. Value reset to default.
Action: Specify a valid value for im.retry.interval

Level: 1

Type: WARNING

Impact: Process

SDP-26208: Invalid value for im.retry.interval. Value reset to default - {0} seconds
Cause: Invalid value for im.retry.interval. Value reset to default.
Action: Specify a valid value for im.retry.interval

Level: 1

Type: WARNING

Impact: Process

SDP-26209: Unable to initialize accounts
Cause: Unable to initialize accounts.
Action: Check username, password and IM server.

Level: 1

Type: ERROR

Impact: Process

SDP-26209: Unable to initialize accounts
Cause: Unable to initialize accounts.
Action: Check username, password and IM server.

Level: 1

Type: ERROR

Impact: Process

SDP-26210: Unable to connect to XMPP server: {0}
Cause: Check the associated stack trace for the cause of the connection failure.
Action: Check the XMPP server hostname and port parameters and make sure the server is up.

Level: 1

Type: ERROR

Impact: Process

SDP-26210: Unable to connect to XMPP server: {0}
Cause: Check the associated stack trace for the cause of the connection failure.
Action: Check the XMPP server hostname and port parameters and make sure the server is up.

Level: 1

Type: ERROR

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.
Cause: Exception while sending message.
Action: Check stack trace and recipient address

Level: 1

Type: WARNING

Impact: Process

SDP-26213: Exception while sending message - from: {0} to: {1}.
Cause: Exception while sending message.
Action: Check stack trace and recipient address

Level: 1

Type: WARNING

Impact: Process

SDP-26214: Caught an exception in XMPP driver while sending out a message.
Cause: An exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26214: Caught an exception in XMPP driver while sending out a message.
Cause: An exception was caught.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26215: The XMPP driver has no previous account to replace.
Cause: No previous XMPP (IM) account was found. Unable to replace previous account.
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26215: The XMPP driver has no previous account to replace.
Cause: No previous XMPP (IM) account was found. Unable to replace previous account.
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26216: No accounts defined in XMPP driver.
Cause: No XMPP accounts defined.
Action: Define a valid XMPP (IM) account.

Level: 1

Type: WARNING

Impact: Process

SDP-26216: No accounts defined in XMPP driver.
Cause: No XMPP accounts defined.
Action: Define a valid XMPP (IM) account.

Level: 1

Type: WARNING

Impact: Process

SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.
Cause: Could not locate an account to deliver this message.
Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26217: Could not locate an account to deliver this message from sender {0}. Using the first account ( {1} ) to deliver this message.
Cause: Could not locate an account to deliver this message.
Action: To retain the original message sender, add sender of the message to 'user' configuration property of the driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26218: I/O problem using HTTP Proxy {0} for account: {1}
Cause: The connection with the HTTP Proxy was broken.
Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.

Level: 1

Type: ERROR

Impact: Process

SDP-26218: I/O problem using HTTP Proxy {0} for account: {1}
Cause: The connection with the HTTP Proxy was broken.
Action: Check stack trace for more information. Check HTTP Proxy settings to see if proxy is correct and reachable.

Level: 1

Type: ERROR

Impact: Process

SDP-26219: Server DNS problem with account: {0}
Cause: The hostname could not be resolved by DNS.
Action: Check the stack trace, account parameters, and DNS server.

Level: 1

Type: ERROR

Impact: Process

SDP-26219: Server DNS problem with account: {0}
Cause: The hostname could not be resolved by DNS.
Action: Check the stack trace, account parameters, and DNS server.

Level: 1

Type: ERROR

Impact: Process

SDP-26220: Server I/O problem with account: {0}
Cause: The connection with the XMPP server was broken.
Action: Check the account parameters and the network connection.

Level: 1

Type: ERROR

Impact: Process

SDP-26220: Server I/O problem with account: {0}
Cause: The connection with the XMPP server was broken.
Action: Check the account parameters and the network connection.

Level: 1

Type: ERROR

Impact: Process

SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.
Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26221: Third-party transport connectivity is no longer supported. Ignoring all applicable configuration properties.
Cause: This is an upgraded XMPP Driver instance making use of third-party transport connectivity that is no longer supported in this version.
Action: None

Level: 1

Type: WARNING

Impact: Process

SDP-26222: Agent registration failed for {0}. Error Code: {1}
Cause: Agent registration failed.
Action: Check error code and from address.

Level: 1

Type: ERROR

Impact: Process

SDP-26222: Agent registration failed for {0}. Error Code: {1}
Cause: Agent registration failed.
Action: Check error code and from address.

Level: 1

Type: ERROR

Impact: Process

SDP-26223: Failed to set presence.
Cause: Failed to set presence.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26223: Failed to set presence.
Cause: Failed to set presence.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26224: Exception occurred when processing incoming presence.
Cause: Exception occurred when processing incoming presence.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26224: Exception occurred when processing incoming presence.
Cause: Exception occurred when processing incoming presence.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26225: Received Error Message. Code: {0} Text: {1}.
Cause: Received Error Message.
Action: Check error code and error message.

Level: 1

Type: WARNING

Impact: Process

SDP-26225: Received Error Message. Code: {0} Text: {1}.
Cause: Received Error Message.
Action: Check error code and error message.

Level: 1

Type: WARNING

Impact: Process

SDP-26226: Unauthorized login to Jabber/XMPP server: {0}
Cause: Invalid username and/or password was supplied.
Action: Check username and password.

Level: 1

Type: WARNING

Impact: Process

SDP-26226: Unauthorized login to Jabber/XMPP server: {0}
Cause: Invalid username and/or password was supplied.
Action: Check username and password.

Level: 1

Type: WARNING

Impact: Process

SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}
Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.
Action: Contact the server administrator for a new account.

Level: 1

Type: WARNING

Impact: Process

SDP-26227: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration. Contact the server administrator for a new account. Now disconnecting from server: {0}
Cause: New account registration failed. It appears that the Jabber/XMPP server does not allow automatic registration.
Action: Contact the server administrator for a new account.

Level: 1

Type: WARNING

Impact: Process

SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}
Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.
Action: Check that the specified account does not exist. Check that your password is valid

Level: 1

Type: WARNING

Impact: Process

SDP-26228: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server. Now disconnecting from server: {0}
Cause: New account registration failed. Either this account already exists and you have entered an incorrect password or there is a problem with the Jabber/XMPP server.
Action: Check that the specified account does not exist. Check that your password is valid

Level: 1

Type: WARNING

Impact: Process

SDP-26229: Plaintext authentication failed; disconnecting from server: {0}
Cause: Plaintext authentication failed.
Action: Check username and password and check with the Jabber/XMPP server administrator.

Level: 1

Type: ERROR

Impact: Process

SDP-26229: Plaintext authentication failed; disconnecting from server: {0}
Cause: Plaintext authentication failed.
Action: Check username and password and check with the Jabber/XMPP server administrator.

Level: 1

Type: ERROR

Impact: Process

SDP-26230: Digest authentication failed. Attempting plain-text authentication: {0}
Cause: Digest authentication failed.
Action: Digest authentication failed. Check with the Jabber/XMPP server administrator.

Level: 1

Type: WARNING

Impact: Process

SDP-26230: Digest authentication failed. Attempting plain-text authentication: {0}
Cause: Digest authentication failed.
Action: Digest authentication failed. Check with the Jabber/XMPP server administrator.

Level: 1

Type: WARNING

Impact: Process

SDP-26231: Failed to login to Jabber/XMPP server: {0}
Cause: Failed to login to Jabber/XMPP server.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26231: Failed to login to Jabber/XMPP server: {0}
Cause: Failed to login to Jabber/XMPP server.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26234: Disconnecting from Jabber/XMPP server: {0}.
Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.
Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26234: Disconnecting from Jabber/XMPP server: {0}.
Cause: 1) The account was disconnected by the XMPP server due to another conflicting login. 2) The XMPP server went offline.
Action: 1) Identify and shut down the conflicting XMPP driver that is using the same account. 2) Check the status of the XMPP server.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26235: Account disconnected: {0}.
Cause: The account was disconnected from the server either due to I/O or authentication error.
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: ERROR

Impact: Process

SDP-26235: Account disconnected: {0}.
Cause: The account was disconnected from the server either due to I/O or authentication error.
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: ERROR

Impact: Process

SDP-26236: Got an exception when receiving a message.
Cause: Got an exception when receiving a message.
Action: Check to see if the message is well-formed.

Level: 1

Type: WARNING

Impact: Process

SDP-26236: Got an exception when receiving a message.
Cause: Got an exception when receiving a message.
Action: Check to see if the message is well-formed.

Level: 1

Type: WARNING

Impact: Process

SDP-26237: The call for conversion does not supply account information. The first account is being used for conversion.
Cause: The call for conversion did not supply the necessary account information.
Action: Provide the correct account information.

Level: 1

Type: WARNING

Impact: Process

SDP-26237: The call for conversion does not supply account information. The first account is being used for conversion.
Cause: The call for conversion did not supply the necessary account information.
Action: Provide the correct account information.

Level: 1

Type: WARNING

Impact: Process

SDP-26238: Cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.
Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.
Action: Enable the transport in the driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26238: Cannot deliver to this {0} user, because {0} transport is not enabled in the driver. Set the value for driver parameter: {1}.
Cause: Because transport was not enabled in the driver, delivery could not be made to the Yahoo, MSN, AOL, or ICQ user.
Action: Enable the transport in the driver.

Level: 1

Type: WARNING

Impact: Process

SDP-26239: Invalid network name in address: {0}
Cause: Invalid network name in address
Action: Specify a valid network name in address.

Level: 1

Type: WARNING

Impact: Process

SDP-26239: Invalid network name in address: {0}
Cause: Invalid network name in address
Action: Specify a valid network name in address.

Level: 1

Type: WARNING

Impact: Process

SDP-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.
Cause: The Max Retry Limit was reached while attempting to reconnect.
Action: Restart the XMPP driver to try again.

Level: 1

Type: ERROR

Impact: Process

SDP-26240: Max Retry Limit ( {0} ) is reached. Restart the driver to try reconnecting for account {1}.
Cause: The Max Retry Limit was reached while attempting to reconnect.
Action: Restart the XMPP driver to try again.

Level: 1

Type: ERROR

Impact: Process

SDP-26241: Reconnecting now... attempt #{0} for account {1}.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26241: Reconnecting now... attempt #{0} for account {1}.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26242: Reconnecting in {0} seconds for account {1}.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26242: Reconnecting in {0} seconds for account {1}.
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26243: Config Parameters:XMPP Server : {0}XMPP Port : {1}XMPP Users : {2}SecurityMode : {3}SASLAuthentication : {4}
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26243: Config Parameters:XMPP Server : {0}XMPP Port : {1}XMPP Users : {2}SecurityMode : {3}SASLAuthentication : {4}
Cause: None
Action: None

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26245: Could not initialize XMPPDriver.
Cause: XMPPDriver was misconfigured.
Action: Check driver parameters, account information and Jabber/XMPP server.

Level: 1

Type: ERROR

Impact: Process

SDP-26245: Could not initialize XMPPDriver.
Cause: XMPPDriver was misconfigured.
Action: Check driver parameters, account information and Jabber/XMPP server.

Level: 1

Type: ERROR

Impact: Process

SDP-26246: Caught exception while closing connection of XMPP server.
Cause: Caught exception in XMPP driver while closing server connection.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26246: Caught exception while closing connection of XMPP server.
Cause: Caught exception in XMPP driver while closing server connection.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26247: Failed to get roster from XMPP server
Cause: Failed to get roster from XMPP server
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26247: Failed to get roster from XMPP server
Cause: Failed to get roster from XMPP server
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Cause: The account was disconnected from the server due to an unknown error.
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: WARNING

Impact: Process

SDP-26248: Account disconnected: {0}. Cause: Unknown. Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.
Cause: The account was disconnected from the server due to an unknown error.
Action: Check account host, username and password configuration. Check the connectivity to the XMPP server.

Level: 1

Type: WARNING

Impact: Process

SDP-26250: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26250: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26251: Could not initialize Proxy Driver
Cause: Could not initialize Proxy Driver.
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26251: Could not initialize Proxy Driver
Cause: Could not initialize Proxy Driver.
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.
Cause: DriverConnection returned by DriverConnectionFactory was null
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26252: Error occurred while initializing Proxy Driver: DriverConnection returned by DriverConnectionFactory is null.
Cause: DriverConnection returned by DriverConnectionFactory was null
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.
Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.
Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26254: Failed to initialize Proxy Driver with GatewayURL={0} and Username={1}. Check driver configuration properties and remote gateway, and restart the driver.
Cause: Failed to initialize Proxy Driver with the specified GatewayURL, Username and Password.
Action: Check stack trace or error log. Check Proxy Driver properties: GatewayURL, Username and Password. Also check the status of the remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26255: Exception occurred while initializing Proxy Driver
Cause: Exception occurred while initializing Proxy Driver
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26255: Exception occurred while initializing Proxy Driver
Cause: Exception occurred while initializing Proxy Driver
Action: Check stack trace or error log. Check Proxy Driver parameters and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26256: Proxy Driver has not been configured. Configure and restart this driver. Required Property: GatewayURL.
Cause: Proxy Driver was not configured.
Action: Configure and restart this driver. Required Property: GatewayURL.

Level: 1

Type: ERROR

Impact: Process

SDP-26256: Proxy Driver has not been configured. Configure and restart this driver. Required Property: GatewayURL.
Cause: Proxy Driver was not configured.
Action: Configure and restart this driver. Required Property: GatewayURL.

Level: 1

Type: ERROR

Impact: Process

SDP-26257: Exception occurred while invoking Proxy Driver remote request
Cause: Exception occurred while invoking Proxy Driver remote request
Action: Check stack trace or error log. Check Proxy Driver configuration and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26257: Exception occurred while invoking Proxy Driver remote request
Cause: Exception occurred while invoking Proxy Driver remote request
Action: Check stack trace or error log. Check Proxy Driver configuration and remote gateway.

Level: 1

Type: ERROR

Impact: Process

SDP-26258: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26258: Lookup of encoded credential value {0} in the credential store for property {1} failed during driver initialization. Passing through the value as-is.
Cause: A property with an invalid encoded credential value was found in 'usermessagingconfig.xml' during driver initialization.
Action: Use a valid encoded credential value and ensure the application has permission grants to access the credential store.

Level: 1

Type: WARNING

Impact: Process

SDP-26300: A Twitter exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26300: A Twitter exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26301: Got an exception when receiving tweets.
Cause: An exception has occurred when receiving tweets.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26301: Got an exception when receiving tweets.
Cause: An exception has occurred when receiving tweets.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26302: Got an exception when receiving direct messages.
Cause: An exception has occurred when receiving direct message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26302: Got an exception when receiving direct messages.
Cause: An exception has occurred when receiving direct message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26303: Exception caught during attributes transferring of an inbound direct message.
Cause: An exception has occurred when transferring attributes of a direct message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26303: Exception caught during attributes transferring of an inbound direct message.
Cause: An exception has occurred when transferring attributes of a direct message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26304: Exception caught during attributes transferring of an inbound tweet.
Cause: An exception has occurred when transferring attributes of a tweet.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26304: Exception caught during attributes transferring of an inbound tweet.
Cause: An exception has occurred when transferring attributes of a tweet.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26305: Got an exception when building an inbound UMS message from a received tweet or direct message.
Cause: An exception has occurred when rebuilding an inbound UMS message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26305: Got an exception when building an inbound UMS message from a received tweet or direct message.
Cause: An exception has occurred when rebuilding an inbound UMS message.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.
Cause: At least one of Twitter consumer key, consumer secret, access token, and access token secret is missing or not set.
Action: Check the log file for the missing field(s).

Level: 1

Type: ERROR

Impact: Process

SDP-26306: Required OAuth login information is missing or incomplete. Consumer key, consumer secret, access token, and/or access token secret is not set.
Cause: At least one of Twitter consumer key, consumer secret, access token, and access token secret is missing or not set.
Action: Check the log file for the missing field(s).

Level: 1

Type: ERROR

Impact: Process

SDP-26307: Required xAuth login information for user {0} is missing or incomplete. Both username and password are required.
Cause: Username or password is missing or not set.
Action: Check the log file for the missing field(s).

Level: 1

Type: ERROR

Impact: Process

SDP-26307: Required xAuth login information for user {0} is missing or incomplete. Both username and password are required.
Cause: Username or password is missing or not set.
Action: Check the log file for the missing field(s).

Level: 1

Type: ERROR



Impact: Process

SDP-26308: No configuration element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.
Cause: No configuration element was found for this Twitter Driver deployment.
Action: Create a configuration and restart this Twitter Driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26308: No configuration element was found for this Twitter Driver deployment. Create a configuration and restart this Twitter Driver.
Cause: No configuration element was found for this Twitter Driver deployment.
Action: Create a configuration and restart this Twitter Driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26309: Twitter Driver not configured. Required property: AuthenticationMode
Cause: Twitter Driver not configured. Configure and restart this driver. Required properties: AuthenticationMode
Action: Configure and restart this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26309: Twitter Driver not configured. Required property: AuthenticationMode
Cause: Twitter Driver not configured. Configure and restart this driver. Required properties: AuthenticationMode
Action: Configure and restart this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26310: Twitter Driver not properly configured. AuthenticationMode {0} is unknown and not supported.
Cause: Twitter Driver not properly configured. AuthenticationMode given is unknown and not supported.
Action: Configure and restart this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26310: Twitter Driver not properly configured. AuthenticationMode {0} is unknown and not supported.
Cause: Twitter Driver not properly configured. AuthenticationMode given is unknown and not supported.
Action: Configure and restart this driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26311: Retweet id string {0} in meta data could not be converted to long. No tweet for messageId {1}
Cause: Retweet id string in meta data could not be converted to long.
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26311: Retweet id string {0} in meta data could not be converted to long. No tweet for messageId {1}
Cause: Retweet id string in meta data could not be converted to long.
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26312: Ignoring reply id string {0} in meta data that could not be converted to long.
Cause: Ignoring reply id string in meta data that could not be converted to long.
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26312: Ignoring reply id string {0} in meta data that could not be converted to long.
Cause: Ignoring reply id string in meta data that could not be converted to long.
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).
Cause: Ignoring geo location string in meta data that could not be converted to (double,double).
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26313: Ignoring geo location string ({0}) in meta data that could not be converted to (double,double).
Cause: Ignoring geo location string in meta data that could not be converted to (double,double).
Action: Check how the application generates the meta data.

Level: 1

Type: WARNING

Impact: Process

SDP-26350: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26350: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26351: Driver property VoiceXMLReceiveURL is empty.
Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.
Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.

Level: 1

Type: ERROR

Impact: Process

SDP-26351: Driver property VoiceXMLReceiveURL is empty.
Cause: VoiceXMLReceiveURL was not set and could not be dynamically generated.
Action: Check the validity of the VoiceXMLReceiveURL property. Ensure the host and port are that of the server where this driver is deployed.

Level: 1

Type: ERROR

Impact: Process

SDP-26352: VoiceXMLOutboundServletURI cannot be null
Cause: VoiceXMLOutboundServletURI is null
Action: Assign proper value for Outbound Servlet URL.

Level: 1

Type: ERROR

Impact: Process

SDP-26352: VoiceXMLOutboundServletURI cannot be null
Cause: VoiceXMLOutboundServletURI is null
Action: Assign proper value for Outbound Servlet URL.

Level: 1

Type: ERROR

Impact: Process

SDP-26356: Socket error from VoiceXML Gateway.
Cause: Socket Error from the Gateway
Action: Check VoiceXML server URL and the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26356: Socket error from VoiceXML Gateway.
Cause: Socket Error from the Gateway
Action: Check VoiceXML server URL and the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26357: VoiceXMLDriver could not initialize.
Cause: Initialization failed.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26357: VoiceXMLDriver could not initialize.
Cause: Initialization failed.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26358: VoiceXMLDriver: Exception while processing the HTTP request.
Cause: Exception while processing the HTTP request
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26358: VoiceXMLDriver: Exception while processing the HTTP request.
Cause: Exception while processing the HTTP request
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26359: VoiceXMLDriver: Caught exception while closing connection
Cause: Caught exception while closing connection
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26359: VoiceXMLDriver: Caught exception while closing connection
Cause: Caught exception while closing connection
Action: Check the stack trace for more details.

Level: 1

Type: WARNING

Impact: Process

SDP-26360: VoiceXML Driver not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.
Cause: VoiceXML Driver was not configured.
Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Level: 1

Type: ERROR

Impact: Process

SDP-26360: VoiceXML Driver not configured. Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.
Cause: VoiceXML Driver was not configured.
Action: Configure and restart this driver. Required Properties: VoiceXMLOutboundServletURI.

Level: 1

Type: ERROR

Impact: Process

SDP-26361: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: ERROR

Impact: Process

SDP-26361: Lookup of encoded credential value for username {0} in the credential failed during driver initialization.
Cause: Lookup of encoded credential value in the credential failed during driver initialization.
Action: Check the stack trace for more details. Ensure that the encoded indirect password and the credential store are properly configured.

Level: 1

Type: ERROR

Impact: Process

SDP-26450: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26450: An exception was caught.
Cause: An exception has occurred.
Action: Check the stack trace for more details.

Level: 1

Type: ERROR

Impact: Process

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.
Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.
Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.

Level: 1

Type: WARNING

Impact: Process

SDP-26451: One or more sets of extension endpoints were configured using identical protocols and mapped domains: {0}. The first endpoint listed in the configuration file will be used.
Cause: Each of the listed protocol/domain pairs is used to configure multiple extension endpoints.
Action: Remove the conflicting endpoint configuration, or ensure that each endpoint has unique protocol and mapped domain parameters.

Level: 1

Type: WARNING

Impact: Process

SDP-26452: No extension endpoint could be found for the specified recipient address.
Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.
Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26452: No extension endpoint could be found for the specified recipient address.
Cause: None of the configured extension endpoints matched the protocol and domain of the message recipient.
Action: Ensure that an endpoint is configured for the desired protocol and domain, or configure a default (empty) domain.

Level: 1

Type: NOTIFICATION

Impact: Process

SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.
Cause: No configuration element was found for this Extension Driver deployment.
Action: Create a configuration and restart this Extension Driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26453: No configuration element was found for this Extension Driver deployment. Create a configuration and restart this Extension Driver.
Cause: No configuration element was found for this Extension Driver deployment.
Action: Create a configuration and restart this Extension Driver.

Level: 1

Type: ERROR

Impact: Process

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Cause: Extension Driver was not configured.
Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: ERROR

Impact: Process

SDP-26454: Extension Driver not configured. Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.
Cause: Extension Driver was not configured.
Action: Configure and restart this driver. The configuration must contain at least one Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: ERROR

Impact: Process

SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Cause: An error occurred while processing the Extension Driver configuration.
Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: ERROR

Impact: Process

SDP-26455: Error while processing Extension Driver configuration for property group with Endpoint URL: {0}. Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.
Cause: An error occurred while processing the Extension Driver configuration.
Action: Check the corresponding property group configuration, then restart this driver. The configuration must contain an Extension endpoint with a valid endpoint URL and protocol.

Level: 1

Type: ERROR

Impact: Process

SDP-26456: An exception occurred while enabling the WS-Security configuration: {0}
Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.
Action: Ensure that any WS-Security policies are specified in the correct format.

Level: 1

Type: ERROR

Impact: Process

SDP-26456: An exception occurred while enabling the WS-Security configuration: {0}
Cause: An exception occurred while attaching a WS-Security policy to a web service client or endpoint.
Action: Ensure that any WS-Security policies are specified in the correct format.

Level: 1

Type: ERROR

Impact: Process

SDP-26457: An exception occurred while constructing the SOAP message: {0}
Cause: An exception occurred while constructing the SOAP message
Action: Check the configurati#on of the server.

Level: 1

Type: ERROR

Impact: Process

SDP-26457: An exception occurred while constructing the SOAP message: {0}
Cause: An exception occurred while constructing the SOAP message
Action: Check the configuration of the server.

Level: 1

Type: ERROR

Impact: Process

PK{6܃PK8zDOEBPS/cover.htm  Cover

Oracle Corporation

PK@t` PK8zDOEBPS/chapter_ucs_messages.htm UCS-10106 to UCS-31204

26 UCS-10106 to UCS-31204

UCS-10106: RemoteAccessFactory is not bound!
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10107: Could not find a property editor for class ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10108: Error initializing the editor. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10109: Failed to export command {1}. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10110: Could not create progress writer. Progress information will be lost.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10111: Exception when converting to string. Reason: {0}
Cause: Internal error
Action: No action required.

Level: 1

Type: ERROR

Impact: Process

UCS-10112: Could not connect to remote resource. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10113: Property class {0} was not found.
Cause: Malformed command-service.xml.
Action: Correct command-service.xml.

Level: 1

Type: WARNING

Impact: Process

UCS-10114: Command ''{0}'' has no help!
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10115: Missing name element for command.
Cause: Malformed command-service.xml.
Action: Correct command-service.xml.

Level: 1

Type: ERROR

Impact: Process

UCS-10116: Object evicted from cache "{0}". Increase the size of the cache or change the expiry delay. Key = "{1}", value = "{2}".
Cause: An object has been evicted form the cache since the cache is to small.
Action: Increase the size of the cache or change the expiry delay.

Level: 1

Type: WARNING

Impact: Process

UCS-10195: Failed to read commands from file ''{1}''. Reason: {0}.
Cause: Reading and/or parsing of commands failed.
Action: Correct the command description.

Level: 1

Type: ERROR

Impact: Process

UCS-10196: Creating Command Service
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10197: Starting Command Service.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10198: Command Service already started.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10199: Stopping Command Service.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10200: Command Service already stopped.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10201: Destroying Command Service.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10202: Loading command: {0}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10203: Could not instantiate the class ''{1}''. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10204: The class or its nullary constructor is not accessible. Reason: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10205: Could not find the class ''{0}''. Make sure that it is available to the system and verify that you wrote the class name correctly.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10206: Loaded {0} (out of {1}) commands into the system.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10207: Could not find the attribute. The only valid attribute names are \"class", \"resource\" and "\"description\". Please verify that you spelled them correctly.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10249: Failed to send error message to client: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10250: MemoryMonitor starting
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10251: MemoryMonitor stopping
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10252: Expected an Integer but found: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10253: Cannot create a tree of type {0}, returning null
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10254: Unknown exception caught. Message - {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10255: Could not find MessageDigest for algorithm {1}, reason: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10256: Failed to create the XML reader: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10257: Exception {0} with ExceptionUniqueID: {1}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10258: SQL error: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10300: Failed to set default attributes.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10301: Could not find a property editor for attribute type ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10302: Failed to set attribute.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10303: Failed to set list of attributes.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10306: Loading persisted data for {0} [{1}]
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10307: Metadata deserialized.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10308: Error loading MBean state.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10309: Persisting metadata for MBean.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10310: store
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10312: Error persisting MBean
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10313: Loading attribute name: {0}, value: {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10316: Created store file: {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10317: Storing data for {0} [{1}]
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10318: Caught null attribute for {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10319: Constructor threw exception.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10320: Failed to undeploy Mbeans
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10321: Trying to load Mbean {0}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10322: Registering MBean {0} with object name {1}
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-10323: Failed to load Mbean.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10324: Failed to deregister Mbean.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10325: Failed to persist MBean.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10326: Failed to load metadata for Mbean from {1}. Reason: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10327: Failed to call MBean lifecycle {1} for bean {2}. Reason: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-10328: Failed to load the jmxframework.
Cause: Internal Error, possibly misconfiguration or missing jars.
Action: Confirm JMX framework is configured / set up properly.

Level: 1

Type: ERROR

Impact: Process

UCS-11051: Error when looking up userservice.
Cause: The J2EE application SubscriberDataServices may not be deployed or started.
Action: Ensure that the J2EE application SubscriberDataServices is running.

Level: 1

Type: ERROR

Impact: Process

UCS-11052: Error when creating userservice.
Cause: The J2EE application SubscriberDataServices may not be deployed or started.
Action: Ensure that the J2EE application SubscriberDataServices is running.

Level: 1

Type: ERROR

Impact: Process

UCS-11179: Command Line Interface connection problems.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11180: No value for ''{0}'' was provided.
Cause: A configuration value for the indicated property was not specified in the ejb-jar.xml file for the subscriberdataservice application.
Action: Specify the corresponding property.

Level: 1

Type: ERROR

Impact: Process

UCS-11181: Failed to find the user ''{0}''. Reason: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11182: Failed to close connection to LDAP store. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11183: Unable to find a user with attribute ''{0}'' = ''{1}''. Reason: {2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11184: Failed to find user attributes for privateId = ''{0}''. Reason: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11185: Error performing SQL operation.
Cause: A SQL operation against the database failed.
Action: Verify that the database is accessible and correctly configured.

Level: 1

Type: ERROR

Impact: Process

UCS-11186: Format error in public identity stored in the database.
Cause: A public identity stored in the database is not a valid SIP URI.
Action: Correct the public identity.

Level: 1

Type: ERROR

Impact: Process

UCS-11187: More than one privateId found for publicId ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11188: Failed to get account status for user ''{0}''. Reason: {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11189: {0} is not supported in DAO implementation {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11191: Failed to obtain the ha1 digest hash for user ''{0}'' for realm ''{1}''. Reason: {2}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11192: Failed to obtain the group membership for user ''{0}'' for realm ''{1}''. Reason: {2}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11193: Failed to obtain all the defined roles. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11194: Failed to get ejb environment property ''{0}''. Reason: {1}.
Cause: The value of the given JNDI name is not in a proper format.
Action: Ensure that the value of the JNDI name is a boolean (that is, true or false).

Level: 1

Type: ERROR

Impact: Process

UCS-11208: Invalidating DirContextPool
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11209: Failed to get an instance of {0}. Reason: {1}.
Cause: Installation is not properly configured.
Action: Verify installation.

Level: 1

Type: ERROR

Impact: Process

UCS-11210: Unable to fetch verifier for ''{0}''. Crypto Scheme not supported.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11211: Unable to fetch verifier for ''{0}''. User without reversible password.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11212: Unable to fetch verifier; user name missing.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11213: Failed to obtain an error code for dynamic verifier. Reason: {0}.
Cause: Problems accessing OID
Action: Verify the availability of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11214: Invalid response control for ''{0}''
Cause: User in OID not configured in a proper way.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11215: Empty verifier found for ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11216: No {0} attribute found for verifier.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11217: Empty password attribute found for verifier.
Cause: User in OID not configured properly.
Action: Correct the configuration of OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11218: More than one password verifier found.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11219: Failed to close NamingEnumeration in dynamic verifier.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11220: Failed to parse expiration time ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11221: Failed to parse lockout time ''{0}''.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11222: No user attributes were retrieved!
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11223: Invalid password format for LDAP credentials
Cause: The format of the LDAP password is not recognized.
Action: Verify the configuration of the OID.

Level: 1

Type: ERROR

Impact: Process

UCS-11224: The registered componenent under the JNDI name {0} was not of type {1}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11225: The function with ObjectName ''{0}'' is not a valid math function.
Cause: Configuration of LockoutService uses a math function that is not recognized.
Action: Correct the configuration.

Level: 1

Type: ERROR

Impact: Process

UCS-11226: Could not find the MBean. Have you configured it correctly?. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11227: The math function threw an exception. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11228: A user tried to login with the username ''{0}'', which is not a known username.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11231: Could not create ObjectName for LoginFailure pattern ''{0}''. Reason: {1}.
Cause: Misconfigured installation.
Action: Correct the configuration.

Level: 1

Type: ERROR

Impact: Process

UCS-11232: User ''{0}'' failed to log in. Will call all the configured LoginFailure-handlers in the system.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11233: User ''{0}'' exceeded the maximum number of login attempts.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11234: Did not find account for ''{0}''.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11235: Problems getting account for ''{0}''. Reason: {1}.
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-11236: Could not create SecurityService => Could not unlock account. Reason: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-11237: Failed to setup radius client pool. Reason: {0}.
Cause: Configuration of Radius Client pool is probably faulty.
Action: Verify and correct configuration of Radius Client pool.

Level: 1

Type: ERROR

Impact: Process

UCS-11238: RadiusException when authenticating: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30001: Charging is not allowed
Cause: Attempted to use charging when charging is not allowed (according to the configuration).
Action: Verify ChargingAllowed configuration

Level: 1

Type: WARNING

Impact: Process

UCS-30002: Ignore the 2xx response at state: {0}.
Cause: Received a 2xx response in an illegal state.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30003: Failed to ACK the 2xx repsonse.
Cause: IOException received when trying to send ACK.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30004: Could not ACK a dialog in the state: {0}.
Cause: Illegal state when trying to ACK dialog
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30005: Failed to send SIP request.
Cause: IOException when trying to send SIP request.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30006: Could not cancel a call in the state: {0}.
Cause: Illegal state when trying to cancel call
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30007: Failed to send out response to BYE.
Cause: IOException when trying to send out response to BYE.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30008: Failed to end the call leg.
Cause: Failed to send Bye.
Action:

Level: 1

Type: WARNING

Impact: Process

<eGdiv class="msgentry">
UCS-30009: Could not cancel call in connected state.
Cause: Illegal state to cancel call.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30010: Failed to parse the SIP address.
Cause: Illegal SIP address
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30011: Failed to create the call.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30012: Could not find call with id: {0}.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30013: Failed to execute the action.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30014: Failed to terminate the call: {0}.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30015: Could not find the application session for call id: {0}.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30016: Failed to create SIP Invite Message.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30017: Failed to send INVITE to ''{0}'' from ''{1}''.
Cause: Check the exception.
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30018: Failed to handle response.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30019: Failed to handle BYE.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30020: Ignore an error response at call state: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30021: Should not receive a BYE message in state: {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30022: Failed to retrieve MaxiumCallDuration from configuration store.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30023: The session should not be NULL here; bad internal state.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30024: Could not terminate a call that is not in connected state.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30025: Failed to cancel the call: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30026: Failed to connect the call due to invalid state: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30027: Failed to connect the call due to resource unavailable: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30028: Could not find the Coherence cache "{0}" in JNDI. Will use a cache created from the com.tangosol.net.CacheFactory.
Cause: The cache was not defined in the web.xml.
Action: Define the cache in a resource-ref element in the web.xml

Level: 1

Type: WARNING

Impact: Process

UCS-30029: The call length supervisor failed to end call: {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-30030: Could not find the TimerManager "{0}" in JNDI. Call-length supervisor is disabled.
Cause: The TimerManager was not defined in the web.xml.
Action: Define the TimerManager in a resource-ref element in the web.xml

Level: 1

Type: WARNING

Impact: Process

UCS-30031: The cache "{0}" could not be retrieved from the CacheFactory. Make sure that the cache is defined in /config/ucs-thirdpartycall-coherence-cache-config.xml.
Cause: Coherence configuration for the cache is missing in the /config/ucs-thirdpartycall-coherence-cache-config.xml file in the thirdpartycallservice.jar
Action: Define the cache.

Level: 1

Type: ERROR

Impact: Process

UCS-30032: Could not find the WorkManager "{0}" in JNDI.
Cause: The WorkManager was not defined in the web.xml.
Action: Define the WorkManager in a resource-ref element in the web.xml

Level: 1

Type: ERROR

Impact: Process

UCS-30033: Could not call ThirdPartyCallListener at address "{1}" due to: {0}.
Cause: The registered ThirdPartyCallListener at specified address could not be invoked.
Action: Make sure that the ThirdPartyCallListener web services is available.

Level: 1

Type: WARNING

Impact: Process

UCS-30034: Could not schedule ThirdPartyCallListener work with callIdentifier "{1}" due to: {0}.
Cause: A work item for the work manager could not be scheduled
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31000: UCS-31000: PLACE-HOLDER MESSAGE
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31001: UCS-31001: Call Control is starting...
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31002: UCS-31002: Call Control has been started
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31003: UCS-31003: Call Control is shutting down...
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31004: UCS-31004: Call Control has been shut down
Cause:
Action:

Level: 1

Type: NOTIFICATION

Impact: Process

UCS-31100: UCS-31100: Failed to handle BYE.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31101: UCS-31101: Failed to handle response.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31102: UCS-31102: Exception when handling expired SipApplicationSession. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31103: UCS-31103: Could not send ACK. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31104: UCS-31104: Configured P-Asserted-Identity header is not an accepted address. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31105: UCS-31105: Could not send BYE. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31106: UCS-31106: Could not send CANCEL. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31107: UCS-31107: Could not send response to BYE. Exception {0}
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31108: UCS-31108: Could not deliver event ''{1}'' to application due to exception in application. Exception {0}.
Cause:
Action:

Level: 1

Type: WARNING

Impact: Process

UCS-31201: JEE application name is not available: {0}.
Cause: JEE application name is not available
Action: Verify that the domain is correctly installed.

Level: 1

Type: WARNING

Impact: Process

UCS-31202: Server name is not available: {0}.
Cause: Server name is not available
Action: Verify that the domain is correctly installed.

Level: 1

Type: WARNING

Impact: Process

UCS-31203: The call detail record (CDR) could not be stored since the CDR is invalid: {0}.
Cause: The call detail record (CDR) could not be stored to the database since the CDR is invalid.
Action: Inspect the logged call detail record (CDR). Correct it and insert manually into the database.

Level: 1

Type: WARNING

Impact: Process

UCS-31204: The call detail record (CDR) could not extracted from the JMS message: {0}.
Cause: The call detail record (CDR) could not be extracted from the JMS message.
Action:

Level: 1

Type: WARNING

Impact: Process

PKeePK8zDOEBPS/chapter_odi_messages.htm ODI-01100 to ODI-999999

21 ODI-01100 to ODI-999999

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: TRACE

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

ODI-01139: The current task of the session ({0}) does not support stop immediate. This session will be stopped normally by the Agent ({1}) before next task begins.
Cause: null
Action: null

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01143: Agent {0} started computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01144: Agent {0} completed computing next steps from step {5} of load plan instance {1} ({2}), run {3} in work repository {4}. Triggering session={6}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

ODI-01158: Agent {0} started invoking load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}. Caused by: step {6}: {7}
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

ODI-01159: Agent {0} completed load plan exception handler {5} for failed step {6} of load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 16

Type: NOTIFICATION

Impact: Other

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

Level: 1

Type: TRACE

Impact: Other

ODI-01161: Agent {0} completed load plan step {5} (status={6}) of load plan instance {1} ({2}), run {3} in work repository {4}.
Cause: null
Action: null

Level: 1

Type: TRACE

Impact: Other

ODI-01162: Scheduled task failed with id {0} of work repository {1} on Agent {2}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01163: The load plan logs purge operation failed on Agent {0}: {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01165: Client requires a repository with version {0} but the repository version found is {1}.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01201: Session start failure on agent {0}: JDBC connection error occurs while connecting to the master repository.
Cause: An incorrect connection was used for the master repository database, or repository database was down.
Action: Verify the master repository connection information and the status of the master repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01202: Session start failure on agent {0}: data source for master repository does not contain a master repository.
Cause: The master repository connection information pointed to a database schema that did not contain a master repository.
Action: Verify the master repository connection information.

Level: 1

Type: ERROR

Impact: Other

ODI-01203: Session start failure on agent {0}: the master repository is in an invalid state.
Cause: The master repository was in a state that did not allow connections. This is the case if an upgrade was being performed.
Action: Verify the state of the master repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01204: Session start failure on agent {0}: the master repository version {1} is not compatible with the agent version {2}.
Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.
Action: Upgrade the master repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

ODI-01205: Session start failure on agent {0}: an authentication error 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-01206: Session start failure on agent {0}: the agent is not defined in the topology for master repository.
Cause: The session was not found in the master repository.
Action: Verify that a session with this ID exists in the repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01207: Session start failure on agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
Cause: An incorrect connection was used for the work repository database, or repository database was down.
Action: Verify the work repository connection information and the status of the work repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01208: Session start failure on agent {0}: database schema {1} does not contain a work repository.
Cause: The work repository connection information pointed to a database schema that did not contain a work repository.
Action: Verify the work repository connection information.

Level: 1

Type: ERROR

Impact: Other

ODI-01209: Session start failure on agent {0}: work repository {1} is in an invalid state.
Cause: The work repository was in a state that did not allow connections. This is the case if an upgrade was being performed.
Action: Verify the state of the work repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01210: Session start failure on agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.
Action: Upgrade the work repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

ODI-01211: Session start failure on agent {0}: work repository {1} is not bound to the master repository.
Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.
Action: Verify that work repository name matches an existing one.

Level: 1

Type: ERROR

Impact: Other

ODI-01212: Session preparation failure: scenario {0} does not exist in work repository {1}.
Cause: The session request was received, but the agent was unable to find the named scenario in the work repository.
Action: Verify that the scenario name matches an existing scenario name in the work repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01213: Session preparation failure: scenario {0} version {1} does not exist in work repository {2}.
Cause: The session request was received, and the scenario existed in the work repository, but not with the specified version.
Action: Ensure that the scenario version matches an existing scenario version in the work repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01214: Session preparation failure: context {0} does not exist in the master repository.
Cause: The session request was received, but the agent was unable to find the context in the master repository.
Action: Ensure that the context matches an existing context code in the Topology.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01220: Session preparation failure: an unexpected exception occurred.
Cause: The remote agent faced an unexpected error while attempting to create the session.
Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Other

ODI-01221: Unable to restart session {0}: session is not found in work repository {1}.
Cause: The session to restart did not exist in the repository. This session may have been deleted, or an incorrect session ID or work repository was supplied.
Action: Verify that a session with this ID exists in the repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01222: Session start failure on agent {0}: logical schema {1} cannot be found in the master repository.
Cause: The object to be executed referred to a logical schema not present in the master repository.
Action: Ensure that the logical schema configuration exists in your master repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01223: Database error while connecting to the master repository.
Cause: The connection for the master repository database was incorrect, or the repository database was down.
Action: Verify the master repository connection information and the status of the master repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01224: Database error while connecting to work repository {0}
Cause: The connection for the work repository database was incorrect, or the repository database was down.
Action: Verify the work repository connection information and the status of the master repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01225: An unexpected exception occurred.
Cause: The agent faced an unexpected exception.
Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: ERROR

Impact: Other

ODI-01226: Step {0} fails after {1} attempt(s).
Cause: This is an execution warning. The session step failed to execute after the maximum number of retries. If step failure was not handled in the package design, the session finished in an error state.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01227: Task {0} fails on the source connection {1}.
Cause: This is an execution warning. The command on the source for this task finished with an error.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01228: Task {0} fails on the target connection {1}.
Cause: This is an execution warning. The command on the target for this task finished with an error.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01229: An error occurred while performing a {0} operation on model code {1}.
Cause: This is an execution warning. The operation specified failed on the model.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01231: An error occurred while performing a {0} operation on datastore {1}.
Cause: This is an execution warning. The operation specified failed on the datastore.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

ODI-01238: Flow {0} fails because the maximum number of allowed errors ({1} rows) is exceeded during the flow check. This flow loads target table {2}.
Cause: This is an execution warning. The interface failed because the number of errors detected in the flow exceeded the value defined in the interface.
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.

Level: 1

Type: WARNING

Impact: Other

ODI-01239: Flow {0} fails because the maximum percentage of allowed errors ({1} %) is exceeded during the flow check. This flow loads target table {2}.
Cause: This is an execution warning. The interface failed because the percentage of errors detected in the flow exceeded the value defined in the interface.
Action: Review the session execution details in the Operator Navigator or Repository Explorer. Review the erroneous records for this interface in the error table.

Level: 1

Type: WARNING

Impact: Other

ODI-01240: Flow {0} fails while performing a {1} operation. This flow loads target table {2}.
Cause: This is an execution warning. The interface failed because one of the statements returned an error return code.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

ODI-01242: Operating system command execution fails.
Cause: This is an execution warning. Execution of the operating system command failed.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01243: Session {0} ({1}) fails because work repository {2} went down.
Cause: Work repository database went down while session was being executed.
Action: Verify the state of the work repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

ODI-01244: Session {0} {1} was prepared successfully but fails because work repository {2} went down before execution could begin.
Cause: Work repository database went down while session was starting its execution.
Action: Verify the state of the work repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01246: The Logical Schema has not been set for {0}.
Cause: Because the logical schema had not been set, the object could not be executed.
Action: Verify the object that you are trying to execute, and set the logical schema for this object.

Level: 1

Type: ERROR

Impact: Other

ODI-01247: Session {0} {1} was prepared successfully but fails because master repository went down before execution could begin.
Cause: Master repository database went down while session was starting its execution.
Action: Verify the state of the master repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01249: Session {0} ({1}) fails because master repository went down.
Cause: Master repository database went down while session was being executed.
Action: Verify the state of the master repository database. The session must be restarted.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01254: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on work repository {3}.
Cause: The agent had incorrect connection for the work repository database, or repository database was down.
Action: Verify the work repository connection information and the status of the work repository database.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01262: Session {0} ({1}) could not be stopped by Agent {2}: a JDBC error occurred on master repository.
Cause: The agent had incorrect connection for the master repository database, or repository database was down.
Action: Verify the master repository connection information and the status of the master repository database.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01266: Agent {0} detected Session as stale session and set to error status.
Cause: The agent detected a stale session and the session status was set to error status.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01267: Session ({0}) could not be stopped by Agent {1} because stop type {2} provided in the request is an invalid stop type.
Cause: The agent attempted to stop a session with an invalid stop type.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01269: Session {0} ({1}) could not be stopped by Agent {2}: session is being run by another Agent with the same name.
Cause: The agent attempted to stop a session that is being run by a different agent.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01270: Session {0} ({1}) could not be stopped by Agent {2}: session {0} ({1}) is being run by {3} Agent which is not a listener Agent.
Cause: The agent attempted to stop a session that is being run by the internal agent and this is not supported.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-01271: The asynchronous jndi name cannot be null for asynchronous jobs. The ESS job status cannot be updated.
Cause: The agent attempted to set the status of the asynchronous ESS job and its jndi name was not set.
Action: Review the jndi name supplied to the Enterprise Scheduler job.

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01275: An error occurred while performing a {0} operation on submodel step {1} of the model code {2}.
Cause: This is an execution warning. The operation specified failed on the submodel operation.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: WARNING

Impact: Other

ODI-01276: An error occurred while executing the OnConnect command on JDBC connection created for data server {0} with transaction label {1}.
Cause: An error was occurred while executing the OnConnect command on the JDBC connection created to the data server.
Action: Review the underlying exception and update the OnConnect command definition configured for the data server.

Level: 1

Type: ERROR

Impact: Other

ODI-01277: An error occurred while executing the OnDisconnect command on JDBC connection created for data server {0} with transaction label {1}.
Cause: An error was occurred while executing the OnDisconnect command on the JDBC connection created to the data server.
Action: Review the underlying exception and update the OnDisconnect command definition configured for the data server.

Level: 1

Type: ERROR

Impact: Other

ODI-01278: Load plan instance {0}, run {1} does not exist in work repository {2}.
Cause: The Load Plan Instance run does not exist in the repository. This Load Plan Instance run may have been deleted, or an incorrect instance ID/run number or work repository was supplied.
Action: Verify that a load plan instance run with this instance ID and run number exists in the repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01279: The Source Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.
Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.

Level: 1

Type: ERROR

Impact: Other

ODI-01280: The Target Logical Schema {0} and Context {1} of the task {2} are not mapped to any Physical Schema.
Cause: The Logical Schema to Physical Schema Mapping is not defined for the Context used.
Action: For the Context used define the Logical Schema to Physical Schema Mapping in the Topology.

Level: 1

Type: ERROR

Impact: Other

ODI-01281: Source Technology {0} of task {1} is not of JDBC Type. When both Source and Target commands are specified, the Source Technology should be of JDBC type.
Cause: When Source and Target commands are specified, the Source Technology should always be of JDBC type.
Action: Make Sure that you modify your Procedure or KM to either use a JDBC Source Technology or edit your step to use only the Target command.

Level: 1

Type: ERROR

Impact: Other

ODI-01282: Invalid log level {0} is specified. A valid log level value is between {1} and {2}.
Cause: Invalid log level specified for scenario/session invocation or for session restart.
Action: Please specify a valid log level.

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-01284: Session {0} ({1}) with Owb audit Id {2} fails.
Cause: The session finished in an error state.
Action: Review the session execution details in the Operator Navigator or Repository Explorer.

Level: 1

Type: ERROR

Impact: Other

ODI-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-01286: Session {0} ({1}) could not find Owb job for this session.
Cause: The session being aborted is not an Owb Job.
Action: Review the session being aborted in the Operator Navigator or Repository Explorer.

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-01291: Workspace {0} cannot be resolved to a physical workspace using context {1}.
Cause: The context does not contain a mapping for the logical workspace.
Action: Review the mappings defined in the context.

Level: 1

Type: ERROR

Impact: Other

ODI-01292: An execution context cannot be determined for this job.
Cause: An execution context cannot be determined for this job.
Action: Use the Context to provide an explicit context for this execution.

Level: 1

Type: ERROR

Impact: Other

ODI-01293: Exception occurred during spawning of ECID to child session.
Cause: Spawning of ECID from parent session to child session failed.
Action: Review the exception raised to get more detail.

Level: 1

Type: WARNING

Impact: Other

ODI-01294: Unwrapping of a wrapped ECID [{0}] failed.
Cause: Unwrapping of ECID failed.
Action: Review the exception raised and the format of wrapped ECID to get more detail on unwrap failure

Level: 1

Type: WARNING

Impact: Other

ODI-01295: Cleanup of Session {0} ({1}) raised the following {2} messages: {3}
Cause: Messages were raised during the Cleanup phase.
Action: Review the messages raised during the Cleanup and you may need to perform some manual cleanup.

Level: 1

Type: WARNING

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-01297: Parallel task "{0}" failed; {1} child task(s) in error; Failed child tasks: {2}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01299: A task "{0}" from one of the parallel branches has failed. Hence aborting the current branch
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01300: ASYNC_JNDI_NAME cannot be null for async job.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01301: Unable to submit Job Definition: {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01302: Logical Agent {0} must be mapped to a Physical Agent in the ContextCode {1}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01303: RuntimeSessionfactory must not be null.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01304: Unable to find request for ID {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01305: jobDefinitionId must not be null
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01306: scheduleDefinitionId must not be null
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01307: ContextCode is null, cannot lookup physical agent
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01308: SchedulingService object was created without an EntityManager, cannot lookup physical agent
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01309: Unable to find logical agent : {0}.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01310: Unable to find context : {0}.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Other

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

Level: 32

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: WARNING

Impact: Other

ODI-01350: Credential map key ''{0}'' not found in credential map ''{1}''.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01351: An unexpected error was thrown during execution of the scenario ''{0} - {1}''
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01352: An unexpected error was thrown during job execution
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01353: RequestId={0} Scenario={1} : Agent URL must be specified. The Job Definition must include the LocalAgent or the job submission must include a physical agent url ({2}) parameter.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01354: Load plan must be asynchronous
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01355: username ''{0}'' from credential map ''{1}'' does not match currentSubjectName ''{2}''
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01356: Credential map key parameter ''{0}'' not found.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01357: Error resolving ADF connection for connectionId=''{0}''.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

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-01402: Agent {0} start failure: the master repository is in an invalid state.
Cause: The master repository was in a state that did not allow connections. This is the case when an upgrade is being performed.
Action: Verify the state of the master repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01403: Agent {0} start failure: the master repository version {1} is not compatible with the agent version {2}.
Cause: The master repository was upgraded but not this agent, or the agent was upgraded but not the master repository.
Action: Upgrade the master repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01406: Agent {0} started with warning: JDBC connection error occurs while connecting to the work repository {1}.
Cause: The work repository information was incorrect, or the repository database was down.
Action: Verify the work repository connection information and the status of the work repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01407: Agent {0} started with warning: connection details of {1} do not contain a work repository.
Cause: The work repository connection information pointed to a database schema that did not contain a work repository.
Action: Review the work repository connection information and revise it as necessary.

Level: 1

Type: ERROR

Impact: Other

ODI-01408: Agent {0} started with warning: work repository {1} is in an invalid state.
Cause: The work repository was in a state that did not allow connections. This is the case when an upgrade is being performed.
Action: Verify the state of the work repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01409: Agent {0} started with warning: work repository {1} version {2} is not compatible with the agent version {3}.
Cause: The work repository was upgraded but not this agent, or the agent was upgraded but not the work repository.
Action: Upgrade the work repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

ODI-01410: Agent {0} started with warning: work repository {1} is not bound to the master repository.
Cause: The work repository specified in the request was not found in the list of work repositories attached to this master.
Action: Ensure that work repository name matches an existing one.

Level: 1

Type: ERROR

Impact: Other

ODI-01411: Agent {0} started with warning: a database error occurs while cleansing stale sessions.
Cause: The agent encountered a database error while attempting to close stale sessions.
Action: Review the status of the sessions for this agent, and manually remove the stale sessions.

Level: 1

Type: ERROR

Impact: Other

ODI-01412: Agent {0} started with warning: an unexpected error occurs while cleaning stale sessions.
Cause: The agent encountered an unexpected error while attempting to close stale sessions.
Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Verify the status of the sessions for this agent, and manually remove the stale sessions.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01414: Error connecting to agent {0}: a JDBC error occurs while connecting to the master repository.
Cause: The remote agent had incorrect connection for the master repository database, or repository database was down.
Action: Verify the master repository connection information and the status of the master repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01415: Error connecting to agent {0}: data source for master repository did not contain a master repository.
Cause: The master repository connection information for the remote agent pointed to a database schema that did not contain a master repository.
Action: Review the master repository connection information and revise it as necessary.

Level: 1

Type: ERROR

Impact: Other

ODI-01416: Error connecting to agent {0}: the master repository is in an invalid state.
Cause: The master repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.
Action: Verify the state of the master repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01417: Error connecting to agent {0}: the master repository version {1} is not compatible with the agent version {2}.
Cause: The master repository was upgraded but not the remote agent, or the remote agent was upgraded but not the master repository.
Action: Upgrade the master repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01419: Warning connecting to Agent {0}: JDBC connection error occurs while connecting to the work repository {1}.
Cause: The remote agent had incorrect connection for the work repository database, or the repository database was down.
Action: Verify the work repository connection information and the status of the work repository database.

Level: 1

Type: ERROR

Impact: Other

ODI-01420: Warning connecting to Agent {0}: connection details of {1} do not contain a work repository.
Cause: The work repository connection information for the remote agent pointed to a database schema that did not contain a work repository.
Action: Verify the work repository connection information.

Level: 1

Type: ERROR

Impact: Other

ODI-01421: Warning connecting to Agent {0}: work repository {1} is in an invalid state.
Cause: The work repository was in a state that did not allow connections from the remote agent. This is the case when an upgrade is being performed.
Action: Verify the state of the work repository.

Level: 1

Type: ERROR

Impact: Other

ODI-01422: Warning connecting to Agent {0}: work repository {1} version {2} is not compatible with the agent version {3}.
Cause: The work repository was upgraded but not the remote agent, or the remote agent was upgraded but not the work repository.
Action: Upgrade the work repository version or the agent version.

Level: 1

Type: ERROR

Impact: Other

ODI-01423: Warning connecting to Agent {0}: work repository {1} is not bound to the master repository.
Cause: The work repository specified in the request was not found in the list of work repositories attached to the master.
Action: Verify that work repository name matches an existing one.

Level: 1

Type: ERROR

Impact: Other

ODI-01424: Agent host or port cannot be reached using {0}.
Cause: Incorrect host or port information was provided, or the agent was not started on the remote host.
Action: Correct the host or port information or start the agent.

Level: 1

Type: ERROR

Impact: Other

ODI-01425: Agent application cannot be reached using {0}.
Cause: An incorrect application name was provided for this agent, or the agent application was not started on the host.
Action: Correct the application name used in the URL or verify the agent status.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01427: invalid parameters
Cause: Invalid parameters were supplied in the request.
Action: Check the parameters that were supplied as part of the request. Ensure that parameter names and cases are correct.

Level: 1

Type: WARNING

Impact: Other

ODI-01428: internal error
Cause: An agent internal error occurred.
Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode).

Level: 1

Type: FATAL

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01431: Agent {0} cannot clean the stale sessions in work repository {1} because the work repository {1} is still down.
Cause: The remote agent was not able to connect to the work repository while attempting to close stale sessions.
Action: Determine the status of the repository. Once this repository is running, manually remove the stale sessions.

Level: 1

Type: ERROR

Impact: Other

ODI-01432: Agent {0} cannot clean the stale sessions in work repository {1} due to an unexpected error.
Cause: The remote agent faced an unexpected error while attempting to close stale sessions.
Action: Contact Oracle Support Services. Provide the error message, a description of the action causing this fault, and the exception stack trace in the log files (with the logging level set to debug mode). Determine the status of the sessions for this agent, and manually remove the stale sessions.

Level: 1

Type: ERROR

Impact: Other

ODI-01433: The Internal agent does not support cleaning stale sessions from multiple work repositories.
Cause: Empty string value was passed for the work repository name in the Clean Stale Sessions request sent to the Internal Agent.
Action: Specify a non-empty valid work repository name in the Clean Stale Sessions request sent to the Internal Agent. If you want to clean the stale sessions across the work repositories, perform this operation on a Remote physical Agent.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01435: Storage space for the IDs of some object types is low in Repository {0}. When no storage space is available, it will not be possible to create obects of these types. Consider creating a new repository for the following object types (Object Type: Number Remaining) {1}.
Cause: Storage space was low for some IDs in this repository.
Action: Consider creating a new repository.

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: WARNING

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01441: Unable to connect to the master repository at JBDC URL={0} with USER={1}.
Cause: An SQLException occurred while creating connection to the master repository with the given parameters.
Action: Verify your Agent configuration and make sure the master repository connection parameters are correct.

Level: 1

Type: ERROR

Impact: Other

ODI-01442: Unable to load JBDC Driver {0} configured for master repository connection.
Cause: ClassNotFoundException occurred while loading the driver class.
Action: Verify your Agent configuration and make sure the driver specified for master repository connection is correct and the corresponding jar is present under driver folder.

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-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-01445: Invalid HTTP/S URL retrieved from the JRF utility : {0}
Cause: JRF utility has returned an invalid HTTP/S URL for the agent.
Action: Verify if ODI agent's dependent modules are successfully deployed on the container.

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-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-01501: Cannot find variable "{0}" in the definition of load plan instance {1}.
Cause: The start/restart load plan request contained startup values for variables that are not defined in the load plan
Action: User error or problem in the IDE invocation code

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01504: Trying to update variables during execution of step "{0}" (load plan instance {1}, run {2}), as part of the exception handler for step "{3}", but variable updates during exception handlers are not supported.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01505: Current value "{0}" of variable "{1}" (while evaluating When clause "{2}") is not a valid value of type {3} (load plan instance {4}, run {5}).
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01509: Load Plan Instance {0} cannot be restarted because the previous run ({1}) status "{2}" is not in "{3}" status.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01512: Variable "{0}" is defined as having datatype "{1}" in Load Plan instance {2}, but as having type "{3}" in scenario "{4}" (version {5}), Load Plan instance step "{6}".
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01518: Parallel step "{0}" failed; {1} child step(s) in error, which is more than the maximum number of allowed errors ({3}) defined for the parallel step. Failed child steps: {2}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-01558: The session {0} corresponding to the load plan step {1} of load plan instance {2}, run {3} is not found. We assume this step to be in error status.
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

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

Level: 1

Type: ERROR

Impact: Other

ODI-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-01580: Unable to set the role OWB_USER for this user.
Cause: An attempt was made to set the role OWB_USER for the connected user.
Action: Check that the role exists and the connected user is an OWB user.

Level: 1

Type: ERROR

Impact: Other

ODI-01581: Unable to set the workspace {0} for this user.
Cause: An attempt was made to select the OWB workspace for the connected user.
Action: Check that the workspace exists and the connected user has got privilege to access it.

Level: 1

Type: ERROR

Impact: Other

ODI-01582: Unexpected error when connecting to Owb workspace {0}.
Cause: An unexpected error occurred when connecting to workspace.
Action: Verify that the Owb repository is up and running.

Level: 1

Type: ERROR

Impact: Other

ODI-01583: Owb workspace {0} does not contain components that enable execution from Odi.
Cause: A component that is required by ODI has not been found in this workspace.
Action: Verify that the Owb repository contains the correct patch for ODI.

Level: 1

Type: ERROR

Impact: Other

ODI-01584: Mandatory parameter {0} is missing for https protocol.
Cause: A parameter that is required to start ODI agent to enable https protocol is missing.
Action: Verify that the parameter is specified in odiparams.[sh|bat].

Level: 1

Type: ERROR

Impact: Other

ODI-01585: A Step with Id {0} does not exist in the Session {1}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01586: A Task with Id {0} does not exist in the step {1} of the Session {2}
Cause: null
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01587: An execution context cannot be determined for OGG operation {0}.
Cause: An execution context cannot be determined for OGG operation.
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01588: The specified operation {0} provided is not supported by this tool.
Cause: The operation provided is not supported by this tool.
Action: Verify the parameters

Level: 1

Type: ERROR

Impact: Other

ODI-01589: The execution of the OdiOggCommand operation {0} failed.
Cause: The execution of the OdiOggCommand operation failed.
Action: null

Level: 1

Type: ERROR

Impact: Other

ODI-01590: The execution of the script failed. {0}
Cause: The execution of the script failed in the BSF Engine.
Action: null

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-01592: Error occurred testing connection to dataserver with agent {0}
Cause: Dataserver connection test failed on the agent
Action: Verify that dataserver connection configuration is valid. Verify that dataserver is available

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-01594: The connection to the data server {0} failed.
Cause: The data server might be down or the data server connectivity settings are not correct.
Action: Verify that you are able to test the data server using the Studio successfully.

Level: 1

Type: ERROR

Impact: Other

ODI-01595: The command script failed with trace {0}.
Cause: There was a failure in the Ftp or Sftp command script.
Action: Verify the trace and resolve the error in the command script passed to the tool.

Level: 1

Type: ERROR

Impact: Other

ODI-01600: Unable to update Opmn Xml file.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01601: Unable to parse Opmn xml file
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01602: Please provide all arguments
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01603: Syntax: java DeleteAgentFromOpmn <Instance Home> <OracleOpmnHome> <Agent Name>
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01604: Unable to parse Opmns Snippet Xml
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME</p>

Impact: Other

ODI-01605: Component already exists in the file.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01606: Please provide the value for {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01607: Error reading file
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Files

ODI-01608: No of values provided for component name and port number are not equal. Please provide the same no of values for both.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01609: No of values provided for component name and JMXport number are not equal. Please provide the same no of values for both.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01610: ODI environment variable {0} is not set and ODI Tool startcmd not launched from interactive console.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01611: Must provide username for {0} before obtaining password.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01612: Unknown parameter ignored: {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01613: Unknown parameter value pair ignored: {0}={1}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01614: {0} is a mandatory parameter
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01615: DESCRIPTION Resumes an execution session. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX restartsession.(cmd|sh) "-INSTANCE=<instance_name>" <session_number> [<log_level>] ["-AGENT_URL=<agent_url>"]
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

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-01619: DESCRIPTION Starts a Oracle Data Integrator command. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX startcmd.(cmd|sh) "-INSTANCE=<instance_name>" <Command Name> ["<command parameter>"]*
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-01624: DESCRIPTION Encode a password. See Oracle Data Integrator documentation for the detailed syntax. SYNTAX encode.(cmd|sh) "-INSTANCE=<instance_name>" <password>
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01625: This must be executed from a domain. System property domain.home cannot be null"
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01626: "Neither parameter {0} nor {1} is specified"
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01627: "Error getting instance properties"
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01628: {0} (arg[{1}]) "{2}" should not be blank.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01629: {0} (arg[{1}]) "{2}" should specify a valid integer.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01630: {0} (arg[{1}]) "{2}" should specify a valid long number.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01631: -STOP_LEVEL parameter value must be one of: {0}, {1}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01632: Session "{0}" is being stopped ({1})
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01650: -AGENT_URL=<agent_url> is a mandatory parameter
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01651: Error while executing:
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01652: Unknown parameter ignored: {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01653: Unknown parameter value pair ignored: {0}={1}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01654: load_plan_instance_id is a mandatory parameter
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01655: Usage: RestartLoadPlan -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-01656: Load plan instance "{0}", run {1} has restarted
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01657: load_plan_name and context_code are mandatory parameters
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01658: Usage: StartLoadPlan -INSTANCE=<instance_name> <load_plan_name> <context_code> [<log_level>] "-AGENT_URL=<agent_url>" ["-SYNC=(no|yes)"] ["-POLLINT=<msec>"] ["-KEYWORDS=<keywords>"] ["<variable>=<value>"]*
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01659: Load plan "{0}", instance "{1}", run {2} has started
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01660: load_plan_instance_id is a mandatory parameter
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01661: Usage: StopLoadPlan -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-01662: Load plan instance "{0}", run {1} has stopped ({2})
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01663: -STOP_LEVEL parameter value must be one of: {0}, {1}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01664: Waiting for completion of load plan execution.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01665: Load plan execution completed in {0} status.
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01700: SessionId is not valid
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01701: The session was not found in the repository: {0}
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01702: This operation is not supported on this platform
Cause:
Action:

Level: 32

Type: SET_AT_RUNTIME

Impact: Other

ODI-01800: Exception {0} has occurred as ESS-EM linking is disabled.
Cause: Unable to connect to master repository.
Action: Check if the master repository is accessible and up. This is not mandatory since master repositories can be down.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

ODI-01814: No repository definition found for work repository {0} in repositories.xml. Search will be disabled for this repository.
Cause: A configuration error has occurred.
Action: Add the jndi entries for all the work repositories for each of the master repositories in repositories.xml.

Level: 1

Type: ERROR

Impact: Configuration

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

ODI-03022: Attaching of Work Repository failed due to error: {2}
Cause: Errored out due to {2} and overwriting of the repository was not chosen
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03023: Attaching of Work Repository failed
Cause: An unexpected error occured and overwriting of the repository was not chosen
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

ODI-03035: Supervisor Password and Confirm Supervisor Password fields should match and only zip files can be uploaded , the {0} upload was unsuccessful.
Cause: Both the password match and zip files to be uploaded conditions failed
Action: Make sure both the passwords are same and file uploaded is zip file

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

ODI-03046: unable to find the agent for given logical agent and context code
Cause: Physical Agent mapping was not defined for selected logical agent and context.
Action: A different set of credentials is required or the mapping needs to be defined.

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03050: failed to start scenario : {0} ? {1} in debug mode.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: DATA

ODI-03082: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.
Cause: CKM SQL does not contain ODI_PK primary key column. Hence unable to delete the error records.
Action: Future release will have the ODI_PK primary key column incorporated in CKM SQL.

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Data

ODI-03090: failed to restart session : {0} in debug mode.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03145: Check the logsPrivilegedActionException {0} was thrown. system-jazn-data.xml might not have the privileges specified.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03150: Invalid Context code. Context code cannot have lower case characters and white spaces. 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-03184: Maximum Cache Entries cannot be less than zero.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03185: Unused Blueprint Lifetime cannot be less than zero.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03186: Maximum Threads Number cannot be less than Max Threads Per Session.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03187: Max Threads Per Session cannot be less than zero.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03188: Maximum Threads Number should be greater than zero.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03189: Maximum Threads Number cannot be less than Maximum Session Number.
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03190: Exception fetching connector points. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03191: Exception fetching model. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03192: Exception fetching physical schema. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03193: Exception fetching Data Server. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03194: Exception fetching Catalog. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03195: Exception fetching Constraints. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03196: Exception fetching connector point properties. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03226: Parameter File could not be Loaded.
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Data

ODI-03260: Failed to apply settings for agent: {0}
Cause: An unexpected error occured
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03261: Exception while applying settings for agent: {0}. Failure reason: {1}
Cause: An unexpected error occurred
Action: Check the logs

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

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

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03267: No valid repository alias is found. Click on management link on top right corner to create one.
Cause: Either there were no repository connection aliases, or those that were created did not have a valid JNDI name
Action: Create a new repository connection alias.

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

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

Level: 1

Type: ERROR

Impact: Data

ODI-03330: Exception while importing attrbutes. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03331: Exception while importing properties. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03332: Exception while fetching attributes. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03333: Exception while fetching properties. Reason: {0}
Cause: An unexpected error occurred.
Action: Check the logs.

Level: 1

Type: ERROR

Impact: Programmatic

ODI-03334: Exception while importing propeties and expressions of attributes. Reason: {0}