CDR_DBSPACE Configuration Parameter

Specifies the dbspace where the syscdr database is created.

onconfig.std value: none
units: any valid dbspace
takes effect: When the database server is shut down and restarted or immediately after the cdr change onconfig command is used

The CDR_DBSPACE configuration parameter specifies the dbspace where the syscdr database is created.

If the CDR_DBSPACE configuration parameter is not set, then syscdr is created in the root dbspace.

You can have Enterprise Replication automatically configure disk space from the storage pool and set the CDR_DBSPACE configuration parameter when defining a replication server. If the CDR_DBSPACE configuration parameter is not set and the database server has a storage pool with sufficient space, the cdr define command performs the following tasks:

Creates a new dbspace using one or more new chunks from the storage pool
Sets the CDR_DBSPACE configuration parameter both in memory and in the onconfig file to the newly defined dbspace.

For clusters, the cdr define command creates new dbspaces and sets the CDR_DBSPACE configuration parameters in all secondary database servers, as well.

Note: A database server's storage pool must have 200 MB of free space for the dbspace, and chunk sizes of 100 MB or greater for the database server to use automatic storage provisioning.

From 2.0.0.0 onwards, row data for smaller transactions of size less than 26KB are stored in-line along with transaction header table trg_send_stxn. Row data for transaction size above 26KB is still stored in ER queue smart blob space configured using CDR_QDATA_SBSPACE configuration parameter. Make sure to have enough space allocated for storage space used to store trg_send_stxn table. trg_send_stxn table is created in space configured using CDR_DBSPACE configuration parameter. If CDR_DBSPACE is not configured, then rootdbs will be used for syscdr database and transaction header table.