CONFIGSIZE specifies the size of the safewrite area, which is a portion of the initial chunk of the root dbspace in which the database server stores coserver-configuration information and other data that is required for maintaining data consistency across coservers.
If you are using a single-coserver configuration with no more that 128 dbspaces, set CONFIGSIZE to SMALL. If you are using more than one coserver or more than 128 dbspaces, use the following table to select a value for CONFIGSIZE. Use the largest value that matches any one of the configuration criteria listed in the table for your database server. For example, if your database server has 30 coservers and 3 logslices, use STANDARD as the value for CONFIGSIZE.
If you need to use more chunks, dbspaces, or dbslices than a CONFIGSIZE of LARGE allows, set the MAX_CHUNKS, MAX_DBSPACES, or MAX_DBSLICES parameter to the desired value. The following table displays the range of CONFIGSIZE values for various items.
| Configuration
Criteria |
Range of CONFIGSIZE Values | |||
|---|---|---|---|---|
| SMALL | STANDARD | LARGE | MAX* Values | |
| Chunks | 1 to 128 | 1 to 2048 | 1 to 8192 | MAX_CHUNKS
0 to 32,767 (See page MAX_CHUNKS.) |
| Dbspaces | 1 to 128 | 1 to 2048 | 1 to 8192 | MAX_DBSPACES
0 to 32,767 (See page MAX_DBSLICES.) |
| Coservers | 1 to 20 | 1 to 256 | 1 to 511 | |
| Cogroups | 1 to 20 | 1 to 256 | 1 to 511 | |
| Cogroup Members | 1 to 400 | 1 to 4096 | 1 to 8911 | |
| Dbslices | 0 to 28 | 1 to 256 | 1 to 512 | MAX_DBSLICES
0 to 2047 (See page MAX_DBSPACES.) |
| Logslices | 0 to 16 | 1 to 63 | 1 to 63 | |
When you allocate the initial chunk for the root dbspace of any coserver, you must ensure that enough space is available for the safewrite area. This space is in addition to any other space you might need for other information that you store in the root dbspace. The following table indicates the amount of space that is required for each value of CONFIGSIZE. Add this amount to the size of the initial chunk of the root dbspace in each coserver.
If you do not provide enough space for the safewrite area, the database writes a message to the transaction log to report this situation. To increase the size of the safewrite area, select the next-larger value for CONFIGSIZE and reinitialize the database server. If insufficient space is available in the root dbspace, you might have to add a chunk before you reinitialize the database server.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]