Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3430398941.

Symptoms

Hi,
I constructed Task based UI for Contact Sceen and the task allows to create a new activity. Upon populating the fields in task ui for created activity. When I hit Next, I am running into error as attached.
So I created this time a new task based on Action BO.. Just inserting a new activity. It didnt failed.

In conclusion, Action creation is not getting possible uncer contact BO where as Activity is successfully getting created in Action BO.


I thing I observed is... When I fill in the Activity Form Applet, I could see the contact Last name in MVG. Once error is thrown, Contact Last name is getting disappered.

Thanks,

Solution

Message 1

For the benefit of other readers, the following behavior was encountered with Task Based UI.
Assume a Task based on busobj Contact.
Assume this task creates an activity in this context.
When submitting the task, the following error occurs.

SBL-DAT-60241: An error has occurred committing the record of business component 'Action'. The user key of the record is
    Activity UID = ""
    S_EVT_COMM.Conflict Id = ""

However, outside of a task, the creation on an activity in the Contact busObj context does not cause any error.

The error comes from the User Property "Contact MVG PreDefault Expression" on buscomp Action. Removing the part, 'Contact.Id', solves the problem. Removing this part should not cause any problem considering that the standard Link "Contact/Action" already handles the relationship. However, workaround should be review and thoroughly tested if customizations have been done between Contact and Action.

Change request 12-1KUV3WB was created to address this problem in the task.

Jérôme Patard, Oracle|Siebel Technical Support.

Applies to:

Siebel Tools - Version: 8.1.1 SIA [21111] - Release: V8
Information in this document applies to any platform.

Symptoms

Tested this Issue in 8.1.1 SIA with Sample DB

Steps to reproduce the issue

1. Created a Task Base UI with one Step which has Contact Form Applet
2. In this Applet there are two MVG's. One MVG is based on Account BC and another MVG is based on CUT Address.
3. Started the Task Base UI and Opened the Account MVG. Added the Record and removed the same record.
4. Closed the MVG and Click the Submit Button.
5. Following Error is encountered


---------------------------
Siebel
---------------------------
[1] Task controller encountered another error while trying to handle the following error. Please use the Pause button to pause the task, or the Cancel button to cancel the task.(SBL-BPR-00537)
[2] An error has occurred committing the record 1-1YH of business component 'Account'. The user key of the record is
Party Name = ""
Location = "Outlet"
Primary Organization Id = "1-1DG"
S_ORG_EXT_SS.Conflict Id = ""
(SBL-DAT-60241)
[3] An internal error occurred retrieving a field value for ''. The field has an invalid logical index.(SBL-DAT-00430)

---------------------------
OK
---------------------------

Solution

For the benefit of the others readers:

CR#12-1V05905 and the FR#12-1V0NEIB was created as a product defect for this issue.

Following QF need to apply to rectify the issue 8.1.1 [21112] QF0060 BugID: SBA: 9037942

Thank you,
Siebel Technical Support

References

BUG:12-1V05905 - MVG IN TASK UI IS GIVINING FOLLOWING ERRORS SBL-DAT-60241 AND SBL-DAT-00430

Applies to:

Product Release: V8 (Professional)
Version: 8.0 [20405]
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-3361198991.

Symptoms

SBL-DAT-00398

Hi,

We are working in Siebel 8 SIA test environment, before we upgrade our actual environment and we have few critical business processes that we need to test in Siebel 8 Task Based UI. For that purpose, i have created a new task for creating or updating the contact.

The update contact part works fine as expected. While creating new Contact, it gives a weird error as attached in the zip file. I checked for that BC in our repository but that BC doesnt exist. I have also attached SIF of entire project as well as the Task SIF so that you can let us know where are we going wrong.

I am testing this using dedicated Siebel client and connected to sql server database.

Please let me know if you need more info.
Kindly note all the files are in the zip file.

Regards,
Akshay

Solution

Message 1

Hello Akshay,

Thank you for using the Siebel SupportWeb.

For the benefit of other readers, a Task had been created (using Task UI in Siebel 8.0) to create a new Contact. However, when the task was submitted, an error was raised :-

ObjMgrTaskLog    Detail    4    2007-06-05 10:24:01    Start processing record '1-O3R3' of BusComp 'Contact - Sales Rep - VisMvgSqlBCDef' with operation code Insert for commit

ObjMgrBusCompLog    Warning    2    2007-06-05 10:24:01    (sqlobj.cpp (29085)) SBL-DAT-00398: Field 'Primary Address Id' does not exist in definition for business component 'Contact - Sales Rep - VisMvgSqlBCDef'.
Please ask your systems administrator to check your application configuration.

ObjMgrBusCompLog    Warning    2    2007-06-05 10:24:01    (tasklogutil.cpp (2457)) SBL-DAT-00398: Field '<?>' does not exist in definition for business component '<?>'.
Please ask your systems administrator to check your application configuration.

ObjMgrLog    Error    1    2007-06-05 10:24:01    (tasklogutil.cpp (2512)) SBL-DAT-60241: An error has occurred committing the record 1-O3R3 of business component 'Contact - Sales Rep - VisMvgSqlBCDef'. The user key of the record is
Parent Id = "1-O3R2"
Child Id = ""
Conflict Id = "0"

The behavior has been re-produced with Siebel SIA 8.0 [20405], and change request 12-1JPUA0N has been logged.

Applies to:

Siebel System Software - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

When attempting to run KEYDBMGR (keydbmgr.exe), the following error is presented:

Error loading dictionary file diccache.dat.(SBL-DAT-60237)
Cleaning up... this may take a while.

Cause

This behavior was caused by an Oracle database specific connectivity issue where the ODBC name must match the tnsnames.ora alias.  The KEYDBMGR utility reads the connect string out of the .cfg file specified on its command line and then attempts to create an ODBC connection.  With Oracle based Siebel implementations, however, the Siebel application normally uses Oracle native connectivity and therefore the connect string value is the tnsnames.ora alias name.

Solution

The suggested workaround is to create an ODBC data source with the same name as the Oracle TNS Names alias referenced in the .cfg file you specify on the keydbmgr.exe command line.

So assume that you have a standard Siebel generated ODBC data source named something like SiebSrvr_Siebel. Look at what the actual Oracle connect string is (for example siebeldb). Then create another ODBC datasource using the same driver but name the ODBC data source "siebeldb" (using my example).

After this is completed, try keydbmgr.exe again.

Applies to:

Siebel Sales - Version: 8.0.0.2 [20412] - Release: V8
Information in this document applies to any platform.

