Correction to the Description of Schema Cache

Schema Cache

When the structure of an object marked for replication is modified—by alter table, for example—Adaptive Server must log special records in the transaction log that later on will help RepAgent identify the correct schema for the object.

This section reports schema activity and RepAgent activity scanning forward and backward in the transaction log looking for object schema changes.

• Usage

  This section reports:

  • The maximum number of active schemas in the Schema Cache since the last restart of Replication Agent
  • The number of times that a schema had to be removed from the Schema Cache to free space for a new one

• Forward Schema Lookups

  This section reports:

  • The number of times RepAgent performed forward scans
  • The total amount of time, in ms, that RepAgent spent performing forward scans
  • The longest amount of time, in ms, that RepAgent spent performing a forward scan
  • The average amount of time, in ms, that RepAgent spent performing a forward scan

• Backward Schema Lookups

  RepAgent performs a backward scan when DDL is performed inside a transaction. This section reports:

  • The number of times RepAgent spent performing backward scans
  • The total amount of time, in ms, that RepAgent performed backward scans
  • The longest amount of time, in ms, that RepAgent spent performing a backward scan
  • The average amount of time, in ms, that RepAgent spent performing a backward scan