Enables or disables autocorrection for marked tables.
ra_set_autocorrection all, enable
To disable autocorrection for all marked tables, follow the ra_set_autocorrection command with the all and disable keywords:
ra_set_autocorrection all, disable
ra_set_autocorrection tablename, enable
To disable autocorrection for one marked table, follow the ra_set_autocorrection command with the tablename parameter and the disable keyword:
ra_set_autocorrection tablename, disable
To display autocorrection status for one marked table, follow the ra_set_autocorrection command with the tablename parameter alone:
ra_set_autocorrection tablename
ra_set_autocorrection mytable, enable
This command enables autocorrection for the marked table named mytable.
ra_set_autocorrection all, enable
This command enables autocorrection for all marked tables.
ra_set_autocorrection mytable, disable
This command disables autocorrection for the marked table named mytable.
ra_set_autocorrection all, disable
This command disables autocorrection for all marked tables.
ra_set_autocorrection mytable
This command displays autocorrection status for the marked table named mytable.
This command is used to support Replication Server autocorrection functionality.
You cannot set autocorrection for tables that have not been marked for replication. If a marked table for which autocorrection is enabled is subsequently unmarked, autocorrection is automatically disabled for the table.
The column_compression and ltl_send_only_primary_keys configuration parameters are disregarded when Replication Agent is replicating a marked table for which autocorrection has been enabled.
When autocorrection is enabled, Replication Server converts each update or insert operation into a pair of operations: one delete operation followed by an insert.
If your primary database is Oracle and table-level supplemental logging has not already been enabled, enabling autocorrection will enable supplemental logging for all columns of the specified table.
If your Replication Agent instance is configured to send minimal column data—column_compression and ltl_send_only_primary_keys are set to true—some column data may be omitted for columns that are specified as searchable in a replication definition. Consequently, errors may occur at a subscribing database where data needed for an insert, subscription migration, or custom function string is missing. Sybase therefore recommends that you enable autocorrection for any table referenced in a replication definition with searchable columns.