Symptoms

Keydbupgrade.exe utility was not working.

Verified this issue by reviewing the output of keydbupgrade execution as below:

D:\sba80\siebsrvr\BIN>keydbupgrade.exe /u SADMIN /p SADMIN /l enu /c .\enu\epharma.cfg
Error loading dictionary file diccache.dat.(SBL-DAT-60237)
Cleaning up... this may take a while.

Cause

Incorrect parameters in epharma.cfg file

Parameter ServerDbODBCDataSource in epharma.cfg file was set to %MASTER_DATASOURCE%.

Solution

1. Open epharma.cfg file
2. Locate parameter ServerDbODBCDataSource under [Siebel] section.
3. Change this parameter to the correct ODBC Data Source.
4. Save and close the file.
5. Execute keydbupgrade.exe utility and confirm if it works fine.

Applies to:

Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3395346953.

Symptoms

SBL-DAT-60237

I change the password on the Siebel databse for AVCI01S and was able to connect with SQL Programmer but I'm getting an error. The following error appears in the log file:
ProcessPluginRequest    ProcessPluginRequestError    1    0000000a468d214c:1    2007-07-05 16:51:27     5844: [SWSE] Failed to obtain a session ID. Error loading dictionary file diccache.dat.

ProcessPluginRequest    ProcessPluginRequestError    1    0000000a468d214c:1    2007-07-05 16:51:27     5844: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

I also renamed the diccache file so that it creates a new one and it still shows the same error. At what time are you available for another web conference? The earlier the better.

Thank You,
Troy

Solution

Message 1

For the benefit of other readers,


Customer was configuring Siebel ADSI Security Adapter (ADSISecAdpt) version 8.0. After all settings were performed, error message below was logged in Object Manager and Siebel Web Server Extension log files:

SBL-DAT-60237: Error loading dictionary file diccache.dat

After further investigation and testing, we were able to find that above error message was caused by shared database account. The shared database credentials are stored in the attribute defined by “Credentials Attribute Type” parameter of ADSI account defined by “Shared Credentials DN”parameter of ADSISecAdpt profile. The shared database credentials are stored in the format below:

username=<username> password=<password>

In previous Siebel versions, it was not required that the shared database accont to exist in Siebel Application as an employee. However, in Siebel version 8.0 this is required. Customer was using AVCI01S database account as shared database. After a new employee with same User ID as AVCI01S was created only in Siebel Application, ADSISecAdpt authentication worked fine and users were able to authenticate against ADSI Directory.

Change Request 12-1K81U2D has been opened to address this Product Defect and allow usage of shared database credentials of an account that does not exist in Siebel Application.

The workaround is to create a new Siebel user with same User ID as shared database account.



Thank you,


Siebel Technical Support

Applies to:

Siebel Tools - Version: 8.0.0.1 [20408] - Release: V8
Information in this document applies to any platform.
***Checked for relevance on 16-Feb-2010***

Symptoms

When opening the Check In / Check Out dialog box in Tools, this error occurs:

 

08001 (-816): [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use

 

In the corresponding log file you might also observe these related error messages:

 

DBCLog DBCLogError 1 00000002487415c8:0 2008-07-09 09:21:32 [Sybase][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 08001: [Siebel Database][ODBC Driver][Adaptive Server Anywhere]Specified database file already in use
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 (wraprmtcmn.cpp (63) err=1114276 sys=600) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (YYYT789).
GenericLog GenericError 1 00000002487415c8:0 2008-07-09 09:21:32 Error connecting to datasource %1 (%2).
ObjMgrLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (ctxtmgr.cpp (2334)) SBL-DCK-00164: Error connecting to datasource SEAW Local Db default instance (YYYT789).
ObjMgrLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (ctxtmgr.cpp (2355)) SBL-DAT-60237: Error loading dictionary file diccache.dat.
ObjMgrSessionLog Error 1 00000002487415c8:0 2008-07-09 09:21:32 (model.cpp (5886)) SBL-DAT-60237: Error loading dictionary file diccache.dat."

Cause

The error is caused by the ODBC data source settings for the local Tools database, which include a value in the "Server name" field by default. This causes a second connection to the local Tools database to fail.

Bug 12-1NCHPDP has been raised for this issue because the Server name field is filled by default by the Tools installation process.

After removing the "Server name" value, the error disappears.

Solution

1. Open the ODBC Administrator.
2. Select the System DSN tab. 
3. Select the local Tools datasource (by default, "SSD Local Db default instance").
4. Click the Configure button.
5. In the configuration window, select the Database tab.
6. Clear the field labeled "Server name".
7. Close the configuration window and exit the ODBC Administrator.

This solution has been successfully tested with a standard Tools installation.

 

References

BUG:12-1NCHPDP - "SPECIFIED DATABASE FILE ALREADY IN USE" ERROR WHEN DOING CHECK IN OR CHECK OUT

Applies to:

Siebel System Software - Version: 8.0 [20405] to 8.1.1 SIA [21111] - Release: V8 to V8
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3317466373.

""""Checked for relevance on 20-Oct-2010""""

Symptoms

Hi Support:

I cannot install Siebel 8.0 at all, I have tried using the standard setup procedure and also with the FastTrack Wizard.

With both procedures, it ends with these errors on the logs when trying to log on for example to http://mysibelserver/ecommunications_enu


ss070403_1412.log (SWE log)

SisnapiLayerLog Error   1       0000002646120eb0:0      2007-04-03 18:26:32       1756: [SISNAPI] Async Thread: connection (0x2e09e80), error (1180682) while reading message
ObjMgrSessionLog        Error   1       0000002646120eb0:0      2007-04-03 18:26:32     Login failed for Login name : HI_USER
ProcessPluginState      ProcessPluginStateError 1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Open Session failed (0x75eb4d) after      0.0661 seconds.
ProcessPluginRequest    ProcessPluginRequestError       1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Failed to obtain a session ID. Error loading dictionary file diccache.dat.
ProcessPluginRequest    ProcessPluginRequestError       1       0000002646120eb0:0      2007-04-03 18:26:32       3052: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

Cause

You have installed Siebel version 8.0 but when trying to login to the application you received an error message:

Login failed for Login name : HI_USER
3052: [SWSE] Set Error Response (Session: Error: 07727949 Message: Error loading dictionary file diccache.dat.(SBL-DAT-60237))

We concluded that the object manager failed to open an anonymous session for user “HI_USER”. This user is not created by default when running the grantusr.sql script, and is also not available as an employee in the standard application.

Solution

The Installation Guide > Installing and Configuring the Siebel Web Server Extension > Configuring the SWSE > Creating the SWSE Logical Profile > Parameters for Creating the SWSE Logical Profile advises that the anonymous user should be created as an Employee:

"The Siebel user ID for a valid employee. Used to start the anonymous session from which the user is shown the login page for an employee application.”

There are two possible workarounds:

1) Temporarily use ‘sadmin’ as the anonymous user, and later modify the eapps.cfg manually

2) Install a separate machine with Windows XP; install the Dedicated Web Client; create the Employee under ‘Administration – User’ screen; and then continue with SWSE installation

