Parameters of the Regional Database Initialization Program
The following table lists some of the parameters and corresponding flags that are available for the Srvrinit utility.
| Parameter | Flag | Description | Required |
|---|---|---|---|
16K Table Space |
ks |
For IBM DB2 installations only, provide the name of the 16K Table space. For more information, see the Siebel Installation Guide. |
No |
32K Table Space |
ls |
For IBM DB2 installations only, provide the name of the 32K Table space. For more information, see the Siebel Installation Guide. |
No |
File System |
filesystem |
File system location on the regional node. The File System parameter must reference the Siebel File System directory with the
|
Yes |
Help |
? help |
Help for usage. |
No |
Index Space |
is |
For Oracle Database and IBM DB2 installations only. Space on the regional database where indexes are created. |
No |
Initialize on new database |
init |
Specifies if the regional database is empty or not:
The default value is N. An old transaction might be invalid for the new schema and can cause failure. You must set this parameter to Y during a major upgrade. |
No |
(Not applicable.) |
comm |
Communication parameters for low-bandwidth connections. |
No |
(Not applicable.) |
l |
Language code. The default value is enu. |
No |
(Not applicable.) |
v |
Verbose mode, that you can set to Y or N. The default value is N. |
No |
ODBC Data Source |
d |
Name of ODBC data source to connect to the regional node. |
Yes |
Parent AppServer Name |
dockconnstring |
Name of the Siebel Server at the parent node where Siebel Remote does the Siebel database extract. |
Yes |
Regional Server Name |
n |
Name of the regional node. |
Yes |
Repository Name |
reposname |
Name of the repository, which is typically Siebel Repository. |
Yes |
Run in Parallel/Number of Threads |
para |
Specifies to run srvrinit in parallel. Specifies the number of threads to run. |
No |
Schema Qualifier |
sq |
For IBM DB2 for z/OS only, the name that the Srvrinit utility uses to qualify database objects it creates that the Siebel application requires. |
Yes |
Server Root Directory |
homedir |
Root folder of the Siebel Server on the Regional
node. In this document, |
Yes |
Table Grouping File |
tg |
For IBM DB2 for z/OS only. Full path to the storage control file, which is a file that contains declarations for database objects. |
Yes |
Table Owner Password/Privileged User Password |
tp |
Password of the table owner on the regional database. For IBM DB2 for z/OS, this password is the same as the Privileged User Password, which is the password for Privileged User ID. |
Yes |
Table Owner/Privileged User ID |
t |
Logon of the Table Owner on the regional database. It must include privileges to create database objects. For IBM DB2 for z/OS, this logon is the same as the Privileged User ID. This account is a user account that includes the necessary database authority and privileges to create, access, and modify Siebel database objects and native database objects and the operations that are required to implement the Siebel application. These environments include rigid controls on user identification. An account must correspond to a real person. |
Yes |
Table Space |
ts |
For IBM DB2 and Oracle Database installations only. Space on the regional database where tables are created. |
No |
User Name |
u |
User name to authenticate the regional database with the Siebel Server of the headquarters node. You can use a database user who is associated with the regional database during the setup, but this user must possess administrator privileges to create logins in the master database, such as SADMIN. For more information about headquarters nodes, see Overview of Siebel Replication Manager. |
Yes |
User Password |
p |
Password to authenticate the regional database with the Siebel Server of the headquarters node. If you configure the users on the regional database, then Replication Manager uses the password that you specify. |
Yes |