Database Configuration

The Extract process makes calls directly to the Sybase Replication API on a source Sybase server. The source database on this server must be configured as follows to support data capture by Oracle GoldenGate.

• Because Extract uses the Sybase LTM to read the Sybase transaction log, it cannot run against a database configured with Sybase Replication Server. Only one process at a time can reserve a context that allows it to read the transaction log on the same database.

• Sybase Multisite availability leverages the Sybase Replication Server to replicate transactions to a Warm Standby and a target subscription database. Oracle GoldenGate for Sybase cannot capture from the primary Warm Standby but can capture from the Multisite availability target subscription database because SAP Sybase Rep Server is not in control of the Transaction Log for that database.

• The DSQUERY variable is used by Oracle GoldenGate to connect to the database using the server name. Set the DSQUERY variable to the server name that contains the database that Oracle GoldenGate will be using. In addition, set the SYBASE environment variable accordingly.

• The Extract process must be permitted to manage the secondary log truncation point. For more information, see Initializing the Secondary Truncation Point.

• Configure the database page size to 4k, 8k,16k, 32k, or larger. To use the UPGRADECHECKPOINT table_name command to updated the checkpoint the target Sybase database, it must be configured to have a row size of more than 2K pages to be programmatically created; it will fail to upgrade the checkpoint if the target database is configured to be a 2K page size. This is valid only for Replicat.