Life Sciences

How To Install Siebel Tools In A Working Environment

I have seen quite a few blog posts on how to setup Siebel Innovation Pack 2016 (IP2016) in a test bed environment, but very little chatter on how to actually install IP2016 Siebel Tools (Tools) and use it in a real development project. Hopefully, this will help some of you out there. Feel free to share any other helpful tips that you have noticed.

In IP2016, Oracle has changed the local database from Sybase to Oracle XE. In addition, Oracle now offers alternative ways of downloading the repository tables to your local database. Sadly, all the ways have associated bugs.

First, note that, when you are installing Tools, a new question is asked: Do you wish to install a local database?

Regardless of how you answer this question, the Oracle XE software will be installed. If you answer “yes” to this question, the vanilla repository will be installed. If you answer “no,” you will be left with an empty database.

These are the steps I followed after performing the installation of Tools, in order to get a working environment for user RSCHMIDT:

  1. Start the new program “Run SQL Command Line”
  2. Enter: CONNECT SYS/SIEBEL AS SYSDBA
  3. Enter: CREATE USER RSCHMIDT IDENTIFIED BY XYZZY
  4. Enter: GRANT SSE_ROLE TO RSCHMIDT
  5. From a DOS Prompt Enter; C:\Siebel\16.0.0.0.0\Tools\BIN\LOCALDBSETUP -s C:\Siebel\16.0.0.0.0\Tools -u RSCHMIDT -p XYZZY -o “SSD default instance” -t SIEBEL -d LOCAL_XE -x C:\Siebel\16.0.0.0.0\Tools\oraclexe -y DCRSE

Be sure to note that step five takes about 22 hours (your mileage may vary depending on your network speed).

Life Sciences - How Artificial Intelligence Can Enhance the Clinical Data Review and Cleaning Process
How Artificial Intelligence Can Enhance the Clinical Data Review and Cleaning Process

This guide analyzes how artificial intelligence – including machine learning – can be used by pharmaceutical and medical device companies to improve the clinical data review and cleansing process.

Get the Guide

Using this method works (and works better than the alternative methods), but the downside is that non-repository objects (e.g., sequences, functions, procedures) are missed by the installer and will need to be created by hand.

The missing pieces can be identified by running this query against the server and the local databases, and comparing the results:

select object_name, object_type from all_objects where owner = ‘SIEBEL’

and object_type in (‘FUNCTION’,’PROCEDURE’,’PACKAGE’)

Here are the commands I used to create the missing sequences:

CREATE SEQUENCE S_SEQUENCE_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_SRM_REQUEST_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_RTS_WQ_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_RTS_STATE_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_ESCL_REQ_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_ESCL_ACTN_REQ_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_EAI_BATCH_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_DCK_TXN_LOG_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_SD_SYNCINFO_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_ASGN_LB_DATA_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

CREATE SEQUENCE S_AUDIT_ITEM_S INCREMENT BY 1 START WITH 1 NOMAXVALUE NOCYCLE CACHE 20;

 

GRANT SELECT ON S_SEQUENCE_S TO SSE_ROLE;

GRANT SELECT ON S_SRM_REQUEST_S TO SSE_ROLE;

GRANT SELECT ON S_RTS_WQ_S TO SSE_ROLE;

GRANT SELECT ON S_RTS_STATE_S TO SSE_ROLE;

GRANT SELECT ON S_ESCL_REQ_S TO SSE_ROLE;

GRANT SELECT ON S_ESCL_ACTN_REQ_S TO SSE_ROLE;

GRANT SELECT ON S_EAI_BATCH_S TO SSE_ROLE;

GRANT SELECT ON S_DCK_TXN_LOG_S TO SSE_ROLE;

GRANT SELECT ON S_SD_SYNCINFO_S TO SSE_ROLE;

GRANT SELECT ON S_ASGN_LB_DATA_S TO SSE_ROLE;

GRANT SELECT ON S_AUDIT_ITEM_S TO SSE_ROLE;

 

COMMIT;

 

Also, note that if you choose to not use this method, checkins and checkouts will be very slow. I suspect that Oracle was not tuned. I found this to be very helpful:

 

spool “C:/Siebel/16.0.0.0.0/Tools/BIN\LocalDbTemplate\stats_upd.log”

EXEC DBMS_STATS.gather_schema_stats (ownname => ‘SIEBEL’, cascade =>true,estimate_percent => dbms_stats.auto_sample_size);

exit;

 

I hope these tips make your installation of IP2016 Tools easier and faster. If you have any questions, reach out!

About the Author

With 20 years of life sciences experience and 10 of working with Siebel, Rene is a Lead Technical consultant @ Perficient. Originally from Montreal, PQ, Rene now resides in Augusta, GA.

More from this Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Subscribe to the Weekly Blog Digest:

Sign Up
Categories