ODBCSQL Utility

the Siebel Server installation, there is a utility called odbcsql.exe in the bin folder. It is very useful in troubleshooting connectivity behaviors that stem from the ODBC layer in the installation.

To test the ODBC data source, type the following commands:

Launch the odbcsql utility:

(Microsoft Windows) Navigate to \siebsrvr\BIN and double-click the odbcsql.exe executable.

(UNIX) Make sure you have the Siebel environment variables set appropriately. Navigate to /siebsrvr/bin and type:

./odbcsql

At the ODBC prompt set the SIEBEL_DATASOURCE_NAME to the ODBC data source for which you want to test the connectivity (for example: SiebSrvr_siebel77). On Microsoft Windows, you can navigate to Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC) > and click on the System DSN tab to locate the name of the ODBC data source. On UNIX, you can find the Data Source Name in the /siebsrvr/sys/.odbc.ini file.

ODBC> set source

Connect as a user with the appropriate privileges, for example:

login SADMIN/

Execute a SQL statement against any table. For example:

ODBC> SELECT APP_VER, COMMENTS from .S_APP_VER;

This should result in the application version and comments (if any) being displayed and should indicate that the connectivity via the ODBC layer is set up correctly. For example:

ODBC> SELECT APP_VER, COMMENTS from S_APP_VER;
APP_VER COMMENTS
------------------------------ ----------------------------------
V7.7 Database Schema for Siebel 7.7
------------------------------
(query+fetch time: 0.07s, rows fetched: 1, time per row: 0.07s)

Any error messages returned at this point would indicate the following:

There are problems downstream from the ODBC layer to the database or
There are problems in the user and password combination or
There are problems with the SSE_ROLE privileges granted to that user.

You can find additional information in the Siebel Bookshelf version 7.7 > Siebel Installation Guide for (Microsoft Window or UNIX): Servers, Mobile Web Clients, Tools > Installing the Siebel Server:

Max Cursor Size

Max Cursor Size and Pre-Fetch Size will determine the number of records Siebel returns at the BC level.

NM Stage Load Balencing Issue

Start Cenrtal Dispatch Server on Siebel 704 box
Start Siebel Resonate Server on Siebel 704 box

Start Siebel Server on Siebel Server 704 box

make 703 a dummy server

Insanity: Doing the same thing over and over again and expecting different results. -Albert Einstein

Siebel User Keys

User keys are the set of columns in a table which can uniquely identify a record.

User Keys are nothing but Unique Indexes on the table will be individually verified. For Example S_PERIOD has 3 Unique Indexes . First U1 gets verified and then U2 verified and at the last U3 will be verified.

Its not that all the Usery keys will be applied in combination but one at a time.

DB2 query to find Indexes for any table

select substr(INDNAME,1,30),substr(tabname,1,10),COLNAMES, UNIQUERULE, UNIQUE_COLCOUNT from syscat.indexes where tabname='S_PERIOD'

Additional systems table for DB2

syscat.references (fkeys)
syscat.tables (table names)
syscat.columns (column names)
syscat.procedures (stored procs, triggers?)

Phone Validation

Validation on Work Phone #, Work Fax are due to field Type "DTYPE_PHONE". One way to remove the validation is to chnage the type to "DTYPE_TEXT" and bring in Validation using eScripts or Validation Administration.

P.S. Formating of phone numbers will be affected by chnage of type from DTYPE_PHONE to DTYPE_TEXT.

Creating Multiple users for Local Database

Log on to local db from command prompt

dbisql55 -c UID=DBA;PWD=SQL;DBF=c:\\local\sse_data.dbf

Create Users in local

grant connect to SSE_ROLE
grant connect to MADHAV identified by MADHAV
grant group to SSE_ROLE
grant membership in group SSE_ROLE to

Create Employee Record in Using Siebel UI for the user you have created with proper responsibility and position

*p.s. Password and User Id sud be upper case

Tool - Local Database initialization - Killing it

You have started the local database extract and then at half way you feel you do not need it. You will stop the extract delete local databse.

You will try to open the tools.

Patak seee extact will restart.... Is there a solution apart from uninstalling Siebel and Reinstalling it ??

Yes !!! Search for upgrade.ucf (ucf = upgrade config file).. delete it. You are all set. Your tools will behave normal.

Tool - Local Database initialization

When you are running the local database initialization using an upgrade wizard you can stop the local database extract half way through. When you log-on to Siebel tools the next time local database extract starts from nearest point where it had stopped.

Local Database Extract keeps loging the status of local database in state.log under Upgrade folder hierarchey. Local database extract is divided into different item.

Exmple of State.log

[Item 0]Status = Complete$TblOwner2 = SIEBELPause = 0

[Item 1]Status = CompleteItem Name = File Copy Entry 0

[Item 2]Status = CompleteItem Name = Sql File Entry 1SQL Statement Prefix = RUN_SQL_SQL Statement Number = 0SQL Statement Status = Success

[Item 3]Status = CompleteItem Name = Sql File Entry 2SQL Statement Prefix = RUN_SQL_SQL Statement Number = 5SQL Statement Status = Success

[Item 4]Status = CompleteItem Name = Sql File Entry 3

[Item 5]Status = CompleteItem Name = Sql File Entry 4SQL Statement Prefix = RUN_SQL_SQL Statement Number = 1SQL Statement Status = Success

[Item 6]Status = ErrorItem Name = Import DML Entry 5Table Name = S_BUTable Index = 118Row Index = 0Imported Row Index = 763402

[Item 7]Status = InComplete

[Item 8]Status = InComplete

[Item 9]Status = InComplete

[Item 10]Status = InComplete

SRF reference by Workflow Process Manager

When you connect to server via a dedicated client, and a call to Workflow process Manager is made via a Workflow Policy. Workflow Process Managers on the server will be fired and it will use the SRF on the Server not the one on your local machine.

During such situations make sure the SRF is recycled on the server too.

Siebel - Using Sleep in eScript on a Windows Machine

SElib.dynamicLink("kernel32.dll", "Sleep", STDCALL, 2000)

STDCALL is Standerd Call

2000 is milliseconds

SElib is trys to use the windows kernal32.dlls sleep function and sleeps the execution of the code for specified milli-seconds.