I have created Change Request 12-1J5GID3 to make it clear in the Installation Guide that the user provided when configuring the SWSE Logical Profile should be created first in the application as an employee.

Applies to:

Siebel System Software - Version: 8.1 SIA [21039] - Release: V8

Information in this document applies to any platform.

Symptoms

Customer was upgrading from 7.8 to 8.1 and when they try to connect with Tools 8.1.1 to run Repository Merge the following errors appear in siebdev.log:
Error loading dictionary file diccache.dat (SBL-DAT-60237)
Error loading dictionary (SBL-DCK-00163)
You are not currently licensed to use Siebel Tools (SBL-DEV-00133)

Also, Additional Message: Repository 'Siebel Repository' does not exist in database.

Cause

The issue is caused by the incorrect Repository name set in the tools.cfg-
they had DockRepositoryName=Siebel Repository, where they have only "New Siebel Repository" in the database.

Solution

To resolve the issue, in tools.cfg change parameter DockRepositoryName to the name of the repository you have, in this case "New Siebel Repository.
Change request #12-1SW8MZP has been logged asking for this to be documented in the Upgrade Guide.

References

BUG:12-1SW8MZP - REPOSITORY 'SIEBEL REPOSITORY' DOES NOT EXIST IN DATABASE.

Applies to:

Siebel Sales - Version: 7.7 [18026] BETA to 8.1.1 [21112] - Release: V7 to V8

Information in this document applies to any platform.

Symptoms

User is encountering the following error when trying to run the encryptupg utility:

Cause

This behavior is most likely caused by the tableowner database userID not having a corresponding Siebel account and/or that account not having adequate responsibilities / positions.

The error messages are actually pretty self-explanatory:

The presence of the second message leads us to believe that the tableowner does not have a matching record in the OLTP's S_USER table. This is not uncommon since, by default, the tableowner is not created as a Siebel userID.

Solution

The most likely cause of the behavior you are seeing is that the user you are using to run the encryptupg.exe is the tableowner for your Siebel on-line transactional processing (OLTP) database. While that is actually a good way of running the encryptupg.exe utility (in Oracle it actually is required), there is an issue that the tableowner database account is not by default a Siebel application login. This is why you are seeing the SBL-DAT-00546 and SBL-DAT-00254 errors.

The solution for this is to create a Siebel login for the tableowner account (the default tableowner is SIEBEL). The easiest way to do this and get adequate permissions is to simply copy the SADMIN user.

1. Log into an employee facing, high interactivity Siebel application such as Sales or Call Center using an administrator ID such as SADMIN.

2. Navigate to Site Map > Administration - Users > Employees.

