Search This Blog

SBL-DAT-60180: Date time format string '%1' is invalid.

Applies to:

Siebel CRM - Version: 8.1.1.2[21215] and later   [Release: V8 and later ]
Siebel CRM - Version: 8.0.0.9[20433] and later    [Release: V8 and later]
Information in this document applies to any platform.

Description

The "SBL-DAT-60180" (invalid date) error may happen under increased load of Siebel Object Manager. For example, when many of Workflow Process Manager tasks run the EAI Siebel Adapter Query in parallel.


Likelihood of Occurrence

Siebel Application - EAI tool set - EAI Siebel Adapter Query


The issue was reported in following Product Releases:

8.0
:  Fix Pack 8.0.0.9, Fix Pack 8.0.0.10

8.1.1: Fix Pack 8.1.1.2, Fix Pack 8.1.1.3


Possible Symptoms

The "SBL-DAT-60180" error happens, even if  the search specification of Query does not use date field in the search expression. It claims syntax error for field value, which was used in the Search Spec expression (usually as the 1st field in the query).

The error causes the EAI Siebel Adapter Query to deliver no record and throw an exception.

Siebel Application log  example (Query for the "SIS OM Order" Integration Object instance of Order Id: "1-ABC" and Root Line Item Id: "1-DEF" ):
...
ObjMgrBusServiceLog InvokeMethod 4 ... Begin: Business Service 'EAI Siebel Adapter' invoke method: 'Query' ...

ObjMgrBusServiceLog InvokeMethod 4 ... Begin: Business Service 'EAI Query Spec Service' invoke method: 'QuerySpecToSiebelMsg' ...

EAIQrySpec EAIQrySpecParams 3 ... The Query Specified for Object Id '' of type 'SIS OM Order' is '[Header.Id] = '1-ABC' and [Line Item.Root Id] = '1-DEF''
...
ObjMgrLog Error 1 ... (eaidateconvutil.cpp (254)) SBL-DAT-60180: Date time format string '1-ABC' is invalid.

ObjMgrBusServiceLog Error 1 ... (eaiqryspec.cpp (461)) SBL-DAT-60180: Date time format string '<?>' is is invalid.

EAISiebAdptPerf EAISiebAdptPerfStat 3 ... Query|0|0

Workaround or Resolution


No Workaround was identified so far.

Apply product fix once in becomes available (delivered as Quick Fix or included in the Fix Pack release).

Patches

