Skip Headers
Oracle® Database Lite Administration and Deployment Guide
10g (10.0.0)
Part No. B12262-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

C Consolidator Requirements in INIT.ORA

This document describes the Consolidator requirements for Oracle and Oracle parameter settings in the file init.ora. Topics include:

C.1 Relationships Between Relevant Parameters

You should set the following parameters in the file init.ora as given below:

Table C-1 lists parameters that must be set in the file init.ora.

Table C-1 init.ora Parameter Settings

Parameter Name Definition
PROCESSES Default value: 59 to 200.
SESSIONS Default value:

Derived: 1.1 * PROCESSES + 5

TRANSACTIONS Default value:

Derived: (1.1 * SESSIONS)

DML_LOCKS Default Value:

Derived: (4 * TRANSACTIONS)


C.2 Values for Processes and DML Locks

Check values for processes and DML_LOCKS. Massive concurrent synchronization processes use the maximum amount of resources. For each one of the concurrent clients, Consolidator requires one database connection (one session, one transaction). Therefore, the parameter value of PROCESSES must be set to be no less than the maximum number of concurrent clients.

During the sync, the Consolidator will make changes to the publication map tables. One DML lock is needed for each client and changed publication:

DML_LOCKS = (Number of changed publications) * (Maximum number of concurrent clients)

During the first and second sync, all publication map tables are changed for each client. So, the required DML locks are:

DML_LOCKS = (Number of publications) * (Maximum number of concurrent clients)

If you have a large number of publications, the default DML_LOCKS may not be sufficient. You should set it explicitly in the file init.ora. For example, CRM has approximately 50 publications. For 30 concurrent first syncs, Consolidator needs 1500 DML locks. The default value for DML_LOCKS with PROCESSES set to 200 is 1000.