Siebel Installation Guide for Microsoft Windows > Configuring the Siebel Database >
Creating Table Owner and Administrator Accounts
Create the table owner and administrator accounts according to the guidelines provided for each database platform identified in this topic. These accounts are created using the
NOTE: For each applicable database platform, if you are planning to use Siebel Marketing, also grant drop table, drop index, create table, and create index rights at the database level within the OLTP schema to the table owner or the database user ID used for Siebel Marketing. For more information, see Siebel Marketing Installation and Administration Guide.
CAUTION: It is strongly recommended not to change the name of the Siebel administrator account,
SADMIN. This account must be created for you to log in to Siebel Business Applications as the Siebel administrator. For information about changing the password for this account, see Siebel Security Guide.
NOTE: Before you execute the
grantusr.sql script, confirm that this script will create all the users you will require. For example, for information about special-purpose user names you specify when configuring the Siebel Web Server Extension, see Requirements for SWSE Installation and Configuration.
Before configuring the Siebel Database, your DBA must review and modify (if necessary) the
grantusr.sql script. The administrator must then execute the
grantusr.sql script against your Siebel Database to create the Siebel table owner (default:
SIEBEL), Siebel administrator account (default:
LDAPUSER account, and the role
SSE_ROLE, and grant them the appropriate privileges.
grantusr.sql, the DBA must copy the following command in the script, so it is defined once for each table space (for data or indexes) in your Siebel implementation:
alter user SIEBEL quota unlimited on table_space_name;
If necessary, the quota value can be adjusted to an appropriate value for each corresponding table space.
grantusr.sql script is located in the DBSRVR_ROOT\ORACLE subdirectory.
grantusr.sql script performs the following functions:
- Creates the role
SSE_ROLE and grants
create session privilege to this role.
- Creates the user
SIEBEL (the Siebel table owner) and grants other appropriate privileges to
- Creates the users
SADMIN (the Siebel administrator) and
LDAPUSER and grants the role
SSE_ROLE to them.
The default user name and password for the login are listed in the
grantusr.sql script. If you want another login, edit the
grantusr.sql script and change all the references to your preferred name. Keep in mind that the length and allowable characters for the login ID and password depend on the rules of your underlying RDBMS platform. For instructions, see your Oracle Database documentation.
To run the grantusr.sql script on Oracle
- Run the
grantusr.sql script from SQL*Plus, using an account with DBA privileges, and using the following command:
NOTE: You must specify the full path to the file above.
- Enter the table space name listed in Deployment Planning Worksheet.
IBM DB2 UDB
Your DBA must manually create the Siebel table owner account (default:
SIEBEL), the Siebel administrator account (default:
SADMIN), and the
SSE_ROLE group. The DBA must then add the Siebel administrator account to the
SSE_ROLE group at the operating system level.
After your database is created and before it is configured, execute the
grantusr.sql script against your database server to grant the appropriate privileges to these users. The
grantusr.sql script must be run before you configure the Siebel Database. The
grantusr.sql script is located in the DBSRVR_ROOT\DB2UDB subdirectory.
Your DBA must review and run this script, which performs the following functions:
- Grants DBA administration (
DBADM) privileges to table owner
CONNECT privileges to the
You cannot create the
LDAPUSER account by running
grantusr.sql. This account must belong to the
SSE_ROLE group and be created by the DBA or the Windows network administrator, as appropriate. For more information about LDAP security adapter authentication, see Siebel Security Guide.
To run the grantusr.sql script on DB2 UDB
- Execute the
grantusr.sql script from a DB2 Command Window, using an account with DBA privileges.
The usual DB2 System Administration account will be called
db2admin for this procedure.
CAUTION: Be sure to use the DB2 Command Window, not the Command Line Processor, to enter these commands, because the Command Line Processor window uses different syntax. The commands in this procedure do not work unless issued in a DB2 Command Window.
- Enter the following commands:
db2 connect to DB2database_alias user
instance_owner_username using password
- Enter the table space name you recorded in the copy you made of Deployment Planning Worksheet and then exit.
Before starting database configuration, proceed to Installing the Stored Procedures and User-Defined Functions on DB2 UDB.
MS SQL Server
Your DBA must run the
grantusr.sql script to set up minimum security so that the Siebel installation can start. Your DBA must review, modify, and run the
grantusr.sql script before you configure the Siebel Database. The
grantusr.sql script is located in the DBSRVR_ROOT\MSSQL subdirectory.
grantusr.sql script performs the following functions:
- Creates logins for
SADMIN (Siebel administrator),
SIEBEL (table owner), and
- Creates users for each of these logins, except for
SIEBEL, which will be turned into a
dbo by the stored procedure
SSE_ROLE to each user, except
To change the login or the name of the database, edit the
grantusr.sql script to change all references to the login or the database name. Keep in mind that the length and allowable characters of the login ID and password depend on the rules of your underlying RDBMS platform. See your Microsoft documentation for instructions.
To run the grantusr.sql script on MS SQL Server
grantusr.sql in MS Query Analyzer.
- Execute the script.