SBL-DAT-00522: A Siebel local database error has occurred. Possibly the database name is invalid.

Applies to:

Siebel Remote - Version: 8.0 [20405] - Release: V8

Information in this document applies to any platform.

Symptoms

In versions 8.x, when using TrickleSync feature or siebsync.exe (standalone command line synchronization) it was observed that Remote synch sessions started by these programs if local SQL Anywhere database is stopped (i.e. by having AutoStopDB=TRUE in application CFG file) will end with following errors in syncthrd_*.log:

DataBase Connection Object was created at 2259b70; DB User: 'TEST1'
(wccon.cpp (2030)) SBL-DAT-00522: A Siebel local database error has occurred. Possibly the database name is invalid.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

Security DB user connect to DB C:\Siebel8\Client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c15p -ch25p with username=TEST1 returns err 7668234 and connection 2259b70.
Security DB user delete DB connectoin 2259b70
DataBase Connection was deleted at 2259b70
(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: A Siebel local database error has occurred. Possibly the database name is invalid.
Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DAT-00522)
Specified database file already in use.

The same sessions would simply run fine if the Mobile Client application is running as well or if Local dbf is simply kept open when TrickleSync or siebsync.exe sessions would start.

Cause

Message "Specified database file already in use" rather seems to point to cases when SQL Anywhere database is already open, but under a different SQL Anywhere "Server Name" parameter.

SQL Anywhere "Server Name" value is generally displayed in the tip box (when mouse is placed over SQL Anywhere systray icon) and should match the string that is defined in ODBC Administration program for "SEAW Local Db default instance" > Database tab > "Server Name" (i.e. "C__Siebel8_Client_local_sse_data_dbf")

Could be observed that when error occurs, this server name is no longer the full string that is defined for ODBC - "C__Siebel8_Client_local_sse_data_dbf" - but only "sse_data" (default value - database name, when nothing else specified as "server name").
[For more details on this parameter type in a cmd prompt (after navigating to client BIN location): "dbeng9.exe -?" or refer to relevant third party SQL Anywhere documentation.]

This unexpected behaviour was reported as Product Defect Bug 12-1RW5VBT .

Solution

Workarounds that can be applied for this case until a permanent fix will be delivered are:

1- setting AutoStopDB = FALSE in application CFG, so database is no longer closed between synchronization sessions.

2- alternately ensure following settings are changed:

a) in the general [Siebel] section of your CFG, "DataSource = Local" is set;
b) add the "/d Local" switch to the command line call of siebsync.exe;
c) add the Server Name value explicitly into ConnectString parameter options in the same CFG [Local] section - i.e.:

ConnectString = C:\Siebel8\Client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c15p -ch25p -n C__Siebel8_Client_local_sse_data_dbf

References

BUG:12-1RW5VBT - SIEBSYNC THROWING ERRORS WHEN USERS TRY TO SYNC

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 5.8

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

Symptoms

SBL-DBC-00105, SBL-DBC-00108, SBL-DAT-00522

Over the last month we have received reports of some 80 incidents of Siebel unexpectedly shutting down on some of our remote users' PenTablets (Tablet PC).

Usually the user is presented with a bland error message and is asked if they wish to send an error report to Microsoft. If the user declines, shuts down their machine and restarts it again they are normally able to continue working. Occasionally they have trouble either shutting down or getting back into Siebel again.

I have attached the spooled SQL and the resultant Siebel.Log file that was being created at the time...

thanks

Cause

Microsoft Windows XP Tablet PC Edition Version 2002 Service Pack 1” Operating System is not supported for v7.7.1

Solution

Message 1

Pen Tablet/Tablet PC’s users were experiencing some errors.

The reason was that “Microsoft Windows XP Tablet PC Edition Version 2002 Service Pack 1” Operating System is not supported for customer currently release Siebel 7.7.1.

“System Requirements and Supported Platforms” document states that only “Microsoft Windows XP Tablet PC Edition 2005” is supported for 7.7.2.1 version.

To solve this issue, it would be necessary to upgrade to 7.7.2.1 (or later).

Note that the Operating System supported is “Microsoft Windows XP Tablet PC Edition 2005” and that SP2 is included in Microsoft Windows XP Tablet PC Edition 2005. Microsoft makes service packs available at: http://www.microsoft.com/windowsxp/sp2/default.mspx