3. On the Employees screen do a query for the login SADMIN (or whatever your administrator user's login is).

4. Click the little Menu button on the list applet and select Copy Record.

5. Fill in the required fields making sure you use the tableowner (SIEBEL in a default implementation) as the login / userID.

6. Save the record.

After doing this, please retest the use of the encryptupg.exe utility.

Also, although not directly related to this behavior, I would like to proactively call your attention to Note 551663.1 on Metalink 3. This discusses a specific issue when using encryption with Oracle databases.

References

NOTE:551663.1 - Error loading dictionary file diccache.dat.(SBL-DAT-60237) when running KEYDBMGR

In this Document
  Symptoms
  Cause
  Solution
  References

---

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Symptoms

Statement of what the issue is
Using Siebel SIA 8.0.0.5 [20420] Universal Customer Master application with third party Trillium product for real-time data quality.

When attempting to match records with fields that contain a special character in them, for example, the apostrophe, ', the following error occurs:

ERROR
-----------------------
SBL-DAT-00354: The query could not be run because the criteria for field '' contained an invalid arithmetic expression. Please ensure that the search criteria is correctly formatted.

This error is often caused by a missing operator (e.g. = or <) or missing quotes. If you aren't sure what may have caused this please contact your systems administrator.

SBL-DAT-60236: Expression does not match any Siebel query language grammar rules.

STEPS
-----------------------
By following these steps the issue can be reproduced:
1. Set up the Universal Connector for data quality matching and set client/object manager to use the appropriate type
2. Set the real-time data matching settings in Administration - Data Quality > Data Quality Settings:
3. Amend the Account Token Expression and Account Query Expression to allow you to capture a suitable number of characters from the address
4. Logout and in again for changes to take effect
5. Enter two accounts e.g. Test Account with site 1 and Test Account with site 2
6. After the second account has been saved, the deduplication popup should show the first as a match
7. Check S_DQ_ORG_KEY table to make sure that Universal Connector is being used - there should be  two records with KEY_VALUE = _____T_____
8. Now add an address to one of them and save it, e.g.
      Street Address = A Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
9. Check the S_DQ_ORG_KEY table. The key should now be '11111TA PLA'
10. Now add an address with an apostrophe (') to the other account and save it, e.g.
      Street Address = A'Place in the Sun
      City = Redwood Shores
      State = CA
      Zip Code = 11111
      Country = USA
11. Receive the following error message:

[1] Invalid search specification '[DQ System Id] = '1-AIZ3' AND [Parent Id] LIKE '1-CF1T' AND [Key Value] NOT LIKE '11111TA'PLA''.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)

[2] Expression does not match any Siebel query language grammar rules. Unexpected token 'PLA' found at or near location 90.(SBL-DAT-60236)

EXPECTED BEHAVIOR
-----------------------
The customer expects that Siebel can handle special characters when performing data matching with third party products via the Universal Connector.

Cause

The cause was determined to be a new product defect.

The following two change requests were logged for this issue:

Bug 12-1V418BZ - SBL-DAT-60236 error message when using Universal Connector with an apostrophe
Bug 12-1V9U44R - UCM dedup token generation expression is causing BDM workflow to fail in 'CDM Match' step

The first (Bug 12-1V418BZ) addresses the real-time user interface scenario and the second (Bug 12-1V9U44R) addresses the integration scenario. The cause is that neither the search specification for the 'Key' business component (e.g. Account Key, Contact Key, Prospect Key) nor the 'Dedup Token' field in the Account, Contact or List Mgmt Prospective Contact business components can handle special characters.

Solution

The problem has been fixed in the following fix packs:

- 8.0.0.9 fix pack and higher

Alternatively, if you are unable to apply 8.0.0.9 fix pack or higher, the following quick fixes were built although they may not be available for all supported languages/operating systems:

- 8.0.0.7 QF0745
- 8.0.0.2 QF02C6/8.0.0.2 QF02D2 (both are needed)

References

BUG:12-1V418BZ - SBL-DAT-60236 ERROR MESSAGE WHEN USING UNIVERSAL CONNECTOR WITH AN APOSTROPHE
BUG:12-1V9U44R - UCM DEDUP TOKEN GENERATION EXPRESSION IS CAUSING BDM WORKFLOW TO FAIL IN 'CDM MATCH' STEP
NOTE:476946.1 - How Can You Implement a Replace String Function in eScript?

Applies to:

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

Symptoms

Whilst querying with an apostrophe in the user interface in the Name field the following errors were seen:

The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

Missing quotes around the search criteria or unnecessary punctuation will often cause an error.(SBL-DAT-00403).

Normally if querying for Jack's for example, one would expect to receive an error. The normal way to accommodate such queries including special characters is to surround the query within speech marks, for example "Jack's". However this did not work either.

Cause

The issue related to some custom eScript that was being used to ensure that users populated certain fields in the user interface.

An example exhibiting the same behaviour is shown below. This was used on the Account business component.

function BusComp_PreQuery ()
{
  var sName = GetSearchSpec("Name");
}

Through testing, it was found that the only special character that would not work in the query was the apostrophe. Other characters such as the following worked fine:

; , . @ # \ | + - = [ ] & *

The same behaviour was also seen in 7.7.2.6, so it is likely widespread across the application versions.

Bug 12-1LG178H: "GetSearchSpec on field in BusComp_PreQuery Event with UI query including apostrophe causes error" was raised as a product defect to address this problem for a future product release.

Solution

The following workarounds were suggested to the customer:

1. Instead of querying for "Jack's", try querying for "'Jack''s'". e.g. double quote, single quote, Jack, single quote, single quote, s, single quote, double quote.

2. Take the GetSearchSpec method off the field and utilise it on alternative fields.

3. Use a Try-Catch-Finally statement to catch the error. More details can be found here:
- Siebel eScript Language Reference > Siebel eScript Language Overview > Siebel eScript Statements > try Statement

4. Alternatively, use the GetSearchExpr() function and do string manipulation to check that relevant fields are populated. More details of this function can be found here:
- Siebel Object Interfaces Reference > Interfaces Reference > Business Component Methods > GetSearchExpr Method

The customer decided to use an alternative instead by basically reconstructing the string and replacing the ' with an * on the PreQuery event.

Keywords: SBL-DAT-60236, SBL-DAT-00354, SBL-DAT-00501, SBL-DAT-00403

Applies to:

Siebel CTI - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

After upgrading to Gplus adapter to 7.5.000.51 the customer no longer received screen pops for inbound calls.

Even though all the EventHandler FilterSpec criteria were being met in the Scomm log file we would see the following:

DPATEL_37748770[07/09/2010 15:10:54:922]:DEBUG:Found no matching EventHandler

Cause

=== ODM Cause Determination ===

In the Scomm log file when the configuration was loaded we could see the following:

SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildPreProcessData end
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:BuildAgentCfg_New begin
SADMIN_10485773[07/19/2010 12:46:07:968]:DEBUG:GetAgentCfg end

"BuildAgentCfg_New begin" but there is no "BuildAgentCfg_New end".

Also, in the OM log file we could see the following error message:

ObjMgrQueryLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '{' found at or near location 59.

ObjMgrLog Warning 2 000000024c3f0d48:0 2010-07-15 20:56:11 (query.cpp (2634)) SBL-DAT-00501: Invalid search specification 'NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}'.

In the .def file we had the following Command defined:

[Command:MakeCallToPhone]
Description = "Make Call to "{@Phone}""
DeviceCommand = "MakeCall"
FilterSpec = "NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}"
Hidden = "TRUE"
OnEditControl = "TRUE"
Profile = "Gplus Voice"
CmdData = "MakeCallToPhone"

If the same change is made in a standard environment then the same behavior is seen.

The issue is caused by the {} brackets around the @Phone:PhoneTypeLookup in the Command FilterSpec

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

This behavior was deemed to be a product defect and CR# 12-1Z1L7WJ was raised for this matter.

Solution

=== ODM Solution / Action Plan ===

To solve the issue in the command MakeCallToPhone change the FilterSpec as follows:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and {@Phone:PhoneTypeLookup}

It should be something like:

NOT [$GetCommandStatus(IsInteractionView)] = 'Enabled' and [@Phone:PhoneTypeLookup] IS NOT NULL

Applies to:

Siebel Tools - Version: 8.0.0.1 [20408] to 8.0.0.3 [20416] - Release: V8 to V8
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] NLD Com/Med
Database: Oracle 10.2.0.3
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Red Hat Linux 4.0

This document was previously published as Siebel SR 38-3455974081.

Symptoms

SBL-DAT-60236

We encountered a problem when setting all LOV entries for the COUNTRY LOV to Multilingual.
The values that contain a single quote in the displayvalue or in the Language Independent Code, can not be set to Multilingual. When you try to change anything to these records they give an error.

We now removed all single quotes from the COUNTRY LOV, so we could set them to Multilingual.

Cote D'ivoire
Korea, Democratic People's Rep
Lao People's Democratic Republ

Bahama's (NLD)

Please let us know if this is the expected behaviour.
Is there a workaround to be able to use single quote's in multilingual LOV's.

Cause

Product defect - change request 12-1K5DYEJ

Solution

The customer noticed that in Siebel 8 a validation error meesage occurs when trying to save a List of Values (LOV) record that contains an apostrophe (single quote) character in either the Display Value or Language Independent Code field.

The error encountered on trying to saving the LOV record in the LOV administration screen was:

Invalid search specification '[Type] = 'AAG_ACCOUNT_TYPE' AND [Language] = 'ENU' AND (([Name] = 'Banking'' AND [Value] <> 'Banking' OR ([Value] = 'Banking' AND [Name] <> 'Banking'')) AND [Id] <> 'OVF-1L699"

Expression does not match any Siebel query language grammar rules. Unexpected token 'Banking' found at or near location 93. SBL-DAT-60236

This error occurs due to the second quote character appearing in the search specification expression that was generated by Siebel 8 as part of new validation logic. For example [Name] = 'Banking''

In previous versions of Siebel it was possible to enter and store LOV records that including the single quote character.

Issue was addressed by change request 12-1K5DYEJ which was fixed in Siebel 8.0.0.3 Fix Pack and is not present in Siebel 8.1.

The only workaround is to not enter single quote characters in to either the Display Value or LIC field of LOV records.

Keywords: WriteRecord; Write; Record; LOV; List; Values; Display; Value; Language; Independent; Code; Validate; search; spec; specification; quote; apostrophe.

Applies to:

Siebel Tools - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Goal

When doing a full compile, I end up with an SRF that is smaller than it should be and is not usable by the server or client. I am connected directly to the server database. This problem is intermittent - sometimes it produces a usable SRF, sometimes it doesn't - with no changes to anything.
This intermittent behavior is happening on a Windows 2003 PC.

Solution

This incorrect behavior was happening for one Siebel Tools client on a windows 2003 box.

Siebel client side logging was enabled for the Siebel Tools client using the Siebel_Log_Events environment variable.  The client side logging for Siebel Tools generated a siebdev.log file with the following types of errors.

ObjMgrQueryLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (13952)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024c400300:0 2010-07-16 13:06:32 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters.

After reviewing the Siebel Tools installation and environment, it was determined that the operating system of windows 2003 is not a supported operating system for the Siebel Developer Client per the
Siebel System Requirements and Supported Platforms documentation.

See the Siebel System Requirements and Supported Platforms > Client Environment Requirements >
Requirements for Employee Applications
Software Requirements for the Siebel Developer Web Client

But, it is not very clear that Employee Applications would include Siebel Tools.

Therefore a documentation defect was raised to address this unclear documentation.

Siebel Tools Product Management confirmed that the following operating systems are the supported platform for Tools/Dclient as per Siebel System Requirements and Supported Platforms documentation.

WinXP

Win7

Vista

Win2000

Note that Win2003 and Win2008 are not supported clients for Tools/Dedicated client.

Change Request CR 12-1Z9S19D is a documentation defect noting that the
System Required and Supported Platforms should be much clearer for Siebel Tools

SUMMARY
The system platforms discusses the environment requirements for Employee applications.
But it is not obvious that Siebel Tools is considered an Employee Application like a Siebel thin client running Siebel Call Center.

Siebel Tools is a considered a different application than a Siebel client application.

DESIRED DOCUMENTATION
The documentation should have a separate listing for Siebel Tools clients.

Siebel
System Requirements and Supported Platforms > Client Environment
Requirements >

Requirements for Employee Applications

Add a separate section for Siebel Tools.

Siebel System Requirements and Supported Platforms > Client
Environment Requirements >

Requirements for Siebel Tools

The recommendation was given to use a different PC with a supported platform for the Siebel Tools client.

Oracle Siebel Support

References

BUG:12-1Z9S19D - SYSTEM REQ SUPPORTED PLATFORMS SHOULD BE MUCH CLEARER FOR SIEBEL TOOLS

Applies to:

Siebel Reports - Version: 8.1.1 [21112] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Siebel Tools displays an error when generating Actuate Reports that include fields associated with Multivalue Links that have brackets in their names. The following error message appears:

The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will ofthen cause an error." "Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21" (see screen shots).

ObjMgrQueryLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (14029)) SBL-DAT-60236: Expression does not match any Siebel query language grammar rules. Unexpected token '(' found at or near location 21.

ObjMgrLog Warning 2 000000024b85100c:0 2010-02-25 09:50:24 (query.cpp (456)) SBL-DAT-00403: The query could not be run because there is an invalid character in the field 'Name'. Please ensure that the value in the field is formatted correctly with only valid characters. Missing quotes around the search criteria or unnecessary punctuation will often cause an error.

STEPS TO REPRODUCE THE ISSUE

1. Install Siebel CRM 8.1.1.2 Fix Pack on Siebel Tools.

2. Launch Siebel Tools.

3. Create a Report object that contains a 'Sub Report' which has fields coming from a Multi Value Link. Make sure that the 'Name' property of the Multi Value Link object under the Business Component  contains parenthesis.

4. Try to 'Generate Actuate Report' using Tools menu > Utilities > Generate Actuate Report option.The generation of ROL fails with above mentioned error.

Cause

The issue has been caused due to the following:

1. The parenthesis character in the 'Name' property of a Multi Value Link are being parsed during the generation of Actuate ROL file.

2. Siebel's internal code fails to generate the ROL when the '(' character is found in the 'Name' property.

Solution

A Product Defect CR# 12-1XLAKV5 (SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD) has been logged to address this issue in a future Siebel release.

WORKAROUND

The issue can be resolved by NOT using parenthesis in 'Name' property. This way it will not impact the ROL Generation.

References

BUG:12-1XLAKV5 - SIEBEL TOOLS - GENERATE ACTUATE ROL FAILS WHEN REPORT FIELD USES A MULTI-VALUE FIELD

Applies to:

Siebel Tools
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] ESN Fin Svcs
Database: Microsoft SQL Server 2005
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: Microsoft Windows 2003 Server SP2

This document was previously published as Siebel SR 38-3461315051.
""""Checked for relevance on 03-Mar-2010""""

Symptoms

We are adjusting ours LOV after the Upgrade and we are founding a problem when activating or changing LOVs with ' in Display Value, Languange Idependent Code, etc.

Example: LOV TYpe: FINCORP_DEAL_LOAN_TYPE
for value: I don't know

Try to inactivate or activate.

I get this error:

[1] Invalid search specification '[Type] = 'FINCORP_DEAL_LOAN_TYPE' AND [Language] = 'ENU' AND (([Name] = 'I don't know' AND
[Value] <> 'I don't know') OR ([Value] = 'I don't know' AND [Name] <> 'I don't know')) AND [Id] <> '0VF-RG2D''.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00501)
[2] Expression does not match any Siebel query language grammar rules. Unexpected token 't' found at or near location
79.(SBL-DAT-60236)

