Bookshelf Home | Contents | Index | Search | PDF

Siebel Remote and Replication Manager Administration Guide > Implementing Siebel Replication Manager >

Initializing the Regional Database

---

The Regional Database initialization process retrieves the database extract created in the previous step, and loads it into the Regional Database. Database objects are created and populated with data.

If you will be reinitializing a regional node with mobile Web clients, it is important to conduct the following test. Verify the mobile Web clients that synchronized with this node can reinitialize without deleting their local databases.

The Regional Database is initialized from the Siebel Server using the Regional Database Initialization utility. This must be done on the Regional Server:

In Windows, the Regional Database Initialization utility is called srvrinit.exe. You can run srvrinit.exe in the GUI or the command-line interface.

NOTE:  You must set the appropriate environment variables before running srvrinit.exe. Set environment variables by running the batch file siebenv.bat, located in the siebel_server directory. Run this batch file in the same command shell in which you will be running srvrinit.

In UNIX, the Regional Database Initialization utility is called srvrinit. You can run srvrinit from the command-line interface only.

In both operating systems, the Regional Database Initialization utility is located in the bin subdirectory under the Siebel Server root directory.

In order for srvrinit to finish successfully, you need to make sure that sufficient transaction space (Rollback Segment) is available on the Regional Server Database. You may want to verify with your DBA and to increase or alter existing rollback segments if necessary.

You must also make sure that the combination of database user ID and password that you will use to run srvrinit exists on both the HQ Server and the Regional Node. Srvrinit only allows you to specify one set of credentials, but srvrinit is required to use those credentials for both machines. If credentials on the two machines are different, the process may not start, or may fail before completion.

If the Applications Server has multiple CPUs and disk arrays, running srvrinit in parallel can dramatically improve performance.

It is possible to reduce the size of the rollback segment required for srvrinit by reducing the dbxtract parameter Maximum data file size (DatFileSize). This is because the srvrinit task commits per file. Therefore the smaller the file, the smaller the rollback segment. See Database Extract Parameters for details about DatFileSize.

To initialize the Regional Database in the GUI

In the same window where you ran siebenv.bat, navigate to <server install on the regional node>\bin and enter srvrinit.exe.

The Regional Database Initialization dialog box appears.

In the Siebel Remote Parameters fields, specify the correct values for each of the parameters used by the Regional Siebel Server to connect to the parent node. For a description of these parameters, see Table 24.
In the Regional Database Parameters fields, specify the correct values for each of the parameters used by the Regional Siebel Server to connect to the Regional Database. For a description of these parameters, see Table 24.
To start the initialization process, click Start Initialization.

The database extract will be downloaded from the server. The Siebel Upgrade Wizard launches automatically and completes the steps required to initialize the Regional Database. If you do not see a dialog box on the screen as the process executes, usually this indicates something is wrong. If this happens, check the log file in the log directory.

There will be two log files. The first one is srvrinit.log. The second one is either upgwiz.log on Windows or srvrupgwiz1.log on UNIX.

After the initialization utility completes successfully, setup of the Regional Database is complete. For instructions on administering the Regional Database, see Administering Siebel Replication Manager.

The Regional Database Initialization utility (srvrinit) has two functions:

It connects to the parent remote server and downloads the database extract for the regional node.
It starts the Siebel Upgrade Wizard to carry out the actual database initialization.

To initialize the Regional Database from the command line interface

Change to the bin subdirectory under the Siebel server root directory and enter:

srvrinit flags

For a list of flags, see Table 24.

NOTE:  If the Regional Database initialization fails (for example, due to insufficient storage space on the database), you must recover from the failure before restarting Replication Manager. To do this, restart the Regional Database Initialization utility.

The built-in state logging ability of the Siebel Upgrade Wizard provides the ability to restart the Siebel Upgrade Wizard. If you encounter an error during the second phase (Siebel Upgrade Wizard) of the regional database initialization process, examine the log file (UpgWiz.log on NT and srvrupgwiz.log on Unix) and take appropriate corrective actions.

NOTE:  The following error messages can be ignored: ORA-01921: role name 'SSE_ROLE' conflicts with another user or role name, ORA-01017: invalid username/password; logon denied, and ORA-00942:table or view does not exist.

After applying the proper fix, simply restart the regional initialization process by running Siebel Upgrade Wizard again. The Siebel Upgrade Wizard remembers the progress of the initialization process and begins from where it left off. The executable name is siebupg1.exe on NT and srvrupgwiz1 on UNIX.

