uCosminexus Service Platform, Messages

[Contents][Index][Back][Next]

KDEC63001-E

The specified telegram is invalid. (cause = aa....aa, information = bb....bb)

aa....aa: Cause code
bb....bb: Information
Cause code Content Information
When executing a single SQL statement When executing multiple SQL statements#1 #2
01 Root element name is invalid Specified root element name
02 There is no element with the SQL identifier name or there are multiple elements with the SQL identifier name Number of specified SQL identifier names Number of specified SQL identifier names (Position)
03 The specified SQL identifier has not been defined in the SQL operation definition Specified SQL identifier name Specified SQL identifier names (Position)
04 DBA_IN_DATA element is missing None SQL identifier name (Position)
05 The DBA_MULTI_SQL element does not exist, or the number exceeds the upper-limit value -- Number of DBA_MULTI_SQL elements specified
06 Elements other than the DBA_MULTI_SQL element exist below the DBadapter element -- Specified element name
11 Argument element is missing Element name SQL identifier name.element name (Position)
12 Nodes other than Text, CDATASection, or Comment nodes exist under the argument element Element name SQL identifier name.element name (Position)
13 The argument element name is repeated Element name SQL identifier name.element name (Position)
14 An element that is neither a parameter element nor IN parameter element is specified under the SQL identifier element Element name SQL identifier name.element name (Position)
21 Attribute value is invalid element-name.attribute-name = attribute-value SQL identifier name.element name.attribute name = attribute value (Position)
22 Data not conforming to the hexBinary type of the XML Schema is detected.
The request message must be revised.
type = classification-of-non-conforming-data
length = string-length
char = non-conforming-characters
The following shows the values that can be displayed for classification-of-non-conforming-data, and the meaning.
  • LENGTH: A character string contains an odd number of characters.
  • CHAR: Characters other than 0 to 9, a to f, or A to F
Either of the following values is displayed for non-conforming-characters depending on the content of classification-of-non-conforming-data:
  • For type = LENGTH: NONE
  • For type = CHAR: Characters not conforming to the hexBinary type
23 Data not conforming to the base64Binary type of the XML Schema is detected.
The request message must be revised.
length = string-length
char = non-conforming-characters
position = position-of-characters-with-error
Characters not conforming to the base64Binary type are displayed for non-conforming-data-type.
The value displayed for position-of-characters-with-error might be the number of characters displayed for string-length or more if, for example, the number of characters is a multiple of 4 plus a single character. In such cases, null is displayed for non-conforming-characters.

Legend:
--: Not applicable.

#1
If the contents of multiple elements are invalid, the information related to the element in which the invalid contents were first detected is output.

#2
Out of the DBA_MULTI_SQL elements in the request message, the position of the corresponding DBA_MULTI_SQL element is displayed with numeric characters. The position starts from 1.

Description
The contents of the request message are invalid.
(S)
Cancels the processing.
(O)
Check, and if necessary, revise the service component invocation processing on the basis of the cause code, and then re-execute the service component invocation request.