For more information please refer the below Alert
- Siebel Support for the Windows XP Tablet PC Platform (Doc ID 477063.1)

Applies to:

Siebel Tools - Version: 7.5.3.15 SIA [16279] and later   [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.15 [16279] Fin Svcs
Database: Oracle 9.2.0.4
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

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

Checked for Relevance on 04-23-2010

Symptoms

SBL-DAT-00522

Hi,

We have a requirement to retrieve the “Team-Support Hierarchy” which consists of all the position ids whose parent position id is same as the parent position id of the user’s active position. For instance, the user’s active position id is “Position Id1”. For this active position, Parent Position Id is “Parent Position Id1”. The “Team-Support Hierarchy” should retrieve all the position ids whose parent position id is equal to “Parent Position Id1”. If the user changes position, the retrieved hierarchy should be updated accordingly (Parent Position Id may be different for the new active position id).

To implement the requirement, we have created the following configurations:
Fields added in Personalization Profile BC:
1.Field Name: Active Position Id
Join: S_EMP_PER
Column: X_ ATTRIB_VAR02

This is a custom field added in Employee BC to store the user’s active position id. The value of this field is set via a business service. This business service is called via runtime events on WebSessionStart of the application and InvokeMethod of Change Position List Applet.

2.Parent Position id
Join: S_PARTY
Column: PAR_PARTY_ID
Source Field: Active Position Id
Destination Column: ROW_ID

3.Team Support Hierarchy
Multivalue: TRUE
Destination Field: Party Id
Multivalue Link is based on Personalization Profile/Party Reporting Relationship link.
Multivalue Link source field: Parent Position Id

When we tried to retrieve the value of this “Team Support Hierarchy” in scripts using TheApplication().GetProfileAttr(“Team Support Hierarchy”), the result returned only one position id.

We then tried adding a calculated field in the Personalization Profile BC, “Team Support Hierarchy Calc” with calculated value GetProfileAttrAsList(“Team Support Hierarchy”). Retrieving this calculated field in scripts via TheApplication().GetProfileAttr(“Team Support Hierarchy Calc”) returned the correct list of position ids with “,” (comma) as the delimiter (ex. 0...

Cause

This is caused by Change request 12-1K9O8HF.

Solution

Message 1

For the benefit of other readers:

Customer is asking how the profile attribute with calculated value using "GetProfileAttrAsList" function can be refreshed. "LoadUserAttributes" method is recommended but it is observed that profile attribute which uses "GetProfileAttrAsList" function does not get re-loaded. Change request 12-1K9O8HF has been logged to address this.

Customer has worked around this by using script to set the profile attribute with the string of position Ids instead.

Note: "GetProfileAttrAsList" function does get refreshed using "LoadUserAttributes" method in version 7.8.2.x.

Additional Keywords:
Cached values, GetProfileAttrAsList, not refresh, not reload

Applies to:

Siebel CRM - Version: 7.8.2.5 SIA [19227] - Release: V7
Information in this document applies to any platform.

Symptoms

On : 7.8.2.5 SIA [19227] version, Security / Authentication

When attempting to run keydbmgr utility
the following errors occur:

ERROR
-----------------------
SBL-SEC-10001: An internal error has occurred within the authentication subsystem for siebel application
SBL-SEC-10018: A Siebel local database error has occurred possibly the database name is invalid.
SBL-DAT-00522: Unable to start the database server.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. run keydbmgr utility using the following command:
keydbmgr /u sadmin /p sadmin /l enu /c E:\sea78\siebsrvr\BIN\enu\fins.cfg
2. In fins.cfg you should have:
[Siebel]
...
DataSource = $(DefaultDataSource)
...
[DBSecAdpt]
SecAdptDllName = sscfsadb
DataSourceName = Local


BUSINESS IMPACT
-----------------------

Due to this issue, users cannot implement data encryption.

Cause

The issue is caused by the following setup:
-You used fins.cfg file which keydbmgr reads to get all the connection information (ServerDbODBCDataSource, ConnectString,$(GatewayAddress), $(EnterpriseServer)).
However, those values were not set to the real values, and that is why the utility returns error.

Solution

To resolve the issue:
1. Open fins.cfg (one you use when running keydbmgr utility)
2. Set the following parameters to the correct values:
DataSource, ServerDbODBCDataSource, ConnectString,$(GatewayAddress), $(EnterpriseServer)
3. Rerun keydbmgr utility.

Note:
The error you are getting when exiting from keydbmgr is:
“Error: Fail to complete the key cache version updating operation.”
Change Request #12-17B65FB has been logged for this error and the problem does not appear in Siebel 8.0. Since the keyfile.bin gets updated, the error is benign and can be ignored.
This is described in document: Data Encryption (Doc ID 490017.1).

References

BUG:12-17B65FB - KEYDBMGR ERRORS WHEN TRYING TO ADD A NEW ENCRYPTION KEY
NOTE:490017.1 - Data Encryption

Applies to:

Siebel Remote Client - Version: 8.0 [20405] to 8.0.0.5 [20420] - Release: V8 to V8
Information in this document applies to any platform.
Area(s):Remote/Replication/Anywhere
Release(s):V8 (Enterprise), V8 (Professional)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:encrypted, local database, mwc, mobile web client, Siebel Tools

This document was previously published as Siebel FAQ 2293.

***Checked for relevance on 13-Oct-2010***

Goal

How Do You Connect Siebel Tools and the Mobile Web Client (MWC) to an Encrypted Local Database?.

Solution

 Purpose
 
In Siebel version 8.0 and higher, when extracting a local database with the default settings, the local database is now encrypted. This is the standard behavior and differs from the earlier versions when you needed to make changes in order to encrypt the local database.
 
One result is that if you download the local database using Siebel Tools, you will not automatically be able to connect to it using the Siebel Mobile Web Client (MWC).
 
This FAQ demonstrates how in Siebel 8.0 and higher you can use the Siebel Mobile Web Client (MWC) to connect to a Local Database extracted by Siebel Tools.
 
Steps
 
1. Run Generate New Database (GenNewDB).
 
2. Run Database Extract (DBExtract).
 
3. Start Siebel Tools and Connect to Local using your USER_ID and PASSWORD.  Due to the fact the local database does not exist on the PC, you will be prompted to download the Local Database.
 
4. Once the local database had downloaded, please ensure you can connect correctly using Siebel Tools.
 
5. Copy the file ${Tools}\local\dicdata.dat to ${Client}\local\dicdata.dat 
    Without this step, you cannot connect to the local database from the Siebel Mobile Web Client.
 
6.  Copy the following parameters from the [Local] section of the Tools CFG to the Siebel Mobile Web Clients CFG file
 
             DSDockEncryptDB=TRUE
             DSHashUserPwd=TRUE
             DSHashAlgorithm=RSASHA1
 
7. In the Mobile Web Client CFG file [Local] section, edit the ConnectString parameter to point to where the local database is located.
 
8. Copy the file ${Tools}\bin\mwc_storage.cfg to ${Client}\bin\mwc_storage.cfg
 
9. Change the ODBC DataSource for the Client by performing the following steps:-
 
a. Navigate to Control Panel  > Administrative Tools > Data Source (ODBC)
 
b. Select the System DSN tab
 
c. In the list, find the DSN Source called “SSD Local DB default instance”.  Double-click on it or click once and then click the Configure button.
 
d. Click the Database tab
 
e. Copy the Server Name (such as: C__SIA_TOOLS_Local_sse_data_dbf).  Click Cancel to close this window and return to the list of System Data Sources.
 
f. Locate the System Data Source for the client called “SEAW Local DB default instance”. Double-click on it or click once and then click the Configure button.
 
g. Click the Database tab
 
h. Paste the data just copied into the Server Name.  Click OK to save the changes.
 

NOTE: It is possible to extract a local database without encryption but you need to specify the parameters below:-

Encrypt client Db password = False
Client Database encryption method = none

If you create a non-encrypted local database, you will still need to copy the file ‘mwc_storage.cfg’ file from the ${Tools}\bin directory to the ${Client}\bin directory and update the local ODBC section in the client CFG file (assumes extraction took place using Tools)
 
Further information on these parameters can be found in the Siebel Remote and Replication Manager Administration Guide version 8.0 > Extracting Databases for Mobile Web Clients > Database Extraction for a Mobile Web Client and Siebel Remote and Replication Manager Administration Guide version 8.0 > Extracting Databases for Mobile Web Clients > Database Extraction for a Mobile Web Client > Parameters of the Database Extract Component.

Additional keywords: SBL-SEC-10018, SBL-DAT-00522, SBL-SEC-10001 and SBL-DAT-00565, SBL-DAT-00522, Incorrect, "missing encryption key"