Issue is identified as the product defect Bug 12-1XBND23 (alternative reference  CR# 12-1ZFCGBV)  the "QuerySpecToSiebelMsg" Method of the "EAI Query Spec Service" Business Service. This method is internally called by the "EAI Siebel Adapter" Business Service during execution of the "Query" Method.

Available Fixes:

* 8.0.0.9 Fix Pack: Quick Fix  - QF0961, Patch Number: 10113588

* 8.1.1.2 Fix Pack: Quick Fix - QF02AR, Patch Number: 10155474

* 8.1.1.3 Fix Pack: Quick Fix - QF0336, Patch Number: 10188281

Modification History



References

BUG:12-1XBND23 - INTERMITTENT SBL-DAT-60180 ON BS EAI QUERY SPEC SERVICE

Applies to:

Siebel System Software - Version: 8.0.0.5 [20420] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms



On : 8.0.0.9 [20420] version, Siebel EAI

When attempting to query for data with EAI Siebel Adapter under high load
the following error occurs.

ERROR
-----------------------
SBL-DAT-60180: Date time format string 'Batch' is invalid.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load with EIM the table S_UCM_CONTACT (could be any other), and ensure some date time fields are not null.
2. Start concurrent tasks of a workflow that does EAI Siebel Adapter, query page on this data and later processes it.
e.g: several calls to Start concurrent UCMBatchProcess tasks:
start task for component UCMBatchProcess with UCMSearchSpec="[Contact.UCM Type Code]='Batch' and [Contact.Job Title]='1' ",UCMCDMMatchFlag="false",UCMCDMExactMatchFlag="TRUE",UCMSurvivorshipEngineFlag="false",UCMCDMCleanseFlag="FALSE",UCMBatchSize = "2"
3. Some of then will fail with error SBL-DAT-60180 even not using any date field on searchspec.
It doesn't fail always then sometimes it's necessary to run the process again some more times.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users face unexpected errors during peak times.

Cause

BUG: 12-1ZFCGBV - Intermittent SBL-DAT-60180 on BS EAI Query Spec Service

has been logged to address this issue.


Solution

This is expected to be fixed at
8.0.0.11 Fix pack
8.1.1.4 Fix Pack

and higher releases.
At the time of writing these releases were not yet available for download.

References

BUG:12-1ZFCGBV - INTERMITTENT SBL-DAT-60180 ON BS EAI QUERY SPEC SERVICE

Applies to:

Siebel CRM - Version: 8.1.1.2[21215] to 8.1.1.3[21219] - Release: V8 to V8
Information in this document applies to any platform.

Goal

Explain the use of  EAI Siebel Adapter input argument UTCCanonical

Solution

There is a new feature introduced by product Change Request  12-1OUCG3F that allows dates output by EAI Siebel Adapter to be optionally in ISO 8601 standard .

This was introduced in Siebel CRM Fix Pack 8.1.1.2 (see   NOTE:880452.1 Siebel Maintenance Release Guide, Version 8.1.1.x )

It consists of a new and optional input argument to EAI Siebel Adapter, methods (Query, Upsert and so on) named UTCCanonical

By default, the feature is turned off to ensure integrations already implemented keep working without the need for changes.

It can be turned on by explicitly passing an additional input argument UTCCanonical = Y .

WARNING:  For updates, the EAI Siebel Adapter accepts only UTC (GMT) time zone other time zones, provided  in ISO date time value will cause the error:
SBL-DAT-60180 Date time format string '...' is invalid.

In summary :
UTCCanonical
Y (new)
ISO 8601 standard in UTC
"2010-01-21T21:43:00Z"
UTCCanonical
Y (causes update error)
ISO 8601 standard with time Zone:
"2010-01-21T22:43:00+1:00"
UTCCanonical
N (default)
Day/month/year hour:minute:seconds
"01/21/2010 10:46:32"

References

NOTE:880452.1 - Siebel Maintenance Release Guide, Version 8.1.1.x

Applies to:

Siebel CRM - Version: 8.1.1.3 SIA[21219] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms


When attempting to deploy the ADM Data Type Web Service - Outbound, the following error occurs:

ERROR
ObjMgrBusServiceLog Error 1 000000e44cd30d84:72799 2010-11-05 09:58:38 (eaiqryspec.cpp (461)) SBL-DAT-60180: Date time format string '<?>' is invalid.



Cause


This is caused by a product defect.

The following document describes the error the customer is experiencing:
Doc ID 1203613.1: Intermittent error "SBL-DAT-60180" (invalid date) in EAI Query Spec Service may cause failure of EAI Siebel Adapter Query and Insert operations.

This issue has been addressed in product defect Bug: 12-1XBND23.



Solution



STEPS:

To implement the solution, execute the following steps:

1. Download and review the readme and prerequisites for 8.1.1.3 Fix Pack: Quick Fix - QF0336    Patch: 10188281.
2. Ensure that you have taken a backup of your system before applying  the recommended patch.
3. Apply the patch in a test environment.
4. Retest the issue.
5. Migrate the solution, as appropriate, to other environments.


References

BUG:12-1XBND23 - INTERMITTENT SBL-DAT-60180 ON BS EAI QUERY SPEC SERVICE
NOTE:1203613.1 - Intermittent error "SBL-DAT-60180" (invalid date) in EAI Query Spec Service may cause failure of EAI Siebel Adapter Query and Insert operations
PATCH:10188281 - 8.1.1.3 21219 SBA QF0336 SEBL_ARU

Applies to:

Siebel eCommunications - Version: 8.0.0.9 SIA[20433] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal


We have applied QF0961 (8.0.0.9 Fix Pack: Quick Fix - QF0961, Patch Number: 10113588) which fixed a Date Time format issue (SBL-DAT-60180: Date time format string '<?>' is invalid)

Afterwards we have observed crashes on our EAI Object Manager so we applied the QF0963.
It has resolved our crash issue and we got a stable system.

However the QF0963 did contain the previous bug fix by QF0961

Is it possible  to apply QF0961 on top of QF0963?

Solution


The Answer is YES.
It is possible, as the dll files being changed and modified by these 2 Quickfixes are different and there is no conflict.

The customer has applied the QF0961 on top of QF0963 and both fixes were successfully implemented.


No comments:

Post a Comment