ADD TRANDATA options employ database features to control how the database propagates LOB data for the specified table. The SQL Server transaction log does not provide enough information by default.ĪDD TRANDATA marks a Sybase table for replication by executing the Sybase sp_setreptable and sp_setrepcol system procedures. Use ADD TRANDATA to provide the extended logging information that Oracle GoldenGate needs to reconstruct SQL operations. When creating a supplemental log group with ADD TRANDATA, Oracle GoldenGate appends the object ID to a prefix of GGS_, for example GGS_18342. If any of the logging details change after Oracle GoldenGate starts extracting data, you must stop and then start the Extract process that is reading from the affected table before any data is changed. Take the following into account when using ADD TRANDATA for an Oracle database:
See Installing and Configuring Oracle GoldenGate for Oracle Database for more information about configuring logging to support Oracle GoldenGate.
61a295 transdata update#
This adds row chaining information, if any exists, to the redo log for update operations. Oracle strongly encourages putting the source database into forced logging mode and enabling minimal supplemental logging at the database level when using Oracle GoldenGate. There must be no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.įor more information, see "ADD SCHEMATRANDATA". It is possible to use ADD TRANDATA for Oracle when DDL support is enabled, but only if you can stop DML on all tables before DDL is performed on them or, if that is not possible, you can guarantee that no users or applications will issue DDL that adds new tables whose names satisfy an object specification in a TABLE or MAP statement. When using ADD SCHEMATRANDATA, you can use ADD TRANDATA with the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters. To use the Oracle GoldenGate DDL replication feature, you must use the ADD SCHEMATRANDATA command to log the required supplemental data. See "Summary of Wildcard Exclusion Parameters" for more information. You can exclude objects from the schema specification by using the exclusion parameters. The ADD SCHEMATRANDATA command ensures replication continuity should DML occur on an object for which DDL has just been performed. If possible, use the ADD SCHEMATRANDATA command rather than the ADD TRANDATA command. See Installing and Configuring Oracle GoldenGate for Oracle Database for more information about how Oracle GoldenGate handles supplemental logging for Oracle databases. You can exclude the LONGVAR clause by using ADD TRANDATA with the EXCLUDELONG option.īy default, ADD TRANDATA for Oracle enables the unconditional logging of the primary key and the conditional supplemental logging of all unique key(s) and foreign key(s) of the specified table. By default, ADD TRANDATA issues the following command to the database:ĪLTER TABLE name DATA CAPTURE CHANGES INCLUDE LONGVAR COLUMNS Use ADD TRANDATA to enable DATA CAPTURE CHANGES on specified tables. The ADD TRANDATA command calls STRJRNPF and is the recommended method to start journaling for tables, because it ensures that the required journal image attribute of Record Images (IMAGES): *BOTH is set on the STRJRNPF command. Use ADD TRANDATA to start the journaling of data.
See the Oracle GoldenGate installation guide for your database for any special requirements that apply to making transaction information available. For other supported databases, this functionality may exist already or must be configured through the database interface.
Use ADD TRANDATA to enable Oracle GoldenGate to acquire the transaction information that it needs from the transaction records.īefore using this command, use the DBLOGIN command to establish a database connection.ĪDD TRANDATA is valid only for the databases that are listed here.
0 kommentar(er)