Cause

This behavior was due to known bug

Solution

Message 1

This is a known issue please see the following item on supportweb:

Service Request #: 38-3455974081
Version: 8.0 [20405] NLD Com/Med
Abstract: Setting LOV's to Multilingual

Change request 12-1L7O0S1 has been raised to address this issue.

Message 2

The workaround suggested in the referenced service request really only applied to creating new LOV's. At this time I do not think it would be appropriate to remove all the single quotes from existing LOV records, as for referential integrity this would mean updating all existing records in the database with the new LOV values. And as you mention it would also mean changing an configuration that includes the values.

A colleague has advised that a possible workaround could be to modify the class property of the List Of Values buscomp from CSSBCListOfValues to CSSBCBase (as it is in version 7.8). I have tested this and it does seem to work but I cannot advise what could be the impact on other areas of the application. Therefore maybe as a temporary workaround you should build a special SRF where the class change had been applied and only use it for LOV admin and then leave the orginal SRF unchanged.

***Update***

The CR: 12-1L7O0S1 and other CRs were opened to have this behaviour addressed.
The parent CR: 12-1K5DYEJ “Unable to activate LOV's in Data Administration with apostrophe in the Language-Independent Code” was addressed in the 8.0.0.3 Fix Pack

References

BUG:12-1K5DYEJ - UNABLE TO ACTIVATE LOV'S IN DATA ADMINISTRATION WITH APOSTROPHE IN THE LANGUAGE-INDEPENDENT CODE