However, there may be occasions when you simply want to restart the Regional Database Initialization process from scratch. To do so, follow the procedure below.

To restart Regional database initialization process from scratch - NT

On the Regional Node, navigate to $SiebelRoot/bin.
Run the Siebel Upgrade Wizard (type the command or double-click siebupg1.exe).
Click Cancel when you are prompted to choose Yes to retry, No to abort, or Cancel to abort and clean up.
Rerun the initialization process.

To restart Regional database initialization process from scratch - UNIX

On the Regional Node, navigate to $SiebelRoot/bin.
Find the file upgwiz.ucf and delete it.
Navigate to $SiebelRoot/upgrade and delete all files with the name state.log under it.
Rerun the initialization process.

Table 24 lists selected parameters and corresponding flags for the srvrinit command-line utility.

Table 24. Parameters and Command-Line Flags for srvrinit Utility

Parameter	Command Line Flag	Description	Required?
16K Table Space	/ks	For DB2/UDB installations only, the name of the appropriate 16K Table space should be provided. For more information, see the Siebel Server installation guide for the operating system you are using.	No
32 K Table Space	/ls	For DB2 installations only, the name of the appropriate 32K Table space should be provided. For more information, see the Siebel Server installation guide for the operating system you are using.	No
N/A	/comm	Communication parameters for modem connection.	No
Parent AppServer Name	/dockconnstring	Name of the Siebel server at the parent node where the database extract was performed.	Yes
Regional Server Name	/n	Name of the Regional Node.	Yes
File System	/filesystem	File system directory on the regional node.	Yes
Help	/? /help	Help on usage.	No
Index Space	/is	For DB2/UDB installations only. Space on the Regional Database where indexes should be created.	No
Initialize on new database	/init	Indicates whether the regional database is empty or not. Use Y if this is the initialization of the regional server on new database, N if it is an upgrade of the existing regional database with new dbxtract. Default value is N. Parameter should be set to Y during a major upgrade—old transactions can be invalid for the new schema and cause failure.	No
N/A	/l	Language code, default is enu.	No
ODBC Data Source	/d	Name of ODBC data source to connect to the Regional Node.	Yes
User Password	/p	Password to authenticate the Regional Database against the Headquarters Server. The password you specify will be used when the users are set up on the Regional Database.	Yes
Repository Name	/reposname	Name of repository, usually "Siebel Repository."	Yes
Run in Parallel/Number of Threads	/para	Indicates srvrinit will run in parallel and the number of threads.	No
Schema Qualifier	/sq	For DB2/390 and AS/400 environments only, the name used to qualify all database objects created that are required by Siebel.	Yes
Server Root Directory	/homedir	Server root directory, on the Regional node where SIEBEL_SERVER_ROOT is the root directory of the regional Siebel Server installation.	Yes
Table Owner Password/Privileged User Password	/tp	Tableowner's password on the Regional Database. For DB2/390 and AS/400 environments, this is the same as the Privileged User Password. This is the password for Privileged User ID.	Yes
Table Owner/Privileged User ID	/t	Tableowner's logon on the Regional Database. Must have privileges to create database objects. For DB2/390 and AS/400 environments, this is the same as the Privileged User ID. This is a user account that has the necessary database authority and privileges to create, access, and modify Siebel database objects as well as native database objects and operations required to implement the Siebel application. These environments have rigid controls on user identification—accounts must correspond to a real person.	Yes
Table Space	/ts	For DB2/UDB installations only. Space on the Regional Database where tables should be created.	No
User Name	/u	User name to authenticate the Regional Database against the Headquarters Server. You can use any database user associated with the Regional Database during the setup, but the user must have security admin privileges in order to create logins within the master database (such as sadmin).	Yes
N/A	/v	Verbose mode, may be set to Y or N. Default is N.	No

After completion of initialization, enable the required server components such as Siebel Remote and the appropriate object managers. For information regarding how to do this for Remote Server components, see Starting and Stopping Siebel Remote Server Components. For information regarding how to do this for object managers and other components, see Siebel Server Administration Guide.

Also, administrators need to install the Siebel Web Server Extension (SWSE). For information regarding how to do this, see the Siebel Server installation guide for the operating system you are using. This is essential for administrators to use the Web client to support users on Regional Nodes.

The SWSE is not required if administrators use the dedicated Web client connected to support users on Regional Nodes.

NOTE:  Administrators must create users (database accounts or others) for all users who will be accessing the Regional Node because srvrinit will no longer create user accounts.

Bookshelf Home | Contents | Index | Search | PDF