Enabling Transaction Logging

Use the ADD TRANDATA command to mark each source table for replication. This command uses the Sybase sp_setreptable and sp_setrepcol system procedures. ADD TRANDATA is the recommended way to mark the tables, instead of using those procedures through the database interface, but the owner or the system administrator can use them if needed. For more information, see the Sybase documentation.

To mark tables for replication with ADD TRANDATA:

On the source system, run GGSCI from the Oracle GoldenGate directory.
Log into the database from GGSCI.
```
DBLOGIN SOURCEDB database USERID user PASSWORD xxx
```
Where:
- database is the name of the database.
- user is the database owner or the system administrator. You will be prompted for the password. This command has encryption options for the password. For more information, see Reference for Oracle GoldenGate for Windows and UNIX.
- xxx is the password for the associated user.
Issue the ADD TRANDATA command for each table to be marked.
```
ADD TRANDATA SCHEMA.TABLE LOBSNEVER | LOBSALWAYS | LOBSALWAYSNOINDEX | LOBSIFCHANGED
```
Where:
- LOBSNEVER | LOBSALWAYS | LOBSALWAYSNOINDEX | LOBSIFCHANGED control whether LOB data is never propagated, only propagated if changed (the default), or always propagated. The ADD TRANDATA command will overwrite the LOB replication setting that is currently set for the table.

Note:

Some ADD TRANDATA options enable the ALWAYS_REPLICATE option of sp_setrepcol. If a LOB column contains a NULL value, and then another column in the table gets updated (but not the LOB), that LOB will not be captured even though ALWAYS_REPLICATE is enabled.