Applies to:

Siebel Tools

Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405] Fin Svcs
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP2
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-3485132211.

Symptoms

SBL-EXL-00145, SBL-DAT-60236

Hi,

We seem to be having issues with some of our PDQs on Service Request List View.
FYI, we have 5 applet toggles on Service Request Detail Applet meaning to say that the bottom form applet toggles based on the Service Request Type that is chosen.
We have couple of PDQs on the Service Request List View, one that returns no records and the other that returns all SRs.
But when we tend to choose any of the PDQs, we end up getting a Microsoft Internet Explorer Error throwing us out of the application.
Do note that we tried to spool but we could not get anything in the spool.
An example of the PDQ that we are trying to execute is as follows:
'Service Request'.Search = "[Id] = ""X""" 'Service Request'.Sort = ""
This example is the one that is expected to returns no records.

Please help in resolving the issue.

Thanks,
Raghu
Emailc
Mob#+61-40-750-5222

Cause

This incorrect behavior is a product defect.

Solution

Message 1

For the benefit of other users.

The behavior that the customer experienced with the toggle applets was reproduced in version 8.x of the Siebel application. Change Request 12-1LXMIR2 has been logged for this behavior so that the product defect gets addressed in future versions of the Siebel application.

Note that product defect 12-1LXMIR2 has been addressed with Siebel 8.0.0.3.

Thank you,
Siebel Technical Support

Applies to:

Siebel CRM - Version: 8.1 [21039] and later   [Release: V8 and later ]
Siebel CRM - Version: 8.1 SIA [21039] and later    [Release: V8 and later]
Siebel CRM - Version: 8.0 SIA [20405] and later    [Release: V8 and later]
Siebel CRM - Version: 8.0 [20405] and later    [Release: V8 and later]
Information in this document applies to any platform.

Symptoms

When task transaction has been disabled, setting DeferWrite=True for Siebel Operation Insert Step causes the task to give the following errors:

SBL-BPR-00187, SBL-BPR-00100, SBL-DAT-60217

The specific error message is:

[1] Error updating business component at step '<step name>'. (SBL-BPR-00187)
[2] This error is returned when the workflow/task is executing the Siebel Operation business service.(SBL-BPR-00100)
[3] Can't write data without validation.(SBL-DAT-60217)

Note that <step name> shown above is a placeholder for the step where the error occurs.

These errors occur in the task when the Siebel Operation step with DeferWrite=True in the task is reached.

Cause

DeferWrite =True is not supported when task transaction has been disabled.

When task transaction has been disabled, DeferWrite=True should not be used.

Note that there are two cases for this, as task transaction can be disabled in two ways:

1. Task Transaction disabled for the entire Task.
   
   When task transaction has been disabled at task level, by setting the Transactional task property to FALSE, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps in that specific task.
   
   
2. Task Transaction disabled at the Business Component Level.
   
   When task transaction has been disabled at Business Component level, by setting Immediate Commit In Task user property to TRUE for a specific Business Component, then DeferWrite=True should NOT be used in any Siebel Operation INSERT steps which are based on that specific Business Component in any Task.

A new documentation change request Bug 12-1X47EZR  has been submitted to request that this information be added to bookshelf.

Disabling Task Transaction should be done only when needed and thoroughly tested, as noted in the Siebel Bookshelf, Business Process Framework: Task UI Guide.

Task transaction is a mechanism that allows you to keep data associated with a task instance separate from the Siebel Business Component tables until the task data is explicitly committed to the database. The default behavior for tasks is to have task transaction enabled. Disabling task transaction can result in unpredictable behavior and must be thoroughly tested before use in production.

Solution

When task transaction has been disabled, then DeferWrite=True should not be used. 

Workaround:

When Task Transaction needs to be disabled, DeferWrite can be set to False on the Siebel Operation INSERT step which is affected by this. Please reference the two cases described above in the Cause section of this document.

When DeferWrite = False, then all of the required fields for that Business Component must be provided some values inside the Siebel Operation step. These values can then be updated by the user in the subsequent Task Views. As mentioned above, this will need to be thoroughly tested.

References

BUG:12-1X47EZR - WHEN TASK TRANSACTIONS ARE DISABLED, SIEBEL OPERATION INSERT STEPS SHOULD NOT USE DEFERWRITE = TRUE

Applies to:

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

Symptoms

Customer has set Task Transaction property False and also Derfer Write property - False. Customer trying to pause the task by the pause button - getting following error.
Customer getting error in task that Can't write data without validation.(SBL-DAT-60217)

Cause

These errors occur in the task when the Siebel Operation step with DeferWrite=True in the task is reached.
But it was set to False.
Steps -

Created Task based in Action BO

Start -> Siebel Operation --> view -->End

Siebel Operation with Defer Write - false and Task - Transaction Property - False

If you modify the some field on applet and pause the task by pause button - giving error - Can't write data without validation

If you hit out side also - it is giving error - Can't write data without validation

This is a Product Defect.

Solution

This is a product Defect. CR #12-1Z6VWWC has been raised to address this issue.
Code fix requires a low level change which may require lot to be compiled. This is going to fix in next fix pack. This can not be provide as Quick fix in current version.
 

