Bookshelf Home | Contents | Index | Search | PDF

Siebel Server Installation Guide for UNIX > Installing the Siebel Database Server for DB2 UDB > Database Server Software Installation for DB2 >

Creating Tableowner and Administrator Accounts for Database Server
on DB2

---

When operating the DB2 UDB Database, the database administrator must manually create the tableowner account (default: SIEBEL), the Siebel Administrator account (default: SADMIN), and the sse_role group at the operating system level. You must then add the two accounts to the sse_role group.

NOTE:  On Solaris, the sse_role group cannot be created using the admintool due to the use of an underscore in the name. Instead, use the command groupadd sse_role to create the sse_role group and ignore the UX: groupadd: sse_role name should be all lower case or numeric warning.

CAUTION:  You can add users to the installation group sse_role group and permit them to use administrative commands to start, stop or otherwise administer the Siebel Server or components. However, you must change the permissions on the directory to enable write access. Use chmod -R 775 on $SIEBEL_ROOT.

Execute the grantusr.sql script against your Siebel Database Server to grant the appropriate privileges to these users. The grantusr.sql script must be run before you configure the Siebel Database Server.

This script is located in the $DBSRVR_PLTFRM_ROOT subdirectory of your $DBSRVR directory. Your database administrator should review and run this script, which performs the following functions:

Grants the appropriate permissions to the Siebel tableowner account that will own all the database objects for your Siebel deployment.
Creates a role (sse_role) with create session privileges.

NOTE:  You cannot create the LDAPUSER account by running grantusr.sql. This account must belong to the sse_role group and be created by the database administrator or the UNIX network administrator, as appropriate. For more information about LDAP, see Security Guide for Siebel eBusiness Applications.

CAUTION:  Do not change the name of the Siebel Administrator Account, SADMIN. This account must be created for you to log on to Siebel as the Siebel Administrator.

Tableowner and Administrator Account for Siebel Marketing

The tableowner or the database User ID used for Siebel Marketing requires additional rights at the database level within the OLTP schema. You must grant drop table, drop index, create table, and create index rights to this user. For more details, see Siebel Marketing Guide.

To run the grantusr.sql script

Run the grantusr.sql script, using an account with DBA privileges.

The usual DB2 System Administration account will be called db2inst1 on UNIX.

Enter the following commands:

db2 connect to DB2database Alias user Instance Owner Username using password

db2 -vf /SIEBEL_ROOT/db2udb/grantusr.sql

where:

DB2database Alias is the DB2 alias you use.

Instance Owner Username is the login ID of the instance owner.

password is the password for the database instance (length and allowable characters depend on the rules of your underlying RDBMS platform).

SIEBEL_ROOT is your Siebel root directory.

NOTE:  You must specify the full path to the $SIEBEL_ROOT directory.

The script prompts you for the default tablespace in which your Siebel objects are to be created.

Enter the tablespace name you recorded in the copy you made of Deployment Planning Worksheets.

Bookshelf Home | Contents | Index | Search | PDF