Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide > Implementing Siebel Replication Manager >
Extracting the Regional Database
Each Regional Database must be extracted on a Siebel Server of its parent node. The Regional Database synchronizes against the Siebel Server on which it is extracted. Database parallel extracts use multithreaded components to make these tasks faster than single-thread operations. Parallel dbxtract requires additional hardware, but can reduce the time to do this significantly.
This section describes the two types of dbxtract: single-thread and parallel. Before beginning either type of database extraction, you must synchronize the server components that are enabled. See Siebel Server Administration Guide for details.
To extract database for Regional server with single thread - GUI
- From the application-level menu, select View > Site Map > Server Administration > Enterprise Operations.
- Select the Component Requests tab.
- In the Component Request form, click New.
- In the Component/Job field, click the select button.
- In the Component/Jobs dialog box, select the Database Extract component and click OK.
Complete the rest of the fields as appropriate.
- In the Component Request Parameters list, click New and then in the Name field click the select button.
- In the Job Parameters Selection dialog box, select the following parameters for the Name field and enter the corresponding value:
Client Name and enter the name of the regional node in the Value field.
Database Init Method and enter DDL in the Value field.
- Add any other component parameters for the component request as appropriate.
For a list of parameters you can specify, see Table 23.
- In the Component Requests form, click the menu button and then Submit request.
The Status field changes from Creating to Queued.
To extract database for Regional server with single thread - Srvrmgr command line
- From the Srvrmgr command line, enter:
start task for comp dbxtract with client=<regional node name>, initmethod=ddl
The parallel dbxtract utility (pdbxtract) is designed to improve performance when extracting large databases for one or more Regional Nodes. It is also possible to use pdbxtract when extracting Mobile Web Client databases, but pdbxtract may not improve performance significantly during Mobile Web Client extractions, so the practice is not recommended. You can run pdbxtract as a component request, from within a Siebel application, or you can run it as a task from a srvrmgr command line. The following two procedures describe these two methods of using pdbxtract.
NOTE: If you plan to use pdbxtract for concurrent extraction of two or more Regional Node databases, be sure to specify all of the applicable Regional Nodes as clients in a single pdbxtract component request or srvrmgr command. Due to the design of the pdbxtract utility, this produces better performance than starting multiple pdbxtract component requests or tasks that attempt to run concurrently.
To parallel extract database for Regional server - GUI
- From the application-level menu, select View > Site Map > Server Administration > Enterprise Operations.
NOTE: Check the value of the parameter Maximum Number of WorkQ Threads from the Server Administration > Components view. The Current Value field is the maximum number of worker threads per work queue. This parameter determines the parallelism of the process.
- Select the Component Requests tab.
- In the Component Requests form, click New.
- In the Component/Job field, click the select button.
- In the Component/Jobs Selection dialog box, select the Parallel Database Extract component and click OK.
Complete the rest of the fields as appropriate.
- In the Component Request Parameters list, click New and then in the Name field click the select button.
- In the Job Parameters Selection dialog box, select the following parameters for the Name field and enter the corresponding value:
- Select Client Name for the Name field and enter the name of the regional node in the Value field. To specify more than one regional node, create a text file and place the name of each regional node on its own line of the file. Enter the path and file name in the Value field, preceded by the @ symbol. For example, a Windows client might specify @D:\workdir\regnodes.txt.
- Select Database Init Method for the Name field and enter DDL in the Value field.
- Add any other component parameters for the component request as appropriate.
For a list of parameters you can specify, see Table 23.
- In the Component Requests form, click the menu button and then Submit request.
The Status field changes from Creating to Queued.
To parallel extract database for Regional server - Srvrmgr command line
- From the Srvrmgr command line, enter:
start task for comp pdbxtract with client=<regional node name>, initmethod=ddl
To specify more than one regional node, separate the regional node names with commas. For example, if RN1, RN2, and RN3 are the names of three regional nodes, the client portion of the command would be entered as follows:
client=RN1,RN2,RN3
For information on running a Database Extract, see Creating Mobile Web Client User Accounts and Privileges.
Table 23 lists component parameters you can specify for the Database Extract task.
Table 23. Parameters for Database Extract Parameter Name Required/Optional Description CD Directory CDDir Optional The directory on the machine of the parent node to which you write the extract files. Client Name Client Required The name of the Regional Database as entered when you registered the Regional Node. See Registering a Regional Node. Database Init Method InitMethod Required Specify DDL. You must set the Database Init Method parameter to DDL. Otherwise, the database initialization will fail. Maximum data file size DatFileSize Optional Sets the maximum size of a data file in megabytes. Minimum size is 1. Maximum size is 1,000. Default is 500.For Parallel Dbextract recommend Minimum size 100 MB. Language Code Language Optional Extract messages for the specified language. The default is ENU, for U.S. English. Specify the mobile client version of Siebel ClientVersion Optional Specifies the client software version. Default is 2000 for v7.x.The following example shows a sample portion of the parent node's server directory tree after you run Database Extract tasks for Regional Nodes named SIEBEL_EUROPE and SIEBEL_PACIFIC:
SIEBEL
DOCKING
SIEBEL_EUROPE
INBOX
OUTBOX
SIEBEL_PACIFIC
INBOX
OUTBOXAfter you initialize a Regional Database, the Regional Node's directory structure will include similar folders for any additional Regional Nodes (given a hierarchy of Regional Nodes) and for any mobile users.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Remote and Replication Manager Administration Guide, Version 7.5, Rev. A Published: 18 April 2003 |