Search This Blog

SBL-DAT-00235: Value too long for field '%1' (maximum size %2).

Applies to:

Siebel Email Response - Version: 7.7.1 SIA [18306] to 8.1 [21039] - Release: V7 to V8
Information in this document applies to any platform.


"Create and Submit Request" method of "Outbound Communication Manager" component through Business Service Simulator get the following error:

ObjMgrSqlObjLog WriteRecord 5 0 2009-12-10 13:30:12 End: WriteRecord for SqlObj at df174d0

CommSrvr CommSrvrError 1 0 2009-12-10 13:30:12 1-1OLFA: Sent 0 out of 0 messages (-1.#IO) seconds. Unable to process request 1-1OLFA due to an invalid communication template.(SBL-CMO-00116) This operation is not allowed when there are no records displayed.

Please execute a query that returns at least one record or add a new record.(SBL-DAT-00215)

ObjMgrBusCompLog Error 1 0 2009-12-10 13:30:12 (buscomp.cpp (23437)) SBL-DAT-00235: Value too long for field 'Status Message' (maximum size 250).


Researched into other service requests, found common link between these errors and language discrepancies.

The information I found from other SRs includes the following resolutions:

1) The cause of the error was found to be the language specified for
“Msg Default Language” and

The cause of the behaviour was identified to be the Locale with which the Communications Outbound Manager had been configured, namely ENG or British English.

This meant that email templates which had been configured to be used with ENU, or American English, were overlooked when the Workflow Process tried to send the mails.

For more information on debugging and tracing techniques for eMail Response, please refer to "Doc ID 477787.1: How To Trace Siebel eMail Response Operations"


Verify the language and locale match between Outbound Communications Manager component and the email templates


NOTE:528772.1 - eMail Response - Auto-acknowledge
NOTE:534937.1 - Communication Outbound Task

Applies to:

Siebel Workflow - Version: 7.7.2 [18325] - Release: V7
Information in this document applies to any platform.


Two problems where discovered with following structure was in place:


Initial Process: Start > EAI Dispatch Service > End, the Rule set uses "Workflow Process Manager" to run following Long Running flow


Main Process: Start > … > Sub-Process > End, the sub-process step passes a Hierarchy and calls following Long Running flow


Child Process: Start > Wait > End


Problem 1:

During the initialization of the Child process gets following error occurred.

Value too long for field 'Value' (maximum size 1999).(SBL-DAT-00235)


Because the above error occurred, the component executing the Main process crashes when the error is propagated back to level up. Stack as below.


void CSSWfStepInst::Stop

unsigned short CSSWfCoordinator::Stop

unsigned short CSSWfEngine::MaintainExcptnState

unsigned short CSSWfEngine::RunSingleProcess

unsigned short CSSWfEngine::StartProcess

unsigned short CSSWfEngine::DoInvokeMethod

unsigned short CSSService::InvokeMethod



Problem 1:

It was due to the fact that one of the process properties passed to the sub process did contain character pipe (|).

When persistence is enabled, the application stores various information in tables to maintain states of the workflow process execution (instance). If tracing is enabled, the log files will show how a process property's value is saved in column PROP_VAL of S_WFA_INST_PROP.

If the data is too long to be save in one record (PROP_VAL is 1999 characters max), the application cuts it into pieces and creates several records. The application adds a pipe (|) at the beginning and end of the pieces. Also, the algorithm based on this is impacted by | in the value itself.


Problem 2:

The above situation cause a crash which is not expected at all.



There is no workaround for the crash and problem was logged under Bug 12-1MMQMKD

However, the crash is due to problem 1, so, addressing it the approach.


Solution to problem 1 is to not have pipe characters in data of user properties.


In this case, the characters pipe came from a XML message sent by the external application though HTTP inbound request. It was not possible to prevent the external application to sent them, so the approach is to remove them in the first thing done by the workflow process, before the XML is converted into a hierarchy.


This should be done with a custom BS Note 476946.1 should help.


Bug 12-1ML9T7H was created for this.



Applies to:

Siebel CRM - Version: SIA [21211] to SIA [21211] - Release: V8 to V8
Information in this document applies to any platform.


Statement of Issue:
The customer was using UCM 8.2 ( + QF3103) and found an error occurring when two contacts are merged in Administration - Universal Customer Master > Existing Duplicates

[1] Error invoking service 'UCM Source Data and History Service', method 'Store' in the step  'Store History'. (SBL-BPR-00162)

[2] The method 'SetFieldValue' in BC 'UCM Contact Source Data and History' (integration component 'Contact ') for the record with the search term [Id] = "1-3EJBU" has returned the following error:

'Value too long for column' Merge Transaction Id '(maximum size: 30). (SBL-DAT-00235) '(SBL-EAI-04451)


The cause of this issue is a mismatch between the business level and database level definitions.  In the 'UCM Contact Source Data and History' and 'UCM Account Source Data and History' business components, the 'Merge Transaction Id' field is mapped to the TRANSACTION_ID column in the S_UCM_CONTACT and S_UCM_ORG_EXT tables respectively. The field length is 100, but the column length is 30. Hence when the application tries to write the 36 character generated Id into the column during a merge it fails with an error.

The following change request was logged for this issue:

Bug 12-1YGSNZB - QF3103: Unmerge fails:TRANSACTION ID column in tables like S_UCM_CONTACT needs extension to 100


The current supported methods to workaround this issue are:

1. Map the Merge Transaction Id field to two new columns for each of the business components affected, namely the 'UCM Contact Source Data and History' and 'UCM Account Source Data and History' business components.

2. Get Oracle Expert Services to alter the standard column definition in the 'Expert Mode' of Siebel Tools.  However, Oracle Expert Services is a billable service.

The issue has been fixed in the upcoming branch quick fix QF3104 and should be fixed in the upcoming fix pack.

No comments:

Post a Comment