Setting Up the Grouper Paging File

Enterprise Replication uses a grouper paging mechanism for evaluating large transactions. A transaction is large if the portion to be replicated meets at least one of the following conditions:
  • It has greater than 5,000 log records.
  • It exceeds one fifth the size of the value of the CDR_QUEUEMEM ONCONFIG variable.
  • It exceeds one tenth the size of the value of the SHMVIRTSIZE configuration variable.
The location of the sbspace used for the paging file is determined by the first of the following ONCONFIG configuration parameters that is set:
  • SBSPACETEMP
  • SBSPACENAME
  • CDR_QDATA_SBSPACE

The best solution is to set up an unlogged sbspace, as specified by the SBSPACETEMP configuration parameter. All updates to the paging files are unlogged.

The size of the paging sbspace should be at least three times the size of the largest transaction to be processed. This sbspace is also used by the database server for other tasks; consider its overall usage when determining size requirements.
Important: If the paging sbspace fills, Enterprise Replication hangs until you allocate additional disk space to the sbspace. If additional space is unavailable, use the cdr stop command to stop replication.