Please refer following doc id for the same - Support Recommended    Task Based UI Task With Transaction Disabled & Siebel Operation INSERT Step With DeferWrite=TRUE Gives
SBL-BPR-00187, SBL-BPR-00100, SBL-DAT-60217 Errors (Doc ID 1066712.1)

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60227: Invalid user name %1 is specified when unloading user attributes.

Scope

This document is informational and intended for any user.

SBL-DAT-60227: Invalid user name %1 is specified when unloading user attributes.

Explanation

The error occurs when User Profile Service is invoked to unload user attributes for a specific user who is not currently loaded.

Corrective Action

You can first invoke User Profile Service to find out the current loaded users and then choose one to unload.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60226: Service %1 did not finish the dedicated block.

Scope

This document is informational and intended for any user.

SBL-DAT-60226: Service %1 did not finish the dedicated block.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. A dedicated block demarcates the boundary within which a stateful service can be executed within a server-managed session.

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60225: Service %1 is not allowed to finish dedicated block started by another service.

Scope

This document is informational and intended for any user.

SBL-DAT-60225: Service %1 is not allowed to finish dedicated block started by another service.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. A dedicated block demarcates the boundary within which a stateful service can be executed within a server managed session.

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60232: Session %1 is Stateless but attempts to use cached business service %2 which has state (session type is Stateful or ServerDetermine).

Scope

This document is informational and intended for any user.

SBL-DAT-60232: Session %1 is Stateless but attempts to use cached business service %2 which has state (session type is Stateful or ServerDetermine).

Explanation

For definitions of session types specified in SOAP headers, see the chapter on Web services in Integration Platform Technologies: Siebel EAI, on Siebel Bookshelf. Here, the Client session is marked as Stateless. However, a Web service running in the sessi

Corrective Action

Change the session type to Stateful or ServerDetermine. If the Client session type is Stateless, only business services marked as Stateless can be invoked.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60231: Too many services have been invoked in session %1. Cannot persist all services to the allocated space.

Scope

This document is informational and intended for any user.

SBL-DAT-60231: Too many services have been invoked in session %1. Cannot persist all services to the allocated space.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. Too many services have been invoked in this session. Cannot persist all services to the allocated space.

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, should collect all component log files, tar all files together and submit this information along with a description of the exact steps that l

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60230: The model is currently running session %1. Cannot get new session ID on the model.

Scope

This document is informational and intended for any user.

SBL-DAT-60230: The model is currently running session %1. Cannot get new session ID on the model.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. The state for the current session needs to be persisted and released before GetNewSessionId can execute.

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60229: Cannot perform session restore on the model currently running session %1.

Scope

This document is informational and intended for any user.

SBL-DAT-60229: Cannot perform session restore on the model currently running session %1.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. Possible internal causes include: model pooling is not enabled; the current session is dedicated; the current session is no

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-60228: Cannot persist session %1.

Scope

This document is informational and intended for any user.

SBL-DAT-60228: Cannot persist session %1.

Explanation

The error message is intended for internal software integrity checking only and should not occur under normal operating conditions. Possible causes of the internal error include: Model pooling not enabled; No valid session ID; The current session is dedic

Corrective Action

The system administrator should collect assert, prefer, and .fdr log files from the Siebel Server /bin directory, collect all component log files, and tar all files together. Submit this data to Siebel Technical Support in a service request, with a descri

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.

Applies to:

Siebel Tools - Version: 8.1.1 [21112] - Release: V8

Information in this document applies to any platform.

Symptoms

When querying for certin audit trail records, application is throwing error.

-06-23 16:36:25 (sqllog.cpp (774)) SBL-DAT-60176: Unexpected end of stream '2*C14*NAME2*N161*AEG Mktg-Technical Writing - TUV Certification press release2*O132*AEG Mktg-Technical Writing - -' at position 115.
Error type2
=======
ObjMgrLog Error 1 0000ab6b4a11707b:0 2009-06-24 10:33:37 (sqllog.cpp (671)) SBL-DAT-60173: A number at position 3*C164*NAME11*PREV_ACT_ID16*TODO_PLAN_END_DT7*OPTY_ID13*APPT_START_DT7*TODO_CD6*X_AREA11*TODO_DUE_DT12*TARGET_OU_ID13*COMMENTS_LONG10*X_SUB_AREA8*LOC_DESC11*EVT_STAT_CD6*SRC_ID18*TODO_PLAN_START_DT11*OWNER_LOGIN3*O1630*NA-TEST WORKSHOP-Natick MA-2000*19*2008-11-21 16:00:000*19*2008-12-01 05:00:0015*Stage Execution18*Natick - Marketing0*0*0*0*0* 11*Not Started8*1-8H52OH19*2008-11-21 15:00:008*CSARKEES3*N160*0*0*0*0*0*0*0*0*0*0*0*0*0*0*0* is expected in the log stream '346'.

Customer already know the issue is due to corrupted data. Now they have a BS to correct the data. However this BS is not working because of the bad data- not moving to the next record.

Cause

because of the error, NextRecord not moving to the next record

Solution

Regarding scripting, igoring the bad record and continuing with the NextRecord, you could try using Try…Catch block inside the while loop.

while(isAuditRecord) {
// do something
try {
isAuditRecord = NextRecord();
}
catch(e) {
// skip broken record:
isAuditRecord = NextRecord();
}
}

Regarding information on the errors, no further information could be found out, Documentation Defect 12-1U0AX8T was created.

 

Thank you

References

BUG:12-1U0AX8T - QUERYING CERTAIN 'AUDIT TRAIL ITEMS' THROWING ERROR

Applies to:

Siebel Tools - Version: 8.0 SIA [20405] to 8.1.1 [21112] - Release: V8 to V8
Information in this document applies to any platform.

Symptoms

On accessing Audit Trail records or navigating through Audit Trail records receiving error: SBL-DAT-60171: End of the log stream is reached.

