Table 63. Parameters and Command Line Flag for the Srvrinit Utility
|
|
|
|
16K Table Space |
ks |
For DB2/UDB installations only, provide the name of the appropriate 16K Table space. For more information, see the Siebel Installation Guide for the operating system you are using. |
No |
32 K Table Space |
ls |
For DB2 installations only, provide the name of the appropriate 32K Table space. For more information, see the Siebel Installation Guide for the operating system you are using. |
No |
File System |
filesystem |
File system directory on the regional node. The file system parameter must reference the parent directory of the att directory. The Srvrinit utility automatically copies the files to the att directory. |
Yes |
Help |
? help |
Help for usage. |
No |
Index Space |
is |
For DB2/UDB and Oracle 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:
- Y. Indicate the initialization of the Siebel Server of a regional node on a new database.
- N. Indicate an upgrade of the existing regional database with a new database extract.
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 modem connections. |
No |
(Not applicable.) |
l |
Language code. The default value is enu. |
No |
(Not applicable.) |
v |
Verbose mode, which 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 performs the server database extract. |
Yes |
Regional Server Name |
n |
Name of the regional node. |
Yes |
Repository Name |
reposname |
Name of repository, which is usually 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 DB2/390 and AS/400 environments 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 directory of the Siebel Server on the Regional node. In this document, SIEBEL_ROOT is the root directory where you install the Siebel Server. |
Yes |
Table Grouping File |
tg |
For DB2/390 installations 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 tableowner on the regional database. For DB2/390 and AS/400 environments, 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 Tableowner on the regional database. It must include privileges to create database objects. For DB2/390 and AS/400 environments, 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 server 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 DB2/UDB and Oracle 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. |
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 |