Step 3: Configure ER disk usage

Configure one or more sbspaces for ER row data (Required)

ER stores spooled transaction row data in sbspaces. ER creates one smart large object per transaction.

The CDR_QDATA_SBSPACE configuration parameter specifies the sbspaces for ER to use. If CDR_QDATA_SBSPACE is configured for multiple sbspaces, ER uses all appropriate sbspaces in round-robin order.

Set the value of the configuration parameter CDR_QDATA_SBSPACE

Choose one or more sbspaces in the table. The table lists the existing sbspaces on the server that you are defining for ER.

Create a new sbspace

1. Enter this information for the sbspace:

   Name: For example sbs1

   Path: For example /home/server/sbs1.chunk

   Offset: The beginning location of the sbspace in kilobytes.

   Size: The size of the sbspace in the selected units: megabytes or gigabytes.

2. Click Create.

   The new sbspace is added to the table and automatically selected. The sbspace is created on the server when you click Finish at the end of the wizard.

Configure the dbspace for ER catalog information (Optional)

ER stores ER catalog information in the syscdr database in a single dbspace.

The CDR_DBSPACE configuration parameter specifies the dbspace for ER to use. If you do not specify a dbspace for these records, ER uses the root dbspace.

Set the value of the configuration parameter CDR_DBSPACE

Choose a dbspace in the table. The table lists the existing dbspaces on the server that you are defining for ER.

Create a dbspace

1. Enter this information for the dbspace:

   Name: For example dbs1

   Path: For example /home/server/dbs1.chunk

   Offset: The beginning location of the dbspace in kilobytes. Must be less than 4 TB.

   Size: Then size of the dbspace in the selected units: megabytes or gigabytes.

2. Click Create.

   The new dbspace is added to the table and automatically selected. The dbspace is created on the server when you click Finish at the end of the wizard.