Following error  has been found in the log file:
ObjMgrLog Error 1 000000064a136020:0 2009-05-20 10:17:49 (sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.

It is occurring when the Method GetAuditTrail of the Business Service CIS General Tools  which is called via a shell script is accessed.

Cause

Bug 12-1NSKPEZ (Audit Trail Error in log fiels in 8.0) has been raised to report the issue. It seems related to database since it is coming from "sqllog.cpp".

Solution

The Change Request is still under investigation. If the error does not harm or stop any functionality, the error can be ignored as per Change Request comments. 

Applies to:

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

Symptoms

OM logs show following errors prior to crash:

(sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.ObjMgrLog Error 1
(sqllog.cpp (671)) SBL-DAT-60171: End of the log stream is reached.DBCLog DBCLogError 1

Oracle RAC is failing over...DBCLog DBCLogError 1
Failover type is SELECTDBCLog DBCLogError 1
Oracle RAC failover ended successfullyDBCLog DBCLogError 1
Oracle RAC is failing over...DBCLog DBCLogError 1
Failover type is SELECTDBCLog DBCLogError 1
Oracle RAC failover ended successfully


- crash.txt shows crash on Oracle client dlls when OM task tries to re login on the killed DB session.

- CALL STACK -
kernel32 RaiseException()
orageneric11 slcra()
orageneric11 skgdbgcra()
orageneric11 kpeDbgCrash()
OraClient11 xaolog()
OraClient11 kpufhndl()
OraClient11 OCIHandleFree()
OCI OCIHandleFree()
sscdo90 CSSOraSqlCursor::~CSSOraSqlCursor()
sscdo90 SSASqlObjLogon() +0x1c5
sscfdm CSSLockSqlCursor::~CSSLockSqlCursor()
sscfdm CSSDbConn::BeginTransaction()
sscfdm CSSLockSqlCursor::Delete()
sscfdm CSSDbConn::CacheSqlCursor()
sscfdm CSSDbConn::CachePendingCursors()
sscfdm CSSLockDbConn::Unlock()
sscfdm CSSDbLock::~CSSDbLock()
sscfdm CSSSqlCursor::NextRecord()
sscfdm CSSSqlObj::AddListRow()
sscfdm CSSSqlObj::NextRecord()
sscfom CSSBusComp::SqlNextRecord()
sscfom CSSBusComp::Home()
SSCASWBC CSSSWEFrame::ExecuteQuery(


- FDR shows the the thread crashes when trying to do "Sql Cursor Destruction"


FdrSub_FDR_CRASH ** CRASHING THREAD **
FdrSub_FDR_CRASH ** CRASHING THREAD **
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_DBC_CURSOR_DSTR Sql Cursor Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_OBJMGR_DATA_LST_DSTR Data List Destruction
FdrSub_FDR_CRASH ** CRASHING THREAD **

Changes

Customer developed new Script that kills session for long running SQL:

select 'REM SID: '||a.sid||' SERIAL#: '||a.serial#||' SQL ID: '||b.sql_id||chr(10)||' /*+ '||sql_fulltext||' */' from v\$session a, v\$sql b where b.address = a.sql_add
ress and program = 'siebmtshmw.exe' and command = 3 and status = 'ACTIVE' and last_call_et >= 300 and username = 'SADMIN';

select 'alter system kill session '||''''||sid||','||serial#||''''||';' from v\$session where program = 'siebmtshmw.exe' and command = 3 and status = 'ACTIVE' and last_c
all_et >= 300 and username = 'SADMIN';

Cause

When Kill SQL script runs for a specific DB session the OM task seems to treat this as RAC failure and OM tries to relogin and continue SQL execution when the crash occurs on the Oracle client dlls.

Solution

Hence suggesting turning off Kill SQL script.
Monitor the OM logs for next two hours and confirm if there are still these "RAC failure..." errors reported.

This resolved the RAC failure errors and OM crashes.

Applies to:

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

Symptoms

Created a new calculated field for audit trail applets and when querying on this field an error(SBL-DAT-00471) is returned.

Cause

Calculated value used: LookupValue('CT_AUDIT_CAPTION', [Field]).
This query fails in Audit Trail context because Audit Trail Item 2 is a VBC.

Solution

As a workaround, display the translated and the original field names side by side so when the users want to query for a specific field they can use the original field name for this query.

The following script can be used to stop querying on certain fields:


function BusComp_Query ()
{
/*------------
Description: Added to stop querying on certain field, user props only stop wildcard queries
------------*/
try
{
var sSearchQuery = this.GetSearchExpr();

if(sSearchQuery.indexOf("CT Field Caption") != "-1")
{
TheApplication().RaiseErrorText("Querying on 'Field' is currently not possible. Please query on 'BC Field' which is available from Columns Displayed.");

}
}
catch(e)
{
throw e;

}
}

References

BUG:12-1NSKPEZ - AUDIT TRAIL ERROR IN LOG FIELS IN 8.0
NOTE:985883.1 - Navigating through Audit Trail Records throw Error SBL-DAT-60171 (End of the log stream is reached)
NOTE:477101.1 - Can you translate the field names displayed in an Audit Trail Item list applet?
NOTE:728852.1 - Error querying the Id field from the 'Audit Trail Item 2' BC
NOTE:820735.1 - Property "Disable Search" on Business Component Field
NOTE:780618.1 - Disable Search User Prop returns error msg with BusComp Field name and not U

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.0

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-51002: Your password will expire in less than %1 days. Please change your password.

Scope

This document is informational and intended for any user.

SBL-DAT-51002: Your password will expire in less than %1 days. Please change your password.

Explanation

Your password will expire soon.

Corrective Action

Please change your password.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00938: The language code %1 is not valid. Please check and try again.

Scope

This document is informational and intended for any user.

SBL-DAT-00938: The language code %1 is not valid. Please check and try again.

Explanation

This error occurs when users try to use an unsupported language.

Corrective Action

Change language code to a valid code (e.g. ENU, JPN etc.). The list of supported languages can be found in Siebel Administration - Data > Languages view.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00940: Login failed as the user is inactive.

Scope

This document is informational and intended for any user.

SBL-DAT-00940: Login failed as the user is inactive.

Explanation

This error occurs when an inactive user tries to login.

Corrective Action

Grant the user Active status before allowing to login.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00939: The time zone %1 is not valid. Please check and try again.

Scope

This document is informational and intended for any user.

SBL-DAT-00939: The time zone %1 is not valid. Please check and try again.

Explanation

This error occurs when users try to use an unsupported time zone.

Corrective Action

Change time zone to a valid time zone (e.g. (GMT-07:00) Arizona)). The list of supported time zones can be found in Siebel Administration - Data > Time Zone Administration view.

Applies to:

Error Message Area:Data Manager - DAT
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00937: The currency code %1 is not valid. Please check and try again.

Scope

This document is informational and intended for any user.

SBL-DAT-00937: The currency code %1 is not valid. Please check and try again.

Explanation

This error occurs when users try to use an unsupported currency.

Corrective Action

Change the currency code to a valid code (e.g. USD). The list of supported currencies can be found in the view Administration - Data > Currencies.